Did you check ownership of the ARSystem database? -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Watson, Benjamin A. Sent: Monday, October 01, 2007 4:29 PM To: arslist@ARSLIST.ORG Subject: ARServer fails to connect to new database server
** List, Once upon a time ago... We had an ARSystem v 7.01 Server (with ITSM 6 apps) running against an MSSQL 2000 database server (all boxes are Windows 2003 Server Standard). This all worked just fine. We then upgraded our SQL to MSSQL 2005. Again, all works just fine. Now we need to move the database server to a different physical box. Ok, let me clear up some stuff first. Actually, we're moving the database server virtual machine from one VMWare ESX server to another VMWare ESX server. We're not actually moving the Virtual Machine (although in hind-sight, this might have been easier as I've done this sort of thing in the past). So, I take note of some things on the current database server, then power it down. I create a new virtual machine on the "new" VMWare server. I install SQL2005, and restore all of the databases (ensure to create the appropriate users and setup default databases and owners using stored procedures). I ensure that the computer name is the same as was previously. Therefore, everything about this new database server is identical to the previous one (that is currently shut down), except that it is not on the domain. I shut down our application server while this was all going on. I power up the application server (which hasn't had any changes since shut down), and edit the Windows hosts file to point the hostname of the original database server to the new IP address of the new one. So now I startup the Remedy services on the application server and see the following in the error logs: Failure during SQL operation to the database (ARERR 552) Login failed for user 'mscBase' (SQL Server 18456) 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) Login failed for user 'mscBase' (SQL Server 18456) Cannot initialize contact with SQL database (ARERR 551) Stop Server AR System server terminated - fatal error encountered (ARNOTE 21) The first thing I check is connectivity from the application server to the database. Since I've modified the host file, the app server can ping the db server just fine. Next, I check to see that I can log into SQL from the application server. I notice that all I have are the SQL 2000 client tools. Guess that is something we forgot to upgrade (but again, it was all working before). So I install the SQL 2005 client tools. After the installation, I launch the SQL client and connect to the database as the user annotated in the error logs just fine. Now, we're grasping at straws. My co-worker thought we should try to uninstall/reinstall ARServer <cringe>. We open up Windows Control Panel --> Add/Remove Programs, and get errors on uninstalling ARSystem (it won't let us). I'm at the point now where I'm looking at powering down the application server and building another one (since it too is a virtual machine). I'd rather not invest all that time in watching progress bars, so is there anything else you can think of for me to check on either the app or db servers as to why ARSystem can't connect to the database? Thanks, Ben __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
