Hi all;

on our Solaris machine, running ASE 12.0.0.4, I encounter the
following problem:
On an irregualr basis, dumps or "exec SYB_BACKUP...sp_who" results in

Can't open a connection to site 'SYB_BACKUP'. See the error log file
in the SQL Server boot directory.

The log file contains:

****

1:00000:00012:2004/05/26 10:41:30.27 kernel nconnect: t_open, System
error
00:00000:00012:2004/05/26 10:41:30.32 server Failed to connect to
remote server bs_server tli ether servername 8001 for site SYB_BACKUP.
Trying the next query entry of this server, if any.
00:00000:00012:2004/05/26 10:41:30.32 server Error: 7235, Severity:
17, State: 0
00:00000:00012:2004/05/26 10:41:30.32 server No other query entry
found for the remote server bs_server - site SYB_BACKUP. Aborting this
site handler, as no remote server responded. Please make sure the
remote server is accepting connections.

****

sysservers shows the correct entry for the SYB_BACKUP server, Port and
IP in interfaces file are correct and the host (and Port) are
pingable.

If anyone has seen this problem before and can help resolving it,
would be very much appreciated.

Carsten

Carsten wrote:
The only times (that I can recall) I've run into this was when the
backupserver wasn't running.

You don't mention if you ran 'showserver' ... do/did you see your
backupserver in the list of processes?

If not, start the backupserver.

If so, have you tried bouncing the backupserver?

--
Mark A. Parsons

Iron Horse, Inc.
iron_horse (AT) NOSPAM (DOT) compuserve.com

Yes, sorry. Forgot to mention it. Backup server is of course up and
running and I can connect to it using isql.
I also tried to dump to this backup server remotely from another
dataserver, with success. Vice versa, dumping to another backup
server, from the initial dataserver results in the same problem.
Together with our Unix team, we think we found the problem.
There was an entry in /etc/hosts called "inadder-any", which is
apparently needed for ASE 12.5 if you point to the localhost (0.0.0.0)
in the interfaces file. After removing it, the connection to
SYB_BACKUP is fine.

Nevertheless, thanks for your help.
Carsten

"Mark A. Parsons" <iron_horse (AT) NOSPAM (DOT) compuserve.com> wrote