Hi,

I upgrade from BES 3.6 to 4.1 this weekend.

The issue i have is that the MDS Services Apache Tomcat Service keeps stopping. I have reinstalled the BES services and changed the Web.xml as per RIM instruction.

The 2000 SQL desktop instance is on default port 1433.

The event log of the Tomcat service is showing:

[INFO ] (06/25 10:28:40) [ConfigMgr] SERVER_CONFIG_DIR=C:\Program Files\Research In Motion\BlackBerry MDS Services 4.1.0\config
[INFO ] (06/25 10:28:41) [JMSMgr] JMSMgr was initialized.JNDI JMS Provider.
[DEBUG] (06/25 10:28:41) [ThreadPool] Thread | Thread pool started. | Name=default;
[INFO ] (06/25 10:28:41) [AbstractManagedService] ThreadPoolMgr | STARTED |
[INFO ] (06/25 10:28:41) [AbstractManagedService] BaseManager | STARTED |
[FATAL] (06/25 10:28:42) [AdminUtil] Server manager. | Failed to start MDS Services. | Exception=Failed to load server settings.:JDBCMgr could not connect to the data source.;
[WARN ] (06/25 10:28:43) [AdminUtil] MDSTomcat service has been stopped, counter=2.
[ERROR] (06/25 10:28:43) [[/mds]] Servlet /mds threw load() exception
net.rim.wica.ag.services.admin.AdminException: Failed to load server settings.

I have checked the permissions on the Mdss bd's and it looks fine.
Email is being sent and received fine on the handsets.

Any ideas what i can try next?

Thanks for your help

Robert

JDBCMgr could not connect to the data source.;

that looks like a java error to me. i would run add/remove programs and look and see how many different versions of java are installed. remove the ones that are needed and keep only the most current version and restart MDS. If the server still throws the error after you uninstall the older version of java, you might have to unistall the only version of java that you have left and do a fresh install of java. the only downside to any of this is that you will have to reboot after you uninstall java runtimes. removing java WILL NOT affect the mail pushing portion of BES. Good Luck.

Check your sql database mdsconfig table. Make sure the ACLAuthorizationDatastore is correct. We did a 3.6 to 4.0 upgrade and I did have several java versions on the server. I deleted all but one and still had the problem. I checked the database and noticed that the ACLAuthorizationDatastore was not set right for the server that was upgraded. Once changed to reflect the same path as our other servers the RIM relay has been working.

Thanks to both of for your replies. I will have a look in the morning and let you know how i get on.
Kind regards
Robert

Hi,

Solved the issue by wiping the BES 4.1, SQL and exsiting Java installs and doing a clean install. Everthing is working as it should be.
Thanks for your advice and help.
Robert

I am having the same problem, the error message is identical. The suggestions above don't solve my problem. However, I am unsure how to check if 'ACLAuthorizationDatastore' has the correct value. Current value is 'net.rim.shared.service.authorization.JDBCAuthoriz ationDatastore'.

Anyone?

Has anyone found removing the extra versions of Java helps here? Add or remove programs shows J2SE Runtime Environment 5.0 Update 4 (which i believe we need), Java 2 Runtime Environment, SE v1.4.2_03 and Java 2 Runtime Environment, SE v1.4.2_08. Can the last two be safely removed?

That value is correct. For all db connection problems check the database connectionstring in the configuration of Tomcat (server.xml) in C:\Program Files\Research In Motion\BlackBerry MDS Services 4.1.0\jakarta-tomcat-5.5.9\conf

Hi All,

I have the same problem here, and i am not good in sql.

Kahill, could you describe more about how to "Check your sql database mdsconfig table. Make sure the ACLAuthorizationDatastore is correct. "?

We're using MSDE (SQL desktop edition), and i can't find any enterprise manager or query analyzer...

Really appreciate your help, thanks in advance..

When using MSDE you don't have the GUI tools like enterprise manager or query analyzer. These are SQL server tools and installed with SQL Server.

How can you check it with MSDE:

1. Log on to the BES with the besadmin account or any localadmin account
2. open up a CMD prompt
3. Type 'OSQL -E'
4. On the first line type 'use BESmgmt' and hit Enter
5. On the second line type 'select machinename from mdsconfig where ACLAuthorizationDatastore = 'net.rim.bmds.shared.service.authorization.JDBCAut horizationDatastore'' and hit Enter
6. On the third line type 'go' and hit enter

If the result will show your BES machinename and it will state <1 rows affected> the column in the mdsconfig table is incorrect. Run the following command to fix:

1. Log on to the BES with the besadmin account or any localadmin account
2. open up a CMD prompt
3. Type 'OSQL -E'
4. On the first line type 'use BESmgmt' and hit Enter
5. On the second line type 'UPDATE MDSConfig Set ACLAuthorizationDatastore = 'net.rim.shared.service.authorization.JDBCAuthoriz ationDatastore'
where ACLAuthorizationDatastore = 'net.rim.bmds.shared.service.authorization.JDBCAut horizationDatastore'
'' and hit Enter
6. On the third line type 'go' and hit enter
7. Try to start the service again