On the Windows operating system rogue DLL's placed in any of the windows system folders can cause the webagent to fail on startup.
When using IIS this often results in "Unable to load HTTPPLUGIN.DLL" been logged, on apache the server hangs with no message. On all web servers this results in a fatal error that prevents loading of the webagent.
If a webagent on a windows system fails to start and no information is logged this is most likely your problem. However this only applies to windows based systems.
Why this happens:
This happens because the Windows operating system uses a hard-coded search routine to locate all DLL files. The search order uses is as follows...
As the path environment variable exists last in the search routine if a DLL exists in any of the windows system folders (Numbered 1 - 5) it will be loaded in place of the DLL located in your \netegrity\webagent\bin\ folder. If the DLL's are of different versions the webagent cannot correctly execute the required function and fails.
The following solution will remove problem DLL's from the system folders. Keep in mind that, if these DLL's utilized by another program that application may fail.
This problem is most often caused by Comerr32.dll and k5sprt32.dll existing in the windows\system32 folder:
On the server running the webagent: