December 27, 2012 at 2:14 pm
I am installing SQL server on cluster but SQL Agent has failed to comeonline with bellow errors in event log.
Cluster event :
This issue occurs because the Cluster service does not register the fully qualified domain names (FQDN) of a resource name to the Local Security Authority (LSA).
The Cluster service registers the FQDN of a resource name to LSA and to the DNS database at the same time. However, the DNS registration occurs one time every 24 hours. Therefore, there is a delay in the registration of the FQDN to LSA.
Due to this i am unnable to bring resouces online on NODE1
Error in event log :
Log Name: Application
Source: MSSQLSERVER
Date: date
Event ID: 18456
Task Category: Logon
Level: Information
Keywords: Classic,Audit Failure
User: user name
Computer: computer name
Description:
Login failed for user user name. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: IP address]
Log Name: Application
Source: SQLSERVERAGENT
Date: date
Event ID: 53
Task Category: Failover
Level: Error Keywords: Classic
User: N/A
Computer: computer name
Description:
[sqagtres] StartResourceService: Failed to start SQLSERVERAGENT service. CurrentState: 1
December 28, 2012 at 12:49 am
Are you using a service account or a local system account like Local System or Network Service? How did you set the credentials for the SQL Server Service? Through the Services MMC or through SQL Server Configuration Manager? Configuration Manager should ensure that the service account will have the proper security rights and ensure those settings get propogated to all the nodes in the cluster.
Joie Andrew
"Since 1982"
December 28, 2012 at 7:29 am
This was happen while we are installing cluster ...after installing\end of the installation caught an error and this leads to SQL Server agent got failed state.
we used domain account while instillation cluster.
Can you please explain below point , what does it mean and how to ensure these details are same across same on all the nodes
Configuration Manager should ensure that the service account will have the proper security rights and ensure those settings get propogated to all the nodes in the cluster.
December 28, 2012 at 7:38 am
When you have a cluster all of the servers, or nodes, of the cluster that can own the cluster resources will need to have the accounts setup properly for SQL Server so that they work as expected when the node takes over the cluster resources and tries to bring them online. SQL Server Configuration Manager will ensure that the service account you select has the proper OS rights (like log on as a service) and will set the username and password credentials for the SQL Server service on all nodes in the cluster so they match.
If one node of the cluster can bring up the SQL Server resource fine but the other one cannot when you try and do a failover you might want to reset the service credentials in SQL Server Configuration Manager to see if that resolves the problem.
Joie Andrew
"Since 1982"
December 28, 2012 at 7:45 am
okay
December 28, 2012 at 7:49 am
I just reread the post. I meant to say reset the credentials for the SQL Server Agent service in SQL Server Configuration Manager.
Joie Andrew
"Since 1982"
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply