17
No other query entry found for the remote server %s - site %s. Aborting this site handler, as no remote server responded. Please make sure the remote server is accepting connections.
Communication between an Adaptive Server and another server requires a site handler to manage connections between the servers. When you log on to Server A, and issue a command that necessitates communication with Server B (such as Backup Server for dumps and loads), Server A uses a site handler to open a connection to Server B, sending the query and receiving results from Server B.
When the first attempt to open a site handler connection fails,
Adaptive Server raises Error 7234 ("Failed to
connect to remote server %s %s %s %s %s
for site %s. Trying the next query entry of this server,
if any."). The server then re-tries the connection
using the next entry, if any, in the interfaces file.
Error 7235 is raised after all such connection attempts fail.
Check that the remote server is up and running. If you see the error after issuing a dump command, for example, type the following:
1> exec SYB_BACKUP...sp_who 2> go
If Backup Server is running, you will get a meaningful response to this query.
Verify the remote server’s network name in sysservers:
1> select srvname, srvnetname from master..sysservers 2> go
The remote server’s srvnetname entry must match the name appearing in the interfaces file. (An incorrect srvnetname can prevent the server from reaching the correct remote server.)
When you call Sybase Technical Support, have the information ready that is listed in “Reporting errors”.
All versions
