NTLM Synchronization Issues

I am running 3 Livelink Servers (Svr1,Svr2,Svr3) connected to the same DB and we are using NTLM synchronization to import users from AD. The NTLM sychronization is configured to run twice daily at 7 pm and again a 1 am. The problem I am having is that all 3 servers kick off synchronization at 7pm each one attempting to update the DB. At some point in the process deadlock occurs and 1 or all of the NTLM sync processes fails to complete and we start having access issues in livelink. Is there a way to stop these three servers from running the sync at the same time causing deadlock on the LL DB.

Find more posts tagged with

Comments

Andrew_Ormesher_(andrew.ormesher@fastman.net.au_(D

Hi Asa,Happy to be corrected, but I understood the sync settings were stored in the opentext.ini file, not in the DB. This means the sync should only operate from one server in your cluster (the one you configured it from). Are you pointing to a common as well as a common DB, or have you copied slabs of the ini file from one server to another? We've set up NTLM sync for heaps of customers, and I've never seen your issue before...Cheers,Andrew OrmesherFastman Consulting Australia

Chris_Wagg

Message from Chris Wagg <cwagg@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

In Directory Services 3.0 the ini settings were moved to the database. But that is not likely the cause of this issue. More likely it is that you have agents running on all three servers. You need to have just one server running agents.

---------------------------------------
Chris Wagg
Principal Product Specialist
Escalations Support Team
Open Text Corporation
Ph: 800-540-7292
---------------------------------------

From: eLink Discussion: Livelink Directory Services Discussion [mailto:directoryservices@elinkkc.opentext.com]
Sent: Monday, February 09, 2009 1:25 AM
To: eLink Recipient
Subject: common opentext.ini file?

common opentext.ini file?		Posted by andrew.ormesher@fastman.net.au (Ormesher, Andrew) on 2009/02/09 01:21
In reply to: NTLM Synchronization Issues		Posted by intdat02 (Elkins, Asa) on 2009/02/03 15:06

Hi Asa,

Happy to be corrected, but I understood the sync settings were stored in the opentext.ini file, not in the DB. This means the sync should only operate from one server in your cluster (the one you configured it from). Are you pointing to a common <OTHOME> as well as a common DB, or have you copied slabs of the ini file from one server to another?

We've set up NTLM sync for heaps of customers, and I've never seen your issue before...

Cheers,
Andrew Ormesher
Fastman Consulting Australia