Error - Management Studio & Remote Connections ???

  • Hello,

    I Installed mssql2005 SE RTM on win2003 SE yesterday; Everything was working fine. Today IIS was installed on box (so i could later install Reporting Services). I can log onto the box using "Remote Desktop", but when i try to launch Management Studio, I now get the folowing error:

    TITLE: Connect to Server

    ------------------------------

    Cannot connect to AMDIPDB.

    ------------------------------

    ADDITIONAL INFORMATION:

    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. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476

    ------------------------------

    BUTTONS:

    OK

    ------------------------------

     

    Many thanks. Jeff

  • when next RDC'ed onto your SQL server box, run the SQL config tool

    C:\WINDOWS\system32\SQLServerManager.msc

    and check the SQL Server 2005 Network Configuration, Protocols for xxx

    - you should see NamedPipes and/or TCP/IP enabled [r-click properties to explore]

    BTW there should also be lines in the SQL ERRORLOG. file

    Server is listening on [ 'any' <ipv4> 1319]

    Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].

    etc which shows the listeners have been started. Sometimes you may find the listener cannot get exclusive on the IP port number and you will see an entry about SuperSocket blah failed.

    If SQL is using a dynamic port, your client must be able to find it, either by knowing the IP port or asking the SQLBrowser service [if you have this stopped then clients will not be able to query via port 1434]

    It is possible that IIS install either made a change or just cycled the SQL service to freshen up an earlier config change

    HTH

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply