You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Office XP SP2 / 3 and ActiveSync 3.8.1 Recurring appt error
| |
| martin.perceval@bankofengland.co.uk 2005-10-24, 4:48 pm |
| Hello all,
Having a bit of an issue around Office XP SP2/3 and ActiveSync 3.8.1.
Here is the scenario:
1. A recurring appointment is created by a user on a machine running
Office XP SP2 and sent to one or more recipients.
2. A recipient accepts the recurring appointment on a machine running
Office XP SP3 and syncs with his/her PDA. No problem so far.
3. The originator of the appointment updates an instance of the
recurring appointment on a machine running Office XP SP2 and an update
is sent to all recipients.
4. A recipient tries to sync the updated appointment to their PDA and
they get the following message :
"ActiveSync Error - One recurring appointment cannot be read from
Microsoft Outlook due to error 80180F02. this item will not be
synchronizes with the mobile device"
The following errors are reported in the wcesmgr.log (pls bear in mind
that the log file is showing three 'dodgy' appointments - as a result
of our testing):
2005-10-24 14:32:24 00000260 - **** Starting synchronization of all
out-of-date items
2005-10-24 14:32:24 00000260 - Synchronizing 4 items
2005-10-24 14:32:24 00000260 - ERROR returned in function
CReplEntry::Synchronize. hr: 0x80140101
2005-10-24 14:32:24 00000260 - ERROR: unable to sync type 1 of
[Appointment, 0, 0xE0023BC].
2005-10-24 14:32:24 00000260 - One Appointment item [Vol: 0, Oid:
0x0E0023BC] flagged, SyncType: LOCAL_CHG
2005-10-24 14:32:24 00000260 - ERROR returned in function
CReplEntry::Synchronize. hr: 0x80140101
2005-10-24 14:32:24 00000260 - ERROR: unable to sync type 1 of
[Appointment, 0, 0x7002567].
2005-10-24 14:32:24 00000260 - One Appointment item [Vol: 0, Oid:
0x07002567] flagged, SyncType: LOCAL_CHG
2005-10-24 14:32:25 00000260 - ERROR returned in function
CReplEntry::Synchronize. hr: 0x80140101
2005-10-24 14:32:25 00000260 - ERROR: unable to sync type 1 of
[Appointment, 0, 0x20000064].
2005-10-24 14:32:25 00000260 - One Appointment item [Vol: 0, Oid:
0x20000064] flagged, SyncType: LOCAL_CHG
2005-10-24 14:32:25 00000260 - WARNING: Processing NACK: FromDevice: 1,
[SSPId: 0x10002, Oid: 0x0E0023BC, Hr: 0x80140101, Flags: 0x00000000]
2005-10-24 14:32:25 00000260 - Failed to sync a [Appointment, 0,
0xE0023BC] object because of error 0x80140101
2005-10-24 14:32:25 00000260 - One Appointment item [Vol: 0, Oid:
0x0E0023BC] flagged, SyncType: LOCAL_CHG
2005-10-24 14:32:25 00000260 - WARNING: Processing NACK: FromDevice: 1,
[SSPId: 0x10002, Oid: 0x07002567, Hr: 0x80140101, Flags: 0x00000000]
2005-10-24 14:32:25 00000260 - Failed to sync a [Appointment, 0,
0x7002567] object because of error 0x80140101
2005-10-24 14:32:25 00000260 - One Appointment item [Vol: 0, Oid:
0x07002567] flagged, SyncType: LOCAL_CHG
2005-10-24 14:32:25 00000260 - WARNING: Processing NACK: FromDevice: 1,
[SSPId: 0x10002, Oid: 0x20000064, Hr: 0x80140101, Flags: 0x00000002]
2005-10-24 14:32:25 00000260 - Failed to sync a [Appointment, 0,
0x20000064] object because of error 0x80140101
2005-10-24 14:32:25 00000260 - One Appointment item [Vol: 0, Oid:
0x20000064] flagged, SyncType: LOCAL_CHG
2005-10-24 14:32:25 00000260 - **** Completed synchronization
We could not replicate the errors when all user's machines were running
Office XP SP3. Any help would be greatly appreciated.
Martin Perceval
| |
| Chris De Herrera 2005-10-24, 4:48 pm |
| Hi,
The error you are seeing is actually from ActiveSync's requests to Outlook's
APIs. So from the error I would suspect that there was a problem with the
users PST file. A detect & repair or scanpst would probably fix it.
--
Chris De Herrera
http://www.pocketpcfaq.com
http://www.tabletpctalk.com
http://www.pocketpctalk.com
http://www.mobilitytalk.com
<martin.perceval@bankofengland.co.uk> wrote in message
news:1130163618.907274.59060@o13g2000cwo.googlegroups.com...
> Hello all,
>
> Having a bit of an issue around Office XP SP2/3 and ActiveSync 3.8.1.
> Here is the scenario:
>
> 1. A recurring appointment is created by a user on a machine running
> Office XP SP2 and sent to one or more recipients.
>
> 2. A recipient accepts the recurring appointment on a machine running
> Office XP SP3 and syncs with his/her PDA. No problem so far.
>
> 3. The originator of the appointment updates an instance of the
> recurring appointment on a machine running Office XP SP2 and an update
> is sent to all recipients.
>
> 4. A recipient tries to sync the updated appointment to their PDA and
> they get the following message :
>
> "ActiveSync Error - One recurring appointment cannot be read from
> Microsoft Outlook due to error 80180F02. this item will not be
> synchronizes with the mobile device"
>
> The following errors are reported in the wcesmgr.log (pls bear in mind
> that the log file is showing three 'dodgy' appointments - as a result
> of our testing):
>
> 2005-10-24 14:32:24 00000260 - **** Starting synchronization of all
> out-of-date items
> 2005-10-24 14:32:24 00000260 - Synchronizing 4 items
> 2005-10-24 14:32:24 00000260 - ERROR returned in function
> CReplEntry::Synchronize. hr: 0x80140101
> 2005-10-24 14:32:24 00000260 - ERROR: unable to sync type 1 of
> [Appointment, 0, 0xE0023BC].
> 2005-10-24 14:32:24 00000260 - One Appointment item [Vol: 0, Oid:
> 0x0E0023BC] flagged, SyncType: LOCAL_CHG
> 2005-10-24 14:32:24 00000260 - ERROR returned in function
> CReplEntry::Synchronize. hr: 0x80140101
> 2005-10-24 14:32:24 00000260 - ERROR: unable to sync type 1 of
> [Appointment, 0, 0x7002567].
> 2005-10-24 14:32:24 00000260 - One Appointment item [Vol: 0, Oid:
> 0x07002567] flagged, SyncType: LOCAL_CHG
> 2005-10-24 14:32:25 00000260 - ERROR returned in function
> CReplEntry::Synchronize. hr: 0x80140101
> 2005-10-24 14:32:25 00000260 - ERROR: unable to sync type 1 of
> [Appointment, 0, 0x20000064].
> 2005-10-24 14:32:25 00000260 - One Appointment item [Vol: 0, Oid:
> 0x20000064] flagged, SyncType: LOCAL_CHG
> 2005-10-24 14:32:25 00000260 - WARNING: Processing NACK: FromDevice: 1,
> [SSPId: 0x10002, Oid: 0x0E0023BC, Hr: 0x80140101, Flags: 0x00000000]
> 2005-10-24 14:32:25 00000260 - Failed to sync a [Appointment, 0,
> 0xE0023BC] object because of error 0x80140101
> 2005-10-24 14:32:25 00000260 - One Appointment item [Vol: 0, Oid:
> 0x0E0023BC] flagged, SyncType: LOCAL_CHG
> 2005-10-24 14:32:25 00000260 - WARNING: Processing NACK: FromDevice: 1,
> [SSPId: 0x10002, Oid: 0x07002567, Hr: 0x80140101, Flags: 0x00000000]
> 2005-10-24 14:32:25 00000260 - Failed to sync a [Appointment, 0,
> 0x7002567] object because of error 0x80140101
> 2005-10-24 14:32:25 00000260 - One Appointment item [Vol: 0, Oid:
> 0x07002567] flagged, SyncType: LOCAL_CHG
> 2005-10-24 14:32:25 00000260 - WARNING: Processing NACK: FromDevice: 1,
> [SSPId: 0x10002, Oid: 0x20000064, Hr: 0x80140101, Flags: 0x00000002]
> 2005-10-24 14:32:25 00000260 - Failed to sync a [Appointment, 0,
> 0x20000064] object because of error 0x80140101
> 2005-10-24 14:32:25 00000260 - One Appointment item [Vol: 0, Oid:
> 0x20000064] flagged, SyncType: LOCAL_CHG
> 2005-10-24 14:32:25 00000260 - **** Completed synchronization
>
>
> We could not replicate the errors when all user's machines were running
> Office XP SP3. Any help would be greatly appreciated.
>
> Martin Perceval
>
| |
| martin.perceval@bankofengland.co.uk 2005-10-25, 5:45 am |
| Hi Chris,
Thanks for getting in touch. Maybe I need to give some more
background. We do not run Outlook with PST files - we run Exchange
2000 at the back-end.
If you wipe the handheld after receiving the updated instance of the
appointment then it will subsequently sync correctly. This gives the
impression that ActiveSync is having trouble reconciling the updated
appointment with the original.
In addition, I have also reversed the tests. I configured a handheld
on a machine running Office XP SP2. Created and updated the
appointments on an Office XP SP3 machine and the handheld synced
perfectly.
Office XP SP3 does update the Outlook security model to bring it in
line with Outlook 2003. Maybe these programmatic blocks are affecting
ActiveSync's ability to update the appointment?
Anymore suggestions would be appreciated. We cannot be the only
organisation experiencing this problem ( or at least - I hope that we
aren't)
Thanks
Martin
|
|
|
|
|
This is interesting: