ConnectionOpen error on SQL server Registration

• Peter Tickler

  Newbie

  Points: 1

  More actions

  July 10, 2006 at 7:59 am

  #67563

  Following an attempt to install a third party package which contains a SQL Server DB on my server, I hit a major problem. I am suddenly unable to open the SQL Server Registration on that server. Whe I try to open or connect or even to look at the properties on the registration, I get an error "A connection could not be established to MYSERVER Reason: SQL server does not exist or access denied."

  I tried to modify the properties of the registration, and tried both Windows and SQL server authentication,  but although it appeared to allow me to modify, I still got a similar error message.

  However, I should stress that I can access the DB from SQL Server installed on another server, and my users' applications can also read and write to the DB.

  I am considering copying all the data to a back-up elsewhere, then deleting and recreating the SQL Server Registration and then copying the Db back, but it would be time-comsuming, disruptive to my users, and a little stressful to me!

  Any bright ideas very welcome!!!

   

  Peter

• Yelena Varshal

  SSC-Dedicated

  Points: 34286

  More actions

  July 10, 2006 at 2:36 pm

  #648330

  Peter,

  I think you problem could be because an entry was created in a Client Network Utility that does not reflect the true connection information or enabled protocol. For example, if only TCP/IP protocol is enabled on you SQL Server and the Client Network utility tries to use Named Pipes it could be a problem. Also if you server has 2 IPs then any mention to LocalHost could not be resolved.

  I suggest:

  1. Go to Server Network Utility (from SQL Server Start menu) and check what protocols are enabled.

  2. Go to Client Network Utility (from SQL Server Start menu) and check what aliases are created there if any and what is default protocol.

  3. From another server where you can connect to DB go to Current Activity window for your misbehaving server and see what protocols the successful connections are using.

  4. In Client Network Utility on the misbehaving server create the alias with the protocol and (if applicable) port that successful connections are using.

  5. Use this alias from #4 to register the server.

  Regards,Yelena Varsha