[wolfkeeper80]

Tried installing service pack 7 for BES4.1 this morning. The Exchange server is being upgraded to 2007 tomorrow, and we were only at SP4.

Everything looked fine until the final restart of services -- now the MDS service fails to start. Same error as outlined here: Could not start the BlackBerry Mobile Data Service on Local Computer. Error 203 The system could not find the environment option that was entered

However, none of the suggested fixes in that KB article are working. Java appears to be installed correctly (version 6 release 15), and the path in the registry key looks good.

The application error in the event log isn't helping either:

The description for Event ID ( 0 ) in Source ( BMDS ) 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:

Error loading: %s

[EN= 203] [EMSG= xxx26708;xxx8293;xxx31091;xxx29811;xxx28005;xxx25376;xxx30063;xxx25708;xxx28192;xxx29807;xxx26144;xxx28265;xxx8292;xxx26740;xxx8293;xxx28261;xxx26998;xxx28530;xxx28014;xxx28261;xxx8308;xxx28783;xxx26996;xxx28271;xxx29728;xxx24936;xxx8308;xxx24951;xxx8307;xxx28261;xxx25972;xxx25970; (0xcb)] [SRC=xxx23598;xxx28531;xxx29301;xxx25955;xxx27228;xxx30305;xxx29537;xxx29285;xxx25974;xxx11890;c][LINE=1251]

Any suggestions?

[nobody7290]

Dont know, if this helps here, but:
If you look in the BESMgmt Database, and show the table: MDSAGconfig
There is the administrator username and password in this table

When you installed the Service pack, the installer might have asked you for the password.
Did you use this password, or something else ?

if you used a different password, then update the table with the new password, and restart the Blackberry services.

[fadmin]

Ugh after SP7 my MDS starts and all seems to be good but getting "Not Authorized to access....". Used Besadmin acct as usual to update BES server.

[TreeDude]

So, I should hold off on SP7 then......

[fadmin]

It messed up with my URL patterns. Fixed now.

[wolfkeeper80]

Originally Posted by nobody7290

Dont know, if this helps here, but:
If you look in the BESMgmt Database, and show the table: MDSAGconfig
There is the administrator username and password in this table

When you installed the Service pack, the installer might have asked you for the password.
Did you use this password, or something else ?

if you used a different password, then update the table with the new password, and restart the Blackberry services.

Thanks for the suggestion, unfortunately it didn't fix it. I will probably contact RIM today on this, and will let everyone know what I find out.

[nyctechguy]

I had the same error after installing sp7. I tried every fix I could find a dozen times and then I tried running the code from Imagepath in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\BlackBerry MDS Connection Service from the command line and changed the -s switch to -c and got an error related to a missing Msvcr71.dll.

I searched for the file and compared between a working server and the broken one and found that Msvcr71.dll was missing in system32. I copied one from either a SQL subfolder or a java subfolder (sorry it was late) that was 340KB and placed it in system32. After that the service started right up.

I hope this helps.

[dest83]

I had the same exact issue after the sp7 install, and I too was missing Msvcr71.dll. After copying it to system32, it worked again. Thanks nyctechguy.

FYI, for whoever else is having the same problem, I found the file here dll-files.com/dllindex/dll-files.shtml?msvcr71

-edit can't post a link, just add h t t p : / / w w w . before the dll-files

[dest83]

Heh, we should have taken another look at the SP7 release notes:

Setup application known issues
(393021) After you install or upgrade to BlackBerry® Enterprise Server version 4.1 SP7, the BlackBerry MDS Connection Service
might not start because the MSVCR71.dll file might not be installed in the proper location on the computer.
Workaround: Copy the MSVCR71.dll file from <drive>:\Program Files\Research In Motion\BlackBerry Enterprise Server\MDSS
\jre\bin to <drive>:\Program Files\Research In Motion\BlackBerry Enterprise Server\MDS\bin.

[aberk]

Had this exact same problem on a new install of 4.1.7. I just spent 2.5 hours on the phone with RIM tech support, and they never mentioned this. They had me uninstalling and reinstalling JRE multiple times, changing registry paths, and finally do another clean install. None of that made any difference.

What did? Exactly what you had here. Copy the MSVCR71.DLL file in to <drive>:\Program Files\Research In Motion\BlackBerry Enterprise Server\MDS\bin

I can't wait until I get the support evaluation form... I want that 150 minutes of my life back.

[nobody7290]

I now did an upgrade of a 4.x server and had a similar problem.
the mds service failed to start - for an unknown reason the installer did not continue the setup after the restart.
however, It could be fixed by again doing an install of 4.1.7 and then executing the batch file in the bin directory:
mdsis-service.bat install

[nyctechguy]

Originally Posted by dest83

Heh, we should have taken another look at the SP7 release notes:

Release notes?? Next you're going to suggest reading the manual

I don't get it though, if they know it's an issue with the installer why don't they fix it?

Oh well, glad I could point you in the right direction. I had no issue with it running under system32 but I've also added the file into mds\bin and it's still working.

[noname]

Originally Posted by aberk

Had this exact same problem on a new install of 4.1.7. I just spent 2.5 hours on the phone with RIM tech support, and they never mentioned this. They had me uninstalling and reinstalling JRE multiple times, changing registry paths, and finally do another clean install. None of that made any difference.

What did? Exactly what you had here. Copy the MSVCR71.DLL file in to <drive>:\Program Files\Research In Motion\BlackBerry Enterprise Server\MDS\bin

I can't wait until I get the support evaluation form... I want that 150 minutes of my life back.

Give that RIM tech guy a break will you? I do know that those guys are always busy engaged online with cases one after another. It's crazy hectic as they are kinda under-staff and minimum are done to address there resources issue. Unless you hit a case with a known issue found in the release note, there is no way you can memorize all the issues as stated in it. If you've been in a contact centre tech support, you will appreciate what I mean. It's Christmas, you will do great with some compassion. Chinese saying, put away your slaughter axe and become a Buddha. God bless.

[ScratchDuffer]

Sure I'll give the support staff a break - this shouldn't have been released with this PROBLEM in the first place. This breaks the upgrade for a lot of people, this isn't an inconvenient bug. I would pull this build and patch the installed... seems like blatant common sense....

[noname]

Originally Posted by ScratchDuffer

Sure I'll give the support staff a break - this shouldn't have been released with this PROBLEM in the first place. This breaks the upgrade for a lot of people, this isn't an inconvenient bug. I would pull this build and patch the installed... seems like blatant common sense....

Support staff did not develop, build and release the software =) If there's blame, it will be somebody else. Everywhere is the same...

[fadmin]

Do you all have MDSS folder in <drive>:\Program Files\Research In Motion\BlackBerry Enterprise Server\MDSS....? I don't .

[jrbes]

Same problem here, get "http 400 bad request" now, I also noticed that our proxy setting was missing in theMDS-CS area. I do not have a MDSS folder under c:\prog file\RIM\BES\

[jrbes]

Originally Posted by fadmin

It messed up with my URL patterns. Fixed now.

What did you enter to fix them. I looked at these settings in teh db and they are gone. How do you determine what the server URL\FriendlyName\etc should be?