How to Install the GroupWise Gateway for Microsoft Exchange

  • 7001367
  • 16-Sep-2008
  • 27-Apr-2012


Novell GroupWise Gateway - 7.x Gateway for MS Exchange
Novell GroupWise 7


GroupWise Gateway for Microsoft Exchange Install fails to result in working Gateway
GroupWise Gateway for Microsoft Exchange Service will not start
ERROR: "1503: The Service did not respond or the start or control request in a timely fashion."
ERROR: "ERROR (E01) 010012: Unable to get configuration information from the MAPI Session"
ERROR: "ERROR (E01) 010012 MAPI code: 11D"
ERROR: "ERROR (E01) 0323004 - Unable to bind to the Gateway Object"


This document is designed to aid in a successful install of the GroupWise Gateway for Microsoft Exchange in regards to "How to Set Rights for Windows users to install and run the Gateway." 

The install and configure documentation should be followed in addition to this TID.  GroupWise GateWay Documentation

The document does not include installation of the Free busy search components.  At the time of writing the GroupWise Gateway for Microsoft Exchange is not intended to be used with Exchange 2007.  Installing the Gateway on a Exchange 2003 server in an Exchange 2007 environment appears to be a valid work-around for using the gateway in an Exchange 2007 environment.

Install the latest version of the Gateway software.  The latest version can be obtained from the Novell download page.  The files can be obtained by opening a service request with support.  If no additional support is required the service request may be closed at no additional charge.

Assumptions about the server where the Gateway will be installed:

Novell Client is installed
Authenticated to Edirectory as Admin
ConsoleOne is installed
Active directory Users and Computers in installed
Exchange system manager is installed
AdsiEdit is installed (possibly not needed)

The install / running of the GroupWise gateway for Microsoft Exchange has been complicated and usually requires additional attention to rights as a result of change made in Exchange
More information about this change can be noted at “Send As” permission behavior change in Exchange 2003.

Preliminary Step to take to insure success before installing the Gateway:
  1. Check for the existence of Gwise address space on current policy and remove.  Find Policy in Exchange system manager | go to properties | remove any old Gwise address space and apply the policy to remove address space from individual users.  Check individual users that the Gwise address space was remove.
  2. Find and remove all Gwproxy.dll on all Exchange servers.  Delete gwproxy.dll from Program Files\Exchsrvr\address\gwise\i386 directory on ALL Exchange servers.  If the file will not delete you may have to stop Exchange services.
  3. Enable the hidden security tab at the top of the Exchange Org to assist in checking for proper rights needed to run the gateway.  The following document will assist in enabling the security tab:
  4. Create a user to run the Gateway service and remove his membership to groups not needed.  IE: remove membership to "users group" as well as any other groups that are not needed.  To remove and add membership to a user go to Active directory Users and Computers | properties of the user | membership tab. 
  5. Add group membership for user used to install the gateway as well as the user used to run the gateway rights to the following groups: Domain admins, Schema admins, Enterprise admins, Exchange Domain Servers
  6. Use the hidden security tab to verify that the Installer user and the Service Runner user do not have deny rights set to the "send as" and "receive as" attributes.  Go to Exchange system manager at the top of the Org | right click and see the new security tab we enabled in Step 3.  Check each group the installer and runner are a members of and remove deny attributes from the "send as and receive as" check boxes.  If the groups are not visible in the Top portion of the properties page use the ADD button to add the group | highlight the user and check the "send as" and "receive as" rights.
  7. Follow the Install and configure documentation for the GateWay
  8. Run the Install for the Gateway.
  9. If the gateway fails to start it is usually an issue with "send as" and "receive as" set to deny.  Use ADSIedit.mcs to find a possible deny that is not visible in Step 6.  To launch ADSIedit go to Start | run | type ADSIeit.msc  (If needed you can install ADSEedit using the following URL suggestions )

    NOTE: Use ADSIedit carefully.  The goal is to check and set a deny / allow right for the above groups and users.  Contact Microsoft support for information regarding the use of this tool.

    Using ADSIedit to find Denys to the Mail Store that are not allowing the user to run the gateway:
    Set all "Send as and Receive as" rights for the above users and groups to allow.  There cannot be any deny on the "Send as and Receive as" for the above groups or users.  Not even if the deny is inherited (greyed out.)

    1. Go into ADSIedit  by going to Start | run | type ADSIeit.msc
    2. Expand the Configuration Container
    3. Drill down to Configuration/Services/Microsoft Exchange/First Organization/Administrative Groups/First Administrative Group/Servers/Exchange/information Store/First Storage Group/ and not the mail store.  
    4. Right click the mail store object in the right hand window of Adsiedit and go to security tab.
    5. Check "Send as and Receive as" and change any Deny to an allow right for the above users and groups.
    6. A Grey check mark set to Deny indicates the right is inherited from above the current container.
    7. Walk up the Tree of containers checking at each section to insure the "Send as and Receive as" is set to allow for the users and groups noted above.
      NOTE:  The most common hidden deny that needs to be removed is found for the Exchange Domains Servers Group and at the Servers Container.
    8. Once all Denys for "Send As and Receive As" have been removed allow some time for replication.  Server Restart have also shown to be helpful when rights are set correctly but service still behaves as if it is lacking the "Send As and Receive As" allow rights.

Additional Information

What we need to know:

The Gateway needs to login to the Exchange mail store on the local Exchange Server and create a mailbox for the user that is specified to run this gateway.  This users rights to the mail store are needed or the gateway will fail to run.

Additional Trouble shooting aids:

  1. Check the Windows Event logs for error when starting the gateway
  2. Set the Gateway in Consoleone to log at verbose logging level
  3. Try starting the gateway as an application during trouble shooting process as it may allow errors to be see that are not logged.  To Start the Gateway as an application when installed as a service Go to / GroupWise domain directory / wpgate/ Exchange / Exegate.exe  right click and select open to launch.