Content overview
Table of Contents |
---|
...
Checking the license
...
Bibliotheken und Verzeichnisse für directword
...
Troubleshooting on IBM i
Determine version
...
Anchor | ||||
---|---|---|---|---|
|
For test/debug purposes, the communication taking place between IBM i and PC can be logged to a DIRWORD/RPRT file. At this point, logging is enabled or disabled.
Valid values are:
" "
Logging is disabled"LL"
Logging is switched on
CHGDTAARA DTAARA(DIRWORD/DWDDTAARA (222 2)) VALUE('LL')
After turning logging off, you should make sure that the log file is cleared again by entering the following IBM i command:
CLRPFM DIRWORD/RPRT
IBM i - log file DIRWORD/RPRT
...
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
2020.01.26 11:08:12 DirectRun started 2020.01.26 11:08:12 Version is: 3.30.38.39 2020.01.26 11:08:12 Event Global\DirectRunRuns2 created 2020.01.26 11:08:12 Cleaning DirectMedia Temp Directory 2020.01.26 11:08:12 Waiting for events. 2020.01.26 11:15:46 Event number: 0 2020.01.26 11:15:46 Session 2, Event occured 2020.01.26 11:15:46 ProcessType: 4 2020.01.26 11:15:46 Waiting for events. 2020.01.26 11:15:46 Event number: 0 2020.01.26 11:15:46 Session 2, Event occured 2020.01.26 11:15:46 ProcessType: 1 2020.01.26 11:15:46 PKOSTEU File: C:\Program Files (x86)\Toolmaker\Directword\Programm\Temp\PKO46CB.tmp 2020.01.26 11:15:46 PKOBKFW File: C:\Program Files (x86)\Toolmaker\Directword\Programm\Temp\PKO46DC.tmp 2020.01.26 11:15:46 Launching Word Editor 2020.01.26 11:15:49 AddIns.Count: 1 2020.01.26 11:15:49 DIRECTWORD.DOT 2020.01.26 11:15:56 Waiting for events. 2020.01.26 11:24:06 Event number: 0 2020.01.26 11:24:06 Session 2, Event occured 2020.01.26 11:24:06 ProcessType: 4 2020.01.26 11:24:06 Waiting for events. 2020.01.26 11:24:06 Event number: 0 2020.01.26 11:24:06 Session 2, Event occured 2020.01.26 11:24:06 ProcessType: 1 2020.01.26 11:24:06 PKOSTEU File: C:\Program Files (x86)\Toolmaker\Directword\Programm\Temp\PKOE57A.tmp 2020.01.26 11:24:06 PKOBKFW File: C:\Program Files (x86)\Toolmaker\Directword\Programm\Temp\PKOE58B.tmp 2020.01.26 11:24:06 Launching Word Editor 2020.01.26 11:24:06 AddIns.Count: 1 <==== hier startet das Makro. Wenn es Probleme geben sollte, dann kommt hiernach eine Fehlermeldung 2020.01.26 11:24:06 DIRECTWORD.DOT 2020.01.26 11:24:12 Waiting for events. |
If you get an error message when executing a directword command, you should briefly read through the following list. Find the chapter heading that best fits your error message or problem and read the tips and references to fix the error.
General errors
If a directword command (e.g. DWMRGDOC) was started, nothing happens at all (no error message, neither in the session nor on the client).
Check if the directword TCP server is started and the port number matches the one stored on the IBM i.
If a directword command (e.g. DWMRGDOC) was started, a document is opened, but no data is merged.
Check if the AddIn directword.dot was loaded in Word.
Make sure that the installation is licensed on the IBM i server.
Check whether the data transfer via the TCP server was error-free. Check the file under C:\Documents and Settings\AllUsers\Application Data\Toolmaker\directword\directword.out.
0459 - directword.out
For VISTA or WINDOWS7: ProgramData\Toolmaker\directword\directword.out
Make sure that the correct data file was passed when calling the DW function. For this purpose you can also view the file PKO...tmp (for exact name and path see entries in the directword.out file) for comparison with a text editor.
WINDOWS7
The firewall must be configured by the administrator DWServ.exe
Visual Basic errors
Visual Basic errors can be recognized by the dialog type and the associated error message. These errors are always caused by the functions executed in Microsoft Word (started from directword ).
Always abort the function with Exit and check the respective settings as described below. Always quit and start Word before the next attempt.
Runtime error 537: The specified macro cannot be executed.
Check the list of all automatically started style sheets in Word via the menu function Tools - Templates and Add-Ins. The directword.dot file must be entered in the list.
Runtime error 53: File POVBAEXT.DLL cannot be found.
This error normally only occurs in the server variant. In this case, the directword Visual Basic extension cannot be found. Check the following settings:
Start the system settings via the button Start- Settings - Control Panel - System
Activate the tab page Advanced - Environment variables and click in the selection list System variables on the variable Path.
Complete the value of the variable by extending the existing text with a semicolon and the installation path of directword. It is mandatory to boot the PC after changing the value. For example, if the remote Windows NT server (PC) is to be accessed through TRN18, the value at the end should be as follows:
C:\......;\TRN18\directword\program
...
Anchor | ||||
---|---|---|---|---|
|
...
Check if the Microsoft Visual C++ 2010 Redistributable Package (x86)(vcredist_x86.exe) is installed (see Installationsvoraussetzungen auf dem Windows Client)
If not:
- Reinstall the package
- Re-register the dirwordlogic.dll, see Fehler "Automatisierungsfehler - Bibliothek nicht registriert"
...
Check if the Microsoft Visual C++ 2010 Redistributable Package (x86)(vcredist_x86.exe) is installed (see Installationsvoraussetzungen auf dem Windows Client).
If they are installed, then the DLL "dirwordlogic.dll" must be re-registered.
...