Problem stopping services

[pjb]

Since moveing to new servers, we are experiencing problems when trying to manually stop the Livelink services. The service attempts to stop and then appears to stall out after a few minutes. Then this error appears
"Could not stop the Livelink Server Livelink service on local computer. Error 1067. The process terminated unexpectedly"

Some times the status gets stuck at "stopping", and I have to re-boot the server.

 

[Syntergy]

The best approach to solving the problem is to turn on logging and review the thread.out files to see what the last transaction for each thread is. These are in the log directory in the thread.out files. When Livelink shuts down gracefully it puts an entry in the thread.out files. You may find that all but one thread shutdown and that the last transaction in the other thread is the reason the shutdown is not completing on time.

We have seen the index process "hang" when trying to index certain documents which in turn seems to cause the Livelink service to hang. You might try stopping the Admin service first and wait for that to terminate before stopping the Livelink service.

 

[DrDDT]

We see this behaviour when Livelink is busy when stopping the service.

We logged a call with OT, but didn't get a solution.

 

[appnair]

Instead of re-booting the servers you can use taskkill or using taskmanager kill the llserver.exe process or howver many proceeeses the livlink server is using.The new livelink indexing is different so it has a lot of dependence on hardware so a good thing that I do is whenever I bring up the admin and when it is "hydrating" (a term to load all metadata into memory) turn that check box off.when resources are manageable turn that on

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937