Cannot connect to MICROSOFT##SSEE SQL 2005 instance using SQL Server Management Studio : The configuration of the AdminConnection\TCP protocol in the SQL instance MICROSOFT##SSEE is not valid., SQL Browser

May 17, 2008 12:06pm pdt

1. chapmandew 1,139,490
2. angelIII 656,012
3. aneeshat... 347,059
4. ee_rlee 305,823
5. dtodd 190,705
6. brejk 170,605
7. ptjcb 151,519
8. mark_wills 146,165
9. PFrog 98,658
10. acperkins 86,575
11. dqmq 75,630
12. dportas 74,146
13. momi_sabag 71,940
14. maradam 71,186
15. Thomasian 70,100

1. angelIII 1,936,203
2. chapmandew 1,139,490
3. aneeshat... 912,164
4. ptjcb 515,911
5. Yveau 505,473
6. dtodd 401,710
7. PFrog 368,686
8. dqmq 346,978
9. imitchie 324,100
10. ee_rlee 305,823
11. appari 277,897
12. Lowfatsp... 220,339
13. rboyd56 192,515
14. SQL_SERV... 183,215
15. acperkins 181,914

03.12.2008 at 08:59AM PDT, ID: 23235559

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.7

Cannot connect to MICROSOFT##SSEE SQL 2005 instance using SQL Server Management Studio

Zones: SQL Server 2005, MS SQL Server

Tags: The configuration of the AdminConnection\TCP protocol in the SQL instance MICROSOFT##SSEE is not valid., SQL Browser

I am recently unable to connect to connect to the MICROSOFT##SSEE SQL instance using SQL Management Studio. It houses my WSUS 3.0 databases. Upon starting the server I see this error in the event log:

Event Type:      Warning
Event Source:      SQLBrowser
Event Category:      None
Event ID:      3
Date:            3/12/2008
Time:            11:41:32 AM
User:            N/A
Computer:      PANDORA-DBS
Description:
The configuration of the AdminConnection\TCP protocol in the SQL instance MICROSOFT##SSEE is not valid.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I have looked at the settings in SQL configuration manager and changed the port to 1433 instead of dynamic. Now when i restart the instance, i get the following error:

Event Type:      Failure Audit
Event Source:      MSSQL$MICROSOFT##SSEE
Event Category:      (4)
Event ID:      18456
Date:            3/12/2008
Time:            11:38:06 AM
User:            NT AUTHORITY\NETWORK SERVICE
Computer:      PANDORA-DBS
Description:
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: <named pipe>]

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 18 48 00 00 0e 00 00 00 .H......
0008: 1c 00 00 00 50 00 41 00 ....P.A.
0010: 4e 00 44 00 4f 00 52 00 N.D.O.R.
0018: 41 00 2d 00 44 00 42 00 A.-.D.B.
0020: 53 00 5c 00 4d 00 49 00 S.\.M.I.
0028: 43 00 52 00 4f 00 53 00 C.R.O.S.
0030: 4f 00 46 00 54 00 23 00 O.F.T.#.
0038: 23 00 53 00 53 00 45 00 #.S.S.E.
0040: 45 00 00 00 07 00 00 00 E.......
0048: 6d 00 61 00 73 00 74 00 m.a.s.t.
0050: 65 00 72 00 00 00 e.r...

Trying to log in to the instance in SQL Management Studio give the following error:

===================================

Cannot connect to PANDORA-DBS\MICROSOFT##SSEE.

===================================

Instance failure. (System.Data)

------------------------------
Program Location:

at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

I am using Windows Authentication to log in. I used to be able to do this. Any help would be greatly appreciated!

Start your free trial to view this solution

Question Stats

Zone: Microsoft

Question Asked By: dshaney

Solution Provided By: vijay4sql

Participating Experts: 2

Solution Grade: A

Translate:

Loading Advertisement...

Microsoft

Internet Protocols
Applications

Development
OS

