Brian McDonald wrote: > I believe it's the tray icon process that is doing this. I get these > messages on a 1-to-1 correlation with logging into the system via > Terminal Services.
Ah, that would explain it! We get this logged far more frequently on our Citrix server - I'd assumed it was a time-out issue and due to the Citrix server being our busiest box. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base/startservicectrldispatcher.asp Says that StartServiceCtrlDispatcher will only work if the process is being started as a service (which the tray icon isn't, I assume) Looking at the return codes for StartServiceCtrlDispatcher: ERROR_FAILED_SERVICE_CONTROLLER_CONNECT Typically, this error indicates that the program is being run as a console application rather than as a service. If the program will be run as a console application for debugging purposes, structure it such that service-specific code is not called when this error is returned. Looks like bacula-fd.exe is being executed at login time and is trying to execute code which only makes sense when being started as a service by the service controller. -- Russell Howe [EMAIL PROTECTED] Today's Nemi: http://www.metro.co.uk/img/pix/nemi_may13.jpg ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
