Error 7202
Contents |
SERVER - Fix Error 7202 Could not find server in sys.servers. Verify that the correct server name was specified August 26, 2014Pinal DaveSQL, SQL Server, SQL Tips msg 7202, level 11, state 2, line 1 and Tricks8 commentsThe other day I received following error when
Could Not Find Server In Sysservers
I tried to restore a database from one server to another server.Msg 7202, Level 11, execute the stored procedure sp_addlinkedserver to add the server to sys servers State 2, Line 1 Could not find server ‘MyLinkedServer' in sys.servers. Verify that the correct server name was specified.Well, this is quite a popular error one
Could Not Find Server In Sys.servers Linked Server
receive when they attempt to restore database containing references of the linked server. The solution is to create a link server and restore database. Here is the quick script which can fix your error.EXEC sp_addlinkedserver @server='MyLinkedServer'
EXEC sp_addlinkedsrvlogin 'MyLinkedServer', 'false', error 7202 spss NULL, 'MyUserName', 'MyPassword'
Well, that's it. Sometimes the solution is much simpler, even though the original problem looks complicated.Reference: Pinal Dave (http://blog.SQLAuthority.com) Tags: SQL Error Messages324Related Articles SQL SERVER - The server network address "TCP://SQLServer:5023" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational. (Microsoft SQL Server, Error: 1418) January 11, 2010Pinal Dave SQL SERVER - Fix : ERROR : Msg 1033, Level 15, State 1 The ORDER BY clause is invalid in views, inline functions, derived tables, subqueries, and common table expressions, unless TOP or FOR XML is also specified. August 12, 2007Pinal Dave SQL SERVER – Network Name resource fails to come online in a Windows Server 2008 R2 Failover Cluster April 13, 2016Pinal Dave 8 comments. Leave new marcel roos March 7, 2015 1:12 pmFix SQL error=7202Reply Pinal Dave
remote query to an Oracle server sql add linked server using an OPENQUERY that makes reference to a linked server, but the developer received the following error http://blog.sqlauthority.com/2014/08/26/sql-server-fix-error-7202-could-not-find-server-in-sys-servers-verify-that-the-correct-server-name-was-specified/ when he executed the OPENQUERY: Error: 7202, Severity: 11, State: 2 Could not find server 'XXXX' in sys.servers. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlinkedserver to http://www.sqlcoffee.com/Troubleshooting134.htm add the server to sys.servers. Cause The linked server existed on the SQL Server instance of the production environment but didn't exist on the SQL Server instance assigned to the test environment. Solution The solution was to configure the Oracle client on the SQL Server instance of the test environment to be able to connect to the Oracle database server, then configure an ODBC data source, and finally use the ODBC DSN to create the linked server with the same name used in the production environment. .Send mail to webmaster@sqlcoffee.com with questions or comments about this web site.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: st: Stata 13 Compatibility From http://www.stata.com/statalist/archive/2013-09/msg00745.html Marta García-Granero