Hardware
Windows Security

Apple

Operating Systems
Hardware

Programming
Networking

Software

Internet

Search Engines
File Sharing
WebTrends / Stats
Spy / Ad Blockers

Web Browsers
New Net Users
Web Development
Chat / IM

Anti Spam
Web Servers
Anti-Virus
Email Clients

Gamers

Tips
Online / MMORPG
Puzzle
Emulators

Action / Adventure
Role Playing
Consoles
Game Programming

Strategy
Sports
Misc
Computer Games

Digital Living

Hardware
New Net Users
New Users

Software
Digital Music
Gaming World

Home Security
Apple
Networking Hardware

Virus & Spyware

Vulnerabilities
IDS
Encryption
Anti-Virus

Operating Systems Security
Software Firewalls
WebApplications
Cell Phones

Operating Systems
Internet
Hardware Firewalls

Hardware

Handhelds / PDAs
Displays / Monitors
Components
Networking Hardware

Peripherals
Laptops/Notebooks
Storage
Servers

Desktops
New Users
Misc
Apple

Software

System Utilities
Industry Specific
Network Management
Photos / Graphics
Page Layout
VMWare
Misc
Web Development

OS
CYGWIN
Voice Recognition
Message Queue
Quality Assurance
Security
Firewalls
MultiMedia Applications

Development
Database
Office / Productivity
Business Management
OS/2 Apps
Server Software
Internet / Email

ITPro

OS
Storage
Encryption
Operating Systems Security
Apple Hardware
Laptops & Notebooks
Servers
Networking Hardware
Peripherals

Devices
Displays / Monitors
WebTrends / Stats
Search Engines
Firewalls
WebApplications
IDS
Vulnerabilities
Email Clients

File Sharing
Spy / Ad Blockers
Web Browsers
Web Servers
Networking
Anti-Virus
Chat / IM
Anti Spam

Developer

Web Servers
Web Browsers
Game Programming
Dev Tools
Industry Specific
Office / Productivity

Database
CYGWIN
Web Development
Search Engines
File Sharing
WebTrends / Stats

Programming
Content Management
Application Servers
Protocols

Storage

Removable Backup Media
Storage Technology
Servers

Grid
Remote Access
Backup / Restore

Misc
Hard Drives

Miscellaneous
Security
Development
Linux
VMWare

MainFrame OS
Unix
Apple
OS / 2
AS / 400

BeOS
Microsoft
VMS / OpenVMS

Database

Oracle
Miscellaneous
MySQL
Software
Sybase
Contact Management
PostgreSQL
Data Manipulation
Clarion
InterSystems Cache

Siebel
MUMPS
OLAP
SQLBase
SAS
GIS & GPS
4GL
Berkeley DB
DB2
Informix

Interbase / Firebird
FoxPro
Reporting
LDAP
Filemaker Pro
MS SQL Server
dBase
MS Access

Security

Misc
Web Browsers
Software Firewalls
Operating Systems Security
File Sharing

Spy / Ad Blockers
Vulnerabilities
WebApplications
IDS
Anti-Virus

Encryption
Anti Spam
Email Clients
VPN
Chat / IM

Programming

Editors IDEs
Installation
Handhelds / PDAs
Multimedia Programming
System / Kernel

Algorithms
Game
Signal Processing
Project Management
Open Source

Database
Misc
Languages
Processor Platforms
Theory

Web Development

Scripting
Blogs
Web Servers
Software
Search Engines
Web Graphics
Images

Internet Marketing
Images and Photos
Components
Document Imaging
Web Languages/Standards
Illustration
WebApplications

Fonts
WebTrends / Stats
Authoring
Digital Camera Software
Miscellaneous

Networking

Protocols
Apple Networking
Network Management
Message Queue
Application Servers
Content Management
File Servers
Email Servers
Misc
Java Editors & IDEs

Wireless
Networking Hardware
Backup / Restore
System Utilities
ISPs & Hosting
Web Servers
Storage Technology
Removable Backup Media
Servers
Broadband

