Hi,
We're doing our own test of the upgrade installers (seems there's alot
of that going on). I have a copy of the prod db and a copy of the prod
app server (vm) in my dev environment, and have updated all the server
references in the new app server vm (i.e., ar.cfg, armonitor.cfg, and
registry, among others). When I got ready to update the server refs in
the db, I couldn't get ARS to start, and there were errors like this in
the arerror.log:
/[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied. (SQL Server 17)//
//SQL database is still not available -- continuing to attempt
connection (ARNOTE 591)//
//The SQL database operation failed. (ARERR 552)/
I was able to log into the db via SQL Management Studio with the ARAdmin
account, and successfully execute a select statement against user_x, so
I contacted the dba who suggested trying to create an ODBC connection
just to test the connection to the db. He said to ensure that the
server name was defined as <myserver,port>, which connected fine. At
that point I went back to the ar.cfg and armonitor for the umpteenth
time, and a colleague suggested adding the port number to the
Sybase-Server-Name parameter, so that the line in the ar.cfg looked like
Sybase-Server-Name: <myserver>,1234
The server started right up, no errors in the error.log, so my question is:
None of the other servers in any of our environments needed the port
added, the old dev server didn't need it (and I'm told that that vm is
turned off), and I don't recall ever seeing a port id in the
Sybase-Server-Name: line.
Any idea, why the ar.cfg needs it now?
Thanks,
rp
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"
