Mobility 2.0 upgrade comnnector problems

I have version 1.2.5 299 running on a virtualised SLES 11 SP2 that is fully
updated, and everything is running great.
When I do the Mobility 2.0 upgrade the upgrade goes through fine, but on
startup of the connector engines, there areEXCEPTION: Exception: Unable to
contact Sync Engine no connections and the logs have errors of "EXCEPTION:
Exception: Unable to contact Sync Engine"
I think it has something to do with Python, but am not sure what to do to
fix it, as pyxml is installed.
Any help would be appreciated.
Mark Behrens

  • Mark Behrens wrote:

    > I have version 1.2.5 299 running on a virtualised SLES 11 SP2 that is
    > fully updated, and everything is running great.
    > When I do the Mobility 2.0 upgrade the upgrade goes through fine, but on
    > startup of the connector engines, there areEXCEPTION: Exception: Unable to
    > contact Sync Engine no connections and the logs have errors of "EXCEPTION:
    > Exception: Unable to contact Sync Engine"
    > I think it has something to do with Python, but am not sure what to do to
    > fix it, as pyxml is installed.
    > Any help would be appreciated.
    > Mark Behrens


    Did you run the update script post install?

  • "Mark Behrens" wrote:

    > When I do the Mobility 2.0 upgrade the upgrade goes through fine, but on
    > startup of the connector engines, there areEXCEPTION: Exception: Unable to
    > contact Sync Engine no connections and the logs have errors of "EXCEPTION:
    > Exception: Unable to contact Sync Engine" I think it has something to do with
    > Python, but am not sure what to do to fix it, as pyxml is installed.


    I had a situation like this last week, and had to edit my XML files to get
    things working. It was only a momentary fix though, because there was a problem
    like this - http://bit.ly/1coJ0GJ

    I suspect that there are some old "database" issues that are causing a few sites
    to fail. Novell isn't sure that the standard database maintenance we recommend
    would help. It's hard to know if this is your issue though, because you'd have
    to get the connectors working first to be able to see this problem.

    --
    Danita
    Novell Knowledge Partner
    GroupWise Mobility Service 2.0 Guide - http://bit.ly/1cv13RE


    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below...
  • Yes I did

    "Rickb" wrote in message
    news:2i%pu.1475$FD5.566@novprvlin0913.provo.novell.com...

    Mark Behrens wrote:

    > I have version 1.2.5 299 running on a virtualised SLES 11 SP2 that is
    > fully updated, and everything is running great.
    > When I do the Mobility 2.0 upgrade the upgrade goes through fine, but on
    > startup of the connector engines, there areEXCEPTION: Exception: Unable to
    > contact Sync Engine no connections and the logs have errors of "EXCEPTION:
    > Exception: Unable to contact Sync Engine"
    > I think it has something to do with Python, but am not sure what to do to
    > fix it, as pyxml is installed.
    > Any help would be appreciated.
    > Mark Behrens


    Did you run the update script post install?

  • Thanks Danita.
    I'm not sure which XML files you edited, but I save a copy of the
    connector.xml in
    /etc/datasync/configengine/engines/default/pipelines/pipeline1/connectors
    for mobility and groupwise before the upgrade.
    Even with replacing the new ones after the upgrade with those from 1.2,
    these is no change.
    Possibly I am looking at the wrong XML's.
    Please let me know which ones you modified and what modifications you did

    Mark

    "DZanre" wrote in message
    news:mpro.mxnjvr07zfayu1wwm.dzanre@no-mx.forums.novell.com...

    "Mark Behrens" wrote:

    > When I do the Mobility 2.0 upgrade the upgrade goes through fine, but on
    > startup of the connector engines, there areEXCEPTION: Exception: Unable to
    > contact Sync Engine no connections and the logs have errors of "EXCEPTION:
    > Exception: Unable to contact Sync Engine" I think it has something to do
    > with
    > Python, but am not sure what to do to fix it, as pyxml is installed.


    I had a situation like this last week, and had to edit my XML files to get
    things working. It was only a momentary fix though, because there was a
    problem
    like this - http://bit.ly/1coJ0GJ

    I suspect that there are some old "database" issues that are causing a few
    sites
    to fail. Novell isn't sure that the standard database maintenance we
    recommend
    would help. It's hard to know if this is your issue though, because you'd
    have
    to get the connectors working first to be able to see this problem.

    --
    Danita
    Novell Knowledge Partner
    GroupWise Mobility Service 2.0 Guide - http://bit.ly/1cv13RE


    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below...

  • "Mark Behrens" wrote:

    > Possibly I am looking at the wrong XML's.


    The one specifically that I had problems with was
    /etc/datasync/syncengine/connectors.xml - the section at the bottom between
    <connectors> and </connectors> was totally blank.

    --
    Danita
    Novell Knowledge Partner
    GroupWise Mobility Service 2.0 Guide - http://bit.ly/1cv13RE


    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below...
  • I Still am unable to upgrade to GMS 2.0 although 1.2.5 299 is working fine.
    Am using an SMT server for upgrade repositories. I keep on having to revert
    my VM to 1.2.5 version

    After upgrade both the mobility-agent.log and the groupwise-agent.log have
    lines similar to the following;

    2013-12-23 10:11:19.548 ERROR [MainThread] [GenericApplicationInterface:412]
    [userID:] [eventID:] [objectID:] [] Unable to connect to Sync Engine,
    connector ID or settings in connectors.xml may be wrong.
    2013-12-23 10:11:19.549 ERROR [MainThread] [util:253] [userID:] [eventID:]
    [objectID:] [] EXCEPTION: ********************
    2013-12-23 10:11:19.549 ERROR [MainThread] [util:256] [userID:] [eventID:]
    [objectID:] [] EXCEPTION: Traceback (most recent call last):
    2013-12-23 10:11:19.549 ERROR [MainThread] [util:256] [userID:] [eventID:]
    [objectID:] [] EXCEPTION: File
    "syncengine/lib/syncengine/GenericApplicationInterface.py", line 298, in
    __init__
    2013-12-23 10:11:19.549 ERROR [MainThread] [util:256] [userID:] [eventID:]
    [objectID:] [] EXCEPTION: File
    "syncengine/lib/syncengine/GenericApplicationInterface.py", line 413, in
    startEngineClient
    2013-12-23 10:11:19.549 ERROR [MainThread] [util:256] [userID:] [eventID:]
    [objectID:] [] EXCEPTION: Exception: Unable to contact Sync Engine
    2013-12-23 10:11:19.549 ERROR [MainThread] [util:257] [userID:] [eventID:]
    [objectID:] [] EXCEPTION: ********************
    2013-12-23 10:11:24.556 ERROR [MainThread] [GenericApplicationInterface:412]
    [userID:] [eventID:] [objectID:] [] Unable to connect to Sync Engine,
    connector ID or settings in connectors.xml may be wrong.
    2013-12-23 10:11:24.557 ERROR [MainThread] [util:253] [userID:] [eventID:]
    [objectID:] [] EXCEPTION: ********************
    2013-12-23 10:11:24.558 ERROR [MainThread] [util:256] [userID:] [eventID:]
    [objectID:] [] EXCEPTION: Traceback (most recent call last):
    2013-12-23 10:11:24.558 ERROR [MainThread] [util:256] [userID:] [eventID:]
    [objectID:] [] EXCEPTION: File
    "syncengine/lib/syncengine/GenericApplicationInterface.py", line 298, in
    __init__
    2013-12-23 10:11:24.558 ERROR [MainThread] [util:256] [userID:] [eventID:]
    [objectID:] [] EXCEPTION: File
    "syncengine/lib/syncengine/GenericApplicationInterface.py", line 413, in
    startEngineClient

    Would appreciate any help in getting this fixed.
    Mark Behrens

    "Mark Behrens" wrote in message
    news:R2Wpu.1462$FD5.1268@novprvlin0913.provo.novell.com...

    I have version 1.2.5 299 running on a virtualised SLES 11 SP2 that is fully
    updated, and everything is running great.
    When I do the Mobility 2.0 upgrade the upgrade goes through fine, but on
    startup of the connector engines, there areEXCEPTION: Exception: Unable to
    contact Sync Engine no connections and the logs have errors of "EXCEPTION:
    Exception: Unable to contact Sync Engine"
    I think it has something to do with Python, but am not sure what to do to
    fix it, as pyxml is installed.
    Any help would be appreciated.
    Mark Behrens

  • On Mon, 23 Dec 2013 08:43:39 GMT, "Mark Behrens" <markb@espa.co.za>
    wrote:

    > I Still am unable to upgrade to GMS 2.0 although 1.2.5 299 is working fine.
    > Am using an SMT server for upgrade repositories. I keep on having to revert
    > my VM to 1.2.5 version


    > Any help would be appreciated.


    Does startup reveal an error on bad decrypt ... digital envelope
    routines:EVP_DecryptFinal_ex:bad
    decrypt:evp_enc.c:337

    If so, your 127.0.0.2 host name does not match the server name, at
    least that was my case.


  • Thanks for your posr
    I get no error on startup. it runs through fine and all agents start. It's
    just that the mobility agent and the groupwise agent logs have the same line
    error;
    2013-12-24 08:16:13.040 ERROR [MainThread] [GenericApplicationInterface:412]
    [userID:] [eventID:] [objectID:] [] Unable to connect to Sync Engine,
    connector ID
    or settings in connectors.xml may be wrong.


    "Alex Warmerdam" wrote in message
    news:pq5gb9t5marftd20ejmn6u11egn9arkpaf@4ax.com...

    On Mon, 23 Dec 2013 08:43:39 GMT, "Mark Behrens" <markb@espa.co.za>
    wrote:

    > I Still am unable to upgrade to GMS 2.0 although 1.2.5 299 is working
    > fine.
    > Am using an SMT server for upgrade repositories. I keep on having to
    > revert
    > my VM to 1.2.5 version


    > Any help would be appreciated.


    Does startup reveal an error on bad decrypt ... digital envelope
    routines:EVP_DecryptFinal_ex:bad
    decrypt:evp_enc.c:337

    If so, your 127.0.0.2 host name does not match the server name, at
    least that was my case.

  • I have finally managed to resolve this issue;
    In my 1.2.5 299 version there is an installed package pyxml. during the
    upgrade process to version 2.0 this package is mysteriously uninstalled
    Once version 2.0 had been installed I downloaded the
    pyxml-0.8.4-194.23.38.x86_64.rpm package off the internet and installed it
    prior to starting up Mobility. It now works perfectly.

    Mark


    "Mark Behrens" wrote in message
    news:R2Wpu.1462$FD5.1268@novprvlin0913.provo.novell.com...

    I have version 1.2.5 299 running on a virtualised SLES 11 SP2 that is fully
    updated, and everything is running great.
    When I do the Mobility 2.0 upgrade the upgrade goes through fine, but on
    startup of the connector engines, there areEXCEPTION: Exception: Unable to
    contact Sync Engine no connections and the logs have errors of "EXCEPTION:
    Exception: Unable to contact Sync Engine"
    I think it has something to do with Python, but am not sure what to do to
    fix it, as pyxml is installed.
    Any help would be appreciated.
    Mark Behrens

  • Thanks Mark, the same situation appended to me. Now it works perfectly!