Error (E01) Unable to bind to Gateway Object when starting the Groupwise Gateway for Exchange

  • 3940684
  • 17-Jul-2007
  • 27-Apr-2012


Novell GroupWise 7
Novell GroupWise Gateway - 7.x Gateway for MS Exchange
Microsoft Windows Server 2003
Microsoft Windows Server 2000
Microsoft Exchange Server 2000
Microsoft Exchange Server 2000


Error (E01) Unable to bind to Gateway Object when starting the Groupwise Gateway for Exchange
Gateway cannot start and is looking for the connector in Active directory in the wrong location under the Child domain configuration container rather then the parent domain / configuration container.

Exchange gateway as well as Exchange is installed on a server in child domain.

Gateway cannot find the connector in Active Directory and is looking in Active Directory for the configuration container to be in the child domain.
The configuration container for Active directory does not reside in the child domain but instead resides in the parent domain always.


This appears to be working correctly in GroupWise gateway for Exchange code dated later then 7-14-08
If unable to download the above dated code please contact Novell support for the files.
The Current work around in older code date is to modify a path in the registry to remove the child domain.

This setting can be found in: HKEY_LOCAL_MACHINE\SOFTWARE\novell\GroupWise
Gateways\Exchange\gateway name\Parameters
Modify the Key "Domain" and remove the DC for the child domain

Example "Domain" Key value: (incorrect)

Modify to read (modified)"

Additional Information

Steps to duplicate.

1) Install two windows 2003 servers. Install the second server in a child domain rather then the parent.

2) Install exchange on the second server in the Child Domain

3) Install the gateway on the second server in the Child Domain

4) Try to start gateway and note the error in verbose logging on the gateway or gateway logs will contain the distinguished path. The distinguished path will show that the gateway is trying to locate the connector but is looking in a path similar to this. ADsPath - LDAP://cn=gateway name,cn=Connections,CN=First
Routing Groups,cn=First Administrative Group,cn=Administrative Groups,cn=First
Organization,cn=Microsoft Exchange,cn=Service,cn=Configuration,DC=child
,DC=Parent domain,DS=com

In this distinguished path you can note the child domain is listed in the path to the configuration container. This is incorrect since the configuration container is in fact always present in the parent domain under Active Directory.