Search This Blog

Tuesday, October 23, 2012

Failed to Open Explicitly Database VirtualManagerDB

 

Scenario:-

  • Installed with DPM 2012 SP1 Beta
  • Installed with VMM 2012 SP1 Beta with SQL Server 2012

Issue:-

  • Unable to backup or create initial recovery point when select VMM Express Writer backup in DPM 2012 SP1 Beta

image

Event log reported, the following error message “Login failed for user NT Authority\SYSTEM. Reason: Failed to Open Explicitly Database VirtualManagerDB”

clip_image002

Resolution:-

1. On the VMM Server, open SQL Manager Studio

2. Connect to the SQL 2012 instance  | select and expand Security | select and expand Logins | right click on the NT AUTHORITY\SYSTEM and select Properties | click on Server Roles |

3. Make sure, sysadmin role is CHECKED.

image

4. On the DPM Server, perform consistency check on the VMM protection group. That should resolve the issue.

5 comments:

  1. Thanks for the quick guide on failures for database opening succession. The issue is not on the sql server support and I'm glad to have read the solution here.

    ReplyDelete
  2. This makes the task easier to monitor the activities of all such persons closely and if anything suspicious is found, his access is cancelled, thus ensuring the better security of the database.create dashboard for oracle

    ReplyDelete