humer2000
asked on
execute sp_addlinkedserver to add the server to sysservers after renaming mu computer
Hi experts,
I have a server with win 2003 enterprise and sql 2005
an ecommerce site is hosted on this server
I have changed my computer name due to netbios issue, and after restarting my server, the web application running on my server does not work proprely
when i intend to write in to the database i get an error
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not find server 'EXPERTHOST-025' in sysservers. Execute sp_addlinkedserver to add the server to sysservers.
Please anyon,e has a fix
thanks
I have a server with win 2003 enterprise and sql 2005
an ecommerce site is hosted on this server
I have changed my computer name due to netbios issue, and after restarting my server, the web application running on my server does not work proprely
when i intend to write in to the database i get an error
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not find server 'EXPERTHOST-025' in sysservers. Execute sp_addlinkedserver to add the server to sysservers.
Please anyon,e has a fix
thanks
You can probably edit it in SSMS, go into Server objects and Linked Servers
sp_dropserver <old_name\instancename>
GO
sp_addserver <new_name\instancename>, local
GO
GO
sp_addserver <new_name\instancename>, local
GO
ASKER
my last instance name was the default instance
so what should i put in
sp_dropserver <old_name\instancename>
GO
sp_addserver <new_name\instancename>, local
GO
so what should i put in
sp_dropserver <old_name\instancename>
GO
sp_addserver <new_name\instancename>, local
GO
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
now i get this error
Server 'EXPERTHOST-025' is not configured for DATA ACCESS
Server 'EXPERTHOST-025' is not configured for DATA ACCESS
Should not you create a new question thread for this? :)
ASKER
rebooting the server corrected the error
thx a lot
thx a lot