August 5, 2003 at 9:22 am
On three different SQL Server 2000 Standard (SP3) systems we periodically have to reset the proxy account for SQL Agent (sometimes daily). After we use Reset Proxy Account everything is fine, but soon the problem comes back. The password on the Windows account is not being changed. Only the password that SQL Server remembers for the account is being changed.
The involved application is browser based, so the only connection that runs the affected code is made from the web server. The affected code works most of the time, then suddenly quits working. To get it working again, we have to (re)enter the password for the proxy account at the server. Resetting the proxy account password for SQL Agent makes the symptom go away.
The only error message I have noticed is on the client, where it occurs because the SQL Server setting gets trashed somehow. The message is:
A severe error occurred on the current command. The results, if any, should be discarded.
xpsql.cpp: Error 1385 from LogonUserW on line 620
This problem affects all three servers almost simultaneously. That may indicate that something external to the servers could be causing the setting (the SQL Agent proxy account password) to change. The only thing that comes to mind along those lines is that there are several development computers with a version of SQL Server installed. Those servers do not have a SQL Agent proxy account set up.
Does anybody have any idea how or why the setting could be getting trashed?
Any thoughts or suggestions would be greatly appreciated.
Thanks,
Brian
Creator of SQLFacts, a free suite of tools for SQL Server database professionals.
August 7, 2003 at 11:02 am
For those who may be interested...
With the help of Microsoft technical support, I think we have this problem resolved. I'm not an expert on Windows 2000 security so I may not describe things perfectly here.
The problem was that the domain account we are using as a proxy did not have a necessary user right. The missing user right was "Log on as a batch job". The act of using Reset Proxy Account on each SQL Server apparently changed the local user right (allowing things to work temporarily), but the domain level user right eventually superseded the local setting (causing things to fail again).
So, SQL Server was not actually forgetting the password, but an external factor (the domain controller) was changing a user right behind the scenes causing the SQL Agent proxy account logon to fail.
Brian
Creator of SQLFacts, a free suite of tools for SQL Server database professionals.
November 23, 2004 at 12:33 pm
Just wanted to say we are having this problem...
Thanks for the post...hope this fixes it...
Brett
😎
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply