[larrydenny]

We're using Blackberry Professional Server, 4.1.4.15 on a Windows 2003 server. Our Exchange 2007 is on a seperate box, with Windows 2008 which was also a DC. Recently, because of an AD issue, we had to demote the Windows 2008 server to a member server. A 3rd box, with Windows 2003 is now the DC.

Since the demotion of the 2008 server, we've been getting several errors for Blackberry server. to me they appear as though the BES database may be corrupt.

Event Type: Warning
Event Source: BlackBerry Messaging Agent STRBUP Agent 1
Event Category: None
Event ID: 20624
Date: 3/18/2009
Time: 2:40:48 PM
User: N/A
Computer: STRBUP
Description:
SCS::PerformDBHealthCheck: GetStyleSheetFromDB failed

And also this type of error;

Event Type: Error
Event Source: BlackBerry Synchronization Service
Event Category: None
Event ID: 16091
Date: 3/18/2009
Time: 2:41:17 PM
User: N/A
Computer: STRBUP
Description:
[SYNC-DSession] Failed to get DbVersion from UserControl object, can't sync this database. [Jon Gangelhoff:10, SID=455095981, CLID=166, ECLID=12, DS=DevMgmt, DB=Handheld Agent]

Any help would be appreciated. thanks

[knottyrope]

Did you try to reboot the BES?

[larrydenny]

Yes. Same events after the reboot.

[stuwhite]

On the BES try this !! as besadmin !!!-

Open BB Server Config app
Change DB
enter the name of the existing DB (i.e. same as you are using already), step through

[larrydenny]

Thanks. Tried it. Same event messages as before.

From what I've read, creating a new database only results in users losing their call logs. Is that correct. Is it worth a try? or is that a last resort type of thing?

[larrydenny]

Actually that has created a new event error;

Event Type: Warning
Event Source: BlackBerry Policy Service
Event Category: None
Event ID: 20000
Date: 3/19/2009
Time: 11:00:12 AM
User: N/A
Computer: STRBUP
Description:
SCS::PollDBQueueNewRequests - Error getting the list of new requests from the database.

[stuwhite]

Have you checked your app log in case this is a SQL Server perms issue? Maybe perms where knocked out during the work mentioned in the OP, might be worth checking to see that besadmin still has the correct db perms set.

[larrydenny]

Yep. Checked the logs. Also went into SQL Management Studio and removed the besadmin account. Restarted SQL, then added the account back. Restarted SQL. Then shut down the BB services, waited 20 minutes, and started them back up.

It must be a permissions issue or corrupt db? Emails are going through fine, calendar events are syncing. Contacts are NOT syncing and the option to sync Contacts wirelessly is no longer even an option on the devices.

One other odd thing. the MDS service, bmds.exe, is now constantly using 40 - 45% of the CPU

[stuwhite]

If all the probs started after the OP issue then I am thinking it has to be more likely that it's perms than corruption. Did you try to shutdown the BES, restart Exchange then bring the BES back up? TBH given what happened it might even be best to do the DC as well (down BES, down Exch, restart DC, Exch up, BES up). The original setup of Exch on a DC isn't ideal so it's safe to assume some rights got messed up along the way.

[larrydenny]

Tried rebooting each server as suggested. Same errors keep showing up.

Some good news. Users were not able to access the web on their handhelds. I created a new IT Policy, sent it to the devices and they can now use the web.

[stuwhite]

Ok so what isn't working now?