January 28, 2008 at 10:23 pm
We performed an upgrade over a month ago and everything has been working fine. now a person in accounting is trying to run a custom report that hit the server that died. The programmer says it will be a few days until he can get back to us and modify the code. in the meantime i thought I would just create an alias to the new server using the old name.
if i am on the server the alias works. if I am not it doesn't:
HResult 0xFFFFFFFF, Level 16, State 1
SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establi
shing a connection to the server. When connecting to SQL Server 2005, this failu
re may be caused by the fact that under the default settings SQL Server does not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
remote connections are allowed...
January 29, 2008 at 4:45 am
you cannot connect remotly using alias name.you can connect to server using instance name .
January 30, 2008 at 1:22 am
There are a few ways to skin this cat.
If the client has SQL Server Tools installed, add the alias on the client.
Add an entry for the old host/server name with the new server's IP address to the users hosts file.
Have your DNS admins update DNS to point the old host name to the new servers IP address.
Joe
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply