my SS name changed withou re-install...strange!!

i think a lot of people using SQL Server 2005 Express has already used to use 'sqlcmd -S .\SQLEXPRESS' to login to the SS or using '.\SQLEXPRESS' as the Server Name to login in to the Management. but today i found that i cant login to my SS using '.\SQLEXPRESS', instead i must use the full name of my computer...that quite a long name and it's really inconvenient, could anyone help me out?

i think that the '.' in '.\SQLEXPRESS' is a short-cut for my computer name, but why i cant us it now? i was using it last week!

PS: what is the value of 'log on as' in ther property page of SQL Server 2005? i remember it is 'local service', but my current value is 'network service'

hi,

DavidShen wrote:

i think a lot of people using SQL Server 2005 Express has already used to use 'sqlcmd -S .\SQLEXPRESS' to login to the SS or using '.\SQLEXPRESS' as the Server Name to login in to the Management. but today i found that i cant login to my SS using '.\SQLEXPRESS', instead i must use the full name of my computer...that quite a long name and it's really inconvenient, could anyone help me out?

i think that the '.' in '.\SQLEXPRESS' is a short-cut for my computer name, but why i cant us it now? i was using it last week!

yes... "." or "(Local)" are shorkeys for the actual local computer, and they both should run...

PS: what is the value of 'log on as' in ther property page of SQL Server 2005? i remember it is 'local service', but my current value is 'network service'

these are accounts under which the actual service is run... "network service" is more limited than "local service", but they both are way to powerfull than required... you can have a look and perhaps modify the permissions "required"..

regards

|||

hi,

i can log in with 'localhost\SQLEXPRESS' or '(local)\SQLEXPRESS', but not '.\SQLEXPRESS'...really strange!! maybe there're some reg-key error, but i cant find it!!!

even though, 'localhost' and '(local)' is much shorter and easier to remember than my full computer name, i still wish to use the old way...

pllllllllllzzzzzzzzz help!

my SS name changed withou re-install...strange!!

i think a lot of people using SQL Server 2005 Express has already used to use 'sqlcmd -S .\SQLEXPRESS' to login to the SS or using '.\SQLEXPRESS' as the Server Name to login in to the Management. but today i found that i cant login to my SS using '.\SQLEXPRESS', instead i must use the full name of my computer...that quite a long name and it's really inconvenient, could anyone help me out?

i think that the '.' in '.\SQLEXPRESS' is a short-cut for my computer name, but why i cant us it now? i was using it last week!

PS: what is the value of 'log on as' in ther property page of SQL Server 2005? i remember it is 'local service', but my current value is 'network service'

hi,

DavidShen wrote:

i think a lot of people using SQL Server 2005 Express has already used to use 'sqlcmd -S .\SQLEXPRESS' to login to the SS or using '.\SQLEXPRESS' as the Server Name to login in to the Management. but today i found that i cant login to my SS using '.\SQLEXPRESS', instead i must use the full name of my computer...that quite a long name and it's really inconvenient, could anyone help me out?

i think that the '.' in '.\SQLEXPRESS' is a short-cut for my computer name, but why i cant us it now? i was using it last week!

yes... "." or "(Local)" are shorkeys for the actual local computer, and they both should run...

PS: what is the value of 'log on as' in ther property page of SQL Server 2005? i remember it is 'local service', but my current value is 'network service'

these are accounts under which the actual service is run... "network service" is more limited than "local service", but they both are way to powerfull than required... you can have a look and perhaps modify the permissions "required"..

regards

|||

hi,

i can log in with 'localhost\SQLEXPRESS' or '(local)\SQLEXPRESS', but not '.\SQLEXPRESS'...really strange!! maybe there're some reg-key error, but i cant find it!!!

even though, 'localhost' and '(local)' is much shorter and easier to remember than my full computer name, i still wish to use the old way...

pllllllllllzzzzzzzzz help!

MY SQL server can not connect with my PC

HI

I have a peoblem when I make connect the SQL server with my PC

and this message apper

{

cannot connect to PC.......\SQLEXPRESS

Additional information:

An error has occurred while establishing a connection to the serves . 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 connection.( provider: SQL Network Interface , error:26 - Error locating

Server/ Instance Specified) ( Microsoft SQL Server )

}

can you help me pleas .....

You need to explicitly enable remote connections for SQL Express since they are off by default. You can enable them during install using the DISABLENETWORKPROTOCOLS flag:

(From template.ini)

;--
; The DISABLENETWORKPROTOCOLS switch is used to disable network protocol for SQL Server instance.
; Set DISABLENETWORKPROTOCOLS = 0; for Shared Memory= On, Named Pipe= On, TCP= On
; Set DISABLENETWORKPROTOCOLS = 1; for Shared Memory= On, Named Pipe= Off (Local Only), TCP= Off
; Set DISABLENETWORKPROTOCOLS = 2; for Shared Memory= On, Named Pipe= Off (Local Only), TCP= On

; Note: DISABLENETWORKPROTOCOLS if not specified has the following defaults.
; Default value for SQL Server Express/Evaluation/Developer: DISABLENETWORKPROTOCOLS =1
; Default value for Enterprise/Standard /Workgroup: DISABLENETWORKPROTOCOLS =2

or after install using TSQL or following this blog:

http://support.microsoft.com/kb/914277

Thanks,
Sam Lester (MSFT)

|||

I have been struggling with this for about a week now. For some reason today when I searched I found this thread relatively quickly, and this reply held the solution.

For me, it was the single line of text "Turn on the SQL Server Browser Service." that solved the problem.

SQL Server Browser Service was not running on my server. I had to use the SQL Server Surface Area Configuration Tool to enable and start the SQL Server Browser Service. As soon as that worked, I had no problems.

Thanks.

Jim Sparks