BES 4.1.4.17 has stopped talking to Exchange 2007, no specific errors

This morning we replaced batteries in one of our UPS units which required a complete power down of our computer room.  On bringing all machines back up, our BES machine is no longer processing for the 3 users who are currently using its services.

- I have Exchange 2007 Standard on Windows 2008 - machine all by it self
- I have BES Express 4.1.4.17 on its own machine, Windows 2003 (x32)

In going through my event logs, there were some warnings and errors, the first of which was the MSSQL service was/is not ready to accept connections.   The BES server booted up before my domain controllers had finished booting so I just rebooted again, this cleared this message.   The SQL installation for BES is on the same box as BES and is whatever the SQL 2005 Express edition, the only database other than system databases is the BESMgmt database.

Upon rebooting, I still did not (and currently do not) have any mail syncing.  


{StartNotifyThreadServer}: DBNS component not installed.
--- doeesn't look critical, have not been able to find what should be installed

[BIPPe] WARNING: Using default BIPP shared secret
--- other posts seem to indicate that this is an information message?

The description for Event ID ( 45058 ) in Source ( BlackBerry Synchronization Service ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event:

The errors / warnings I have in the event log at this point are:
{StartNotifyThreadServer}: DBNS component not installed..

I started getting the below messages when I setup more information logging on database calls through the Options dialog under tools:
301 - Server returned a fault code = 12 message = ''
102 - 'UserConfig' Property Set has no definition for property 'Email'



I can use the Blackberry Manager and send PIN messages to the devices registered.  I can also send e-mails to the users mailboxes.

From the Blackberry Server Configuration, I have run TestSQL Server connection which is successful, ensured that my SRP Key & ID are valid, Tested and confirmed that my Blackberry Router / Network connection is successful.

Following the device of some posts here and several articles on the web including the Blackberry Forums, I removed the profiles from HKCU\Software\Microsfot\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles --- both the Blackberry Manager and Blackberry Server keys.  I did this with all the blackberry services stopped.  I then used the Blackberry Configuration program to setup the MAPI profiles and when launching the manager software, setup again.   During both MAPI setups, I validated the username against the exchane server prior to pushing apply & OK.

BBSRPTest.exe shows clean:
C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Utility>BBSrpTe
st.exe
NetworkAccessNode is srp.us.blackberry.net.
Attempting to connect to srp.us.blackberry.net (206.51.26.33), port 3101
Sending test packet
Waiting for response
Receiving response
Checking response
Successful


FixMapiSVC says information is already there:
MSEMS service information already exists in C:\Program Files\Common Files\SYSTEM\MSMAPI\1033\mapisvc.inf

Now - If I run IMESTest.exe WITH the Blackberry services started, on the BlackBerryServer profile, it fails:

C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Utility>IEMSTest.exe
BlackBerry Enterprise Server Utility - IEMSTest.exe (IExchangeManageStore), Version 1.0
Copyright (c) Research In Motion, Ltd. 1999. All rights reserved.
OpenMsgStore() for this profile failed (8004011c)

If I run it on the same profile with services stopped, it succeeds
C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Utility>IEMSTest.exe
BlackBerry Enterprise Server Utility - IEMSTest.exe (IExchangeManageStore), Version 1.0
Copyright (c) Research In Motion, Ltd. 1999. All rights reserved.
OpenMsgStore() for this profile failed (8004011c)

Whether services are started or stopped, IMESTest against BlackBerryManager succeeds:
C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Utility>IEMSTest.exe
BlackBerry Enterprise Server Utility - IEMSTest.exe (IExchangeManageStore), Version 1.0
Copyright (c) Research In Motion, Ltd. 1999. All rights reserved.
Opening Default Message Store Mailbox - BESADMIN.
Opening message store for Mark A. Lappin using /O=Lee Michael's/OU=LMFJ/cn=Recip
ients/cn=MarkL /o=Lee Michael's/ou=Exchange Administrative Group (FYDIBOHF23SPDL
T)/cn=Configuration/cn=Servers/cn=LMFJEX07/cn=Microsoft Private MDB.
Mark A. Lappin's Mailbox opened successfully.
Root Folder opened successfully.
Folder created successfully.
Test folder deleted successfully.
Test completed successfully for Mark A. Lappin.


Earlier I decided to TRY and remove my BES account and disassociate my device from the server, re enterprise activate and see if that would jumpstart things.  When I redo enterprise activation, the RIM network message sits in my mailbox and is never consumed by the BES system even though all services are running.  The encrypted .DAT file is intact and is not being replaced with an anti-virus or anti-spam warning, so systems changse have been made since yesterday except for UPS Battery replacements (due to age, my systems do not have hot swappable batteries).

