Hi All

I had some problems yesterday when i tried to move the BESMGMT Database from a SQL2000 to a SQL2005 server.
We are running 4.1.6 BES on a W2K3 R2 server (VMWARE).
I followed the instructions given for moving the Database and all seemed to go well. However the Blackberry Dispatcher service would just not start. Below is a list of the errors in the event log. Also MDS wouldnt start either. Do the BESMGMT and the MDSS , MDSS_DIS databases need to co-exist on the same Sql box? Are the co-dependent.? One other thing i noticed was that the Blackberry Database Consistency Checker service was running which i had never seen running before. Luckily because it was VMWARE i was able to revert to snapshot and all was good.
Any Help would be greatly appreciated.

Thanks in advance

Pete

The description for Event ID ( 50075 ) in Source ( BlackBerry Dispatcher STBES01 ) 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: Starting BlackBerry Dispatcher STBES01 - Version 4.1.6.10.


The description for Event ID ( 20659 ) in Source ( BlackBerry Dispatcher STBES01 ) 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: VerifySchema: COM exception.

The description for Event ID ( 20641 ) in Source ( BlackBerry Dispatcher STBES01 ) 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: COM Error 0x470BE0 in VerifySchema - Error 70010, severity 10, state 1 was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage. - IDispatch error #3092.
The description for Event ID ( 20642 ) in Source ( BlackBerry Dispatcher STBES01 ) 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: Database error in VerifySchema (err=0x80040E14, native err=18054) - Error 70010, severity 10, state 1 was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage


