BEUtility - "Failed to start the SQL service"

[deeroad]

Have made many changes to Backup Exec servers. Goal was to change service account and reset everything related to it. All SQL services are now running. Backup Exec can read database but I guess it can't write to database?

BEUtility is unable to do any of the SQL operations. It can't check database, age, compact, dump etc. All fail with same result: "Failed to start the SQL service" but it is already running?

• checked "setspn.exe -L serviceaccountname" and it is ok
• detached BEDB database and attached it back
• serviceaccount is running SQL server services

• Security - Logins - serviceaccountname - Server Roles: public and sysadmin
• Security - Logins - serviceaccountname - User Mapping:
  • BEDB; db_datareader, db_owner, public
  • MSDB; public, RSEXecRole, SQLAgentOperatorRole, SQLAgentReaderRole, SQLAgentUserRole
  • ReportServer; db_owner, public, RSExecRole
  • ReportServerTempDB; db_owner, public, RSExecRole

Already done BEUtility "Change Service Account" successfully. Tried to do "Change Database Access" with old and with new service accounts. Both fail: "Failed to start the SQL service on: servername".

How to get BEUtility fixed so that it can handle all SQL operations again?

[VJware]

What is the size of the BEDB ? Any errors/warnings in the event viewer ?

And is the SQL instance using the local system account ?

[deeroad]

BEDB_DAT.DF is 1,1GB. Can't find any info at Windows logs.

SQL instance is using specific domain/domainadmin level account. NTFS-security should be correct, this account has FULL access to both Backup Exec and SQL directories.

Finally I used Sysinternals Process Monitor against BEUTILITY.EXE. It shows following:

Operation: RegQueryValue
Result: NAME NOT FOUND

HKLM\SOFTWARE\Symantec\Backup Exec For Windows\Adamm\Database Server Name
HKLM\SOFTWARE\Symantec\Backup Exec For Windows\Adamm\Database Name
HKLM\SOFTWARE\Symantec\Backup Exec For Windows\Adamm\ODBC Driver Connection String (Migration)
HKLM\SOFTWARE\Symantec\Backup Exec For Windows\Adamm\ODBC Driver Connection String (Destination)

HKLM\SOFTWARE\Symantec\Backup Exec For Windows\BEDatabase\Server Database Path
HKLM\SOFTWARE\Symantec\Backup Exec For Windows\BEDatabase\Server Database Log Path
HKLM\SOFTWARE\Symantec\Backup Exec For Windows\BEDatabase\Server Database Server Name
HKLM\SOFTWARE\Symantec\Backup Exec For Windows\BEDatabase\Server Database Name
HKLM\SOFTWARE\Symantec\Backup Exec For Windows\BEDatabase\Catalog Database Server Name
HKLM\SOFTWARE\Symantec\Backup Exec For Windows\BEDatabase\Catalog Database Name

HKLM\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Server\AllowRemoteDatabaseAccess
HKLM\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Server\OriginalInstalledDBServer
HKLM\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Server\OriginalInstalledDBName

HKLM\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Server\DjmMgr
HKLM\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Server\DjmClient
HKLM\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Server\DjmEnabled
HKLM\SOFTWARE\Microsoft\MSSQLServer\Setup
HKLM\SOFTWARE\KVS\Enterprise Vault
HKLM\Cluster
 

Guess only first ten are important ones. They are all either missing or empty. Can't find much information of these. I will try adding

[VJware]

Set the SQL instance to run under a local system account and not a domain account.

And fill up these registry keys with their values as well:-

HKLM\SOFTWARE\Symantec\Backup Exec For Windows\Adamm\Database Server Name

Specify the media server name if default SQL is being used, else specify the remote SQL server name

HKLM\SOFTWARE\Symantec\Backup Exec For Windows\Adamm\Database Name

By default, this would be BEDB

HKLM\SOFTWARE\Symantec\Backup Exec For Windows\BEDatabase\Server Database Path

By default, the path would be C:\Program Files\Symantec\Backup Exec\Data\bedb_dat.mdf

HKLM\SOFTWARE\Symantec\Backup Exec For Windows\BEDatabase\Server Database Log Path

By default, the path would be C:\Program Files\Symantec\Backup Exec\Data\bedb_log.ldf

HKLM\SOFTWARE\Symantec\Backup Exec For Windows\BEDatabase\Server Database Server Name
HKLM\SOFTWARE\Symantec\Backup Exec For Windows\BEDatabase\Server Database Name
HKLM\SOFTWARE\Symantec\Backup Exec For Windows\BEDatabase\Catalog Database Server Name
HKLM\SOFTWARE\Symantec\Backup Exec For Windows\BEDatabase\Catalog Database Name

These last 4 keys would be again similar to the first 2 ones.

[deeroad]

Thank you. All these should be now fine. When I start Backup Exec Utility -> choose local server -> repair database, it finds two things: 1) Backup Exec =  this is right, it's same as a hostname 2) Database instance: Backup Exec. I'm not sure this is correct?Still it "fails to start SQL server service".

Made three additional registry changes:

HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Adamm\Database Instance Name = MSSQLSERVER
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\BEDatabase\Catalog Database Instance Name = MSSQLSERVER
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\BEDatabase\Server Database Instance Name = MSSQLSERVER

BEUtility still doesn't work but maybe we are very close now.

[VJware]

The default SQL instance name is BKUPEXEC. Are you sure the instance name is MSSQLSERVER ?

[deeroad]

Can you guide some way to verify which one it is?