BES and ZCB Beta 3 ... single device ..arrgh

[nlongmuir]

I've been struggling with Zimbra support over intermittent problems regarding a new deployment of ZCB Beta 3

I have a new installation of Zimbra version 5.0.8, ZCB Beta 3 and the latest BES server. Outlook 2007 is installed and SP'd

What I'm seeing is a device which initially was refusing to be deployed, I then made sure the BES services were started according to the correct sequence (although if your reboot your machine as I do since it is a VM and has no users currently on it, the start sequence is not an issue).

I managed to deploy the device (although I still saw errors/warnings in the event viewer re: user sync failures )

The device seems to be limping along re: receiving and sending email but the calendar syncing is definitely sick, in fact syncing in general seems to be suspect.

The appropriate logs have been sent to support but I just wanted to see if others were affected.

My only suspect in all this would seem to be the device ( a BB 7000 series) as I will be sure to have the latest OS on it tomorrow and try again.

Cheers

[nlongmuir]

9/4/2008 9:51 AM | Neil Longmuir


The following are the three repeating errors from the event viewer

**************** ONE *****************************

Event Type: Error
Event Source: BlackBerry Messaging Agent SMS-BES-SCALAR Agent 1
Event Category: None
Event ID: 10007
Date: 9/4/2008
Time: 9:21:30 AM
User: N/A
Computer: SMS-BES-SCALAR
Description:
CalICSSynchronizer::Initialize - OpenProperty failed: (0x80004002)

******************** TWO ***********************

Event Type: Warning
Event Source: BlackBerry Messaging Agent SMS-BES-SCALAR Agent 1
Event Category: None
Event ID: 20041
Date: 9/4/2008
Time: 9:21:30 AM
User: N/A
Computer: SMS-BES-SCALAR
Description:
CalICSAgent::Start Could not Initialize Synchronizer for joe.blow@host.ca: (0x80004002)


************** THREE ***************************

Event Type: Warning
Event Source: BlackBerry Messaging Agent SMS-BES-SCALAR Agent 1
Event Category: None
Event ID: 20280
Date: 9/4/2008
Time: 9:21:30 AM
User: N/A
Computer: SMS-BES-SCALAR
Description:
{joe.blow@host.ca} DoICS() failed: ERR_FAIL

[alee]

9/4/2008 9:51 AM | Neil Longmuir


The following are the three repeating errors from the event viewer

**************** ONE *****************************

Event Type: Error
Event Source: BlackBerry Messaging Agent SMS-BES-SCALAR Agent 1
Event Category: None
Event ID: 10007
Date: 9/4/2008
Time: 9:21:30 AM
User: N/A
Computer: SMS-BES-SCALAR
Description:
CalICSSynchronizer::Initialize - OpenProperty failed: (0x80004002)

******************** TWO ***********************

Event Type: Warning
Event Source: BlackBerry Messaging Agent SMS-BES-SCALAR Agent 1
Event Category: None
Event ID: 20041
Date: 9/4/2008
Time: 9:21:30 AM
User: N/A
Computer: SMS-BES-SCALAR
Description:
CalICSAgent::Start Could not Initialize Synchronizer for joe.blow@host.ca: (0x80004002)


************** THREE ***************************

Event Type: Warning
Event Source: BlackBerry Messaging Agent SMS-BES-SCALAR Agent 1
Event Category: None
Event ID: 20280
Date: 9/4/2008
Time: 9:21:30 AM
User: N/A
Computer: SMS-BES-SCALAR
Description:
{joe.blow@host.ca} DoICS() failed: ERR_FAIL

These are warning errors. Sometimes BES tries to do things one way but reverts to doing it another way if it is not supported by ZCB. Without seeing any logs, its hard to say what is going wrong. If you open a support case, you can create a test users and have someone here in support activate a newer device against your server to see if it is a device related problem.

[nlongmuir]

Thanks Anthony ...

STATUS:
- I re-installed everything according to the latest ZCB Beta 3 release notes.
- I successfully activated my own BB (Bell 8830) on the second try
- All Calendar Events, Email, Tasks and Contacts are successfully sync'd

ISSUE:
- Any newly created event (in Zimbra or Device), received email does not show up on BB or Zimbra Desktop.
- Once I restart the BES Controller everything synchronizes, only to fail on any new stuff.

HERE is what I grabbed from the ZCO logs:

04-09-2008 14:34:58.296 [2996]: *64* ERROR: Zimbra::Rpc::Connection::SendRequest - failed on WinHttpSendRequest(...), Error Code: 12007(The server name could not be resolved.)
04-09-2008 14:34:58.296 [2996]: Zimbra::Store::CWaitRequest::WaitRequestThread. RPC Exception - SendRequest failed with Error 0x2ee7. Desc The server name could not be resolved.
04-09-2008 14:34:58.296 [2996]: Zimbra::Store::CWaitRequest::WaitRequestThread. unexpected RPC exception, reissuing the request
04-09-2008 14:34:58.296 [2996]: Zimbra::Store::CWaitRequest::WaitRequestThread. failed adding wait account from user list: neil.longmuir@scalar.ca

Any ideas ???

[alee]

Thanks Anthony ...

STATUS:
- I re-installed everything according to the latest ZCB Beta 3 release notes.
- I successfully activated my own BB (Bell 8830) on the second try
- All Calendar Events, Email, Tasks and Contacts are successfully sync'd

ISSUE:
- Any newly created event (in Zimbra or Device), received email does not show up on BB or Zimbra Desktop.
- Once I restart the BES Controller everything synchronizes, only to fail on any new stuff.


HERE is what I grabbed from the ZCO logs:

04-09-2008 14:34:58.296 [2996]: *64* ERROR: Zimbra::Rpc::Connection::SendRequest - failed on WinHttpSendRequest(...), Error Code: 12007(The server name could not be resolved.)
04-09-2008 14:34:58.296 [2996]: Zimbra::Store::CWaitRequest::WaitRequestThread. RPC Exception - SendRequest failed with Error 0x2ee7. Desc The server name could not be resolved.
04-09-2008 14:34:58.296 [2996]: Zimbra::Store::CWaitRequest::WaitRequestThread. unexpected RPC exception, reissuing the request
04-09-2008 14:34:58.296 [2996]: Zimbra::Store::CWaitRequest::WaitRequestThread. failed adding wait account from user list: neil.longmuir@scalar.ca

Any ideas ???

getting time out RPC errors from the wait request thread is ok because that means that nothing has changed for that mailbox on the server. if you are getting hostname resolution problems, it is something totally different?

there are 2 things that we can do
1) you can download winhttptracecfg and run it while running BES so we can see exactly where the requests are going (you can contact zimbra support for help with that)
2) try to look for something near the beginning of the ZCB logs that says "GetInfoResponse". this should also tell us where your subsequent requests are going.

what domain do you have the MAPI profiles pointed to? is there something tricky with the DNS that is available for the BES box?