KB: Windows NT services monitored by AVIcode may fail to start automatically

KB: Windows NT services monitored by AVIcode may fail to start automatically

  • Comments 1
  • Likes

imageHere’s a new Knowledge Base article we published this morning. This one talks about an easy fix for an issue you may run into where a Windows NT service fails to start automatically if monitored by AVICode.

=====

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].

Cause

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

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)".

More Information

This article applies to Windows NT services that are monitored with AVICode 5.6 or 5.7

=====

For the most current version of this article please see the following:

2695741 : Windows NT services monitored by AVIcode may fail to start automatically

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • I believe increased startup timeout is not always the cause here. It is more likely about the dependency between the service being monitored and avicode agent. During startup, avicode agent has to start another service(intercept service), so one service becomes sort of dependent on the other and it just cannot start