Migrating from Novell GroupWise to Exchange 2003 Server

Testing Messaging Connectivity in GroupWise

The best way to test messaging connectivity between Novell GroupWise and Exchange 2003 is to send e-mail messages to an Exchange user from a Novell GroupWise client. To determine which GWISE proxy address to specify for an Exchange recipient, start Active Directory Users and Computers, display the properties of the user account, and then switch to the E-mail Addresses tab. Verify that a proxy e-mail address of type GWISE has been assigned to the user, such as Exchange.First Administrative Group.Administrator, and then use this address to specify the recipient in your Novell GroupWise client.

Remember to ensure that the message routing works in both directions. The fact that messages are being delivered from Novell GroupWise to Exchange 2003 does not mean that messages are being transferred from Exchange 2003 to Novell GroupWise. To test message transfer in the other direction, reply to the test message in Outlook, and ensure that the message is received in Novell GroupWise.

When you test messaging connectivity, it is a good idea to increase the level of event logging for the Connector for Novell GroupWise service in Exchange System Manager. To do this, display the properties of the bridgehead server, switch to the Diagnostics Logging tab, select LME-GWISE from the Services list, and then select Controller, GroupWise Interface, Transport to Exchange, Transport from Exchange, and Exchange to GroupWise Conversion, as well as GroupWise to Exchange Conversion and GroupWise Router from the Categories list. Set the logging level to Maximum to obtain the most detailed information. You might also want to set the logging level for categories of the MSExchangeGWRtr service (Connection, General, and Housekeeping) to obtain detailed information about these processes in the application event log.

Note :

Setting the diagnostics logging level to Maximum can cause a large number of events to be written to the application event log. As a best practice, set the size of the application and system event log to 30 MB, and enable the option to overwrite events as needed. Remember to reapply the default setting of None after you finish testing your connector.

Examining Message Flow Between Novell GroupWise and Exchange 2003

If messages are not transferred correctly, check the individual repositories and processes involved in transferring messages between Novell GroupWise and Exchange 2003. Figure 5.4 shows the individual stages in message transfer from Novell GroupWise to Exchange 2003.

Figure 5.4 Message flow from Novell GroupWise to Exchange 2003

Check the message flow from Novell GroupWise to Exchange 2003 in the following order:

Check the \WPCSOUT folder in the Novell GroupWise API Gateway directory The \WPCSOUT folder is the Novell GroupWise MTA outbound queue where outgoing messages are placed when you send a message from Novell GroupWise to an Exchange 2003 recipient. The Novell GroupWise MTA transfers the message to the API gateway that is linked to your Exchange foreign domain. If messages are queuing up in the \WPCSOUT folder, verify the status of your API gateway instance running on the Novell NetWare server.

Check the \API_OUT and \ATT_OUT folders in the Novell GroupWise API Gateway directory The API gateway converts outbound messages into keyword-based text files and places them in these folders, as follows:

•	\API_OUT Message header with an .api file name extension
•	\ATT_OUT Message body and attachments with a .bdy file name extension

If files queue up in these folders, the Microsoft Exchange Router for Novell GroupWise (Gwrouter.exe) might not be running or might be having access problems. Check the application event log for events for which the source is MSExchangeGWRtr. For example, if the path to the API gateway directory is incorrect in the connector configuration, the following description is logged: The following directory could not be found: \server01\api\API_OUT\. In Exchange System Manager, display the properties of Connector for Novell GroupWise, and verify the path and account settings.

Check the subdirectories under \Program Files\Exchsrvr\Conndata\GWRouter The Router for Novell GroupWise moves the header and body files into subdirectories in the connector store, as follows:

•	\GW2MEX Message header with an .api file name extension
•	\GW2MEXA Message body and attachments with a .bdy file name extension
•	The GW2MEX process picks up the files from the connector store. Gw2mex.exe converts header and body files to messages in Exchange format and places them into the READYIN folder.

Note :

If you find .bdy files in the \GW2MEXA folder without corresponding header files in the \GW2MEX folder, check the \Badfiles folder in the same location. You can retry a failed transfer by moving the header files back into the \GW2MEX folder. However, remember that header files for messages from Exchange to Novell GroupWise are also placed into the \Badfiles folder if the Router for Novell GroupWise cannot transfer the messages into the API gateway. If such files are incorrectly moved to the \GW2MEX folder, Gw2mex.exe will move these files back to the \Badfiles folder, because the correct place for them is the \MEX2GW folder. There is more information about message transfer from Exchange to Novell GroupWise later in this section.

Check the READYIN folder of Connector for Novell GroupWise To examine this folder, in Exchange System Manager, open the Queues container under the bridgehead server object in Exchange System Manager. Select READYIN in the details pane, click Find Messages, and then, in the Find Messages dialog box, click Find Now to list all messages in this folder under Search Results. If messages are stuck in this folder, you might be experiencing a problem related to the LSMEXIN process. Lsmexin.exe performs address translation and Active Directory lookup for the intended recipients of a message. The LSMEXIN process also moves the messages from the READYIN folder to the connector's MTS-IN folder.

Note :

If Connector for Novell GroupWise is unable to transfer messages from the READYIN folder into the MTS-IN folder, check the application event log and look for events for which the source is MSExchangeGWISE and the Category information is Transport to Exchange. Also look for events for which the Category is GroupWise Interface to verify that the LSMEXIN process started successfully.

Check the connector's MTS-IN folder To examine this folder, in Exchange System Manager, in the Queues container, select MTS-IN, and then click Find Messages. If you find messages in the MTS-IN folder, these messages are waiting for the store driver to move them to the Exchange MTA. Ensure that the Exchange MTA is started (in the Services tool, check the Microsoft Exchange MTA Stacks service). There is more information about message transfer through the Exchange MTA later in this chapter.

