Livelink service terminating unexpectedly 2

[mtmorris000]

Has anyone had problems with Livelink 9.5 crashing unexpectedly on Windows Server 2003? The Livelink service has been leaving this error in the Windows event log: “The Livelink Server service has terminated unexpectedly. It has done this 4 times.” The event source is the Service Control Manager. When this happens, Livelink shuts down and is inaccessible. A quick restart and it is on its way again, but it is starting to become a problem due to its frequency – every couple of days. We do not restart the service nightly. Any ideas on this issue would be greatly appreciated.

Thanks, Mike

 

[mtmorris000]

Addendum to first message in thread:

We have also seen this error before: "Microsoft Visual C++ Runtime Library Runtime Error! Program D:\opentext\bin\llserver.exe. This application has requeed the Runtime to terminate it in an unusual way."

Not sure if the errors are related. Either way, looking for anyone that has experienced similar Livelink instability.

 

[appnair]

The service control manager log starts when *you* start the service to a non-responding livelink.Say you get a call and you see all the livelink.exe's queued up and in your hurry you re-start the service.Next time it will show 5 and so on.I don't know how long it remembers this.When livelink dies on your server it does not show in the event log.
The way would be to run logs with debug=2 to see if there is a pattern(huge deletes,moves etc happening ) and isolating the problem.
Another way is to set the livelink service to automatically start on failing although I have never seen this working.

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

 

[menu]

It happens to me once while I was uninstalling some module manually by removing it from module folder. And as far as I remember I modified Opentext.ini file by removing this module from there as well.

 

[aspdrugdealer]

Mike-
This just happened to me. It was driving me crazy! I had to babysit the server all day long. Here is what I did to solve the problem.

There is a known issue with the JRE that ships with LL 9.5, if your running 9.5 SP1 then this is ok. I was only using 9.5 so I had to upgrade the JRE (java runtime). However, if you are thinking of going to 9.5 SP1, think again. They have some problems with document filters in this version, so I am waiting to upgrade. After a JRE upgrade, your gonna have to rebuild your index.

The second thing was the virus scanner on the server. I forgot to exclude my livelink data stores and indexes. This will cause a problem also.

Finially and what ended up being my solution was to turn off hyperthreading on the server. If your using intel processors, make sure this is turned off. This is a known problem with livelink....just not documented very well.

Let me know if this helps. That was a really hard one to figure out.

Doug

 

[appnair]

Curious is this my problem"However, if you are thinking of going to 9.5 SP1, think again. They have some problems with document filters in this version, so I am waiting to " after 5 days of upgrade I have crossed 1 % of my index on my ll95SP1.I have opened a support ticket and I will let you know what they find.There are absolutely no-errors in any of the processes.

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

 

[aspdrugdealer]

appnair -
I almost posted to your thread, on the subject, but my source is nothing more then casual conversation with a tech. Here is what I was told....

Opentext tried to write document filters themselfs for SP1 instead of using the 3rd party vendor they had been using. I guess they got tired paying $$ for the filters. Let me know what you find out. I am interested myself.

Thanks,
Doug

 

[appnair]

Well at least on 95SP1 the filters is a new install CD accompaniment.We almost have verything excuded for doctype conversion stuff such as tiff etc.We add a bunch of things to the opentext.ini file.I never change the default 1 minutes that the extractor comes as default.Has anybody succesfully changed it to lesser and seen any improvement.
My EFS is huge close to 700 GB and I have never seen such slow indexing.

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

 

[mtmorris000]

Wow, aspdrugdealer, you hit the nail on the head. We actually did some of those things shortly after my original post - and indeed, the crashing has stopped. We turned off the hyperthreading and excluded the appropriate LL directories from constant virus scanning. We have plans for upgrading the JRE and upgrading to 9.5 SP1. I'm not sure I'm following the issue on the document filtering with SP1. Bottom line, should we upgrade now or wait until the next patch for SP1? Thanks for everybody's help.

 

[davidt50]

You will want to get the latest monthly patch for 9.5sp1. Some may be aware that in 9.5, the search engine was replaced and there are some issues that have been addressed in the monthly patch. There are also some fixes that address the slow indexing issue reported by people, it seems the Enterprise Extractor had some "not nice" SQL associated with it.

 

[davidt50]

As for setting the extractor time < 1 minute, you could but I wouldn't set it below 30 seconds. Once the monthly patch is installed, I would look at the performance behaviour again.

 

[appnair]

YEP did put the new patch on Saturday.Really some bad bugs in indexing.When august patch is relaesed re-index official OT version.So the story ain't complete yet.

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

 

[davidt50]

Really some bad bugs in indexing"

Hmm, not really an excuse but the previous search engine (8.0 to 9.2sp1) had years to mature. The new search engine seems to have some teething issues.

Did you find the July patch helping with the extractor issues?

 

[bhartnett]

I'm having the service shut down when using Explorer pro to move a whack of documents into the repository. It's been messing with me because sometimes it will move 1 gig of documents before failing, sometimes only 50 megs..

Thanks for the tip on hyperthreading. I'll try that, as I've already excluded the index and docstore from the virus scan.

 

[lalluser]

bhartnett,

Did the disabling of hyperthreading resolve your problem?

lalluser

 

[bhartnett]

Sorry it took so long to get back to you. I've been planning upgrades and trying to get budgets..

It wasn't hyperthreading, it was the Directory Services module. When I turned off NTLM authentication the errors ceased.

We purchased LiveLink though an OEM partner of OpenText's, so I haven't cruised the KB for backup info, but the tech reps said there was a problem running Win 2k3 and LL9.5 with that module. It has supposedly been addressed in SP1, and I will be loading a machine with that in the near future for testing. For now, I'm running 9.5 with LL authentication. No problems in the few months we've run it that way.

I wish there was a way OpenText would let people who buy though thier partners to access the KB.

 

[ggriffit]

Many of the Partners I know provide access to the KC for their customers, suggest you speak to your partner.