October 27, 2009 at 8:40 am
Hi,
Today I am confronted with a (to me) peculiar situation:
A developer has installed SQL Server Express 2008 on a virtual server. He could not connect from a remote desktop to the named instance(servername\sqlexpress), but he CAN connect to a 'default' instance: servername.
I started to look into this, haven't done anything with the Express Editions. I logged in to the server, wher the instance should reside. I checked services and sauw an SQL Server instance running named SQLEXPRESS. Browser and SQLagent where running as well. I opened SSMS for Express and tried to connect to the named instance: succesful! Then I logged in on the PC which is used to connect to this instance and tried to connect to the NAMED instance servername\SQLExpress. Nothing.
I pinged to the server and this was succesfull. Tried connecting again, nada. I then tried to connect to a default instance: servername, and lo! I had a connection. I was flabbergasted: I switched back to the server and saw the NAMED instance in SSMS, while on the PC I was connected to a DEFAULT instance. I checked services again, but no, only a NAMED instance service was running for SQL Server.
On the server where I had a connection to the NAMED instance I tried to connect to a DEFAULT instance and lo! I created a succesfull connection to the DEFAULT instance as well. So I had 2 instances running, it seemed. I checked SQLServer properties and Object properties, and they seem similar. Databasefiles are in the same DIR, same logins, etc. Next I checked configurations with Surface Area tool and see only the SQLEXPRESS settings, which are correct for remote connections via TCP and Named Pipes.
What am I missing here? On the (virtual) server I can connect to a Default and a Named instance, from a remote desktop I can only connect to a Default instance. Is the default instance actually the named instance? The developers are, understandingly, a bit worried: they don't know if what they see on Default is The Truth.
Greetz,
Hans Brouwer
October 27, 2009 at 3:04 pm
I started to look into this, haven't done anything with the Express Editions. I logged in to the server, wher the instance should reside. I checked services and sauw an SQL Server instance running named SQLEXPRESS. Browser and SQLagent where running as well. I opened SSMS for Express and tried to connect to the named instance: succesful! Then I logged in on the PC which is used to connect to this instance and tried to connect to the NAMED instance servername\SQLExpress. Nothing.
I don't understand what you are saying SQL Server Express does not come with the Agent and even in the developer edition the Agent installs disabled so you need to go into configuration manager in 2008 and SAC for 2005 and enable remote connections and both TCP/IP and Named Pipes, you also need to tell the developer to install a local Express instance with Management Studio and configure it so the person can register the remote Express.
Kind regards,
Gift Peddie
October 28, 2009 at 3:31 am
You are right, not the Agent, but VSS Writer and Actiove Directory helper. My issue is with connection though.
Any1?
Greetz,
Hans Brouwer
October 29, 2009 at 7:28 am
Have you tried connecting using the port number - MSSQLSERVER\NamedInstance,port number.
October 30, 2009 at 12:30 pm
SQLEXPRESS is the default instance name for Sql Express, just as MSSQLServer is the default instance name for Standard.
See
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply