If only it did. That particular article is essentially useless to me. It essentially says 'just set your dependencies and you should be good', but I have the dependencies set properly and I'm not good....the issue that I'm specifically having is that one of their own products is incorrectly reporting as 'started' when it's not available (sql server). The article goes on to say that if you need your service to start 'later' in the process, then to just make it dependent on spooler or messenger. I have done that and STILL it doesn't start late enough in the process to allow SQL to actually become available....so no...that article doesn't give me everything I'm looking for unfortunately.
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Avy Mann Sent: Wednesday, June 13, 2012 7:09 AM To: arslist@ARSLIST.ORG Subject: Re: Remedy Startup ** You want to delay the startup of the AR service. Here is an article that should give you everything you are looking for: http://support.microsoft.com/kb/193888 Enjoy! ________________________________ From: "Longwing, LJ CTR MDA/IC" <lj.longwing....@mda.mil> To: arslist@ARSLIST.ORG Sent: Wednesday, June 13, 2012 8:57:54 AM Subject: Re: Remedy Startup Andrew, You are correct....SQL Server is reporting itself as online, when it's not fully available, and this is screwing up Remedy because it's trying to connect to a DB that's not yet available. I'm looking for a way to delay that startup -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Andrew Fremont Sent: Tuesday, June 12, 2012 3:13 PM To: arslist@ARSLIST.ORG Subject: Re: Remedy Startup ** It could be that the SQL service is not up yet by the time AR start. It happened on one of our dev machines after rebooting where both AR and SQL are installed. Andrew. On Tue, Jun 12, 2012 at 2:03 PM, Longwing, LJ CTR MDA/IC <lj.longwing....@mda.mil> wrote: 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" _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
