Hello Listers, ARS 8.1.00 MS SQL Server 2008 R2 (remote) OS Windows Enterprise 2003
I am having the worst time trying to get a bare bones Remedy ARSystem server installed. I have admin rights for the user running the setup.exe file. That windows user also is the db_owner of the ARSystem_test database which was created during the installation process. It takes forever to complete, the starting services time is the longest. When it does complete the install is flagged as failed because the ARSystem would not start in a "timely fashion". I have a ticket open with BMC Support and they have given me some things to check that was pulled out of the installation logs. The settings that they questioned were supposedly confirmed by the DBA but all I can tell is that the MS SQL Server DB is "owned" by the windows account. Because of all of these oddities I dare not touch my production system (7.6.03) or my sandbox (7.6.04 SP3) for fear of breaking them too. They were upgraded from earlier versions and have a legacy sql account as the owner but the services run on the ARS machine with the same domain account as the one I'm using for the test. System policy does not allow for giving the sa account out and local SQL accounts are discouraged so I am using a windows domain account to run the install, own the DB and run the services on the ARSystem server machine. Has anyone seen any gotchas like file system permission restrictions on a windows server or some other idiosyncrasy that could prevent the installation from completing successfully? Thank you, --- John J. Reiser Remedy Developer/Administrator Senior Software Development Analyst Lockheed Martin - MS2 The star that burns twice as bright burns half as long. Pay close attention and be illuminated by its brilliance. - paraphrased by me _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
