my name is Marcin Zastawny (from a company called Infocon in Poland).
We use M-Business for Linux 5.7 b48 on Linux (Application edition), with
clients based on 5.7 build 32 (Microsoft Windows Mobile devices ie. PockePC
Back in august last year, we exchanged the certificate file issued by
avantgo (you might remember this: http://www.sybase.com/detail?id=1029262 ).
Things have been quite smooth until a few weeks ago, where "please update
your ssl certificate" alerts have been popping up on some of the PDAs
syncing via the cradle (this does NOT apply to GPRS syncs).
Surely the situaltion can be resolved by switching to a non ssl port, but
that is not the best solution.
I have not tried to reinstall those mbusiness windows setup files, but then
again these were working fine all this time, until now.
Maybe some Windows Patch has done this? (these are all Windows XP machines,
although we have not yet tested on other machines).
Has anyone seen a similar situation?
I am posting this, because maybe somebody has gone through all the different
tests already ?
Thanks in advance for any answers that might help.
PS - I will post my findings once we solve the issue.
From: "Marcin Zastawny" <firstname.lastname@example.org>
Subject: certificate expiry
X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Date: 29 Nov 2005 12:08:44 -0800
X-Trace: forums-1-dub 1133294924 126.96.36.199 (29 Nov 2005 12:08:44 -0800)
X-Original-Trace: 29 Nov 2005 12:08:44 -0800, 188.8.131.52
Xref: forums-1-dub ianywhere.public.mbusinessanywhere.general:649
Article PK: 9002
Subject: Re: certificate expiry
X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
X-RFC2646: Format=Flowed; Original
Date: 29 Nov 2005 18:55:36 -0800
X-Trace: forums-1-dub 1133319336 10.22.120.220 (29 Nov 2005 18:55:36 -0800)
X-Original-Trace: 29 Nov 2005 18:55:36 -0800, vpn-dub-220.sybase.com
Xref: forums-1-dub ianywhere.public.mbusinessanywhere.general:652
Article PK: 17751
This is not an issue that has been reported before you should contact