Troubleshooting Form Letters

These topics discuss:

  • Troubleshooting the SQR process.

  • Troubleshooting the WORDINIT process.

  • Troubleshooting the PSMERGE Application Engine process.

  • Troubleshooting the Process Scheduler.

  • Troubleshooting the Winword Directory.

  • Troubleshooting Winword processes.

  • Troubleshooting the PSMERGE process.

Troubleshooting the SQR Process

For the SQR data extract process check that:

  • The process is run with the output Type set to File and Format set to LP. If you have run the SQR with any other output type or format, make sure that you delete these data extract files.

  • The data extract file has been produced in the format xxx.ltr in the Process Scheduler log/output directory.

  • Use the Process Monitor to delete all failed Process Requests.

Troubleshooting the WORDINIT Process

If the WORDINIT process fails and the environment is correctly configured, the most likely cause is macro security. Switching off the macro security works for some Microsoft NT networks. You may also need to consult your Systems Administrator.

In some networks, Microsoft Word automatically switches the security level back to "high" when running the process. For example, if Winword macro security is defined at the NT User Profile level then you need to set macro security to "low" for the NT ID that starts the PeopleSoft Process Scheduler service.

Note:

Windows locks and caches the macro virus protection settings for Winword and this may cause difficulties when turning off the macro virus protection.

Try hard-coding the path to PS_HOME in the Process Definition for WORDINIT:

  1. Navigate to PeopleTools, and then Process Scheduler, and then Processes.

  2. Select Process Name in the Search By field and enter WORDINIT.

  3. Select the Override Options page.

  4. In the Parameters field replace %%PS_HOME%% with the hard-coded path to the directory.

Troubleshooting the PSMERGE Application Engine Process

If the PSMERGE Application Engine process does not complete and you have added extra fields to the SQR data extract process, check that the fields have also been included in the document template and that the fields occur in the same order.

Troubleshooting the Process Scheduler

Check that the Process Scheduler is configured correctly:

  • You must define a separate Process Scheduler server at Process Scheduler Definition level with the Transfer Log Files to Report Repository check box deselected.

  • Confirm that the WINWORD parameter is correctly specified in the prcs.cfg file.

Check that all failed attempts at running the form letters have been deleted using the Process Monitor. Delete any Process Requests that have failed.

Use the Windows Task Manager to check that there are no Winword processes still running. Delete these before rerunning the form letter report.

Once Microsoft Word is interacting with the desktop it may try to reinstall itself. To avoid this, disable the Windows Installer.

Troubleshooting the Winword Directory

Check that the template files are in the correct directory with the correct access:

  • The Winword templates and the macros must be located in the %PS_HOME%\winword directory.

  • The files psmerge.doc and psmerge.dot and the document templates in the %PSHOME%\winword directory must be read-only.

See PeopleTools PeopleSoft Process Scheduler

Troubleshooting Winword Processes

To display errors and debug the Winword Processes, modify your Process Scheduler configuration file, psprcs.cfg, by adding the following line to the Process Scheduler section of the file (after the line for the Allow Dynamic Changes parameter): 

Allow To Interact With Desktop=1

Save the changes, clear the cache and re-start the application server.

See PeopleTools PeopleSoft Process Scheduler, "Using the PSADMIN Utility".

Troubleshooting the PSMERGE Process

If the PSMERGE Application Engine process is failing or the status remains as Processing, take the trace file, AE_PSMERGE_<PI>.trc (where <PI> is the process instance number), and extract the arguments from the file, combine them and run them from a command line. This tests the process outside the Process Scheduler.

For example if AE_PSMERGE_<Pl>.trc is set up as follows: 

cmd = D:\PSHR88\WINWORD\run.bat
	cwd = (null)
	argc = 5
	argv[0] = D:\PSHR88\WINWORD\run.bat
	argv[1] = C:\PROGRA~1\MICROS~4\OFFICE\WINWORD.EXE
	argv[2] = D:\PSHR88\appserv\prcs\HCUPG3WD\log_output\AE_PSMERGE_387\387_PARAM.TXT
	argv[3] = D:\PSHR88\WINWORD\PSMERGE.DOC
	argv[4] = /mPSMERGE

You run them from the DOS command line as follows: 

D:\PSHR88\WINWORD\run.bat  C:\PROGRA~1\MICROS~4\OFFICE\WINWORD.EXE
D:\PSHR88\appserv\prcs\HCUPG3WD\log_output\AE_PSMERGE_387\387_PARAM.TXT
D:\PSHR88\WINWORD\PSMERGE.DOC  /mPSMERGE

See PeopleTools PeopleSoft Application Engine, "Tracing Application Engine Programs"