TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to [EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems! ----------------------------------------------------------------------------
I understand that it is bad form to post a reply to ones own message but, (as the post was delayed many days) I thought that others may benefit from my experience. The problem was due to a corrupt policy file which occured silently - this (as I am told from ISS Tech Supp), was during the 1.1 SR update for the event collector. replacement of a newly crafted policy file from tech support (thankyou) and a reboot fixed the problem. Clinton Clinton Smith wrote: > TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to > [EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems! > ---------------------------------------------------------------------------- > > Has anyone seen this? > > On one of our networks we have RS 6.5 server sensors being > managed by a console (event collector installed locally). > > All was running perfectly. We rebooted the system and when it was > restarted the following events occurred in the NT event log and the > issdaemon fails to start > > Event 103 - Daemon is starting > Event 103 - Starting IssDaemon Version = 7.0.2002.155 > Event 103 - IssDaemon initialization info. > using action configuration from > D:\Program Files\ISS\IssDaemon\common.policy > Event 101 - Engine dll name not specified for engine "event_collector_1" > > Engine will not be managed. > Event 101 - removeEngine(): Unable to call removeEngine for engine > event_collector_1, removeEngineFunc symbol not > set in. > Event 103 - IssEngineManager::init(), the daemon found no engines to > manage. > Event 101 - IssDaemonCommServer::init(), strong authentication is > selected but no public key directories are > specified. > Event 101 - theDaemon::init(), EngineManager init failed. > the Daemon must exit. > > On attemtpting to restart the issdaemon service the following error is > produced: > > "Windows could not start the IssDaemon on local computer. For more > specific information review the system event log. > If this is a non-microsoft service, contact the service vendoe, and > refer to service specific error code -1." > > Sincere Regards, > Clinton
