BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 01-23-2012, 05:03 PM   #1 (permalink)
New Member
 
Join Date: Jan 2012
Model: 9780
PIN: N/A
Carrier: Bell Mobility
Posts: 1
Post Thanks: 0
Thanked 0 Times in 0 Posts
Exclamation BESX crapped the bed and I can't figure out why

Please Login to Remove!

Several months ago we installed BESX version 5.0.3 along with the Google Apps connector to connect BESX to our Google Apps account. Until Saturday, it's been working perfectly.

Looks like there was a "dirty" shutdown sometime around then, and now.... no emails are syncing. At all.

Here's what I'm seeing in the Windows Event Log:

"BlackBerry Messaging Agent BESX Agent 1 failed to start. Error code 5305"

and

"Invalid MAPI profile BlackBerryServer: PR_PROFILE_HOME_SERVER_DN is missing or invalid. This profile cannot be used."

and

"Invalid MAPI profile BlackBerryServer: PR_PROFILE_USER is missing or invalid. This profile cannot be used."

and

"'BESX' agent 3: will not restart - reached the maximum of 10 restarts per 24 hours, next restart on Tue Jan 24 12:38:28 2012" (five times, one for each agent)

This was a functioning server with zero past issues, until Saturday at about 1pm MST.

I've been Googling up a storm trying to find a resolution to this, so far without any form of success. One user suggested I stop the Dispatcher, delete GAB*.db, then restart - which I did, and the GAB*.db file very quickly reestablished itself. Then I restarted the Controller, and within a few seconds I get all of those errors in the Windows Event Viewer all over again.

This has really got me flummoxed.

I had an open ticket with Google on another (possibly related) issue and so I've asked them for help, but they've been silent. They did, earlier, ask me to provide them with some info:

"If the above does not help please provide all Google Connector logs after a reboot.

- BlackBerry log for the affected day
C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs\{date}\*MAGT*
- Google Apps Connector logs for the affected day
C:\Program Files\Google\Google Apps Sync\Logs\BlackBerryAgent\Trace-{date}-*"

...and I've attached the logs he asked for to this post, if that helps.

I also called RIM's incident-based support and they don't support BESX-with-Google-Connector, so there's another brick wall.

Panic!

Can anyone help?
Attached Files
File Type: zip Sharp'sAVGoogleAppsTrace.zip (7.5 KB, 0 views)
File Type: zip Sharp'sAVMAGTlogs.zip (668.8 KB, 0 views)
Offline  
Old 01-23-2012, 07:19 PM   #2 (permalink)
BlackBerry Mensa
 
tsac's Avatar
 
Join Date: Mar 2005
Location: Others run out when we run in
Model: Z10
OS: 10.010219
PIN: No Pin just a Tack
Carrier: at&t
Posts: 8,302
Post Thanks: 43
Thanked 580 Times in 575 Posts
Default Re: BESX crapped the bed and I can't figure out why

Read these\

KB14186-BlackBerry Messaging Agent fails to start when the BESAdmin mailbox is not accessible 0 1992688749

KB24421-"Failed to retrieve the server DN" appears in the MAGT log with error 5305 and BlackBerry Messaging Agent will not start 0 1992688749
__________________
If someone helps, tell them by clicking the Thanks button


9810 BES
Z10 on BES
9700 BIS
Offline  
Old 05-17-2012, 02:21 PM   #3 (permalink)
New Member
 
Join Date: May 2012
Model: 9900
PIN: N/A
Carrier: Verizon
Posts: 1
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default Re: BESX crapped the bed and I can't figure out why

I had the samme issue today and decided to post my fix because this was a pain in the arse.

1. Stop all BlackBerry Services, and set the start up type to Manual for all services.
2. Backup HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles
3. Delete HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles
4. From the Start Menu, run Google Apps Connector -> Google Apps Connector Manager, then click profiles.
5. Re-enter the Service email account, OAuth Comsumer key and OAuth Consumer Secret.
6. Check in HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles that new BlackBerryManager and BlackBerryServer keys have been created.
7. Reboot the BlackBerry Enterprise Server.
8. Open Services and change the start up type for all BlackBerry Services except the Synchronization, Policy and Mailstore services to Automatic.
9. Start the BlackBerry Controller Service, then the Dispatcher Service and then the remaining BlackBerry Services.

Cheers
Offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





Copyright 2004-2014 BlackBerryForums.com.
The names RIM and BlackBerry are registered Trademarks of BlackBerry Inc.