Having Difficulties Syncing Calendar

Are you using the Zimbra Connector for BlackBerry? Post your comments and questions here.
wagazarm
Posts: 18
Joined: Fri Sep 12, 2014 11:11 pm

Having Difficulties Syncing Calendar

Postby wagazarm » Mon Sep 08, 2008 3:21 pm

I updated to BETA3 and now I seem to be having problems with calendar appointments not synchronizing properly.
I'm taking a look in the Outlook log and this is what I see:
08-09-2008 12:41:10.323 [4184]: ----------------------------------

08-09-2008 12:41:10.323 [4184]: 1 rows Unmapped:

08-09-2008 12:41:10.323 [4184]: Zimbra::Store::ZimbraMAPITable::RestoreMappedRow. mapped rows

08-09-2008 12:41:10.323 [4184]: ___________________________________

08-09-2008 12:41:10.323 [4184]: 1 rows

08-09-2008 12:41:10.323 [4184]: PR_ROW_TYPE PT_LONG x1 or 1

08-09-2008 12:41:10.323 [4184]: PR_DEPTH PT_LONG x0 or 0

08-09-2008 12:41:10.323 [4184]: PR_INSTANCE_KEY PT_BINARY 4;00201844

08-09-2008 12:41:10.323 [4184]: UNKNOWN (6670) PT_BINARY 24;000000003015C9B746313742B00A6C55D00DB63C44182000

08-09-2008 12:41:10.323 [4184]: PR_ENTRYID PT_BINARY 24;000000003015C9B746313742B00A6C55D00DB63C44182000

08-09-2008 12:41:10.323 [4184]: PR_MESSAGE_CLASS PT_UNICODE IPM.Appointment

08-09-2008 12:41:10.323 [4184]: UNKNOWN (1080) PT_ERROR MAPI_E_NOT_FOUND

08-09-2008 12:41:10.323 [4184]: PR_NORMALIZED_SUBJECT PT_UNICODE July 4th holiday

08-09-2008 12:41:10.323 [4184]: PR_SUBJECT PT_UNICODE July 4th holiday

08-09-2008 12:41:10.323 [4184]: PR_CONVERSATION_TOPIC PT_UNICODE July 4th holiday

08-09-2008 12:41:10.323 [4184]: UNKNOWN (e2c) PT_ERROR MAPI_E_NOT_FOUND

08-09-2008 12:41:10.323 [4184]: PR_MESSAGE_FLAGS PT_LONG x9 or 9

08-09-2008 12:41:10.323 [4184]: PR_STORE_ENTRYID PT_BINARY 310;0000000038A1BB1005E5101AA1BB08002B2A56C200004C534D5353502E444C4C00000000000000004E495441F9BFB80100AA0037D96E0000000043003A005C0044006F00630075006D0065006E0074007300200061006E0064002000530065007400740069006E00670073005C00410064006D0069006E006900730074007200610074006F0072002E004D0041005200540049004E004400490052004500430054005C004C006F00630061006C002000530065007400740069006E00670073005C004100700070006C00690063006100740069006F006E00200044006100740061005C004D006900630072006F0073006F00660074005C004F00750074006C006F006F006B005C0042006C00610063006B0042006500720072007900530065007200760065007200310039002E007A00640062000000

08-09-2008 12:41:10.323 [4184]: PR_PARENT_ENTRYID PT_BINARY 24;000000003015C9B746313742B00A6C55D00DB63C42810000

08-09-2008 12:41:10.323 [4184]: PR_MSG_STATUS PT_LONG x0 or 0

08-09-2008 12:41:10.323 [4184]: Named Property (80a2) PT_UNICODE

08-09-2008 12:41:10.323 [4184]: Named Property (807b) PT_BOOLEAN True

08-09-2008 12:41:10.323 [4184]: Named Property (800b) PT_SYSTIME 7/4/2006 0:0:0

08-09-2008 12:41:10.323 [4184]: Named Property (807c) PT_LONG xf or 15

08-09-2008 12:41:10.323 [4184]: Named Property (807e) PT_SYSTIME 7/3/2009 23:45:0

08-09-2008 12:41:10.323 [4184]: Named Property (8003) PT_BINARY 80;043004300D200200000020FA03000C0000000000000004000000232000000A000000000000000000000000000000E04DB60CDF80E95A063000000930000000000000A005000000000000000000000000

