Re: Groupwise API Exchange 2003 Connectivity

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Josh Fooks [MSFT] (jfooks_at_online.microsoft.com)
Date: 11/19/04 

Date: Fri, 19 Nov 2004 10:10:59 -0800

Hi Jeremy,

Hopefully I can restore your sanity here. There's a very very good chance
you have everything setup correctly, but replication simply won't work.

329041 XFOR: Exchange Support for Novell GroupWise 6
http://support.microsoft.com/?id=329041

The short of it is the API has changed in Groupwise 6 and replication
doesn't work. I've played with this myself doing a best effort for a couple
of customers and the Groupwise 6.5 server just do not respond to the
directory replication message request that's sent over. At least that's
what I saw on the two customer systems I was trying to fix. I wish I had a
better answer to give you, but I haven't heard of when this support will be
added.

-Josh

"Jeremy Scribner" <jeremys@alextech.edu> wrote in message
news:ObLp8TezEHA.352@TK2MSFTNGP14.phx.gbl...
>I am working on setting up a Exchange 2003 Server for our department and
> connect it to the rest of our organization which is running GroupWise 6.5.
> I can send message from GroupWise to Exchange using Exchange.First
> Administrative Group.Username and the message is delivered to the Exchange
> user. I am unable to reply to the message. Also I am unable to sync the
> address books. Following MS troubleshooting directions I have configured
> Exchange to archive all message sent or received through the connector.
> The
> Exchange server sends a -GET-DIRECTORY- Administrative message but the
> GroupWise Server responds message with no Directory entries. I do receive
> message from the GroupWise server when a user account is deleted, but
> that's
> it. I'm assuming that this is a GroupWise problem, but I am not sure. I
> have followed the directions according to MS Connectivity Guide Appendix
> B.
> Hopefully someone out there has experienced this problem and can point me
> in
> the right direction.
>
> Another option would be to use Novell's Connector 2.1, but that isn't
> compatible with 2003, has anyone successfully made that work, maybe in
> 2000
> Compatibility mode?
>
> Thank you in advance
>
> Jeremy Scribner
> Center for Automation and Motion Control
> Alexandria Technical College
>
>

Relevant Pages

  • Re: 2 mail servers hosting same domain
    ... Since Exchange 2007 does not have a Groupwise Connector, you should be still be able to configure the "forward undeliverables" setting in GWIA and a Send Connector on your hub transport to send mail destined for your email domain to your GWIA. ... the Groupwise server even if it's part of the same ...
    (microsoft.public.exchange.setup)
  • RE: The list of servers for this workgroup is not currently available.
    ... Verifing that the local machine exchange, ... Connecting to directory service on server exchange. ... The replication generated an error: ... The last success occurred at 2003-10-22 09:58.47. ...
    (microsoft.public.win2000.active_directory)
  • Re: MSCS DR
    ... but LifeKeeper for Exchange can easily be ... quality of the support they receive from the vendor, ... an incompatibility with the third-party replication mechanism. ... CX400 arrays so it looks as though we will be looking at Replistor ...
    (microsoft.public.windows.server.clustering)
  • Re: Configuration / Protocols Missing
    ... and I removed the E55 server. ... the ADCConfigCheck deployment tool (Check Exchange ... The tool searches Active Directory by ... >> its endpoints are the Site Replication Service and a global catalog ...
    (microsoft.public.exchange.setup)
  • Re: Moving from GroupWise to Exchange 2003
    ... I can tell you that the GroupWise connector and Calendar connector seemed a ... The connector is part of the Exchange system and it talks to a GroupWise API ... well this is not available on W2K3 server anymore and it is IPX only. ...
    (microsoft.public.exchange.clients)