troubleshooting Question

Could not find ' ' server in sysservers. New server, changed dsn

Avatar of sfghadmin
sfghadminFlag for United States of America asked on
Microsoft SQL Server
16 Comments1 Solution1925 ViewsLast Modified:
I had a db server crash and burn after a bad power event.  I have reinstalled the SQL and the databases (SQL and D3) on a new server and recreated the DSN settings with the new server name.  But when I try to execute a set of commands I get the following error:

Server: Msg 7202, Level 11, State 2, Procedure shipping_data_fill, Line 2
Could not find server 'act1' in sysservers. Execute sp_addlinkedserver to add the server to sysservers.

"act1" is the name of a data source where I changed the connection to reflect the new server name.  The old server was named "ACT1SERVER" so I am guessing that this  refers to the dsn entry rather than the actual server name.

If the DSN is pointing to the new server (which is the local server) why does it still reference the old configuration?  When I check the sysservers table the new server does exist.  If I add in an "act1" entry I don't get the sysserver error but an error that the server does not exist.

Any help??  
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 16 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 16 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros