Quote:
Originally Posted by jkoyle  After installing (then re-installing) BES Professional Express and ZCB last night I now have a BB 8700 functioning. As mentioned in another post, it's not a simple install procedure.
The first time I installed then activated a device it sat on the waiting for services screen. I then removed the user and tried to re-add them, but BES wouldn't allow that as I was over the single user allotment in the free version (I haven't purchased any licenses from them yet).
I believe the initial problem I had was because I'm using an external GAL and the first email address listed in the GAL is firstname.lastname@domain.com. Zimbra accounts are setup with the account id of firstinitialLastname@domain.com.
So, I now have ZCB installed and it's syncing with the BB and looking good except for several warnings/errors in Windows Server Application event log. I see the following error:
CalICSSynchronizer::Initialize - OpenProperty failed: (0x80004002)
and the following warnings:
CalICSAgent::Start Could not Initialize Synchronizer for user@domain.com: (0x80004002)
{user@domain.com} DoICS() failed: ERR_FAIL
{user@domain.com} MsgMemStateDb::GetRefIdByEntryId(uc*,l) - EntryId is 0
{user@domain.com} MsgMemStateDb::AddMessageState - EntryId is invalid
Any idea what is causing those and how to clean them up?
Thanks,
John |
Hi John,
The first problem that you mention about the activation just sitting there is a problem that we see from time to time. RIM performs OTA activation via email. When you were waiting for the device to activate did you see a "special" message in that mailbox that was obviously generated by RIM? If you didn't see it...this was a latency issue with the cloud. We have seen this issue before. Also, BES needs to pick up that message and respond to it and sometimes this is not done in a timely fashion. Its probably due to many calendar events that it is trying to process while the activation request has been put it. This issue is outlined in the RIM knowledge base at the link below:
BlackBerry Search Results
The license issue that you saw was because, when you deleted the user, you need to wait for the BES Manager to purge it. You can force the purge in the "Users Pending Delete" tab of the manager. Once that user is purged, you can reprovision them. Otherwise, you have to wait for the Manager to eventually purge them.
Regarding the error messages. They are not fatal error messages and we are aware of them.
I was wondering what your plan was for this BES. How many users do you plan to provision (once you buy the licenses) and how quickly do you plan to ramp this up?
Thanks so much for your feedback!
--Tony