The information in this article applies to:
SYMPTOMSDirectory synchronization (dirsync) between Novell GroupWise and Exchange Server may not finish when you request an update from GroupWise to Exchange Server. CAUSEThe Microsoft Exchange Connector for Novell GroupWise is hardcoded to expect a full directory list of the GroupWise system as part of the dirsync process. Entries in the directory list are compared to current entries in Exchange Server, and any updates or new GroupWise users are subsequently imported into the Exchange Server directory. Thus, the concept of an update dirsync cycle does not exist from GroupWise to Exchange Server. However, if the Directory Synch/Exchange configuration on the API gateway is set to Synchronization, then the GroupWise Connector cannot ask for a directory list from GroupWise. Instead, any modifications or additions in GroupWise result in an immediate update sent to the API_OUT directory. The router for GroupWise automatically processes these API files as part of its polling cycle. RESOLUTIONPerform the following steps to check the configuration of the GroupWise API Gateway: GroupWise 5.x
GroupWise 4.x
STATUSMicrosoft has confirmed this to be a problem in Microsoft Exchange Connector for Novell GroupWise. MORE INFORMATIONThe GroupWise Connector logs will indicate that the connector is waiting for the inbound dirsync files from GroupWise. The connector will time out after an hour and log an error indicating that dirsync was incomplete. Additional query words:
Keywords : exc55 |
Last Reviewed: June 3, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |