[migra]

Hello

I keep getting this warning 40578 at least once a minute in the event viewer. Does anyone have any information on what it means and how to resolve this? I running BES 4.1 with Exchange 2003.

what dit in the past or this day was to migration from 4.0 to 4.1.4.15 after this everything looks fine and worked and now i get this error 400578

CDO helper 06ce1450 - worker thread 00001b5c not responding, Calling SetCDOCalendar

please help thanks

[hdawg]

are there any other errors around this one in your bes logs?

[migra]

Originally Posted by hdawg

are there any other errors around this one in your bes logs?

Hi HDAWG

thanks for youre help after restart is the warning gone, but now i got a lot of other warnings like this

20280
20044
and the most is 20042

and i can not find anything in the knowledgebase from RIM strange but it worked now hopfully till i die

[hdawg]

anyway you can post the event details?

[hdawg]

... and lets not talk about death ... unless perhaps you're talking about the Deathly Hallows

[porod]

We've been trying to deal with this for a week. Right now RM had me turn off wireless calendar synchronization via an IT policy. This got rid of the 40578 event. We have exchange 2007 and BES 4.1.4.

Our 40578 event reads a little different, "locking CDO mutex"

We still get 20273, 20265, 20301, 20222, 20185 an other events. I think some of these might be due to an Exchange reboot that wasn't followed up with a BES reboot, trying to verify.

[hdawg]

ok, if you can post the contents of the events that'll help more too.

[porod]

8/1/2007 9:35:11 AM BlackBerry Messaging Agent MOBILECOMM1 Agent 1 Warning None 40578 N/A MOBILECOMM2 CDO helper 04c4eed0 - worker thread 0000188c not responding, Locking CDO mutex

8/2/2007 6:36:40 AM BlackBerry Messaging Agent MOBILECOMM1 Agent 1 Warning None 20265 N/A MOBILECOMM2 {xxx@fvtc.edu} MAPIMailbox::RescanPIMItems - GetProps (0x80040115) failed

8/2/2007 6:33:22 AM BlackBerry Messaging Agent MOBILECOMM1 Agent 1 Warning None 20176 N/A MOBILECOMM2 {xxx@fvtc.edu} GetNewMessages() failed: ERR_NETWORK_PROBLEM


8/2/2007 6:33:28 AM BlackBerry Messaging Agent MOBILECOMM1 Agent 1 Warning None 20274 N/A MOBILECOMM2 {xxx@fvtc.edu} GetMessageStatusUpdates() failed

[porod]

8/3/2007 7:40:42 AM BlackBerry Messaging Agent MOBILECOMM1 Agent 1 Warning None 20174 N/A MOBILECOMM2 {xxx@fvtc.edu} ReloadPagerStats() failed

8/3/2007 7:39:59 AM BlackBerry Messaging Agent MOBILECOMM1 Agent 1 Warning None 20539 N/A MOBILECOMM2 {xxx@fvtc.edu} RescanPIMItems(1) failed: ERR_NETWORK_PROBLEM


8/3/2007 7:39:59 AM BlackBerry Messaging Agent MOBILECOMM1 Agent 1 Warning None 20535 N/A MOBILECOMM2 {xxx@fvtc.edu} RescanPIMItems - Failed getting contents table (type=Address Book) (0x80040115)


8/3/2007 7:38:39 AM BlackBerry Messaging Agent MOBILECOMM1 Agent 1 Warning None 20222 N/A MOBILECOMM2 {xxx@fvtc.edu} TransactionComplete() failed: ERR_FAIL

8/3/2007 7:37:51 AM BlackBerry Messaging Agent MOBILECOMM1 Agent 1 Warning None 20185 N/A MOBILECOMM2 {xxx@fvtc.edu} GetRIMMessage() failed: ERR_FAIL, EntryId=146795

[migra]

Hi

here is the LOG

CDO helper 06c94188 - worker thread 00001210 not responding, Locking CDO mutex

but just warning not errors,

[rmund2000]

Hi Porod,

Did you ever get a resolve to your issue. We are having the same problem.

[porod]

No, RIM had basically told to to reenterprise activate everyone. I balked at that and they suggested turning off wireless calendar synch for everyone and turn it back on to smaller groups of users to try and isolate the problem mailboxes. I tried that and the 40758 error seemed to go away with the calendar off. It however created problems with the users as they didn't quite understand and they were continuing to schedule meetings on the devices and of course it wasn't synching. I then turned the wireless calendar synch back on for everyone. I'm rebooting the server every morning which clears up the 40758 for a few hours anyway. I am reactivating all users whose accounts were created before our migration to Exchange 2007 and subsequent mailboxe moves to different stores, as part of reactivation I'm deleting them from BES and choosing to remove the data from th email server as part of the delete. Rim thinks some of the BES data in the mailboxes is corrupted but can't tell me which mailboxes those may be.

[danny.nicholson]

Check KB14066 there's you fix, this is a known bug in 4.1.4

[porod]

Rim had me perform the steps in KB14066 a couple weeks ago, so far so good.

[morser]

I cannot find document KB14066 in the RIM knowledge base. Tried searching for just 14066 as well. If someone has a link can you please reply.

[Joluth]

I was trying to find it yesterday and couldn't either but luckily had a copy of the text from an old email to a co-worker:

Problem
The following events appear repeatedly in the Event Viewer log :
Event Type: Warning
Event Source: BlackBerry Messaging Agent <Server> Agent 2
Event Category: None
Event ID: 40578
Date: 8/10/2007
Time: 8:59:51 PM
User: N/A
Computer: <Server>
Description:
CDO helper 07abb208 - worker thread 000016a8 not responding, Starting.
Event Type: Warning
Event Source: BlackBerry Messaging Agent <Server> Agent 2
Event Category: None
Event ID: 40578
Date: 8/10/2007
Time: 8:59:50 PM
User: N/A
Computer: <Server>
Description:
CDO helper 07924270 - worker thread 00002198 not responding, Locking CDO mutex.
In addition to these errors, BlackBerry smartphone user may report delays in receiving email messages.

Cause
The issue is caused by an error within the Messaging Application Programming Interface (MAPI) subsystem during a profile creation. These errors may be transient and may be caused by temporary network connectivity issues, server performance or other reasons.

Resolution
This is a previously reported issue that has been escalated internally to our development team. No resolution time frame is currently available.

Workaround
To workaround these errors, create a new registry key by completing the following steps:
Warning: The following procedure involves modifying the computer registry. This can cause substantial damage to the Microsoft® Windows® operating system. Document and back up the registry entries prior to implementing any changes.
Open the Registry Editor, and locate HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\Agents.
Create DWORD MaxTimeoutOnCalHelper (This key does not exist by default).
Specify a value of decimal 180.
Close the Registry Editor.
Restart the BlackBerry Enterprise Server.

[morser]

Wow. Thank you very much.

I wonder why it was pulled.