Now trying a fresh install of ARSystem on a new app server which VM. Also, installs were successful but unable to start the ARSystem Server and getting login failures in arerror.log.
Please advise. On Oct 22, 10:49 am, "Kiran, Ravi" <[email protected]> wrote: > Hello Basil, > We had no plan, at least one that is working. > > Our 32Bit SQL server is "test" bed where all the initial work was done to set > Remedy up. > > It is Production ready, so the goal is simply to MOVE the DB to the ^$BIT > Production SQL server. > > We thought it would be as easy as backup, restore and change ar.cfg We must > be missing a set somewhere. > > Also, got an update from the BMC Support, > Here is what BMC person replies: > > As per your query, > > You need to use 32 bit Database client in order to connect with 64bit > database. > > What do you think now ? > > Thanks, > Raj > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Webster, Basil > Sent: Thursday, October 22, 2009 7:42 AM > To: [email protected] > Subject: Re: Where to make changes for DOMAIN change ? > > Well it is obvious that the app cannot connect to the DB. > > Are there any other applications in the environment with a similar config, ie > split app and db, and are they working? Just trying to eliminate a network > issue. Make sure that the SQL ports are open 1433 and 1434. Theoretically you > only need the TCP port 1433 but check both. > > Not sure if I quite understood your install plan that you followed, but this > is what I would have done:- > > 1) On db box, install and configure SQL. > 2) On app box, do fresh AR Server install to the db. Remember that you will > need to select a remote database. (If at install time a connection to your db > server cannot be made then either your servers have a problem or there is a > network problem.) > 3) Stop AR services on the app box, perform SQL restore and run scripts, > start AR services. > > This has worked for me every time, and I have done numerous installations > like this. As I said previously, if the AR install cannot connect to the db, > I load the SQL client tools (not sure if that just sets up the servers ports) > and then all is fine. Do you have an entry in your host file (on the app box) > for the FQDN and simple name of the server, eg servername.domain.com and > servername. > > Why are you trying to load the 32bit client tools onto a 64bit installation? > > I am 100% sure that the restoring of a db from a 32bit into a 64 will not > cause a problem. If SQL accepts the db, then there is no problem. > > Kind Regards, > Basil Webster > Remedy Developer > > Siemens Southern Africa > IT Solutions and Services (Pty) Ltd > Infrastructure Operations > 300 Janadel Avenue, Halfway House, 1685 > T : +27 11 652 7523 > F : +27 86 506 2883 > M : +27 82 452 9389 > [email protected] > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Kiran, Ravi > Sent: Thursday, October 22, 2009 1:02 PM > To: [email protected] > Subject: Re: Where to make changes for DOMAIN change ? > > -----Original Message----- > From: Kiran, Ravi > Sent: Thursday, October 22, 2009 5:00 AM > To: '[email protected]' > Subject: RE: Where to make changes for DOMAIN change ? > > Hello Basil, > Attached is the compatibility matrix and the error log. > Here's what the error log looks like. > > Thu Oct 22 03:33:24 2009 PreloadTableThread : AR System server terminated -- > fatal error encountered (ARNOTE 21) Thu Oct 22 03:35:16 2009 : Action Request > System(R) Server Version 7.5.00 Patch 002 200906100308 > (c) Copyright 1991-2009 BMC Software, Inc. > Thu Oct 22 03:36:58 2009 PreloadTableThread : Failure during SQL operation > to the database (ARERR 552) > Thu Oct 22 03:36:58 2009 [DBNETLIB][ConnectionRead (recv()).]General > network error. Check your network documentation. (SQL Server 11) > Thu Oct 22 03:37:13 2009 PreloadTableThread : SQL database is now available > (ARNOTE 592) Thu Oct 22 03:37:13 2009 PreloadTableThread : SQL database is > not available -- will retry connection (ARNOTE 590) > Thu Oct 22 03:37:13 2009 PreloadTablesThread > Thu Oct 22 03:37:13 2009 PreloadTableThread : AR System server terminated -- > fatal error encountered (ARNOTE 21) > > Our main concern is : > > Originally, the DB was installed to a Win 2003 STD SP2 32Bit. > When Remedy was installed the DB was created on that server. > > Trying to move the DB to new Win 2003 R2 ENT x64 SP2 > > The Application server was and still is Win 2003 R2 ENT x64 SP2 > > The SQL Management Studio was not installed. > We are experiencing issues trying to load the 32bit SQL Client and the 32Bit > Management studio. > > Thanks, > Raj > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Webster, Basil > Sent: Thursday, October 22, 2009 3:57 AM > To: [email protected] > Subject: Re: Where to make changes for DOMAIN change ? > > Hi Raj, > > Yes, I mean the SQL Management Studio in the case 2005. In 2000 is was called > Enterprise Manager. > > We are running our application machine as a 32bit installation as a VM. Our > database is a 64bit SQL 2005 installation. We don't have any issues. If you > supply the error you are receiving in the error log file. To confirm this, > please get the compatibility matrix off of the support site as this will > provide this detail. At present I am not able to access the site otherwise I > would have checked for you. > > The application password would not stop you from starting the services. I > would do the following check:- > > 1) Can you log into the database with the management studio, as user aradmin > with the password you used when doing the install. If you can't then there is > your problem. > 2) Hopefully you have a standard database password, if you have deviated, > change it to the same as your "old" environment and then copy the line > containing this from your old ar.cfg to the new ar.cfg. First change the > aradmin password via the SQL management Studio. > 3) If (1) is not the problem, would you consider running the scripts I > provided and would you install the management studio on the app server? > 4) When you did the installation, did the app server successfully create the > initial database on the DB server? What I am trying to understand is your > install process, if you did a fresh install and then did a restore or did you > restore and then try do the installation. > > Kind Regards, > Basil Webster > Remedy Developer > > Siemens Southern Africa > IT Solutions and Services (Pty) Ltd > Infrastructure Operations > 300 Janadel Avenue, Halfway House, 1685 > T : +27 11 652 7523 > F : +27 86 506 2883 > M : +27 82 452 9389 > [email protected] > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of Raj > Sent: Thursday, October 22, 2009 9:34 AM > To: [email protected] > Subject: Re: Where to make changes for DOMAIN change ? > > Hello Basil, > May I know which client tools are you talking about ? > Database is MS SQL Server 2005 , are you talking about MS SQL Management > Studio ? > > Thanks, > Ravi > > On Oct 21, 11:23 pm, "Webster, Basil" <[email protected]> > wrote: > > Hi Raj, > > > What is the error you get in the arerror log file. Is it something > > like "unable to contact the database"? > > > We use SQL and I have often found that you need to load the SQL client > > tools on the app server before the AR Server will connect, even though > > you can ping or tracert to the db server. Have you tried adding host > > file entries (I assume you are on a windows environment). If you are > > using SQL, there are some scripts \ commands that you might look at > > running especially after restoring a db that was owned by another > > server. Confirm that your ARAdmin db name and password are the same as > > the previous server (in the ar.cfg this is encrypted). > > > If you are using SQL, try running these (first ensure that there are > > no other connections to the db because you must have exclusive access > > and make sure that you run it on the correct database. It goes without > > saying, you must have a backup to fall back on if required):- > > > exec sp_changedbowner 'sa' > > exec sp_dropuser 'ARAdmin' > > exec sp_changedbowner 'ARAdmin' > > exec sp_defaultdb 'ARAdmin', 'ARSystem' > > update field_table set tfServer = '@' > > update actlink_open set serverName = '@' where not (serverName = '@') > > update char_menu_query set server = '@' > > update char_menu_sql set server = '@' > > > Hope this helps, or at least gives you some ideas. > > > Kind Regards, > > Basil Webster > > Remedy Developer > > > Siemens Southern Africa > > IT Solutions and Services (Pty) Ltd > > Infrastructure Operations > > 300 Janadel Avenue, Halfway House, 1685 T : +27 11 652 7523 F : +27 86 > > 506 2883 M : +27 82 452 9389 > > [email protected] > > > -----Original Message----- > > From: Action Request System discussion list(ARSList) > > [mailto:[email protected]] On Behalf Of Raj > > Sent: Thursday, October 22, 2009 4:22 AM > > To: [email protected] > > Subject: Where to make changes for DOMAIN change ? > > > Hello All, > > > Here is how our current environment set up. > > > Remedy Applications Server > > > Remedy Web Server > > > Remedy Database Server. > > > All these are seperate boxes directed to common domain. > > > But now, we are going through server consolidation and domain change > > and all these boxes will direct to new domain. > > > So where in the Remedy files I need to make adequate changes. > > > I know, I should make the changes accordingly in ar.cfg file. > > > Where else should I be making appropriate changes. > > > After making the necessary changed on ar.cfg file after domain change > > of production database( moved the database from one server to other > > server on different domain). > > > Am trying to restart the ARSystem Server but it fails every time. > > > Is there anywhere else ,I need to make change or just the change in > > ar.cfg is enough ? > > > Please advise, > > > Thanks, > > > Raj > > > ______________________________________________________________________ > > __ > > _______ > > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.orgPlatinum > > Sponsor:[email protected] ARSlist: "Where the Answers Are" > > ______________________________________________________________________ > > __________________ > > > Disclaimer and Confidentiality Note > > ... > > read more » _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
