Dealing With Event Id 6062, 6066 And 6067 Of Groupwise Connector

By Author: DiskDataRecovery
Total Articles: 50
Comment this article

Transferring emails and other email items from Novell GroupWise to exchange is an intricate task. Various problems do arise while performing migration from GroupWise email environment to Exchange Server platform. Like if you use the Microsoft Exchange Connector for Novell GroupWise, you might 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.

Reasons behind these event IDs

You get these errors when connectivity to the Novell Server is infrequent or is very much slow. An antivirus program or another process might be blocking the files from getting executed properly. Files could be locked due to some other process gaining access to the files at the same time as the Exchange Connector for Novell GroupWise.

On occurrence of these event IDs, you are not able to export email messages from GroupWise to Exchange Server.

Resolution

To resolve this issue, make some change in settings of GWROUTER service, which is designed to move email messages from Exchange to the API_IN and ATT_IN folders in the API gateway on the Novell server. You must 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), then the above error messages are bound to occur and get 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.

If anyone wants to have seamless and effective migration from Novell GroupWise to Exchange, then it would be fruitful to use advanced GroupWise to Exchange migration software that provides with accurate and successful migration of emails and all other email items existing. It efficiently converts emails, contacts, attachments, images, email properties, journals, calendars, to-do list, appointments, and email items from work in progress, cabinet and trash items to user mailboxes on MS Exchange Server. User gets option of migrating single mailbox or multiple mailboxes at once.