Configuring Arbortext Publishing Engine > Troubleshooting Arbortext Publishing Engine Operations > Troubleshooting Errors
  
Troubleshooting Errors
Review the information for how to use the tracing and logging parameters in the e3config.xml file, as well as other tracing and logging tips. If you're troubleshooting Arbortext PE sub-process startup problems, you can check the transaction archive.
When you're troubleshooting the Arbortext Publishing Engine, you may decide to run Arbortext Publishing Engine Interactive. If you created a specific user account for Arbortext Publishing Engine, be sure to log on the system with that user account name to better simulate its environment.
You can also run Arbortext Publishing Engine Configuration program from your PTC program group. It reports information about your setup, including COM registration. You can also check your Tomcat integration.
Be sure to check all log and temporary directory folders used by the servlet container and the Arbortext PE server. Some of these may be explicitly set in the e3config.xml file. Check that the paths specified there exist on the system.
The Tomcat log files in TOMCAT_HOME\logs contains log messages written by the Arbortext PE Request Manager. The pelog.xml file contains log4j messages that can be used for troubleshooting.
* 
• If the Tomcat Windows service won’t start, it’s possible that it can’t find msvcr71.dll. Try updating the Windows PATH environment variable to add the JRE bin directory. For example:
C:\Program files\Java\jre1.1.8_45\bin;
Tomcat has an AJP connector defined in server.xml which monitors port 8009. However, if port 8009 is already in use, Tomcat doesn't address the conflict. Arbortext Publishing Engine Configuration configures isapi_redirect.properties to use port 8009 to integrate with Tomcat.