In your ar.cfg file is the correct database SID showing. I recently found out that when the db created it he gave it the same name as the production database so on dev he gave it an alias. Worked fine on 5.1.2 but on 7.0.1P1it wanted the actual db name. Once correct in the ar.cfg file it came up fine. This was Oracle 10g but maybe SQL has the same issue. Maybe the way 7.0.1P1 connects is an issue. Oh and by the way, while on v7.0 no patch it connected just fine.
I just loaded this patch a week ago and have nothing but little glitches all over the place. We're doing the production server on 4/14 and I'm nervous about it. I've never seen so many issues after an upgrade. Susan On 4/3/07, ARSList <[EMAIL PROTECTED]> wrote:
** Can you connect to the DB via MS SQL Enterprise or QUERY utilities under the ARAdmin and appropriate password? ------------------------------ *From:* Action Request System discussion list(ARSList) [mailto: [EMAIL PROTECTED] *On Behalf Of *Dunn, Eric *Sent:* Tuesday, April 03, 2007 11:52 AM *To:* [email protected] *Subject:* Re: Upgrade Failure - 5.01.02 to 6.03 No, I did not change the password. I went ahead and retyped in the password to make sure with no luck. *Eric W Dunn* Programmer Analyst III - Remedy/Collaboration (281)465-1265 ------------------------------ *From:* Action Request System discussion list(ARSList) [mailto: [EMAIL PROTECTED] *On Behalf Of *L. J. Head *Sent:* Tuesday, April 03, 2007 12:10 PM *To:* [email protected] *Subject:* Re: Upgrade Failure - 5.01.02 to 6.03 ** did you set a password other than ar#admin# for your DB? Change the ARAdmin password in the DB to ar#admin# and see if Remedy can connect ------------------------------ *From:* Action Request System discussion list(ARSList) [mailto: [EMAIL PROTECTED] *On Behalf Of *Dunn, Eric *Sent:* Tuesday, April 03, 2007 10:39 AM *To:* [email protected] *Subject:* Upgrade Failure - 5.01.02 to 6.03 ** I have just completed a dry run on my development/test server of the server upgrade 5.01.02 to 6.03. I did not receive any error messages during the upgrade and the server was rebooted after the upgrade. I am running Windows 2003 server with SQL 2005. I am not able to connect to the server via the admin tool or the client tool. ARERR [90] Cannot establish a network connection to the AR System server What did I forget? Tue Apr 03 09:47:28 2007 390600 : Failure while trying to connect to the SQL database. Please ensure the SQL database is running or contact the Database Administrator for help (ARERR 550) Tue Apr 03 09:47:28 2007 Cannot open database "ARSystem" requested by the login. The login failed. (SQL Server 4060) Are the errors in the error log. *Eric W. Dunn* Programmer Analyst III - Remedy/Collaboration McLeod USA, Inc. - Network Engineering 8665 New Trails Dr. The Woodlands, TX 77381 (281)465-1265 (281)465-1951 *fax* *NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail.* __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ *NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail.* __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
