BES 5 calendar sync (won't sync from phone to calendar)
- I have recently installed a test environment for the BES version 5 to evaluate this before an eventual upgrade. After using the transporter tool to move a few users from the production environment to the test environment i've been having some issues with calendar sync.
The problem is that appointments that are created on the phones connected to the BES5 environment wont sync in to Outlook, but if I create an appointment in outlook it is sent to the BB unit within seconds.
I am guessing that this is just a policy issue or something like that but I have not found any solutions yet.08-19-09 03:00 AMLike 0 -
- What server OS and service pack level for the BES 5 server and what version of Exchange?
And you have to make sure and install the Exchange System Manager components on the BES if you are running an Exchange 2003 environment. Just having the files isn't enough. Also make sure your Exchange SPs match; if you have Exchange SP2 on the Exchange server, you install Exch SP2 for the Exchange components on the BES as well. This is also a common oversight.
Check permissions once again, and make sure the users you are testing on aren't members of a protected group (this one has bitten me in the @ss several times).
It really sounds like a permissions issue (BESAdmin can open mailbox to see the changes and writes to BES and subsequently the handheld, but cannot write back to the mailbox). In Active Directory Users and Computers go into the testing users properties and make sure you see the BESAdmin rights propagating all the way down to the Exchange permissions for the individual users.
I know this is redundant and basic stuff, but I am stabbing in the dark without more environment info. If you want more detailed help, PM me. I have deployed several BES 5 servers already into production environments.08-19-09 04:02 AMLike 0 - Try to switch service account... Create new account mailbox and give all permissions required to it. And then switch BES to this new service account...08-19-09 04:14 AMLike 0
- BES5:
Windows 2003 server standard R2 SP2
BES 5.0.0 MR1 bundle 236
cdo.dll 6.5.7654.12
Exchange System Manager components installed with SP2
Exchange:
Windows 2003 server SP2
Exchange 2003 SP2
cdo.dll 6.5.7654.12
I haven't created any groups on the BES5 yet so this should not be an issue, right?
I know it sounds like an permission issue and i would think the same, however the same besadmin account is in use for the production environment here and in this environment the users CAN sync contacts from BB to outlook.
I really appreciate every reply here so just keep 'em coming08-19-09 04:18 AMLike 0 - Dumb question: Anything coming up in the Windows Application Event Log or BES logs?
Try and do a Reconcile Now from Messages when there are items to push from handheld to Exchange Calendar and see if anything pops up in the log. Also, check BES log for that time period and see if there is anything. Post log results here if there is relevant info please.
I will check back in the morning. Server maintenance I have been working on is finally done so I am going to bed now. 2:30am PST. Bed time for IT people.08-19-09 04:26 AMLike 0 - I had one of these warnings for every user on the BES5 in the application log in event viewer:
Event Type: Warning
Event Source: BlackBerry Messaging Agent XXXXXBES002 Agent 1
Event Category: None
Event ID: 20216
Date: 8/19/2009
Time: 9:53:02 AM
User: N/A
Computer: XXXXXBES002
Description:
{[email protected]} Synchronize() failed: ERR_FAIL, Tag=1856
Any particular BES logs i should keep an eye on when attempting the reconcile now?08-19-09 04:28 AMLike 0 - OK so i received a couple of warning messages in the application event log on the BES5 server, all of them occured after first deleting the calendar service book and resending service books from server.
Then i noticed that the CICAL did not reappear on the phone so i undeleted the service book. After this I did the "reconcile now" feature under messages and here are the errors that was generated in the minutes after these actions were performed:
1#
Event Type: Warning
Event Source: BlackBerry Synchronization Service
Event Category: None
Event ID: 20000
Date: 8/19/2009
Time: 11:23:05 AM
User: N/A
Computer: XXXXXXBES002
Description:
[BIPPe] WARNING: Using default BIPP shared secret
2#
Event Type: Warning
Event Source: BlackBerry Messaging Agent XXXXXXBES002 Agent 1
Event Category: None
Event ID: 20216
Date: 8/19/2009
Time: 11:25:04 AM
User: N/A
Computer: XXXXXXBES002
Description:
{user@domain} Synchronize() failed: ERR_FAIL, Tag=1928
The first error occured twice and the second one occured three times. the user it is referring to is the same user i tried the reconcile now & service books stuff with...08-19-09 04:33 AMLike 0 - BIPP errors are normal. Just telling you it is using the default BIPP key since you don't have a custom one specified.
Another dumb question: When you installed BES, were you logged in as the BESAdmin account and does that account have full local admin rights on the BES server?
I googled and found similiar problems on 4.1 from being logged in as an account other than the BESAdmin when installing BES. This would also apply to BES 5.08-19-09 04:46 AMLike 0 - BES5 was installed with the besadmin user logged in. I actually performed the installation with a RIM support technician monitoring the process over WebEx so I would like to think that atleast the installation was performed correctly
I just noticed however that the mailflow has also stopped on the phones connected to this test environment... I'm not sure why this is, i tested the BB messenger as well but somehow this worked (go figure)...08-19-09 04:51 AMLike 0 - Only other thing I can come up with is corruption in the mailbox. Can you create a clean dummy user, setup on BES, activate to a handheld, and test it that way? Only other item I can come up with offhand is mismtached Exchange .dlls which we have ruled out.
Also, try and reboot the BES. We had several issues with our when we first brought it up on 5. There were some Java issues among others. Reboot seemed to clear everything else up and now it is okay.08-19-09 04:56 AMLike 0 - Here are a couple of lines from a BES log that i suspect might be relevant in this case:
Code:[30002] (08/19 12:12:16.708):{0x19A8} Server = exhcluster01, Mailbox = /o=XXXX/ou=First Administrative Group/cn=Recipients/cn=ss Description = The information store could not be opened. [MAPI 1.0 - [MAPI_E_LOGON_FAILED(80040111)]] [30180] (08/19 12:12:16.708):{0x19A8} {ss} CDOCalendar::Initialize - Error in call m_spCalendarFolder = m_spCDOSession->GetDefaultFolder [40000] (08/19 12:12:16.708):{0x19A8} CDO initializing failure in CDO helper 05A77008 (4) [30002] (08/19 12:12:23.365):{0x19A8} Server = exhcluster01, Mailbox = /o=XXXXX/ou=First Administrative Group/cn=Recipients/cn=ofl Description = The information store could not be opened. [MAPI 1.0 - [MAPI_E_LOGON_FAILED(80040111)]] [30180] (08/19 12:12:23.365):{0x19A8} {ofl} CDOCalendar::Initialize - Error in call m_spCalendarFolder = m_spCDOSession->GetDefaultFolder [40000] (08/19 12:12:23.365):{0x19A8} CDO initializing failure in CDO helper 05A77008 (4)
Code:[30311] (08/19 12:22:06.570):{0x16EC} {Lund} Forwarding status to relay, intTag=2276, Tag=7476472, Status=1 [30222] (08/19 12:22:06.586):{0x16FC} {Lund} MTH: contentType=CMIME, sizeOTA=100, sizeOTW=26, TransactionId=-896807456, Tag=7905 [30310] (08/19 12:22:06.586):{0x16FC} {Lund} Forwarding internal data to device, contentType=CMIME, routing=T96475811, device=2100B2D7, size=137, cmd=0x3, ack=0, TransactionId=-896807456, intTag=1806, Tag=7905, Submit=1 [30368] (08/19 12:22:07.598):{0x16F4} {Lund} Packet has been delivered to device, Tag=7905 [30388] (08/19 12:22:07.598):{0x16F4} [BIPPa] {Lund} Forwarding status to BES Agent (T96475811_001), intTag=1806, extTag=7905 [30450] (08/19 12:22:20.854):{0x1724} {Lund} User unchanged (disp): id=1, [email protected], device=2100B2D7, routing=T96475811, agent=001, time=4A88317D, ext=1, wl=0, keys=(A:A:A) [30222] (08/19 12:22:25.355):{0x1728} {Lund} MFH: contentType=CICAL, sizeOTA=116, sizeOTW=49, TransactionId=1031478679, Tag=7476473 [30308] (08/19 12:22:25.355):{0x1728} [BIPPa] {Lund} Forwarding CICAL data to BES Agent (T96475811_001), size=85, intTag=2277, Tag=7476473
also a bunch of these errors popped up in eventviewer just now :
Code:Event Type: Error Event Source: BlackBerry Router Event Category: None Event ID: 10000 Date: 8/19/2009 Time: 12:12:52 PM User: N/A Computer: XXXXXXBES002 Description: [SERVICE_RELAY_SESSION:T96475811:0x003FF348] Service transaction not found. SERVICESESSION_TAG=7476442
Last edited by lund; 08-19-09 at 05:27 AM.
08-19-09 05:17 AMLike 0 - IEMStest output from BES5 test server:
Code:╪ivind Fosheim Lund: Opening message store using /o=Terra Drift/ou=First Administrative Group/cn=Recipients/cn=ofl /o=Terra Drift/ou=First Administrative Group/cn=Configuration/cn=Servers /cn=EXHCLUSTER01/cn=Microsoft Private MDB ╪ivind Fosheim Lund: Mailbox opened successfully ╪ivind Fosheim Lund: Root Folder opened successfully ╪ivind Fosheim Lund: Folder created successfully ╪ivind Fosheim Lund: Test folder deleted successfully ╪ivind Fosheim Lund: MAPI test completed successfully ╪ivind Fosheim Lund: CDO Server Name: EXHCLUSTER01 ╪ivind Fosheim Lund: CDO Mailbox DN: /o=Terra Drift/ou=First Administrative Grou p/cn=Recipients/cn=ofl ╪ivind Fosheim Lund: CDO logon successful ╪ivind Fosheim Lund: CDO COM exception: Code = 800406f9, WCode = 04f9, Code mean ing = IDispatch error #1273 Description = The information store could not be opened. [MAPI 1.0 - [MAPI_E _LOGON_FAILED(80040111)]]. ╪ivind Fosheim Lund: CDO test failed ╪ivind Fosheim Lund: No Send As permission for the {TERRA-GRUPPEN\besadmin} acco unt operator.
IEMStest output from BES4.6 production server (both using the same BESADmin user):
Code:BlackBerry Enterprise Server Utility - IEMSTest.exe (IExchangeManageStore), Vers ion 1.0 Copyright (c) Research In Motion, Ltd. 1999. All rights reserved. Opening Default Message Store Mailbox - BESAdmin. Opening message store for ╪ivind Fosheim Lund using /o=Terra Drift/ou=First Admi nistrative Group/cn=Recipients/cn=ofl /o=Terra Drift/ou=First Administrative Gro up/cn=Configuration/cn=Servers/cn=EXHCLUSTER01/cn=Microsoft Private MDB. ╪ivind Fosheim Lund's Mailbox opened successfully. Root Folder opened successfully. Folder created successfully. Test folder deleted successfully. Test completed successfully for ╪ivind Fosheim Lund.
Last edited by lund; 08-19-09 at 06:47 AM.
08-19-09 06:39 AMLike 0 - Wow, this is kind of embarrassing but I finally figured out what the issue was and how to fix it.
Sometimes you just have to look in the most obvious of places!
The test server I have was placed in a 172.21.50 network, however the exchange server is in a 172.21.40 network and there are no DNS servers to resolve the name of the exhcange server when the BES was trying to reach it.
Obviously all i needed was an entry in the hosts file to make the BES server able to reach the exchange server by name and once this was set up, i could both browse the public folder store and the mailbox store through the Exchange System Administrator on the BES and the Blackberry devices on this server can now write appointments to the outlook calendar.
If I had only started this day with pinging the exchange server from the BES then all of this could have been avoided, i'll take it as a lesson in life and next time I will remember to look at the most basic possibilities
Thank you very much for the responces and suggestions given here today, it has been a learningful experience in many ways08-19-09 08:45 AMLike 0 -
- I was so hopeful reading the first page of posts because it's the same issue I'm having, but reading the solution disappointed me because that's not my problem.
Glad you got it working, I'm still poring over logs. Something changed 2 weeks ago while I was on vacation and I'm lost as to what it is.08-21-09 10:31 AMLike 0 - Sorry to disappoint you
but you have the same problem and it just occured without any changes in the BES or Exchange environment?
have you checked the cdo.dll versions, maybe the exchange server got an update?
there are various things that can cause this issue like a lack of permissions, hidden mailboxes etc...
what happens if you run the IEMScheck tool?08-21-09 10:43 AMLike 0 - Sorry to disappoint you
but you have the same problem and it just occured without any changes in the BES or Exchange environment?
have you checked the cdo.dll versions, maybe the exchange server got an update?
there are various things that can cause this issue like a lack of permissions, hidden mailboxes etc...
what happens if you run the IEMScheck tool?08-21-09 11:12 AMLike 0 - Got it, I went back through the tutorial and re-ran everything and it's fine now. I couldn't find exactly what was missing, but it's good now.
More Pieces � Blog Archive � Switch BES Admin Accounts08-21-09 12:52 PMLike 0
- Forum
- Enterprise
- BlackBerry Secure UEM & Productivity Suites
BES 5 calendar sync (won't sync from phone to calendar)
« Blackberry Web Desktop Manager not recognizing associated devices
|
Exchange 2007 and BES Admin Account Migration »
LINK TO POST COPIED TO CLIPBOARD