I have 3 DPM servers and one Dell ML6000 Tape Library.  Attempting to set up a shared library between them with DPM-2 as the Library server.  I have set up the SQL Server and Server Agent with a domain account.  I have enabled Named Pipes, and verified that Medium Changer devices is not enabled on the client DPM.  The problem is that the client will not execute the Client SQL Server or the Client DPM Server configuration after seemingly successfully configuring the Global SQL config.

On the client:

AddLibraryServerForDpm.exe -DPMServerWithLibrary dpm-2.hcpss.org
Configuration successful.

On the server:

AddLibraryServerForDpm.exe -ShareLibraryWithDpm dpm-3.hcpss.org
Configuration successful.

On the client:

SetSharedDpmDatabase.exe -DatabaseName DPM-2\MSDPM2012\DPMDB

Enter administrator credential for Global SQL Server (DPM-2)
Domain:hcpss
Username:dpmlibsa
Password:*******

(DPM-2) : Global SQL Server configuration Successful.
Failed to execute SharedLibraryConfigureDb.sql on DPM-3\MSDPM2012

I have attempted to remove the Library sharing from both the server and client, and add it back, with the same results.

I'm having the same issue. Two DPM 2012 servers, trying to share a Dell TL4000 library. I'm getting the same Failed to execute SharedLibraryConfigureDb.sql error. I have an open ticket with Microsoft tech support, and it's been escalated. If the command SetSharedDpmDatabase -DatabaseName <SqlServer\Instance\DatabaseName> [-DoNotMoveData] is run with the -DoNotMoveData option then the command is successful, but the library still doesn't show up correctly on the DPM client. With the changer disabled and the tape drives enabled on the DPM client, the tape drives show up as two separate libraries, which is incorrect. It sees those locally as the library is attached via iSCSI and both the library server and library client can see the TL4000.

The issue I had turned out to be that the AD credentials I used for the SQL server were not part of the local admin group. 

• Marked as answer by cbrun Friday, November 30, 2012 5:59 PM

The issue I had turned out to be that the AD credentials I used for the SQL server were not part of the local admin group. 

• Marked as answer by cbrun Friday, November 30, 2012 5:59 PM

i had the same prob.

i resol it

http://social.technet.microsoft.com/Forums/en-US/dataprotectionmanager/thread/60273619-6534-4776-a56c-e663a092b15c

if it can help you

Chartmann8, did you ever figure out what the problem was?

I am facing exacly the same problem. :(

The issue is fixed in DPM 2012 R2 UR5 

http://support.microsoft.com/en-us/kb/3021791 

• Proposed as answer by Manu Jeewani1 4 hours 37 minutes ago

The issue is fixed in DPM 2012 R2 UR5 

http://support.microsoft.com/en-us/kb/3021791 

• Proposed as answer by Manu Jeewani1 Thursday, April 02, 2015 3:00 AM

The issue is fixed in DPM 2012 R2 UR5 

http://support.microsoft.com/en-us/kb/3021791 

• Proposed as answer by Manu Jeewani1 Thursday, April 02, 2015 3:00 AM