Ahh, thanks for refreshing my failing memory with being able to change the DB User. Removing the Db-password trick works. I had to do it not to long ago when I changed the password but fat fingered it and we had to reset it.
Dave ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza Sent: Tuesday, October 02, 2007 1:34 PM To: [email protected] Subject: Re: ARServer fails to connect to new database server ** At the time of installation on a fresh install ever since version 4.5, you can change the DB User and DB password to use custom instead of defaults. You can change and use custom instead of defaults during that stage of the install Joe D'Souza -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Shellman, David Sent: Tuesday, October 02, 2007 1:28 PM To: [email protected] Subject: Re: ARServer fails to connect to new database server Ben, I never heard of any one else that has gone ahead and set up the system in a manner that doesn't user the aradmin user. Was it ever documented that the folks actually changed the password. That maybe why the Db-password line doesn't show up in the ar.cfg file. Then again you might just be in new territory and need to forge ahead without us. Dave -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Watson, Benjamin A. Sent: Tuesday, October 02, 2007 1:16 PM To: [email protected] Subject: Re: ARServer fails to connect to new database server When we initially created our AR Servers and associated databases, we already had the DB logins created. Therefore, when running the AR System installer, we told it to use a specific SQL login rather than the default. Having done that and never changing the password for these logins in the past, I can assume that's why I don't see the Db-password: line in my ar.cfg file. So it is probably forging ahead using that DB login and whatever password was used at initial installation. Therefore the ar.cfg "hack" won't work. I kind of like Joe's idea. 1. I'll power down the current "new" DB server, then power up the "old" one. 2. Start up Remedy (I know this works as I tested it this morning). 3. Change the password in Remedy (and RECORD it!). 4. Stop Remedy 5. Power down the "old" DB server and power up the "new" one. 6. Change the corresponding SQL login's password in SQL 7. Start Remedy It feels like a dirty hack, but sometimes that is all we have. As a last resort, I think I can copy the entire Database Virtual Machine from one box to the other. But the thought of FTP'ing 170GB over our crappy network is painful. Ben __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