08-09-2008 12:41:10.323 [4184]: Named Property (80ec) PT_BOOLEAN False

08-09-2008 12:41:10.323 [4184]: Named Property (80ee) PT_ERROR MAPI_E_NOT_FOUND

08-09-2008 12:41:10.323 [4184]: Named Property (80ef) PT_ERROR MAPI_E_NOT_FOUND

08-09-2008 12:41:10.323 [4184]: Named Property (8008) PT_BINARY 48;E001000000000000C4FFFFFF000000000B00000001000200000000000000000000000300000002000200000000000000

08-09-2008 12:41:10.323 [4184]: Named Property (806e) PT_ERROR MAPI_E_NOT_FOUND

08-09-2008 12:41:10.323 [4184]: Named Property (809e) PT_ERROR MAPI_E_NOT_FOUND

08-09-2008 12:41:10.338 [4184]: Named Property (809f) PT_ERROR MAPI_E_NOT_FOUND

08-09-2008 12:41:10.338 [4184]: Named Property (80a6) PT_ERROR MAPI_E_NOT_FOUND

08-09-2008 12:41:10.338 [4184]: Named Property (80a0) PT_ERROR MAPI_E_NOT_FOUND

08-09-2008 12:41:10.338 [4184]: Named Property (809c) PT_BOOLEAN False

08-09-2008 12:41:10.338 [4184]: Named Property (809d) PT_ERROR MAPI_E_NOT_FOUND

08-09-2008 12:41:10.338 [4184]: Named Property (80a4) PT_ERROR MAPI_E_NOT_FOUND

08-09-2008 12:41:10.338 [4184]: Named Property (807a) PT_BOOLEAN True

08-09-2008 12:41:10.338 [4184]: Named Property (80a3) PT_ERROR MAPI_E_NOT_FOUND

08-09-2008 12:41:10.338 [4184]: Named Property (800c) PT_ERROR MAPI_E_NOT_FOUND

08-09-2008 12:41:10.338 [4184]: Named Property (8001) PT_BOOLEAN True

08-09-2008 12:41:10.338 [4184]: ----------------------------------

08-09-2008 12:41:10.338 [4184]: Mapped:

08-09-2008 12:41:10.338 [4184]: Zimbra::Store::ZimbraMAPITable::RestoreMappedRow. table parent folder: Reminders

08-09-2008 12:41:10.338 [4184]: Zimbra::Store::ZimbraMAPITable::RestoreMappedRow. unmapped rows

08-09-2008 12:41:10.338 [4184]: ___________________________________

That same error about MAPI can be found in the Blackberry Agent log as well.
Could that be the problem?
I checked windowssystem32 and the mapi32.dll file was 135kb, and I noticed it had a date modified date of 12/10/2002! This was different from the one I had previously. I checked the driver signature and it said it was for Exchange SP3! The mapi32.dll.zco file was 113kb so I renamed the existing mapi32.dll and replaced it with a copy of the mapi32.dll.zco file.
I cannot reboot the box yet to see if this completely resolves things, but as of now I am still getting this error and calendar appointments are not completely synchronizing.


wagazarm
Posts: 18
Joined: Fri Sep 12, 2014 11:11 pm

Having Difficulties Syncing Calendar

Postby wagazarm » Tue Sep 09, 2008 8:40 am

Okay well, rebooting the system definitely solved the problem but the error about "MAPI_E_NOT_FOUND" still exists.
10339alee
Zimbra Alumni
Zimbra Alumni
Posts: 406
Joined: Fri Sep 12, 2014 10:31 pm

Having Difficulties Syncing Calendar

Postby 10339alee » Sun Sep 21, 2008 12:42 am

[quote user="wagazarm"]Okay well, rebooting the system definitely solved the problem but the error about "MAPI_E_NOT_FOUND" still exists.[/QUOTE]
that is not an error. it is legit to ask for a property via MAPI w/o it existing.

when scanning the logs...exceptions are the easiest ways to track a potential issue unless it is an RPC exception in the wait set code, that is ok too.
--Tony
wagazarm
Posts: 18
Joined: Fri Sep 12, 2014 11:11 pm

Having Difficulties Syncing Calendar

Postby wagazarm » Mon Sep 22, 2008 9:48 am

Thanks Tony. I appreciate the response!

Return to “Zimbra Connector for Blackberry”

Who is online

Users browsing this forum: No registered users and 4 guests