Error logging in to SQL to move WSUS

Question

I am running SBS 2008 and trying to move the SUSDB database from the C: drive to another drive but when logging in to SQL Server management studio I get the following error: "Cannot connect to \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query login failed for user DOMAIN\Network Admin error 18456.

I was following this guide http://blogs.technet.com/b/sbs/archive/2009/09/23/how-to-move-wsus-content-and-database-files-to-a-different-partition.aspx and have tried everything I can think of. I have done this before on a different SBS 2008 server and didn't have this issue.

Answer 1

Please verify in the error log will your account logging in successfully,

which account you are using to move is that one DOMAIN/NETWORK Admin, so please does it have proper accesses i,e Sysadmin onSQL server and it should be part of local administrator in the box....

to perform this you should have sysadmin,ensure you have all the full control permission on the folders where you are moving from the files

what is the SQL server edition you are using..

Also -this might help

http://blog.kazmarek.com/2010/3/3/move-wsus-sql-database-to-another-location/

http://www.passionateaboutit.net/KnowledgeBase/tabid/113/EntryId/25/How-to-move-susdb-mdf-for-WSUS-3-0-in-Windows-SBS-2008.aspx

---

Rama Udaya.K ramaudaya.blogspot.com ---------------------------------------- Please remember to mark the replies as answers if they help and un-mark them if they provide no help.

Answer 2

Since this is a Windows 2008 server, most likely, the User Access Control is causing the issue.

When you want to connect the instance, right click on SSMS and Run as Administrator.  And give the above name pipe, you should be able to get in.

Starting with Windows 2008, with UAC enabled, you always have to use right as administrator.  If you wish to use the BUILTIN\Administrator permissions on SQL Server.

---

Mohit K. Gupta --- MCTS, MCITP, MCC2011
My Blog OpsVault My MSDN Blog Twitter @SQLCAN

Answer 3

Since this is a Windows 2008 server, most likely, the User Access Control is causing the issue.

When you want to connect the instance, right click on SSMS and Run as Administrator.  And give the above name pipe, you should be able to get in.

Starting with Windows 2008, with UAC enabled, you always have to use right as administrator.  If you wish to use the BUILTIN\Administrator permissions on SQL Server.

---

Mohit K. Gupta --- MCTS, MCITP, MCC2011
My Blog OpsVault My MSDN Blog Twitter @SQLCAN

Bumping an old thread, but I had this exact problem, and UAC was the issue. Thank you!