[JPenrose]

Hi group,

Came in today to update an antivirus pkg on the gateway srv (which is also the BES 4.0 srv). Some of the prerequisites for the upgrade were MSMQ, SP1 for win2k3, IIS www service and .NET 2.0. I installed these one at a time starting with the SP and progressing through to .NET 2.0. It seems that after one of the installs the BES broke. I get an error stating unable to open database. I've seen several posts about this error and have tried pretty much all the suggested fixes to no avail. The MAPI profile is correct and is the same one we've used for years. I non the less recreated it (no change).

I ran the change database wizard from the bb server config and pointed it to the srv instance and database name. After doing that I received a couple messages on the handheld and was then able to send mail to myself but only myself.

During the install of MSMQ (MS message queuing service) I did notice that a configuring sql server box poped up but stalled. When I finished the component install wizard (it installed MSMQ and WWW) the sql window disappeared and I had to reboot to get MSDE back. The BES has been hosed ever since.

The MNGR log shows the following message:

30000] (01/14 14:22:31):{0x684} Current Date: 2007/01/14
[30000] (01/14 14:22:31):{0x684} [DIAG] EVENT=Thread_report, THREADID=0x684, THREADNAME="DebugLogger"
[40000] (01/14 14:22:31):{0x684} [DIAG] EVENT=Syslog_disconnected, ERROR=10049, EVENTMSG="Connect failed to 0.0.0.0"
[30145] (01/14 14:22:31):{0x1020} Starting BlackBerry Manager - Version 4.0.5.13
[30146] (01/14 14:22:31):{0x1020} Initializing the MailboxManager with profile BlackBerryServer
[40206] (01/14 14:22:31):{0x1020} MailboxManager::SubsystemInitialize - Using MAPI profile 'BlackBerryServer'
[20137] (01/14 14:22:31):{0x1020} MailboxManager::SubsystemInitialize - g_pSession->OpenMsgStore (0x8004011d)
[10160] (01/14 14:22:35):{0x1020} A failure was encountered trying to initialize the BlackBerry Manager.
[40403] (01/14 14:22:35):{0x1020} RIMDatabase - GetBlackBerryServers

I've never seen this log before so I presume it appears if there are problems.

I'm wondering if this is a mailbox permissions issue for the BESadmin srvc account? How can an install on the BES server mess up the permissions for mailbox access? Did the SP1 install change some permissions for the BESadmin that I'm unaware of? Other log files seem to indicate that logins to user mailboxes fail which leads me to the mailbox permissions conclusion.

Can anyone offer some help? I can post more logs here if necessary.

TIA
JPenrose

[dev]

A quick way to test (apart from the fact that others aren't receiving mail), is to run the IEMSTest.exe test on a few users. This test allows the service account to access and create&delete a folder in the users' mail box. If the results are negative (as I'm sure it will), then the permissions have changed on the mail boxes. You should be able to use the ESM tool to re-apply the permissions at the MailboxStore-level.

[JPenrose]

Holy cow, what a mess.

Somehow on Friday, a No Override flag was set on the Domain GPO and a block inheritance flag set on the Default Domain Controllers GPO. The combination of these + the reboot of the BES after the SP1 install started the problem. The BES couldn't connect to the exchange box b/c the information store and the MTA was offline b/c the topology scans were failing due to the GPO flags. Like I said, what a mess. Resetting the GPOs back to where they should be allowed the IS and MTA to fire which inturn allowed the BES to fire.

All is apparently quiet in the village now.

Thanks for the response!!

-J-