Servlet Engine

System

Trying to login to TS5.5.1 on a Windows 2000 server (which used to work fine).

When entering <servername>/iw in a browser window, the following error message is returned:

The TeamSite Web Daemon was unable to contact the TeamSite Servlet Engine. The TeamSite Servlet Engine may be down, or running on an unexpected host or port.

Please contact your system administrator.

However, the standard causes of this error message do not apply to my system. The servlet engine is running when I do the launch, I have not changed the hostname, and the machine is still on the network.

After getting the error message, the servlet engine stops unexpectedtly, most of the time.

Any clues?

Migrateduser

Rob and I were both working on this when the solution came. He wrote it up under the integrations section. I'm including it here for completeness.

I doubt that too many other folks are having to deal with running PHP on the same machine as TeamSite, but if you are, here is something to keep in mind.

The PHP installation instructions suggest copying the required DLLs to C:\winnt\system32. Among these libraries is one called libeay32.dll. iwservletd is dependent on a library by the same name. Depending on what order it searches your library paths at startup, iwservletd may find the one in C:\winnt. If these happens, iwservletd will die the first time a user tries to authenticate.

This can be avoided by installing those libs not to C:\winnt, but to the same directory as the server api lib for PHP, php4isapi.dll in the sapi directory of the php installation directory by default.


David M. Doggette
Independent Consultant