Opentext content server 10.5 build 1855 issue

[newbie2018]

Dear Forum,

I am hoping that you can assist with an issue reading files.

I have an opentext installation with 500 licensed users and 548 active users.

Starting on thursday last week, I can't open content that I saved from the either the web farm that I am running or from the Index/Search/Admin server directly. I can tell by looking at the file server that the data that I write to OTCS is being stored.

The MS SQL server appears to be running as normal although there was a schema change last monday to the database.

Here's the weird bit, I have one web server that isn't in the load balancer and is in the same subnet as the other web servers, only on this one server, we can read the files back that we've written. I've tried taking another web server out of the load balancer, rebooted etc, can't read content back from it.

Any known issues around Microsoft patches effecting content server?

Thanks for your advice.

Best wishes, Scotty.

 

[appnair]

What I would do is to go to the Admin/index server enable debug=2 ,wantlogs=true and re-start.Then using the address of this box in a browser(if localhost works then that) try to add documents and retrieve documents then look in the thread<nn>.out and connect<nn>.out for any obvious errors.Theoretically if the Front ends and admin are rone by the same service users and they are connected to the same DB and they are working against a filestore path that all servers can see(meaning the EFS entry should not look like c:\myserverefs\) then you should have some success.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

http://www.livelink.in

 

[LAMINI]

I know youve never heard of this one... when did this issue arise? What changes were made to the system around that timeframe?

As a lazy troubleshooter, I tend to backup the systems prior to making changes for this sole purpose. Something goes bad, go back to known good last backup. At the very least compare the key files and check deltas.