Content overview

Checking the license

Bibliotheken und Verzeichnisse für directword

Troubleshooting on IBM i

Determine version

IBM i version

GO LICPGM, selection 10, key F11

directword version

WRKLIB DIRWORD - the description contains the version number

DSPDTAARA DIRWORD/prdrel

WOPiXX

Configuration commands

Start/Stop commands

Subsystem and jobs

Logs/Protocols/Dumps

Log file DIRWORD/RPRT - Turn logging on and off

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

select SRCDTA from DIRWORD/RPRT

Contents of the DIRWORD/RPRT if it has been run correctly

Makro Name: DWMRGDOC                                                                                                                                                                                                                                          
Job Name: P13ARCAD1                                                                                                                                                                                                                                           
IP Adresse des Fernen Systems: 192.168.42.152                                                                                                                                                                                                                 
Systemname : DEAET01 L                                                                                                                                                                                                                                        
Initiator Port: -09806                                                                                                                                                                                                                                        
Editor Name: WORD                                                                                                                                                                                                                                             
Timeout der Operation: 0000                                                                                                                                                                                                                                   
Oeffnen der TCP Verbindung                                                                                                                                                                                                                                    
Portnummer: 50004                                                                                                                                                                                                                                             
Port for client communication is:55825                                                                                                                                                                                                                        
Zugriff zu PC erstellt                                                                                                                                                                                                                                        
Daten erfolgreich gesendet                                                                                                                                                                                                                                    
Oeffnen der Datei DWSTEU : DIRWORD/DWSTEU(SP13ARCAD1)                                                                                                                                                                                                         
DWSTEU erfolgreich gesendet                                                                                                                                                                                                                                   
Oeffnen der DWBKFW Datei : DIRWORD/DWBKFW(SP13ARCAD1)                                                                                                                                                                                                         
DWBKFW erfolgreich gesendet                                                                                                                                                                                                                                   
Receiving Response: 258 bytes                                                                                                                                                                                                                                 
Received  258 bytes                                                                                                                                                                                                                                           
Feedback Status: 1; Im Klartext:Makro erfolgreich ausgeführt<zeile mit X'20' aufgefüllt>
Kommunikation mit PC erfolgreich abgeschlossen                                                                                                                                                                                                                
Status:Makro erfolgreich ausgeführt<zeile mit X'20' aufgefüllt>

Troubleshooting on the Windows client

Determine version

Windows

Microsoft Office

directword version

Start → Programs → directword→ directword Administrator, About tab.

Configuration commands

Start/Stop commands

Logs/Protocols/Dumps

Turn logging on and off

Start→ Programs → directword → directword Administrator, Server Data tabs

Log files: %PROGRAMDATA%\Toolmaker\DirectWord\dirword.out

Also displayable via Start→ Programs → directword → directword Show log file

dirword.out - when running properly

26.01.2020 11:15:46 Local Port is: 3615
26.01.2020 11:15:46 Receiving timeout value for sync communication
26.01.2020 11:15:46 GetProcIDDirect for port: 3611
26.01.2020 11:15:46 Process not found by proc id direct. Try by Proc ID
26.01.2020 11:15:46 GetProcID Begin 
26.01.2020 11:15:46 strCommandLine
26.01.2020 11:15:46 GetProcID End true
26.01.2020 11:15:46 Session is : 2
26.01.2020 11:15:46 Opening event: Global\ToolmaEv2
26.01.2020 11:15:46 Status entry for synchron process:1
26.01.2020 11:15:46 RunCacls
26.01.2020 11:15:46 open cacls "C:\ProgramData\Toolmaker\DirectWord\DirwordStatus.bin" /E /G TMS\Cornel:f
26.01.2020 11:15:46 LaunchMakro
26.01.2020 11:15:46 Session is : 2
26.01.2020 11:15:46 open cacls "C:\Program Files (x86)\Toolmaker\Directword\Programm\Temp\PKO46CB.tmp" /E /G TMS\Cornel:f
26.01.2020 11:15:46 open cacls "C:\Program Files (x86)\Toolmaker\Directword\Programm\Temp\PKO46DC.tmp" /E /G TMS\Cornel:f
26.01.2020 11:15:46 Opening event: Global\ToolmaEv2
26.01.2020 11:15:50 Wait for feedback from macro/watchdog
26.01.2020 11:15:56 Send response to caller
26.01.2020 11:15:56 Wait for status of response
26.01.2020 11:15:56 Response is:716269695
26.01.2020 11:15:56 Synchron Process lasted for: 0 seconds

Log files: %USERPROFILE%\AppData\Roaming\Toolmaker\DirectMedia\directrun.out

Here we log what happens during the macro execution

directrun.out if run correctly

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

Basic test programs

There are a number of test programs available in the DIRWORD library that can be used to check the basic operation of directword.

These programs are all called BEISP*. Their sources can be found in the source file DIRWORD/QCLPSRC.

Ensure that the "Advanced Protocol" is enabled

Start the directword administrator(Start → Programs → directword → directword Administrator) and make sure that the Extended Protocol is active in the "Server Data" tab:

Shuffle Word document locally and then edit it: BEISP0200

ADDLIBLE DIRWORD
CLRPFM RPRT
CALL BEISP0200
1. The document should now appear on the PC and be merged, then remain open for editing
DSPPFM RPRT

Shuffle and print Word document on server: BEISP02110

Make sure that the name "DWBATCH" is connected to the server PC

ADDLIBLE DIRWORD
GO DIRWORD, selection 4
Make sure that
1. the queue "DWBATCH" is linked to the correct IP address/name of the server PC
2. the program DWServe.exe is running on the server PC and is configured to the specified port
3. on the server PC the service "DirWordService" is not active is

Port 50004 is configured on PC, as on IBM i:

DWServ.exe is running on the server PC:

The service "DirWordService" is not active:

Call the test program BEISP0210

ADDLIBLE DIRWORD
CLRPFM RPRT
CALL BEISP0210
DSPPFM RPRT

Hotline cases

DWMRGDOC (etc.) - call does not arrive at the PC or server (2000040)

There is no indication of any activity by the DWMRGDOC (or other DW commands) in the log of the PC or server.
In the file DIRWORD/RPRT (siehe: Protokoll-Datei DIRWORD/RPRT - Protokollierung ein- und ausschalten) you will find the line:

0000000000ERROR : getservbyname

Solution:

The service table entry for port 50004 was missing:

Check with WRKSRVTBLE and scroll until you find it:

If not present, add:

ADDSRVTBLE SERVICE(DWRDSRV) PORT(50004) PROTOCOL(TCP) TEXT('directword')

Error "DIRWORDLOGICLib.control" could not be created

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"

Error "Automation error - library not registered" (dirwordlogic.dll not yet registered) (210000010)

Error display:

Solution:

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.

To do this, open an administrative CMD box and enter the following command:

regsvr32.exe "C:\Program Files (x86)\Toolmaker\Directword\Program\dirwordlogic.dll".

After that you can use the test programs to check if the installation is correct Grundlegende Test-Programme.

Browser not supported