It's a little bit of a kludge but in effect you make services dependent on others. I've yet to find a while to just set an actual numerical order.
In my case PCAnywhere was killing Exchange so we made PCAnywhere dependent on Exchange - it could only try to start after Exchange was up and running. The technique is detailed here: http://support.microsoft.com/default.aspx?scid=kb;EN-US;193888 It may take some playing, but making CF dependent on a service that's taking a while could fix it or making that service dependent on CF. Hope this helps, Jim President, http://www.depressedpress.com Webmaster, http://www.firstnight.org Webmaster, http://www.cfAdvocacy.org Senior Consultant, http://www.metlife.com > -----Original Message----- > From: DURETTE, STEVEN J (AIT) [mailto:[EMAIL PROTECTED] > Sent: Friday, June 06, 2003 4:01 PM > To: CF-Talk > Subject: RE: Very unsatisfied with Macromedia's support attention ... > > Jim, > > How do you change the order in which things start up? > > I've had a dev server that has this problem also, we don't reboot it often > so we usually just start it manually. > > If I could change the order and make cfmx last it might clear up my > problem. > > Thanks, > Steve > > > -----Original Message----- > From: Jim Davis [mailto:[EMAIL PROTECTED] > Sent: Friday, June 06, 2003 3:19 PM > To: CF-Talk > Subject: RE: Very unsatisfied with Macromedia's support attention ... > > > > -----Original Message----- > > From: Bryan Stevenson [mailto:[EMAIL PROTECTED] > > Sent: Friday, June 06, 2003 2:04 PM > > To: CF-Talk > > Subject: Re: Very unsatisfied with Macromedia's support attention ... > > > > Hey Mike, > > > > Personally I would be pretty ticked if I had to start my CF services > > manually. I'm not sure why they are saying this is a known bug. Can > you > > shed some light as to why this "bug" is happening on your setup > > specifically? or are they saying it has to do with Updater 3? > > However if running a batch file DOES work then you should look at the > order at which things start up - rearranging them should fix the > problem. > > We had a problem with PCAnywhere, for example, it would take a bit > longer than it claimed to start up and interfere with later services (in > our case Exchange 2000). Once we moved PCAnywhere to start up last the > problem went away completely. > > Since you make very well be using PCAnywhere (sine this is a remote box) > I'd try that just for kicks. There's a technote at Symantec.com about > this. > > Jim Davis > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