Check the SMTP Mailbox Store queue The Exchange MTA puts the message to be transferred in its SMTP Mailbox Store queue. To view this queue, in Exchange System Manager, in the Queues container, select SMTP Mailbox Store, and then click Find Messages. The store driver picks up the message from this queue and transfers it to the SMTP service. The SMTP transport engine receives the message, categorizes it, and then routes it to the target recipients. There is more information about message transfer through the SMTP service later in this section.

The message queues and connector processes differ when messages are transferred in the opposite direction. Figure 5.5 shows these queues and processes for Exchange 2003 to Novell GroupWise message transfer.

Figure 5.5 Message flow from Exchange 2003 to Novell GroupWise

Check the Exchange 2003 to Novell GroupWise message flow in the following order:

Check the Outbox folder in your Outlook client When you send a message to another user, the mailbox store receives the message from your client and then the store driver passes the message to the SMTP service for routing and transfer. If messages do not leave your Outbox, check that the SMTP service on your mailbox server is running.

Check the internal message queues of the SMTP transport engine There are several SMTP message queues in the Queues container in Exchange System Manager. These queues contain messages at various stages in the routing process. For more information about SMTP message queues, see the section "Troubleshooting SMTP Connectivity" later in this chapter.

For Novell GroupWise recipients, the routing proceeds as follows:

1.	The message is passed to the Advanced Queuing component in the SMTP service, where it is placed in a pre-categorization queue.
2.	The categorizer resolves both recipient and sender addresses, and expands any mail-enabled groups. For Novell GroupWise recipients, the message is then placed in a post-categorization queue. The categorizer is also discussed in Chapter 4, "Interoperating with and Migrating from Other Non-Exchange Messaging Systems."
3.	Because the message is for a remote recipient, the advanced queuing engine moves the message to the pre-routing queue.
4.	The routing engine picks up the message from the pre-routing queue and determines the routes for delivering the message. It assigns the message to the Connector for Novell GroupWise instance that handles the address type of the recipient (that is, GWISE). Because the Exchange MTA is responsible for messaging connectors to non-Exchange messaging systems, such as Connector for Novell GroupWise, the routing engine passes the message to the Exchange MTA.

Check the Connector for Novell GroupWise message queue The Exchange MTA places the message into an internal message queue, which the MTA maintains separately from the Exchange store on the file system (\Program Files\Exchsrvr\Mtadata). You can only view this queue in Exchange System Manager when the Microsoft Exchange MTA Stacks service is running. In the Queues container, select Connector for Novell GroupWise, and then click Find Messages.

Note :

If you suspect that a corrupted message is blocking the Connector for Novell GroupWise message queue, use the MTA Check tool to check the MTA message queues for consistency. You can also use the MTA Check tool to repair the MTA message queues, if necessary. To download this tool, visit http://go.microsoft.com/fwlink/?LinkId=25924. For more information about troubleshooting Exchange MTA problems, see the section "Troubleshooting X.400 Connectivity" later in this chapter.

Check the MTS-OUT folder of Connector for Novell GroupWise The Exchange MTA wraps the message in a message transfer envelope (MTE) and places it in the MTS-OUT folder for delivery through Connector for Novell GroupWise. Note that the Exchange MTA continues to deliver messages to the MTS-OUT folder even if the Connector for Novell GroupWise service is paused or stopped. This can cause a backlog of messages to collect in the delivery queue. In the Queues container in Exchange System Manager, select MTS-OUT, and then click Find Messages to examine this message queue.

If messages accumulate in the MTS-OUT folder, you might be experiencing a problem related to the LSMEXOUT process. Lsmexout.exe picks up messages from the MTS-OUT folder, accesses Active Directory to perform address translation for the target recipients, and then places the messages into the READYOUT folder.

Note :

If Connector for Novell GroupWise is unable to transfer messages from the MTS-OUT folder into the READYOUT folder, check the application event log and look for events for which the source is MSExchangeGWISE and the Category information is Transport from Exchange. Also look for events for which the Category is GroupWise Interface to verify that the LSMEXOUT process started successfully.

Check the READYOUT folder Messages that have been placed in the READYOUT folder await processing through the MEX2GW process. Mex2gw.exe obtains the messages from the READYOUT folder, converts them into Novell GroupWise format, and places them into the connector store. If messages are accumulating in the READYOUT folder, this might indicate a MEX2GW problem. In the Queues container, select READYOUT, and then click Find Messages to list all messages that are currently in this queue.

Check the subdirectories under \Program Files\Exchsrvr\Conndata\GWRouter The MEX2GW process places the converted header and body files into the following subdirectories in the connector store:

•	\MEX2GW Message header with an .api file name extension
•	\MEX2GWA Message body and attachments with a .bdy file name extension

The Router for Novell GroupWise process picks up these files from the connector store and places them into corresponding folders in the API Gateway directory.

Check the \API_IN and \ATT_IN folders in the Novell GroupWise API Gateway directory The API gateway receives the inbound messages as keyword-based text files and places them in the following folders:

•	\API_IN Message header with an .api file name extension
•	\ATT_IN Message body and attachments with a .bdy file name extension

If files are queuing up in these folders, the Novell GroupWise API Gateway might not be running on the Novell NetWare server.

Check the \WPCSIN folder in the Novell GroupWise API Gateway directory The \WPCSIN folder in the Novell GroupWise API Gateway directory is the Novell GroupWise MTA inbound queue. The Novell GroupWise MTA transfers the message to the Novell GroupWise domain and post office where the Novell GroupWise user resides. If messages are queuing up in the \WPCSIN folder, verify that the Novell GroupWise MTA for your API gateway is running on the Novell NetWare server.