I have verified Exchange 2007 extended permissions for BESAdmin that it has exchange view only admin, Receive As and Send Ass on all mailboxes.

I'm running out of ideas and hoping some folks here can help me out!     It appears that whatever the service or mechanism is which monitors or actually does the "Receive As" operation for the BES users, is not operating properly since all other checks seem to work.  Further, users on their hand helds cannot look up exchange user information, send e-mail, get calendar notifications etc.  The last synchronize time for their handhelds is not updating in the Blackberry manager either.

I have tried doing an install on top of the existing install in hopes of fixing a service or repairing a corrupted file, but to no avail.

What am I missing?

Mark L.
LappiMAAsked:
Who is Participating?
 
LappiMAConnect With a Mentor Author Commented:
Well - I reformatted the box, loaded it all back up and poof, presto chango, no changes to exchange, started working again (had to wipe and reactivate my hand helds but everybody is glad its back up).  Still no clue what happened to it before or why it wasn't working.  Funny thing is, the errors I have in my event log now are exactly the same.   Everything as far as I can tell is the same, versions, patch levels everything.

Very odd but its working again.
0
 
jderaCommented:
Since you are using Exchange 2007, the first thing I would do is update to the latest version of BES 4.1.6.
0
 
Gary CutriData & Communications SpecialistCommented:
Hi, make sure you restart the BES again as Exchange 2007 must be online and running when BES boots up.  Also make sure the BESadmin account isn't locked out in AD and then follow the guide below to clear and recreate the MAPI profiles.

http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB10285
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Gary CutriData & Communications SpecialistCommented:
P.S. Make sure to public folder store is mounted as the BES cannot operate without access to the OAB.
0
 
Gary CutriData & Communications SpecialistCommented:
Any updates?
0
 
LappiMAAuthor Commented:
I don't have an update yet -- had some out of town company in this weekend,  I'll be working on it tomorrow.

To answer some of the above questions:

(1)   Public Folder Store --- I think when BES first came online after my power failure, the public folder store was not mounted as I had some legacy client issues with EX 2007 and Outlook XP & 2003.   Restarted exchange services and the store mounted and other clients connected.   Rebooted BES multiple times after that.

(2)   MAPI Profile Rebuild Link - the KB article posted is the one I was using on Friday to recreate the profiles with.

(3)   Upgrading - was downloading when I left the office on Friday, was planning to do upgrade this weekend but will have to wait until the morning.  Will post back in about 15 hours.

Mark
0
 
jderaCommented:
Good luck with the upgrade.
0
 
Gary CutriData & Communications SpecialistCommented:
From memory BES 4.1.4.17 is Blackberry Professional build.  If this is the case you are unable to apply SP6 to this version so please confirm this before attempting any updates.
0
 
Gary CutriData & Communications SpecialistCommented:
Also to rule out an issue with the Public Folders you can change the BES configuration so it is not reliant on them (use for testing only).  To change this setting you can follow my post in the link below:

http://www.blackberryforums.com.au/forums/microsoft-exchange/2554-bes-may-not-work-correctly-exchange-2007-environments-without-public-folders.html
0
 
LappiMAAuthor Commented:
garycutri - you are correct 4.1.4.17 is a professional build.  When I unzipped the upgrade download I noticed it was the same major version 4.1.4, and in reading the release notes for 4.1.6.whatever I downloaded as a service pack rollup, it doesn't seem like it would apply.   I'm about to go look for any applicable updates to 4.1.4.17 that are available.

0
 
Gary CutriData & Communications SpecialistCommented:
I can confirm that there are no updates for BlackBerry Professional (it is now an end of life product).
0
 
Gary CutriData & Communications SpecialistCommented:
I personally believe it is a public folder issue or a corruption of the BlackBerry service account.  I recommend restarting Exchange and you need to ensure the Public folder mounts correctly and the OAB is accessible (or disable the requirement for Public folders as per my steps above).  If it is a corrupt of the service account it can be resolved with this guide below:

http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB04293&sliceId=1&docTypeID=DT_SUPPORTISSUE_1_1&dialogID=68844251&stateId=0 0 69239872
0
 
LappiMAAuthor Commented:
Exchange restarted, all stores mounted successfully and without errors.

All BES servers restarted (whole box rebooted as well) - no joy.

BESAdmin domain account is not locked out, has a non-expiring password, is permitted to logon as a service, and has the receiveas, sendas and view only admin status on exchange (confirmed again).

Rebuilt MAPI profile's again.

Reg entry to ignore public folder in place, still no luck.

I'm thinking time to rebuild the box from scratch?

0
 
jderaCommented:
It sounds like it, who knows what happened when those batteries went down.  From experience there is a limit to troubleshooting when it just takes more time to do that then just rebuilding.
0
 
LappiMAAuthor Commented:
Agreed!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.