Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-02-27 : 07:30:53
|
| Jaseem writes "We are currently using SQL server 6.5 with Service Pack 3 (yes, you read correctly), and are setting up database log shipping between the production and Disaster Recovery site servers. Both sets of servers are set up identically and the process works on one pair of servers. However, it doesn't work on the other servers where the following error message is returned if I try to run a remote process on the DR servers from the ISQL session in the production servers:Msg 18481, Level 16, State 2Unable to connect to site 'drservername' because it is unavailable or does not exist.(where I have substituted the real remote server name with 'drservername').On the production servers, I have set up the remote servers as follows:EXEC sp_addserver DR_server_nameEXEC sp_addremotelogin DR_server_name, 'sa'EXEC sp_remoteoption DR_server_name, sa, NULL, trusted, TRUELikewise I have set up the production server on the DR server.I am very confused as to why I keep getting this error (18481) as the same setup is working on one pair of servers.The following article is all that I found on this subject (MS TechNet 163452) but it doesn't explain why I keep getting the problem. Any help would be greatly appreciated.Jaseem." |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-02-27 : 12:38:10
|
| First of all, you need to apply service pack 5a for SQL Server 6.5. That service pack has lots of fixes in it. Second, do you get this error all of the time when you try to run a remote process on the DR server? Or do you only get it occassionally? If you get it every time, then there is some configuration problem. Can these servers communicate via IP (can they ping each other)? Are they listening on the default port? According to the article that you mentioned, you need to run SQL Trace and trap those errors to determine exactly what is occurring. |
 |
|
|
|
|
|
|
|
Unable to connect to remote server