Update: Our DBA contacted Microsoft support and basically it came down to stopping the SQL server (and all SQL components), starting SQL server in single user-mode and using SQLCMD -E to establish a connection.
We then quit the SQLCMD session and immediately initiated the restore. While it worked for us first time, MS explained that it can be hit-and-miss as it is all about grabbing the connection when it becomes available before an application can. Expressing to MS that there should be a better solution, like configuring the SQL server when in single-user mode to only allow a connection from a certain application, process, or even IP address. Surprisingly their reply was no. If there is a better way perhaps one of the SQL gurus can share. I'm sure it would help many present and future TSMer's who rely on these threads for solutions. ~Rick -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Carlo Zanelli Sent: Wednesday, November 16, 2011 3:42 PM To: [email protected] Subject: Re: [ADSM-L] TDP Restore of SQL 2008 master database Hi Rick, In su mode only one admin at a time is accepted, probably at the master DB restore time another admin was logged. Check this or run server in multi user mode. Hope this helps. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Rick Adamson Sent: Wednesday, November 16, 2011 8:45 PM To: [email protected] Subject: [ADSM-L] TDP Restore of SQL 2008 master database I have been asked to restore the master DB on a Windows 2008 cluster for SQL Server 2008 and have no problems putting the SQL server in single-user mode but the restore still fails. The error message is 11/16/2011 13:21:31 ACO5424E Could not connect to SQL server; SQL server returned: 11/16/2011 13:21:31 Failed to connect to server sqlserverinstance-name. 11/16/2011 13:21:31 Login failed for user 'username'. Reason: Server is in single user mode. Only one administrator can connect at this time. (HRESULT:0x80131501). I have shut down all services except the SQL Server service (SQL Agent, reporting services, etc.), closed all SQL tools (config mngr, SQL studio,etc.) monitored the authentication logging on the SQL Server in hopes of identifying the culprit, and even setup a IPSEC policy limiting access to the server only for RDP and the TSM server .... and no success. Has anyone experienced this behavior and found out what the issue is? Am I missing something? TDP Client version 5.5.4.2 TSM Server version 5.5.5.2 I am able to restore other (non-master) databases. Thanks in advance.... ~Rick Jacksonville, FL. ----- Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute nel messaggio e negli eventuali allegati sono riservate al/ai destinatario/i indicato/i. Nel caso di erroneo recapito, si chiede cortesemente a chi legge di dare immediata comunicazione al mittente e di cancellare il presente messaggio e gli eventuali allegati. Si invita ad astenersi dall'effettuare: inoltri, copie, distribuzioni e divulgazioni non autorizzate del presente messaggio e degli eventuali allegati. ---------- According to Italian law (D.Lgs 196/2003) information contained in this message and any attachment contained therein is addressed exclusively to the intended recipient. If you have received this message in error would you please inform immediately the sender and delete the message and its attachments. You are also requested not to make copies, nor to forward the message and its attachments or disclose their content unless authorised.