The description for Event ID ( 35004 ) in Source ( BlackBerry MDS Connection 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: <2009-04-07 18:37:44.593 BST>:[17818]:<MDS-CS_STBES01_MDS-CS_2>:<EVENT>:<LAYER = SRP, server lost SRP connection with UID S357438 due to shutdown>
.

The description for Event ID ( 15000 ) in Source ( BlackBerry MDS Connection 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: <2009-04-07 18:37:44.593 BST>:[17820]:<MDS-CS_STBES01_MDS-CS_2>:<ERROR>:<LAYER = SRP, EVENT = Exception, java.io.InterruptedIOException
LAYER = SRP, EVENT = Exception, at net.rim.protocol.srp.d.c.connect(Unknown Source)
LAYER = SRP, EVENT = Exception, at net.rim.protocol.srp.d.c.write(Unknown Source)
LAYER = SRP, EVENT = Exception, at net.rim.protocol.srp.d.d.write(Unknown Source)
LAYER = SRP, EVENT = Exception, at java.io.DataOutputStream.write(Unknown Source)
LAYER = SRP, EVENT = Exception, at java.io.DataOutputStream.write(Unknown Source)
LAYER = SRP, EVENT = Exception, at net.rim.protocol.srp.h.a.writeToStream(Unknown Source)
LAYER = SRP, EVENT = Exception, at net.rim.protocol.srp.f.a.c(Unknown Source)
LAYER = SRP, EVENT = Exception, at net.rim.protocol.srp.d.f(Unknown Source)
LAYER = SRP, EVENT = Exception, at net.rim.protocol.srp.e.b.uD(Unknown Source)
LAYER = SRP, EVENT = Exception, at net.rim.protocol.srp.e.b.run(Unknown Source)
<2009-04-07 18:37:44.593 BST>:[17820]:<MDS-CS_STBES01_MDS-CS_2>:<ERROR>:<java.io.InterruptedIOException>
<2009-04-07 18:37:44.593 BST>:[17820]:<MDS-CS_STBES01_MDS-CS_2>:<ERROR>:<at net.rim.protocol.srp.d.c.connect(Unknown Source)>
<2009-04-07 18:37:44.593 BST>:[17820]:<MDS-CS_STBES01_MDS-CS_2>:<ERROR>:<at net.rim.protocol.srp.d.c.write(Unknown Source)>
<2009-04-07 18:37:44.593 BST>:[17820]:<MDS-CS_STBES01_MDS-CS_2>:<ERROR>:<at net.rim.protocol.srp.d.d.write(Unknown Source)>
<2009-04-07 18:37:44.593 BST>:[17820]:<MDS-CS_STBES01_MDS-CS_2>:<ERROR>:<at java.io.DataOutputStream.write(Unknown Source)>
<2009-04-07 18:37:44.593 BST>:[17820]:<MDS-CS_STBES01_MDS-CS_2>:<ERROR>:<at java.io.DataOutputStream.write(Unknown Source)>
<2009-04-07 18:37:44.593 BST>:[17820]:<MDS-CS_STBES01_MDS-CS_2>:<ERROR>:<at net.rim.protocol.srp.h.a.writeToStream(Unknown Source)>
<2009-04-07 18:37:44.593 BST>:[17820]:<MDS-CS_STBES01_MDS-CS_2>:<ERROR>:<at net.rim.protocol.srp.f.a.c(Unknown Source)>
<2009-04-07 18:37:44.593 BST>:[17820]:<MDS-CS_STBES01_MDS-CS_2>:<ERROR>:<at net.rim.protocol.srp.d.f(Unknown Source)>
<2009-04-07 18:37:44.593 BST>:[17820]:<MDS-CS_STBES01_MDS-CS_2>:<ERROR>:<at net.rim.protocol.srp.e.b.uD(Unknown Source)>
<2009-04-07 18:37:44.593 BST>:[17820]:<MDS-CS_STBES01_MDS-CS_2>:<ERROR>:<at net.rim.protocol.srp.e.b.run(Unknown Source)>

did you do this?
View Document

Hey Knot...the only problem with that doc you linked is that the server.xml document doesn't exist in 4.1.5+. It got absorbed into BESMgmt. I thought it was that easy too... until I tried to find the friggin file.

@Simmo
We just moved (and renamed) our BESMgmt from the local BES server to a dedicated SQL 2005 server. While it's not the same as what you're describing, the error was dead-on-balls accurate. The problem is with the permissions from the BES to the SQL server. You need to give the Server Admin and Database Creator permissions on the SQL box to the account that installed the BES originally. You also need to assign the same permissions for the BES to access the SQL server. See KB12096

And YES, you need to put the MDSS and MDSS_DIS on the same box as your BESMgmt database.

When I used SSMS I was logged into it as myself on SQL and when importing the DB the permissions on then DB changed to me instead of BESAdmin. I had to change them all back to BESAdmin after. Looking forward might be better to login SSMS as BESAdmin instead of any other SQL admin account.

RIM painstakingly writes in every documentations and articles you could get, but mistakes are still made... "Perform the following tasks using the account that was used to install the BlackBerry Enterprise Server software unless otherwise stated"... blah blah blah...

Awalys use the same service account that you first installed your BES, you will never go wrong. If you are using Windows authentication, your SQL DBA had already granted you the necessary SQL permissions to start off. Problems come when you use a difference service account and then SQL just block you, why? You don't have the bloody permissions!

Since I'm planning on doing this same thing this evening, I would like to clarify this. I don't need to do anything special in order to get the MDS databases to work on the new server? I just follow the move configuration DB instructions RIM provides but add in the step of moving the MDS databases to the new server. Configuring the BES to see the config database on the new server is enough to get BES to see the new location for MDSS and MDSS_DIS? I'm running 4.1.6.

Thanks!

Yep.
Back them up and detach.
Run the config wizard and let it create the new, blank BESMgmt on the new SQL server. After it's up and running, restore the backup (with MDSS & MDSS_DIS) over the blank and restart your services. Should pick right up and continue chugging along.

Great. One other question though. When you say "Run the config wizard", are you talking about the change database wizard that you get from Database Connectivity in the BlackBerry Server Configuration Panel?

I'll be following the instructions at:
How to move the BlackBerry Configuration Database to a remote Microsoft SQL Server

Thanks

Yep yep. When you get to step 4 and create blank DB, walk away and get some coffee, a sandwich or watch an episode of South Park. It'll take a while.

Hugheser,

Did you do succesfully the movement?

I want to do the same thing but I don't know if with the guide "How to move the BlackBerry Configuration Database to a remote Microsoft SQL Server" restore too the MDS databases and work perfectly all with the new SQL server.

regards

Mostly. We had some trouble with the collaboration service but after spending a day with a few RIM engineers, I was able to fix it. We put the MDS databases on the remote sql and everything worked.