In case this saves someone time troubleshooting... ARS 6.3 Windows 2003
A couple weeks ago the server that our ARS server used for LDAP queries was shut down for good. I was not informed, and learned of it when LDAP errors began popping up in our ARS application. Changing the server to another in the ARDBC LDAP Configuration screen should have taken care of the situation. It didn't. I even bounced the server. The network account used is a service account dedicated to Remedy for accessing network resources. To get it working I entered my network credentials. Today I did some troubleshooting and found that I had to tickle the network service account to "fix" whatever the issue was with that account in Active Directory. The solution: Add a group permission to the network service account, save it, then remove the group permssion. This forced Active Directory to re-write the properties for the user object. It's running fine now. -- Stephen Remedy Skilled Professional _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
