Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Update > Failed connection to MSSQL$MICROSOFT##SSEE

Reply
Thread Tools Display Modes

Failed connection to MSSQL$MICROSOFT##SSEE

 
 
CWPBSusan
Guest
Posts: n/a

 
      11-21-2008
Hi,
I went ahead and loaded the SQL Native Client and SQLCmd utility on the Server
to reindex the WSUS 3.0 database as instructed at this site....

http://technet.microsoft.com/en-us/l.../cc708594.aspx

When I run the command to run the script on the server (script location is
the c:\Path\WsusDBMaintenance.sql. I receive a connection error message
stating the
following:
[SQL Native Client]Named Pipes Provider: Could not open a connection to SQL
Server [53].
[SQL Native Client]Login timeout expired
[SQL Native Client]An error has occurred while establishing a connection to
the server. When connecting to SQL Server 2005, this failure may be caused by
the fact that under the default settings SQL Server does not allow remote
connections.

Further research tells me that I need to enable the SQL Browser server to
allow the
connection. Can you tell me how to enable that service? I know it was
enabled at installation but I don't know when it was disabled. I've been
looking for line command instructions on how to enable the service. The only
instructions I could
locate tell you how to enable the SQL Browser using SQL Server Management
Studio but that isn't installed on the server. Do I have to to install the
SQL Server Management Studio to do this and if so how will that impact the
WSUS database and in the future the SP1 upgrade?


 
Reply With Quote
 
 
 
 
PA Bear [MS MVP]
Guest
Posts: n/a

 
      11-21-2008
[Right pew, wrong church. Forwarded to WSUS newsgroup
(microsoft.public.windows.server.update_services) via crosspost as a
convenience to OP. NB: OP may have multiposted...again.

On the web:
http://www.microsoft.com/communities...pdate_services

In your newsreader:
news://msnews.microsoft.com/microsof...ate_services]]

CWPBSusan wrote:
> Hi,
> I went ahead and loaded the SQL Native Client and SQLCmd utility on the
> Server to reindex the WSUS 3.0 database as instructed at this site....
>
> http://technet.microsoft.com/en-us/l.../cc708594.aspx
>
> When I run the command to run the script on the server (script location is
> the c:\Path\WsusDBMaintenance.sql. I receive a connection error message
> stating the
> following:
> [SQL Native Client]Named Pipes Provider: Could not open a connection to
> SQL
> Server [53].
> [SQL Native Client]Login timeout expired
> [SQL Native Client]An error has occurred while establishing a connection
> to
> the server. When connecting to SQL Server 2005, this failure may be caused
> by the fact that under the default settings SQL Server does not allow
> remote
> connections.
>
> Further research tells me that I need to enable the SQL Browser server to
> allow the
> connection. Can you tell me how to enable that service? I know it was
> enabled at installation but I don't know when it was disabled. I've been
> looking for line command instructions on how to enable the service. The
> only instructions I could
> locate tell you how to enable the SQL Browser using SQL Server Management
> Studio but that isn't installed on the server. Do I have to to install
> the
> SQL Server Management Studio to do this and if so how will that impact the
> WSUS database and in the future the SP1 upgrade?


 
Reply With Quote
 
RunDMC
Guest
Posts: n/a

 
      11-21-2008
My guess is that your named pipe syntax is incorrect. You may have a
non-default database name.

To check that, double click the SQL agent icon running in the system tray.
Mine is the default of "MICROSOFT##SSEE". You could also try running the
command without specifying the named pipes connection.

When I tested the script, I didn't get the same error you did but I did get
another one. I switched around the parameters to the sqlcmd command and it
worked.

sqlcmd -i c:\temp\wsusdbmaint.sql -S
np:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

If none of that works, are you running Windows Internal Database or SQL
Server 2005 Express edition?



"CWPBSusan" wrote:

> Hi,
> I went ahead and loaded the SQL Native Client and SQLCmd utility on the Server
> to reindex the WSUS 3.0 database as instructed at this site....
>
> http://technet.microsoft.com/en-us/l.../cc708594.aspx
>
> When I run the command to run the script on the server (script location is
> the c:\Path\WsusDBMaintenance.sql. I receive a connection error message
> stating the
> following:
> [SQL Native Client]Named Pipes Provider: Could not open a connection to SQL
> Server [53].
> [SQL Native Client]Login timeout expired
> [SQL Native Client]An error has occurred while establishing a connection to
> the server. When connecting to SQL Server 2005, this failure may be caused by
> the fact that under the default settings SQL Server does not allow remote
> connections.
>
> Further research tells me that I need to enable the SQL Browser server to
> allow the
> connection. Can you tell me how to enable that service? I know it was
> enabled at installation but I don't know when it was disabled. I've been
> looking for line command instructions on how to enable the service. The only
> instructions I could
> locate tell you how to enable the SQL Browser using SQL Server Management
> Studio but that isn't installed on the server. Do I have to to install the
> SQL Server Management Studio to do this and if so how will that impact the
> WSUS database and in the future the SP1 upgrade?
>
>

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
What is error code 0x80070643 during MSSQL Server 2005 SP2 update? fuzzy Windows Update 3 09-04-2008 01:51 PM
Re: The connection to the server has failed. Microsoft Email on Vi breanna Windows Vista Mail 3 08-21-2008 11:06 PM
Re: The connection to the server has failed. Microsoft Email on Vi breanna Windows Vista Mail 0 08-21-2008 05:25 PM
MSSQL$SHAREPOINT starts and then stops - after Windows Update on 7 javisa Windows Update 5 07-24-2008 01:59 PM
MSSQL Mason Windows Vista General Discussion 2 06-20-2007 08:01 AM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59