NDSMP not syncing after GrpWise Move to Linux

Hi.

Data synchronizer mobility pack 1.2.5.4417

I just successfully completed a move of my entire Groupwise 8 SP3 system from Netware to SLES 11 SP2. I had assumed that when the move was completed, I would be able to just change the IP address for the post office in the Groupwise and Mobility connectors using the management console for NDSMP.

However after the change there was still no syncing of emails. I then found a discussion about this same problem and the solution that worked for that person was to create a new Trusted Application Key in Console 1 for NDSMP. I did so and changed the key name and key in the NDSMP Groupwise Connector window.

Restarting the connector after the change produces the error:

An error has occurred starting the connector Error: Please verify that the connector manager is running and that the connectors.xml file is correctly configured.

I then tried to change back to the old key, whcih at least allowed the connector to start, however \i get the same error.

What do I need to do to get this up and running.

Thanks,
Scott
  • Hi Scott,

    When creating the Trusted App key did you specify an IP address or DNS name? If you did, recreate the key without this information.

    Also, I recommend that the key file name conform to 8.3 naming convention - others may disagree, but I have had a lot of problems with keys having long names.

    Let us know how it goes.

    Cheers,
  • Hi Scott,

    Further to what I've said above regarding your Trusted App key....

    You may well have to manually edit the connector.xml file in order to point it to the new IP of your GroupWise system.

    I only have a GMS (not datasync) server in front of me currently, and I found this entry listing the IP of my primary GroupWise server:

    <soapServer>10.100.x.x:7191/.../soapServer>

    Perhaps look for something similar.

    File is found here: /etc/datasync/configengine/engines/default/pipelines/pipeline1/connectors/groupwise/connector.xml

    Let us know how it goes.

    Cheers,
  • Hi Laura.

    Keeping you busy today! I checked the connector.xml file and it is showing the correct IP and Trusted App key.

    I also kept the file name of the Trusted App file under 8 characters and I did not fill in the ip address or dns name when creating the key, however did use all CAPS. I created another one with only lowercase. Again the connectors.xml updates with the new information but I still have the same error trying to start the Groupwise connector.

    Scott


    >>> On July-07-14 at 7:26 AM, in message <laurabuckley.6gvydb@no-mx.forums.novell.com>, laurabuckley<laurabuckley@no-mx.forums.novell.com> wrote:



    Hi Scott,

    Further to what I've said above regarding your Trusted App key....

    You may well have to manually edit the connector.xml file in order to
    point it to the new IP of your GroupWise system.

    I only have a GMS (not datasync) server in front of me currently, and I
    found this entry listing the IP of my primary GroupWise server:

    <soapServer>10.100.x.x:7191/.../soapServer>

    Perhaps look for something similar.

    File is found here:
    /etc/datasync/configengine/engines/default/pipelines/pipeline1/connectors/groupwise/connector.xml

    Let us know how it goes.

    Cheers,


    --
    Laura Buckley
    Technical Consultant
    IT Dynamics, South Africa

    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below...
    ------------------------------------------------------------------------
    laurabuckley's Profile: https://forums.novell.com/member.php?userid=122
    View this thread: https://forums.novell.com/showthread.php?t=478114
  • Hey Scott,

    Glad that you are keeping me busy :)

    Check: /etc/datasync/syncengine/connectors.xml for any incorrect information.

    Let us know :)

    Cheers,
  • Looks like it started this time. I used rcdatasync to stop then restart all the datasync services and now the admin console is showing the Groupwise and Mobility connectors as Running.

    After this I stopped and restarted the Groupwise Connector just to see if I could and and was able to do so without error.

    However my phone (a blackberry Z10) is still not connecting correctly. I have an Alert on my phone that says Login Account Information needed. This usually means that the password has to be re-entered. When I do so though, I get

    Your login information for account " my account here" has changed or is incorrect. Update your login information and try again.

    Thoughts?

    Thanks Laura!


    >>> On July-07-14 at 12:46 PM, in message <laurabuckley.6gwd6n@no-mx.forums.novell.com>, laurabuckley<laurabuckley@no-mx.forums.novell.com> wrote:



    Hey Scott,

    Glad that you are keeping me busy :)

    Check: /etc/datasync/syncengine/connectors.xml for any incorrect
    information.

    Let us know :)

    Cheers,


    --
    Laura Buckley
    Technical Consultant
    IT Dynamics, South Africa

    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below...
    ------------------------------------------------------------------------
    laurabuckley's Profile: https://forums.novell.com/member.php?userid=122
    View this thread: https://forums.novell.com/showthread.php?t=478114
  • Hi Scott,

    Considering the changes that you've made in your environment e.g. migrating your GroupWise server.... is your datasync using LDAP or GroupWise authentication? Is your authentication source pointing to the correct server.

    Glad to be here for you Scott :)

    Cheers,
  • Looking under the mobile connector in the datasync admin console we are using secure ldap. The ldap server is the old groupwise server (which is still our main file server).

    This has worked in the past when Groupwise was still on the main file server, so that points to the issue being between the new Groupwise server and the old (also current LDAP) server. Maybe the same issue that my Gropwise user is having with the certificate file?

    Scott


    >>> On July-07-14 at 1:46 PM, in message <laurabuckley.6gwfyn@no-mx.forums.novell.com>, laurabuckley<laurabuckley@no-mx.forums.novell.com> wrote:



    Hi Scott,

    Considering the changes that you've made in your environment e.g.
    migrating your GroupWise server.... is your datasync using LDAP or
    GroupWise authentication? Is your authentication source pointing to the
    correct server.

    Glad to be here for you Scott :)

    Cheers,


    --
    Laura Buckley
    Technical Consultant
    IT Dynamics, South Africa

    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below...
    ------------------------------------------------------------------------
    laurabuckley's Profile: https://forums.novell.com/member.php?userid=122
    View this thread: https://forums.novell.com/showthread.php?t=478114
  • Hey Scott,

    Perhaps double-check that your certificates have not expired! Just a suggestion ;)

    Cheers,
  • I did. They are good until 2023.


    >>> On July-07-14 at 2:26 PM, in message <laurabuckley.6gwhtb@no-mx.forums.novell.com>, laurabuckley<laurabuckley@no-mx.forums.novell.com> wrote:


    Hey Scott,

    Perhaps double-check that your certificates have not expired! Just a
    suggestion ;)

    Cheers,


    --
    Laura Buckley
    Technical Consultant
    IT Dynamics, South Africa

    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below...
    ------------------------------------------------------------------------
    laurabuckley's Profile: https://forums.novell.com/member.php?userid=122
    View this thread: https://forums.novell.com/showthread.php?t=478114
  • Hey Scott,

    That's odd, coz a server cert is [normally] only valid for two years!

    Here's a suggestion... go to https://yourserverip and see if you get a certificate error - then take a closer look at the error i.e expiration date.

    Let us know as per usual - thanks :)

    Cheers,