Re: Groupwise connector error

From: Fitz Crittle [MSFT] (fitzcrit_at_online.microsoft.com)
Date: 09/30/04


Date: Thu, 30 Sep 2004 15:39:03 -0500

Here's a suggestion that has worked:

- Uninstall the "Client for Netware Services (CSNW)"/GroupWise Services for
NetWare (GSNW) for Windows 2000 or 2003
- Install the 32bit Novell Client on the Windows 2000 or 2003 from the
Novell Web site.

Note: Keep in mind that the 32bit Novell Clinet is NOT the same as the
GroupWise Client.

- Make sure you can map to the API folders from the Exchange server to the
GroupWise server.
- Load the API Gateway Service in GroupWise
- Start the Connectivity Controller, Connector for Novell GroupWise and
Novell GroupWise Router services on Exchange 2003

This response contains a reference to a Third party World Wide Web site. You
should know that Third party sites are not under the control of Microsoft.
Accordingly, Microsoft can make no representation concerning the content of
these sites. Microsoft is providing this information only as a convenience
to you. This is to inform you that Microsoft has not tested any software or
information found on these sites and therefore cannot make any
representations regarding the quality, safety, or suitability of any
software or information found there. There are inherent dangers in the use
of any software found on the Internet, and Microsoft cautions you to make
sure that you completely understand the risk before retrieving any software
on the Internet.

Thanks,
Fitz Crittle

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email to this address, post a reply to this newsgroup

"Justin Nolan" <anonymous@discussions.microsoft.com> wrote in message
news:19d501c4a712$3679ac10$a401280a@phx.gbl...
> We are migrating from Groupwise 6 to Exchange 2003 and I
> for the most part seem to have everything ironed out with
> the API and using the Migration Wizard to move mail (we
> don't use the calendar functionality that much in GW). I
> have containers setup for migrated users in AD (we have a
> fully functional 2003 AD structure setup) and it seems
> everything is working properly except for one thing. I
> have tested the API per the documentation in the 2003
> interoperability doc and it does seem to work BUT I get
> an error in my Exchange Server application log regarding
> the Connector for Groupwise. It's Event ID 6061 and the
> entry looks like this: "The following directory could
> not be found:
> \\groupwiseserver\apps\v_domain\wpgate\api\API_OUT\.
> Please make sure the directory setting is correct and the
> Groupwise Server is running. The system error code is
> 1317. The specified user does not exist." Now I assume
> this error is referring to the user in the connector
> settings on the Exchange Server (Netware Account in the
> settings). I have tried my migration account and a
> couple other admin accounts with rights in both locations
> (including leading periods) to no avail. I continually
> get this error message. I have CSNW installed on the
> Exchange Server and I'm able to map the above path (the
> path specified in the connector as well
> \\groupwiseserver\apps\v_domain\wpgate\api) and create
> and modify folders and text files in these directories
> from the Exchange Server. I even see the test emails I
> sent sitting in the API_OUT and the ATT_OUT directories.
> I am going nuts trying to figure out what I need to do to
> make the connector happy. Any suggestions are GREATLY
> appreciated. Thanks!
>
>
>
> Justin Nolan, MCSA, MCSE+I, MCDBA, CCNA, CCA
>
> IT Manager
>
> Vistacom Inc.
>
>



Relevant Pages

  • Re: Groupwise connector error
    ... > GroupWise Client. ... > - Make sure you can map to the API folders from the Exchange server to the ... Microsoft can make no representation concerning ... >> this error is referring to the user in the connector ...
    (microsoft.public.exchange.connectivity)
  • Re: Putting anything Novell related on a Win2K3/Exchange03 server
    ... we aren't using GroupWise 6. ... Novell products should never be put on an Exchange server because they ... > I would never do that, and it is not necessary for a migration at all. ...
    (microsoft.public.exchange.misc)
  • Re: Groupwise to Exchange 2003 migration
    ... In our migration plan people will be moved in "like" ... Use the Microsoft connector for exchange with the API gateway. ... AD accounts but make sure you use the latest API from Novell. ... >> I am about to undertake a Groupwise to Exchange migration and need to ...
    (microsoft.public.exchange.connectivity)
  • Any Documentation for Exchange SP2 CTP on setup Interop for GW?
    ... I have the Exchange Server 2003 Interoperability and Migration Guide May 2004 ... And I was reading about article: Q329041 (Exchange support for Novell ... GroupWise 6). ...
    (microsoft.public.exchange.setup)
  • Re: Conditional data validation.
    ... Give each of your dependent lists a descriptive defined name. ... Exchange Server 5 users, Exchange Server 10 users, Exchange ... Novell 5 users,Novel 10 users,Novel 50 users ... Microsoft Excel MVP ...
    (microsoft.public.excel.misc)