Renamed instance of sql server using sp_addserver, but not working [sql2005]
Hi,
I have a server i did the following to.
1. dropped server instance name
2. added new instance name
3. rebooted server.
4. ran help server and got result shown below.
However when I open MStudio and try to connect to new server name "argus\attis" i get error message :
"
An error has occurred while establishing a connection to the server. 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 connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (.Net SqlClient Data Provider)"
I can connect via 'argus\argus' however.
What am I missing ?
Also, I did not get any error messages when i used dropserver and addserver to do the instance name change.
Mo
I have a server i did the following to.
1. dropped server instance name
2. added new instance name
3. rebooted server.
4. ran help server and got result shown below.
However when I open MStudio and try to connect to new server name "argus\attis" i get error message :
"
An error has occurred while establishing a connection to the server. 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 connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (.Net SqlClient Data Provider)"
I can connect via 'argus\argus' however.
What am I missing ?
Also, I did not get any error messages when i used dropserver and addserver to do the instance name change.
Mo
sp_helpserver select @@servername =
Name Network name status ID Collation
argus\attis argus\attis rpc,rpc out,use remote collation 0 NULL
bull_rider
Can you check if you have enabled named pipes plus tcp ip in sql server surface area configuration?
ASKER
yes this is an old server and had been working before
so yes
tcp, named pipes - are all on
listening on default 1433 port for tcp
tcp is order 1 in client protocols configuration
so yes
tcp, named pipes - are all on
listening on default 1433 port for tcp
tcp is order 1 in client protocols configuration
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hmmm
I have gone to SAC - and checked the article youve linked to.
Server as already set to local and remote connections and using both tcp and named pipes
SQL Server browser was already running.
Firewall exceptions - I am using a RDP session to the server - log in via a domain admin account on this server - and try to connect that way - so no firewall issues as on the server itself.
All of the above done already and no changes needed to be made by me ..
so unfortunately it didnt fix the problem
Im thinking do i need to un-install sql server and re-install from scratch...?
I have gone to SAC - and checked the article youve linked to.
Server as already set to local and remote connections and using both tcp and named pipes
SQL Server browser was already running.
Firewall exceptions - I am using a RDP session to the server - log in via a domain admin account on this server - and try to connect that way - so no firewall issues as on the server itself.
All of the above done already and no changes needed to be made by me ..
so unfortunately it didnt fix the problem
Im thinking do i need to un-install sql server and re-install from scratch...?
:( Oops I am afraid that is the only option left out which I can see.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.