Windows NT services monitored by AVIcode may fail to start automatically

View products that this article applies to.

Symptoms

Some Windows NT services may fail to start automatically on computer startup if they are monitored by AVICode. However, the services can be started manually afterwards. If you check the Intercept event log, you see an error similar to this:

[DATA],[TIME],Intercept Stub,Error,None,4000,N/A,A01-CRM-TRNS22,"An error has occurred. Please contact Technical Support if this issue persists.
Error: Monitor initialization timeout expired.
Please contact your system administrator.
Code: [CODE] Type: Internal External Time [DATE] [TIME] Thread: [TID] Raised in: (ret == WAIT_OBJECT_0). CInitThread::InitAndWaitFinish, Caught in: CProfilerCallback::Initialize.

System information:

Agent version: [INTERCEPT_AGENT_VERSION]
Windows version: [OS_VERSION]
Process ID: [PID]; Instance ID: [IID];
InstanceName: [NAME_OF_THE_SERVICE].

↑ Back to the top

Cause

Startup time for services can increase due to the way the .NET CLR Profiling API works.

↑ Back to the top

Resolution

Configure a startup dependency for each of the services that are not starting automatically, to be dependent on the Intercept service (AVICode agent) using this article:

193888 - How to delay loading of specific services (http://support.microsoft.com/kb/193888)

Also make sure that the Intercept service is set to "Automatic" startup and NOT "Automatic (Delayed start)".

↑ Back to the top