Highlighted
New Member.
961 views

Syncengine not running after SLES 11 SP2 Online Update

Hi All,

after the last online Update of my SLES 11 SP2, the sync Enginge will not start anymore.

Couldn't find the issue I decided to update to the latest 1.2.5.299 (coming from .250). Still the syncengine will not start.

Looking into the engine.log file I found the Exception:

EXCEPTION: WebFault: Server raised fault: 'No module named ext'

Does anybody have an idea?

thanks and best regards
Arne
Labels (1)
0 Likes
5 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Re: Syncengine not running after SLES 11 SP2 Online Update

On 26.07.2013 20:56, brandao-dm wrote:
>
> Hi All,
>
> after the last online Update of my SLES 11 SP2, the sync Enginge will
> not start anymore.
>
> Couldn't find the issue I decided to update to the latest 1.2.5.299
> (coming from .250). Still the syncengine will not start.
>
> Looking into the engine.log file I found the Exception:
>
> EXCEPTION: WebFault: Server raised fault: 'No module named ext'
>
> Does anybody have an idea?


http://www.novell.com/support/kb/doc.php?id=7012948

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Highlighted
New Member.

Re: Syncengine not running after SLES 11 SP2 Online Update

Massimo, thanks!
Kb to new to be found (by me) ...
0 Likes
Highlighted
New Member.

Re: Syncengine not running after SLES 11 SP2 Online Update

Very good solution....
Thank You me to...
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Syncengine not running after SLES 11 SP2 Online Update

Hi Arne
Please apply latest SUSE patches (again). SUSE has fixed the python issue with a patch yesterday.

Thx, Kai
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Syncengine not running after SLES 11 SP2 Online Update

mrosen;2274677 wrote:

Support | GroupWise and Mobility connectors fail to start after updating python

The TID seems to be wrong. In step 3, the search term should be 'python-xml', not 'pyxml'.

Joost
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.