Microsoft KB Archive/265308

= XFOR: Event ID 6062 6066 and 6067 with the GroupWise Connector =

Article ID: 265308

Article Last Modified on 2/27/2007

-

APPLIES TO


 * Microsoft Exchange Server 5.5 Standard Edition
 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q265308





SYMPTOMS
If you use the Microsoft Exchange Connector for Novell GroupWise, you may receive the following error messages:

Event ID: 6062

Source: MSExchangeGwRtr

Fail on dispatching message '\\EXCHSRVR\connect$\exchconn\gwrouter\MEX2GW\74f3fd1b.api' from '\\EXCHSRVR\connect$\exchconn\gwrouter\MEX2GW\'

Event ID: 6066

Source: MSExchangeGwRtr

Trying to move file '\\EXCHSRVR\connect$\exchconn\gwrouter\MEX2GW\74f3fd1b.api' to '\\EXCHSRVR\connect$\exchconn\gwrouter\badfiles\'

Event ID: 6067

Source: MSExchangeGwRtr

Failed to move file '\\NWSERVER\data\office41\gwdomain\wpgate\api41\API_IN\7524ce6c' to '\\NWSERVER\data\office41\gwdomain\wpgate\api41\API_IN\7524cef3.api'

The system error code is 3

The system cannot find the path specified.

Event ID: 6067

Source: MSExchangeGwRtr

Failed to move file '\\NWSERVER\data\office41\gwdomain\wpgate\api41\API_IN\7520b4a7' to '\\NWSERVER\data\office41\gwdomain\wpgate\api41\API_IN\7520b4f7.api'

The system error code is 32

The process cannot access the file because

it is being used by another process.

Event ID: 6067

Source: MSExchangeGwRtr Failed to move file '\\EXCHSRVR\connect$\exchconn\gwrouter\MEX2GW\7521dff8.api' to '\\EXCHSRVR\connect$\exchconn\gwrouter\badfiles\7521e068'

The system error code is 2

The system cannot find the file specified.

These error messages occur when connectivity to the Novell Server is over a slow wide area network (WAN) link or is sporadic, or if files are being locked because an antivirus program or another process is gaining access to the files at the same time as the Exchange Connector for Novell GroupWise.

When you receive the preceding error messages, you may expect that e-mail messages are not being delivered and are moving the Badfiles folder. However, this may not always be the case.



CAUSE
This issue can occur because the GWROUTER service is designed to move e-mail messages from Exchange to the API_IN and ATT_IN folders in the API gateway on the Novell server, and then rename the file from xxxxxxxx to xxxxxxxx.api to enable the GroupWise message transfer agent (MTA) to pick up the message. If these files are in use by another process (for example, an antivirus program or another gateway polling the API folder on the Novell Server), the preceding error messages are logged in the Application event log.

However, in some situations, the GroupWise MTA may pick up the message from the API_IN and ATT_IN folder before the GWROUTER Service has a chance to rename the file.

The GWROUTER service is designed to retry the move and rename operation, which explains why e-mail messages can cause these types of error messages but not actually be lost. In fact, in these situations, e-mail messages should be delivered successfully.



MORE INFORMATION
This is a timing issue. This issue may occur more often over a slow WAN link and during periods of high usage. In most situations, you can safely ignore these error messages.

Additional query words: vapi

Keywords: kbprb KB265308

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.