Trouble backing up SQL - "Failed to get the state of service 'MSSQL$ACRONIS'"
Acronis Backup Advanced 11.7, with SQL agent installed. Windows Server 2012 with an existing MS SQL server for a patient management system. Acronis Backup was installed to the existing server by specifying only the system name "SQL01" for the database instance during a custom installation, and installation finished successfully without errors.
When trying to run a backup plan with single-pass backup enabled, I get the errors below. I'm not (yet!) well-versed in database administration, but I suspect that the key to this problem is found in the message field after error code 285, below. Is the service name listed in quotes supposed to be a <server name> $ <instance name> ? If so, then both are wrong, and I don't know how to correct the Acronis configuration.
Command 'Backing up' has failed.
Additional info:
--------------------
Error code: 61
Module: 309
LineInfo: 4a8728dc8a1c9510
Fields: $module : service_process_vs_50256
Message: Command 'Backing up' has failed.
--------------------
Error code: 22
Module: 309
LineInfo: 8d165e86fb819666
Fields: TraceLevel : 1, $module : gtob_backup_command_addon_vs_50256
Message: TOL: Failed to execute the command. The 'Backing up' command backs up the specified data to the specified location.
--------------------
Error code: 54
Module: 482
LineInfo: 5c71ebf434f0c47a
Fields: $module : disk_bundle_vs_50256
Message: Failed to collect all of the data required for single-pass backup of Microsoft SQL Server.
--------------------
Error code: 285
Module: 87
LineInfo: 2f0200007114185
Fields: $module : ArsAgentProvider_vs_50256
Message: Failed to get the state of service 'MSSQL$ACRONIS'.
--------------------
Error code: 65520
Module: 0
LineInfo: bd28fdbd64edb8ee
Fields: code : 2147943460, $module : ArsAgentProvider_vs_50256
Message: The specified service does not exist as an installed service
--------------------
Hello James,
The above error message usually means that the registry contains information about an SQL instance that doesn't exist any more, but we still try to capture it. You can remove information about the non existent instance MSSQL$Acronis from registry, this should resolve the issue.
!! To be on thew safe side, export the registry before applying any changes !!
Check the following key for presence of MSSQL$Acronis and remove these entries if found
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\Instance Names\
Then look for entries MS.SQL, SQL Express Edition (Acronis) in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Currentversion\Uninstall
Reboot and re-attempt backup.
Should the backup job still fails, make sure the user account has all necessary privileges and SQL Server VSS Writer service is up and running, follow instructions from https://kb.acronis.com/content/42648
Thank you,
Thank you for your detailed response.
Unfortunately, though, I'm still having much the same errors with SQL backups.
I was able to remove an instance name of "Acronis" from the first registry key that you provided. After a reboot, I used "SQLCMD -L" to list instance names and Acronis no longer showed up in the list.
As for the second registry key you provided, I suspect you meant "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\Currentversion\Uninstall" (note the inclusion of the word "Windows"). Regardless, no references to an instance name of "Acronis" were found or removed.
After rebooting, I ran a single pass backup and received all of the previous error messages, with one difference: the first one is now an error 41 instead of an error 61:
Error code: 41
Module: 307
LineInfo: e6792a5ee190de98
Fields: $module : agent_protection_addon_vs_50256
Message: Failed to execute the command.
After receiving the same error messages, I decided to uninstall Acronis Backup and reinstall. Prior to reinstalling, I also:
Deleted Acronis databases and deleted Acronis security logins via SQL Server Management Studio.
Restarted server.
Deleted all Program Files, ProgramData and Acronis-related User directories.
When installing, I chose a custom install. When entering SQL access credentials for the SQL agent, the installation program displays an instance name of MSSQLSERVER, which does not exist on this system. The only instance name is a blank one, referenced as the machine name. I bring this up because the SQL agent portion of the installation generates a series of warning messages. It did this before as well, but I neglected to record them or mention them above. Here is the warning stream:
Acronis Backup 11.7 Agent Core
Code: 013763087
Line tag: 0x851efe822fcbb3c5
Message: Failed to add the machine to the management server.
Suberror
Code: 014417960
Line tag: 0x2a4cf6302dc72c47
Message: Internal error: Command execution has failed.
Suberror
Code: 014417953
Line tag: 0x2a4cf6302dc72c7d
Message: Failed to add Acronis Managed Machine Service to Acronis Backup Management Server.
Suberror
Code: 014417952
Line tag: 0x2a4cf6302dc72ca0
Message: Failed to create the trust relationship.
Suberror
Code: 013434886
Line tag: 0x645a5d6dcc57f0fd
Message: Failed to retrieve the full certificate for service '0'.
Suberror
Code: 0197626
Line tag: 0x2db96111a09da190
Message:
Suberror
Code: 0262164
Line tag: 0xf35f747b3b21fa66
Message: Access to the file is denied.
Suberror
Code: 05
Line tag: 0xbd28fdbd64edb8ee
Message: Access is denied
Looking at these warnings now, and realizing that they are for SQL Agent or the Agent Core, it seems very relevant to this problem.
How do I specify the correct instance for the SQL Agent to connect to? I have the right credentials (Windows Administrator and associated password), but the credential specification screen continues to show a non-existant instance name of MSSQLSERVER. Even "Tools \ Provide SQL Server Credentials" shows the same instance name, and displays a status of "Sysadmin role is granted". But if it can't connect to the right instance, sysadmin credentials won't matter.
Or am I barking up the wrong tree - is the instance name not the issue here?