Let us take a closer look at the SQL server agent error 1068, the causes, and the troubleshooting steps necessary to remove the error. At Bobcares our MSSQL support services will give you a detailed overview of the Error and the Troubleshooting steps.

The SQL Server service and the SQL Server Agent Service fail to start on a standalone server

The SQL Server service and the SQL Server Agent Service might not start on a standalone server. This article explains how to fix the issue.

Causes for the SQL server agent error 1068

• Issue 1: On a standalone server, the MSSQLSERVER service may fail to start, resulting in the error message:

  While performing this service activity on the MSSQLServer Service, an error 1068 – (The dependant service or group failed to start.) occurred.
• Issue 2: The SQLServerAgent service may also fail to start, resulting in the following error message:

  While performing this service action on the SQLServerAgent Service, an error 1068 – (The dependant service or group failed to start.) occurred. When both of the following circumstances are met, Issues 1 and 2 occur:

  1: The server computer is a member of a workgroup rather than a domain. 2: Both the MSSQLSERVER and SQLServerAgent services are configured to start with a domain account.
• Issue 3: On a domain member server, the MSSQLSERVER service may fail to start during server startup, resulting in the error message:

  Due to the following issue, the MSSQLSERVER service was unable to connect on as domainmssqlsvc with the presently specified password:

  NetLogon is the source. There are currently no logon servers available to handle the logon request. The MSSQLSERVER service suddenly stopped.

This issue and the SQL server agent error 1068 happens when all of the following circumstances are met:

• The server belongs to a domain.
• Both the MSSQLSERVER and SQLServerAgent services are configured to start with a domain account.
• The MSSQLSERVER and SQLServerAgent’s startup mode is set to Automatic.

Causes for the errors

As the server is a standalone machine, the NetLogon service does not start on the server, so no domain-wide logon authentications are available.

Issue 3 occurs when SQL Server services attempt to start before the NetLogon service.

Resolution for the SQL server agent error 1068

Follow these procedures to resolve Issues 1 and 2:

• Change the MSSQLSERVER and SQLServerAgent starting accounts to utilize the local system account.
• Reboot the server.

Use the following workarounds to resolve Issue 3:

• Configure SQL Server startup to be delayed for specific Windows servers, and other Windows services such as NetLogon will complete before SQL Server starts.
• Set the SQL Server startup to retry; the startup can be finished on the second attempt.
• Change the value of Duplicate Address Detection (-DadTransmits) for all network interfaces on the server to 1. For further details, see Set-NetIPInterface.
• Change the SQL Server and SQL Server Agent recovery parameters. For the failure alternatives, select Restart the service as the action.

  We can carry out this option via the Administrative Tools Services applet, utilizing the familiar Service Control Manager interfaces.

If the delayed start option does not resolve Issue 3, we can add the SQL Server service to the following dependencies:

• IP assistance service
• Server Service
• Network list service

Using the following command, we can add the dependencies:

SQL

sc.exe qc MSSQLSERVER ::view dependencies sc.exe config MSSQLSERVER depend=iphlpsvc/LanmanServer/netprofm ::add service dependencies.

[Need assistance with similar queries? We are here to help]

Conclusion

To conclude, we have now learned more about the SQL server agent error 1068 the causes that triggered it, and the resolutions or the troubleshooting steps necessary to deal with the error with the support of our MSSQL support services.