none
DPM could not connect to SQL server instance. ID: 966 RRS feed

  • Question

  • Okay so I recently set up DPM 2012 Beta and after some configuration everything seemed to be working smoothly such as backups of shares, volumes, and system protection all work. However when I set up a new protection group and go to Expand either the sharepoint server or the SQL server. I get the error that

    "DPM could not connect to SQL server instance USSSQL on the protected computer USSSQL.randomdomain. (ID: 966)"

    I also get an error for every database on that server saying this: (same for every database just replace model with DB name)

    "DPM could not enumerate application component USSSQL\model on protected computer USSSQL.randomdomain. (ID: 964)"

    Both the SQL Server and the Sharepoint server are Windows Server 2008R2 Virtual Machines, we are running Microsoft SQL 2008R2 and Sharepoint 2010.

    I already checked the "vssadmin list writers" command and made sure that the SqlServerWriter is running and Stable.

    Writer name: 'SqlServerWriter'

       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

       Writer Instance Id: {aa90bc7f-3a71-4925-ae12-a6229ac8edc3}

       State: [1] Stable

       Last error: No error

     


    Austin Brogle Computer Specialist Computer Center II, Room 209E University of Central Florida
    • Edited by Austin Brogle Monday, January 30, 2012 1:14 PM
    • Moved by Larry Yin Wednesday, March 28, 2012 10:32 PM (From:DPM 2012 Beta - Locked)
    Thursday, January 26, 2012 4:11 PM

Answers

  • I solved the problem, the problem was that NT Authority\System did not have sysadmin rights on the SQL instance. After adding those rights, it now works flawlessly.
    Austin Brogle Computer Specialist Computer Center II, Room 209E University of Central Florida
    • Marked as answer by Austin Brogle Monday, January 30, 2012 7:41 PM
    Monday, January 30, 2012 7:41 PM

All replies

  • I solved the problem, the problem was that NT Authority\System did not have sysadmin rights on the SQL instance. After adding those rights, it now works flawlessly.
    Austin Brogle Computer Specialist Computer Center II, Room 209E University of Central Florida
    • Marked as answer by Austin Brogle Monday, January 30, 2012 7:41 PM
    Monday, January 30, 2012 7:41 PM
  • NT Authority\System also resolved the same issue for be when using DPM 2012 (RTM) to protect SQL 2012 (RTM)

    Thanks Austin ;o)

    Friday, November 23, 2012 2:07 PM