Grid
OS / 2
Novell Netware
Unix Networking
Windows Networking
Security
Telecommunications
Operating Systems
Linux Networking

Other

Community Advisor
Lounge
Community Support
New Net Users

Philosophy / Religion
Math / Science
Miscellaneous
URLs

Expert Lounge
Politics
Puzzles / Riddles

Community Support

Suggestions
New to EE
New Topics
Community Advisor

CleanUp
Announcements
General

Feedback
Input
EE Bugs

03.12.2008 at 09:04AM PDT, ID: 21107442

Rank: Genius

ptjcb:

Check in the SQL Server Configuration Manager > Network Protocols > Protocols for MICROSOFT##SEEE

Right-click and choose Properties. Is the Hide Instance column set to Yes? Change that to no.

You may have to restart MICROSOFT##SSEE.

03.12.2008 at 10:33AM PDT, ID: 21108551

dshaney:

Hi ptjcb,

Both Hide Instance and Force Encryption are set to No.

03.12.2008 at 10:37AM PDT, ID: 21108609

Rank: Genius

ptjcb:

Good.

In the SQL Server Surface Configuration Manager, have you set the remote connections for Microsoft##SSEE for tcp/ip and named pipes?

03.12.2008 at 11:30AM PDT, ID: 21109213

dshaney:

They are both enabled. The TCP/IP settings are identical to another instance that has no issues (there are two SQL instances). The named pipes actual name is different, but i'm assuming it needs to be. It is:

\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

Shared memory is also enabled.

03.12.2008 at 11:41AM PDT, ID: 21109316

dshaney:

The surface configuration is set for using both TCP/IP and named pipes.

03.12.2008 at 11:50AM PDT, ID: 21109398

Rank: Genius

ptjcb:

Hmmmm.

You might try

From http://channel9.msdn.com/ShowPost.aspx?PostID=316309

ÿI had the same problem, but the difference was that instead of SQL Server Management Studio Express, I had installed the original SQL Server Management Studio (Not the Express one). I solved the problem by going to SQL Server Configuration Manager --> SQL Native Client Configuration ---> Aliases ---> Right click on Alias name: <servername>\Microsoft##SSEE ---> properties ---> Change the Alias Name from <servername>\Microsoft##SSEE to <servername>\##SSEE.

03.12.2008 at 12:20PM PDT, ID: 21109702

dshaney:

I have no aliases listed. Should there be?

03.12.2008 at 12:28PM PDT, ID: 21109781

Rank: Genius

ptjcb:

I don't know. The first two steps worked at this location.

03.12.2008 at 07:43PM PDT, ID: 21112905

vijay4sql:

The connectivity on embedded edition is little nasty. It does not listens on tcp.. or np (well if it listens it doesnt correctly reports it in log files)

try connecting as
np:the pipe name that u see in the sql log files
or
just specify the pipe name

* Hope u didnt change the pipe name by now.

tx-vj

Accepted Solution

dshaney

03.21.2008 at 06:09AM PDT, ID: 21179606

I was able to connect through SQL Server Management Studio by using the named pipe ( \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query) instead of the default server name (SERVER)\MICROSOFT##SSEE in the Connect to Server dialog box using Windows authentication.

At this point i am still not sure why it stopped working as the default server name, but at least i can get to it now. :)

dshaney

03.21.2008 at 08:35AM PDT, ID: 21180632

Follow up:

Tried to migrate the SUSDB from Windows Internal Database to the main SQL instance per http://technet2.microsoft.com/windowsserver/en/library/b4852133-5ed3-48d7-8a95-e7866e638c181033.mspx?pf=true

This returned an error, so i uninstalled WSUS and reinstalled, selecting the main SQL instance as the database. Problem solved!!! Should have done that from the beginning, it was pretty painless.

20080236-EE-VQP-29 / EE_QW_2_20070628