Ok...my box is running Remedy and SQL Server both and on startup the Remedy service fails to start properly. The arerror.log shows an error about ARAdmin login failing twice, then the process dies. An immediate attempt to start the service functions fine. Checking the SQL Logs I see something along the lines of
12:00:00 Starting ARSystem 12:00:01 Attempted login from ARAdmin failed 12:00:02 Scanning ARSystem 12:00:06 Recovery of ARSystem complete That's not a copy of the log (because I can't get that to the internet)...but that's close to what it says....this is only happening on one of my boxes, and I suspect that it's a memory related issue because when I check a functional box, I see everything except the login failed line, but it all happens within a second of each other...and my remedy doesn't have any problems starting. I have the Remedy service set to depend on the SQL service, but according to the internet (and my personal experience) the SQL Service reporting as 'up' does not mean that DB's are available. MS recommends that if you need to 'delay' the startup of a particular service that you should set it dependent on 'Spooler'...I've done this but it doesn't help...I need another 5-10 seconds delay with the attempted starting of Remedy service....any recommendations? _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
