I've learned to watch for the installer to seemingly stall at the point
where it does that restart. If it does stall, I immediately head to the
ar.cfg to see if the DB host values ("Sybase-Server-Name:" or similar?) are
correct and if not, edit them with notepad to get it going again. It is a
bit forgiving since the restart will keep trying to connect to the DB for a
loooooong time (not sure how long or how many attempts), but as soon as I
save the file, it seems to pick it up and continue on the next attempt.The cause could be self-inflicted, as in -- the customer initially gives me DB info without specifying the port and I try 1433 to start, only to have the DBA later say, "Oh yeah, I changed the port to (blah)...". Then it seems the installer config file may on some occasions appear to stubbornly keep referencing the initial incorrect value or something (I'm not sure exactly what/why). I've also been given DB hosts that, during the install, I find they can't be resolved in DNS and I have to edit the hosts file mid-install to get the DB to ping by hostname. I usually do check that before install, but sometimes you work with folks who seem quite competent and the last thing you expect is that they stand up a DB server and for whatever reason, they don't mention that they either forgot or intentionally didn't create a DNS entry for it. Weirder things have happened... Best of luck and I hope you get it figured out! -JDHood On Sat, Jun 7, 2014 at 5:43 PM, Zandi <[email protected]> wrote: > ** > Weird. I have several servers in one case I could make it work with. > Host name,700 > In the ar.conf. Never seen that one before. Lol > But the ones that were patched and then unmatched we cannot get to work > > Sent from my iPhone > > On Jun 7, 2014, at 3:00 PM, JD Hood <[email protected]> wrote: > > ** > Have you tried editing the ar.cfg manually? I've edited it in the middle > of an active install to get around this. > > Good Luck!! > -JDHood > > > On Sat, Jun 7, 2014 at 11:22 AM, patrick zandi <[email protected]> > wrote: > >> ** >> ENV 2008 r2 64 bit server >> Server is VM with ARS 8.1.01.001 actively running fine against a MSSQL >> cluster. >> >> All of a sudden all systems stopped working >> >> so we tried a fresh install, and now (after if was working for months) a >> bug/error where during the install it creates the instance on the cluster >> using a unique port 700 lets say, and then it restarts the ARS application >> and starts connecting to 1433 ? >> What in the World --- support is almost non resistant. I opened a >> Critical ticket but is is being thrown under the bus. >> >> Any Idea's >> >> Question: BMC Does not even reference using the mssql client... and is >> there a way to tell the application to use the client, just wondering. >> >> -- >> Patrick Zandi >> _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
