The So called MS Sql Server throws up a
ERROR 1069 : Logon failure everytime you change indows password .
The way to get it working is :
o correct the password in Microsoft Windows 2000 Server and Microsoft Windows XP:
| 1. | Click Start, point to Settings, and then click Control Panel. |
| 2. | Double-click Administrative Tools, and then double-click Services. |
| 3. | Use one of the following steps based on your instance type:| • | For a default instance of SQL Server, double-click MSSQLServer, and then click the Log On tab. | | • | For a named instance of SQL Server, double-click MSSQL$YourInstanceName, and then click the Log On tab. Replace YourInstanceName with the actual name of the SQL Server instance. | | • | For a default instance of SQL Server Agent, double-click SQLAgent, and then click the Log On tab. | | • | For a named instance of SQL Server Agent, double-click SQLAgent$YourInstanceName, and then click the Log On tab. Replace YourInstanceName with the actual name of the SQL Server instance. |
|
| 4. | Type the correct password in the Password and Confirm password textbox, and then click OK. |
2 comments:
Ran into this error, and the password was correct. What the System Event Log said:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7041
Date: 10/8/2008
Time: 9:33:09 AM
User: N/A
Computer: ComputerName
Description:
The SQLSERVERAGENT service was unable to log on as DomainName\SQLAgent with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.
Service: SQLSERVERAGENT
Domain and account: DomainName\SQLAgent
This service account does not have the necessary user right "Log on as a service."
User Action
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account, and the user right appears to be removed, a Group Policy object associated with this node might be removing the right. Check with your domain administrator to find out if this is happening.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
...sure enough it had been removed from the "Logon as a service" list. Hope this helps your readers.
It's not usual to run the services under your own user account. One option is to set up a special account just to run services under (this account should be set up so that the password does not change). As the previous comment mentions, the account will need permission to log on as a service. The other option is to run it under the local system account. This may not be appropriate for the SQLServerAgent if it needs to access remote resources. Either way the password will never change and you will never have a problem.
This is not related to the credentials you use to actually log in to a database.
Post a Comment