Error 1068: The dependency service or group failed to start

[mickmac06]

Hi,

I am having an issue with my Vault not starting. I get the following error message:

Windows could not start the SQL Server Agent (AUTODESKVAULT) service on local computer.

Error 1068: The dependency service or group failed to start.

I am not using a server, the vault client and server are installed on a local machine.

Anyone able to help?

Cheers,

Mike

[DarrenP]

try starting the service manually: https://knowledge.autodesk.com/support/vault-products/learn-explore/caas/sfdcarticles/sfdcarticles/A...

[mickmac06]

Hi Darren,

Thanks for the suggestion. I had already tried this, I get the Error 1068 message when I try and manually start the 'SQL Server Agent (AUTODESKVAULT)' from the services window.

Thanks again,

Mike

[GunnarNilsson]

The SQL Server Agent isn't needed for Vault to function. I have a local vault server Pro 2020 on my laptop, and that service isn't even running.

Can you please tell us more in detail what your problem is? How does it manifest itself? Vault version and edition?

Your error message states that the dependency service failed to start. That dependency service would be SQL Server (AUTODESKVAULT). Check if that service is running.

[mickmac06]

Hi Gunnar.Nilsson,

I am using Vault Basic 2020 with Inventor/ AutoCAD 2020.

When opening Inventor the Vault Log In window opens and in the bottom left hand corner is says 'Testing server compatibility' (see screen shot 'Vault Error 3') this happens for about 10 minutes then the messages changes to 'Authenticating with server' then I get an error message (see screen shot 'Vault Error 4'). I then go onto the Services app to see if the SQL services are running (see screen shot 'Vault Error 5'). When I try to start them manually I get the following error message:

Windows could not start the SQL Server (AUTODESKVAULT) on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 3418.

Hope this helps.

[GunnarNilsson]

All is down to the fact that the SQL Server service isn't starting. Try to do a repair of the SQL installation from the control panel.

[ihayesjr]

@mickmac06 ,

Try the solution found in this article. Changing the startup account.

[mickmac06]

Hi ihayesjr,

Thank you for the suggestion, unfortunately it didn't work. Neither did repairing the SQL Server as suggested by @GunnarNilsson . I've attached a photo showing how the SQL services are currently running on my laptop. Does this make any sense to you?

Cheers,

Mike

[GunnarNilsson]

On my computer SQL Server (AUTODESKVAULT) is running under NT AUTHORITY\NETWORKSERVICE instead of LocalSystem. But you have another SQL Server running as LocalSystem, so that should be ok.

Try and start the  SQL Server (AUTODESKVAULT) and check the Event logs in Windows to see if they catch anything.

[ihayesjr]

Try changing the Log On As user to the same user as the other SQL Express server that is running on your machine. NT Service account.

[mickmac06]

Hi @ihayesjr & @GunnarNilsson 

Thanks for taking the time to try and help me solve this problem, unfortunately still no joy. I've attached a screen shot what happens when I try to manually start the server after changing the Log On As setting.

Cheers,

Mike

[GunnarNilsson]

Check the Event logs in Windows to see if they catch anything

[mickmac06]

Hi @GunnarNilsson 

There are a lot of errors connected with the SQL server, I've attached a screen shot of the first error in the event log. Does this mean anything to you?

Cheers,

Mike

[GunnarNilsson]

Check this out, might be problem with Beta Unicode settings in Regional Settings:

https://feedback.azure.com/forums/908035-sql-server/suggestions/35221357-installing-service-pack-cum...

 

[ihayesjr]

@mickmac06 , according to the last image you posted, the SQL Master database is having a problem. At this point I recommend that you uninstall SQL and re-install it. Your other option is to create a support case with Microsoft to see if they can resolve the problem. It might be faster just to re-install SQL.