Hello Leonardo!

Here the last status from Friday late afternoon.

>-----Ursprüngliche Nachricht-----
>Von: User support <user at open-xchange.org>
>Gesendet: 12.01.07 10:47:47
>An: User support <user at open-xchange.org>
>Betreff: Re: [OX User] Outlook Connector Crashing when Calendar data is
>processed - OXLook
>On Jan 12, 2007 10:06 AM, JU <magog001 at web.de> wrote:
>
>>Hello!
>
>Hello,
>
>>We have this problem sind end of december 2006 with two new groupware
>>user which
>>need the Connector to sync with their Windows PDAs.
>>
>>We've tested OXLook v3.8.9, v4.0.18, v4.2.3 and v4.2.5.
>>
>>The Groupware Server is still 0.8.0-6 as the currently available
>>OpenSource
>>0.8.2-x has an error at the project tasks (no access) which has been
>>fixed on 31.08.2006. This doesn't help when it's not released as
>>OpenSource.
>
>Please update to the newest server version.

Release the current version as OpenSource which includes the following
fix (see below) I'll update ASAP
I only need to apply our developed addon/patches and after a test it
will be installed.

BugZilla:
http://www.open-xchange.org/bugzilla/show_bug.cgi?id=2994


> >From the stacktrace I can see that the XML that comes from the server
> >is
>not valid. Please try to sniff the connection to see whats wrong.

I've already done that but nothing shows up that may be the problem or I
can't see it.
I assume you can access the official tickes so look at this one:
Ticket#2007010510000814

I can attach the complete output I stored Friday morning where I got an
error on my private Notebook (OXLook v4.2.5, Outlook Crash Dump, OXLook
Debugger Output and Captured Data (using EtherDetect on Windows)).


On Friday afternoon we tried the following:
==============================
1.) With my VFPData Converter (VFPDC) I retrieved all data from OX
0.8.0-6 (Productive) and stored it locally (XML files)
2.) Removed all data from OX 0.8.0-6 by uploading the data just stored
with the "DELETE" option from VFPDC.
3.) Created the user on the Development system which uses OX 0.8.2-0
(first OpenSource release of 0.8.2).
4.) Created new Outlook profile, installed OXLook v4.2.5, deleted
Partnership? with PDA
5.) Created one calendar entry in Outlook and one entry on the Groupware
6.) Synced Outlook <--> OX 0.8.2-0 (Development).
7.) No problems, everything works
8.) Deleted both entries
--
9.) Started regedit and modified the server url (changed it back to the
0.8.0-6 productive server)
10.) Restart PC
11.) Pushed the data saved in step 1 back into 0.8.0-6 production
server, so they seem to be "NEW" to OXLook/Outlook and get synchronized
to Outlook.
12.) Started Outlook and synced with the production server
13.) All data there --- YES!!!

So far so good!

14.) Added PDA (using ActiveSync v4.2)
15.) Synced PDA with Outlook
16.) Data transfered but....

The problem we now have...
-If you create an appointment on the PDA it is correct in Outlook and OX
v0.8.0-6.
-If you create an appointment in Outlook its okay in OX v0.8.0-6 and
PDA.
-If you create an appointment at the Groupware Server the entry on the
PDA is not stored at the given day and timeframe. Instead the
appointment shows up the following day as for the complete day
(Ganztagestermin).
Interesting thing is that it's ok in Outlook. The only difference
between appointments created at the Groupware and those from Outlook is
that appointments created at the Groupware don't show up with the "Face"
symbol (no Tab/Karteireiter "Status" - if you open the appointment entry
in Outlook). I think this is normal.


We've searched Google an found that this has also been a problem other
users had. The solution to set the correct timezone doesn't work as it
is already correct.
This was the result with OXLook v4.2.5.
Then we tried OXLook v4.2.3. There it's sometimes correct and sometimes
not. --> Not useable because unstable behaviour.
The most stable connector we tried so far is v3.8.9 but it doesn't work
at all this time (no sync).

AHHHH!


We didn't have the time to log the traffic as the user wanted to get
home and took the PDA with him.
Next try on Tuesday. I've restarted the server processes on Sunday
evening.


Kind regards,
Jürgen Ulbts

-- 
IBIT - Groupware Administration
https://groupware.uni-oldenburg.de
http://www.uni-oldenburg.de/groupware