Troubleshooting

Troubleshooting Common Problems

There can be many things that interfere with TCP/IP communications!

1) Diagnosing application problems can be a tricky issue. The #1 support call received here at HermeTech about ANY of our products is because of a lack of knowledge of DEP (Data Execution Prevention) and how it is used in MS Windows operating systems beginning with MS Windows XP service pack 2 and MS Windows Server 2003. For more info on DEP click HERE. There IS code in the FSPM which WILL trigger DEP and cause Windows to close the application. If you receive fatal errors which close the application or cause the service to stop unexpectedly verify that DEP is not the culprit first!

2) Firewalls and 3rd party network monitoring software, including the Windows Firewall as well as Norton's and Symantec's virus scanning and network protection suites can cause problems especially if you are trying to access network resources.

3) Windows Vista. The program is incompatible with the UAC features which is enabled by default in Windows Vista. If you have issues, try disabling UAC.

4) The service will not run. If the FSPM will run fine when being run locally but fails to start as a windows service (professional license required) verify the following:

•	Are you using 'Network Share' folders for any of the FSPM folders (central distribution, destinations, message collection, rubbish bins etc.)? If so, make sure that you are following the guidelines discussed in Using Network Folders.

•	Are ALL folders valid? Run a test to determine if there's a problem.

•	Review the system log files.