Topic Last Modified: 2006-07-13

The Microsoft® Exchange Server Analyzer Tool examines the Exchange Function Call Log (FCL), the Store.fcl file, for events that indicate a predominance of ongoing cross component calls from the Exchange Information Store service (Store.exe) to the Virusscan Virus API (VAPI) component.

Ongoing calls are requests from the Microsoft Exchange Information Store service (Store.exe) to other components that have not received a response at the time the Exchange FCL data is written to the Store.fcl file.

If the Exchange Server Analyzer finds that events in the Store.fcl logging file reflect a predominance of ongoing calls from the Microsoft Exchange Information Store service (Store.exe) to the Virusscan VAPI component, the Exchange Server Analyzer displays an error.

When cross-component calls from the Microsoft Exchange Information Store service (Store.exe) wait for a response, remote procedure call (RPC) threads can back up behind these requests and lead to Exchange Server performance issues such as delays in server responses to clients.

Ongoing calls from the Microsoft Exchange Information Store service to the Virusscan VAPI component can be caused by the following conditions:

• Updates to a virus scanner that generate a re-scan of items in the information store.
  
  
• A misconfigured virus scanner
  
  
• Virus scanner software processes a large message or attachment
  
  

To resolve this error, take the following steps:

• Schedule updates to your virus engine for times when resource consumption is low, that is, off-peak demand hours.
  
  
• Consider reinstalling the virus scanning software, but reinstall at off-peak demand intervals.
  
  
• Examine the configuration of your virus scanning engine for the correct thread configuration, file level exclusions, and so on. See Microsoft Knowledge Base article 823166, "Overview of Exchange Server 2003 and antivirus software" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=823166).
  
  
• Review the articles in the For More Information section of this document.
  
  

For More Information

© 2009 Microsoft Corporation. All rights reserved.