zenworksb
asked on
blackberry issue
i have a exchange 2003 and a blackberry enterpriose server. we have one user right now. the user has been working great, but today around 7:00 am sending and recieving stopped working on his blackberry. i went into the event log and saw this event.
source blackberry messaging A
category-none
type-warning
event id 40578
decription cdo helper 00d20a28- worker thread 000001be0 not responding calling processreqrespfromapi
i restarted all the blackberry services and it started working. how can I find out why it stopped in teh first place and maker sure it does not do it again
source blackberry messaging A
category-none
type-warning
event id 40578
decription cdo helper 00d20a28- worker thread 000001be0 not responding calling processreqrespfromapi
i restarted all the blackberry services and it started working. how can I find out why it stopped in teh first place and maker sure it does not do it again
Is the BES on the Exchange server? Or on its own hardware. Did you start another application using CDO on the BES?
Look in also in the MAGT log on the BES. What was it saying amore there?
Regards,
Bob
Look in also in the MAGT log on the BES. What was it saying amore there?
Regards,
Bob
ASKER
it is on its own server
And what is in the MAGT log file (around 7:00am) on that day?
Regards,
Bob
Regards,
Bob
ASKER
some mapi errors what exactly do you need
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
hey, Duffman
I'm having the same issue with bes. The cdo.dll and mapi.dll files are not the same version. My Bes server is on a separate server from the exchange. What should I do to resolve this issue?
I'm having the same issue with bes. The cdo.dll and mapi.dll files are not the same version. My Bes server is on a separate server from the exchange. What should I do to resolve this issue?
I would get the latest BES server version and all the patches.
Also you can turn on debugging on the server to get more explicit log files.
I hope this helps !