The BES software is on APPSERVER, and does not have exchange installed on it. The exchange server is called MAIL.
Main Topics
Browse All TopicsI installed windows updates on my BES and Exchange 2003 SP/2 server last night. Since then, BES has stopped working. There are numerous errors in the event log. Blackberry forums have been no help. Attached are the application errors (event.txt). Users are receiving SOME e-mail, and i cannot activate phones (i had wiped a phone, and tried to re-activate it, and nothing happens). I tried re-entering the MAPI information, and i still have the problem. I have restarted all services, and restarted the server. I looked for the updates in Add/Remove programs on both the Exchange and BES server, and NONE of the updates are listed - so removing the updates is not an option. The server talked about in the event log's APPSERVER is the BES server, not the Exchange server (MAIL). I need this working very soon. Thank you.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Ignore those errors. When i had restarted the Blackberry Server, it failed to restart itself. After starting it. I get these errors when activating the phone:
Event Type: Warning
Event Source: BlackBerry Dispatcher APPSERVER
Event Category: None
Event ID: 20000
Date: 3/19/2009
Time: 12:49:21 PM
User: N/A
Computer: APPSERVER
Description:
{user
Event Type: Warning
Event Source: BlackBerry Dispatcher APPSERVER
Event Category: None
Event ID: 20000
Date: 3/19/2009
Time: 12:49:36 PM
User: N/A
Computer: APPSERVER
Description:
{user
Event Type: Warning
Event Source: BlackBerry Dispatcher APPSERVER
Event Category: None
Event ID: 20000
Date: 3/19/2009
Time: 12:50:26 PM
User: N/A
Computer: APPSERVER
Description:
{user
Any ideas?
Hi,
Normally when this issue occurs you need to delete the registry key below and then restart the dispatcher service.
HKEY_CURRENT_USER\Software
Now that you have uninstalled BES and you ensured the registry keys are removed (e.g. HKEY_CURRENT_USER\Software
The main issue is: 550 5.7.1 Missing purported responsible address
It's an smtp issue
Sender ID can cause this error when the message or address is malformed - http://spf.pobox.com
I have run into this exact problem too (Old OTAKEYGEN packet is cancelled) when trying to do an over the air activation after a device was previously activated. My device was stolen so ISP had to reissue a new SIM. I put it in the new device and deleted the user from the BES (4.0). When I recreated the user, the error you mention above happened. The only way around this was to log onto a computer as the user, create a mapi profile (configuring outlook for user) and then connect the device after opening Blackberry Manager. The device was recognized and the Enterprise activation started automatically on its own and was successful. It appears that OTA activation mechanisms were the fault in my case.
Business Accounts
Answer for Membership
by: jar3817Posted on 2009-03-19 at 09:36:30ID: 23931383
Based on those events, it looks like it is having trouble communicating with the exchange server. Is the BES software on a separate machine than the exchange server?