Shrestha, I've seen this before, and have posted to the list twice the resolution, and it has helped other people.
Unfortunately, I do not have my archive of emails right now to pull up, but if you search for posts from me, you'll find one that discusses this. It may not solve your issue, but it does definitely solve the issue of remedy trying to start up before sql server does. The problem is that windows thinks sql server is up before it really is. The key is to set a dependency for remedy to not start up until the sqlserveragent starts up. Sqlserveragent has sql server as a dependency, and sqlserver agent takes 10+ seconds to start up. So, by the time sqlserveragent starts up, the database engine is fully functional, so remedy will start without issue. Gary -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Shrestha, Manjari R. Sent: Friday, August 29, 2008 11:41 AM To: [email protected] Subject: When I reboot my server Windows 2003, it takes 20 minutes to startup ** Hello, When I reboot my server Windows 2003, it takes 20 minutes to startup. When I checked the event log I found the above error 390600 : Failure during SQL operation to the database (ARERR 552) and Cannot open database "ARSystem" requested by the login. The login failed. (SQL Server 4060) I am thinking this is because of dependencies of SQl server on Remedy and Remedy on SQL. I would appreciate any information on how to resolve the issue. Thanks! Manjari R. Shrestha Junior Programmer Analyst SAIC 12530 Parklawn Drive, Suite 350 Rockville, MD 20852 Office: (301) 998-7364 [EMAIL PROTECTED] __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
