|
From: Jason R B. <jas...@rh...> - 2007-07-18 21:00:22
|
In case anyone is interested, it appears the only answer is to setup a domain controller in your environment, to ensure that Net Logon will start. After doing so, the problem went away, and our service started without issue. Regards, Jason Lewis Leal wrote: > What account does your service run under (machine, domain, or local > system)? > Can you post your log? > > On 7/2/07, *Jason R Briggs* < jas...@rh... > <mailto:jas...@rh...>> wrote: > > Hi > > Apologies if this has been answered elsewhere, but I couldn't find > any > related messages with SF's rather abysmal search. > > I'm trying to use the service wrapper in our UAT environment and > failing > miserably. We've had it running on various development machines > without > any problems, and it starts up fine when run from the command > prompt on > the UAT server. > > After much fiddling, I eventually tracked the problem down to the fact > that it appears the wrapper has a dependency on Net Logon to be > running. But in this environment, Net Logon starts up and > straight away > shuts down. I believe this has something to do with the fact that > there's no domain controller... but I'm not sure on that front. I'm > seem to have as much difficulty finding info about Microsoft error > messages as I do finding messages on this mailing list... ;-) > > Anyone come across this problem? Is there a workaround or do we > have to > get the environment reconfigured so Net Logon runs properly? > > Thanks for any pointers you can give me. > > Jason > |