toolsignAfter upgrading the AVIcode Intercept Studio Agent, the following events may be logged every few seconds in the Intercept EventLog:

Log Name:      Intercept
Source:        Intercept PerfCounterMonitor
Date:         
Event ID:      4299
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      <COMPUTER>
Description: Probably registry keys for performance counters was been corrupted. Please contact Techical Support if this issue persist.

System information:
Agent version: 5.7.491.0
Windows version: 2.6.1.3.400.0.9.0.

Log Name:      Intercept
Source:        Intercept PerfCounterMonitor
Date:         
Event ID:      4000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      <COMPUTER>
Description: An error has occurred. Please contact Technical Support if this issue persists.
Error: The system cannot find the file specified.
Code: 80070002  Type: COM object  External Time <time> Thread: 2964 Raised in: hr. CCounterController::FinalConstruct, Caught in: CCounterController::FinalConstruct.

System information:
Agent version: 5.7.491.0
Windows version: 2.6.1.3.400.0.9.0.

Log Name:      Intercept
Source:        Intercept PMonitor
Date:         
Event ID:      3020
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      <COMPUTER>
Description:  Cannot call controller method.
The system cannot find the file specified. Error: The system cannot find the file specified.
Code: 80070002 Type: COM object

System information:
Agent version: 5.7.491.0
Windows version: 2.6.1.3.400.0.9.0;
.NET Framework: v2.0.50727
Process ID: 1112; Instance ID: 0;
InstanceName: w3wp.exe [x64];
Application Pool: <Application Pool>.

Cause

One or more Performance Counters have become corrupted preventing AVIcode Intercept Studio Agent from setting counter information upon Agent installation.

Resolution

Perform the following steps to unregister the Intercept Counters module, rebuild Performance Counters and then re-register the Intercept Counters module:

  1. Stop the Intercept Service service.
  2. Open a Command Prompt and navigate to C:\Windows\System32 (x86) or C:\Windows\SysWOW64 (x64).
  3. Type regsvr32 /u InterceptCounters.dll and press Enter.
  4. Type lodctr /r and press Enter.
  5. Type regsvr32 InterceptCounters.dll and press Enter.
  6. Start the Intercept Service service.

Hope this helps,

Jeff Fanjoy | Senior Support Escalation Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis

clip_image001 clip_image002