Unable to connect to Interwoven Servlet Engine

I am not able to log in to Interwoven Teamsite

It displays the below message

" The Interwoven Web Daemon was unable to contact the Interwoven Servlet Engine. The Interwoven Servlet Engine may be down, or running on an unexpected host or port. Please contact your system administrator"

We have issued all the commands.

1.iwreset -a
2.iwreset -ui
3.iw.server stop
4.iw.server start

when checked the status of the server -- ./iwstat - c it displays default -- Running Workflow -- Running

Find more posts tagged with

Comments

Bubas_IWOV

Hi,

Have you checked your IWHOME/install/tsisvalid.log file for error messages?

Regards
Bruno

Migrateduser

Is this a new install or an upgrade? Do you know what has changed since the last time you tried? How soon after rebooting did you try to log in? Sometimes it takes a few minutes for all the servers to get settled.

lissa

NathanW

Hiya

When we first upgraded our development TS environment to 5.5.2 we had all sorts of similar problems getting TeamSite to allow users to login - OpenDeploy also...... Whilst all the services were started and the TS environment was "active" it wasnt making all the necessary connectionsin the background. We now have a script that runs whenever the server is started the brings up the services in the precise order needed - the services themselves are set to manual (Windows).....

I dont have a copy of the script on me but if you want it send me a message.

The really weird thing - it didnt happen when we upgraded production.. - go figure.

Nathan Wall
Department of Transport and Regional Services (Australia)

Bowker

We experienced the same issue on 5.0.2 and about twice per week on 5.5.2. We found that if we delay the starting of the services by a couple of minutes the underlying subsystem TS wants available (security, Network...?) becomes ready.

I don't have a copy of the script we use, I'm not in the 'hardware' group. If you really need it let me know and I'll beg them for it.

tiroth

On Teamsite Windows (5.5.2) we sometimes have to bounce the servlet engine once the rest of the system finishes coming up. This gets rid of the error.