The configuration of the AdminConnection\TCP protocol in the SQL instance SQLEXPRESS is not vali
Hello,
I am getting the following warning in the Application Event Log:
The configuration of the AdminConnection\TCP protocol in the SQL instance SQLEXPRESS is not valid.
The warning is logged by the SQLBrowser service.
This is happening on Windows 2003 server with SQL Server Express 2005. On the same machine SQL Server 2000 is installed.
I am currently unable to connect from remote clients to the instance of SQL Express and I believe it has to do with this warning (I've tried all the usual remote connection troubleshooting without success - enabled protocols, SQL Browser Service running, there is no firewall on the server, I disabled firewall on the client when trying to connect).
Does anyone know how to resolve this issue?
If you need additional information please let me know.
I guess you have configured these two instances to use the same port. Thats nor possible, so better change the port with the configuration utilities to a different than the SQL Server 2k (which is by default 1433)
HTH, Jens Suessmeyer.
We are getting the same error on an SBS 2003 server with SQLExpress 2005 in stalled but it does not have SQL Server 2000 installed.
We are also having performance problems with SQL Express 2005 but I have looked at the performance monitoring and there isn't anything obvious taking up too much ram or CPU time etc..
Any troubleshooting ideas would be great, Thanks
I am seeing same warning in the Application event log on my Windows XP Professional machine. I have only one instance of SQL Server on my machine: SQL Server 2005 Express Edition and I have never had any instance of SQL Server 2000.
Here's a recap of the details:
Event Type: Warning
Event Source: SQLBrowser
Event Category: None
Event ID: 3
Date: 03/04/2006
Time: 20:58:29
User: N/A
Computer: xxxxxx
Description:
The configuration of the AdminConnection\TCP protocol in the SQL instance SQLEXPRESS is not valid.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
At the current time, there is no additional information at the Help & Support Centre (click the referenced link "For more information...").
Thank you Jens for pointing me to some useful information. Based on your comments and the explanation given in that blog I went back & reviewed the configuration on my machine.
Summary: I did find/correct some misconfiguration, but it DID NOT prove to be the culprit.
Details as follows:
Going into SQL Server Configuration Manager, and looking at the Protocols for SQLEXPRESS under SQL Server 2005 Network Configuration, I did remind myself that I had disabled Named Pipes recently, leaving the following protocols enabled/disabled as follows:
- Shared Memory: Enabled
- Named Pipes: Disabled
- TCP/IP: Enabled
- VIA: Disabled
Looking then at the Client Protocols under SQL Native Client Configuration heading, I did find what I thought was the culprit - that Named Pipes was enabled here (client-side), where it was not enabled on the server-side. So I disabled Named Pipes here, leaving the protocols enabled/disabled as follows:
Protocol Name | Order | Enabled/Disabled
- Shared Memory | 1 | Enabled
- TCP/IP | 2 | Enabled
- Named Pipes | - | Disabled
- VIA | - | Disabled
After making this change, I shutdown/restart SQL Server 2005 Express and the SQL Server Browser in the following order:
- Stop SQL Server Express (service name "MSSQL$SQLEXPRESS")
- Stop SQL Server Browser (service name "SQLBrowser")
- Restart SQL Server Express
- Restart SQL Server Browser
Having done all this I looked in the Application event log. The warning message was still there (and yes, I was looking at the events associated with the just-completed restart).
Questions:
Maybe I got off on the wrong track here - I was thinking that SQL Server Browser connected to SQL Server using the SQL Native Client / SQL Native Client's protocol. Is this not the case? Does SQL Browser have its own configuration settings (configured somewhere else?)
Did you get your problem fixed. I am getting the same error and am curious to find a solution.
Any input will be highly appreciated.
Thanks
Hello,
We are having the same issue with a Windows 2003 SBS SP1 server with SQL Express. Has anyone found a resolution as of yet?
Thanks
I have the same issue on XP Pro SP2. I saw this error in the logs this morning after some trouble making a remote connection from our production SQL 2005 server when installing on the client yesterday.
Here was our connection issue.
Our standard remote install is still running MSDE with the instance named store1, store2, etc.
As we proceed in moving to SQL 2005 we have been using rather default installs of SQL express at the store level. After install we config to accept local and remote connections on TCP/IP.
We couldn't connect to this one and found that it had come up named rather oddly. Rather than the instance being storexxx it was showing as storexxx\sqlexpress.
After goofing about a bit we enabled the browser service on the client (disabled by default). management studio THEN connected and after that it didn't seem to require the browser service to be running.
In management studio it lists as "storexxx(storexxx\sqlexpress)" instead of the standard "storexxx".
Anyone ideas?
SQL Server can be installed multiple times on the same machine -- these are called "instances". The only time SQL Server shows up without an instance name and just a server name (ie. storexxx vs. storexxx\instancename) is when you install SQL Server as a default instance. This is, by the way, the default installation option. -- Brian
Oh, I forgot to mention I have the same "AdminConnection\TCP protocol..." warning in my EventLog. It's driving me nuts. If anyone solves this, please post. I reinstalled SQL Server SP1 but that didn't fix the issue. Is Microsoft monitoring this post? MS, can you guys please explain because the ports are configured properly and there is no port overlap between instances. Thanks! -- Brian
Hmmm...what it seems to be doing in a default instance install is naming it "storexxx\sqlexpress". This isn't a problem in itself but is inconsistant with existing MSDE locations which show up as "storexxx". I'm only concerned about consistancy for scripting, maintenance, etc...
Is there an easy way of changing the instance name?
We found this in the SQL Server Logs...
2006-10-19 09:39:00.59 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
... which implies that the SQL Browser service is picking up that a particular feature is deliberately disabled in SQL Express. Hence it looks as if it's not a problem, but we won't be able to make the eventlog messages go away.
David.
http://web.coop
Has anyone figured this out yet? I just rebuilt my PC and I too have this issue. I have enabled TCP/IP and done what I can per the articles I've read but this issue still plagues me. Please advise!!
I solved this problem, and this is what I did to make message(s) stop. I first when into SQL Manager and for both Client and Server Connections I enable TCP. After that I uninsatlled SQL Server 2000. (I had SQL Server2000 and SQL Server2005 installed.) After uninstall I rebooted, no more messages.
