Thanks, Jibi. I was seaching on 1.5.0.4

"Just be sure to change the startup parameter for the MDS service, else it'll just fail"


how do you that?

see the link above... :-)

Well you need SP1 in order to get MDAC 2.8 SP1. I don't know why that's needed but that's your answer.

My results: Installed on WS2003SP1 without getting the install failure message mentionned in the KB article or having to click Ignore on anything, and JRE was upgraded to 1.4.2.08 by Setup.

Here is the official answer RIM gave me for needing SP1:

The reason why Windows 2003 Server service pack 1 is now a requirement for BlackBerry Enterprise Server 4.0 service pack 2 is because our software now requires MDAC 2.8 SP1. According to Microsoft, MDAC 2.8 SP1 stand-alone release is not supported on the Microsoft Windows Server 2003 operating system. To update the MDAC version, you must use the operating system service packs or Windows update. For more information from Microsoft, please click on the following link: http://support.microsoft.com/default...b;en-us;899456

Why is it that the list of "known issues" is usually twice as long as stuff that gets fixed.

So does SP2 fix the problem with opening Powerpoint attachments? If I read correctly, it is still a known issue, but sounded like SP2 fixes it if you upgrade from SP1 - HF2.

Thats good to know. I'm about to update a W2K3 machine to BES 4.0.2 and was curious... I simply copy/paste/format these posts and I rarely actually read them... heh. :-)

The funny thing is that MDAC 2.8 comes with 2003...it just doesnt have the updated XML parser, which you have to download separately. Ten bucks SP1 just includes this.

Very interested in feedback from anyone who has upgraded from 4.0 SP1 HF2 to SP2 in production!
Has it introduced any surprises that were not already documented? Are you stable?
How long have you had SP2 running?

I just completed that upgrade. I had serious memory leaks with every version between 4.0 HF2 up through 4.0 SP1 HF3. Had to restart the server 2-3 times a week. I did the SP2 upgrade on Sunday and the server remains stable and responsive as of 5PM Thursday. So the signs are very, very positive.

No reports of problems from users at this point, either. About to do the 1st OTA activation since SP2 install. If that goes well, and the server keeps humming, and I don't have to wipe & reactivate BBs every couple weeks, I will be happy with BES for the first time.

and i've had it running for a little over a week now with no issues.

Thanks for the comments. Sounds promising that they may have made some improvements in getting right this time.

I'm running BES 4.0 SP2 on Windows 2003 without SP1 and I'm not having any issues... Or at least ones known to me. We've been running SP2 for a couple of weeks now, with many OTA's, no problems. Actually we are having far fewer problems then ever before.

Something that I am noticing however, the Handheld Configuration Tool is not quite acurate in reporting who does and who doesn't have a password on their device. So far I've found 5 users of the 7250 and 1 7750 who are reported as not having a password but infact they do. Anyone else seeing that?

Have you checked in the database to see if it is showing a password being enabled for those incorrect users?

Its in SyncDeviceMgmtSummary and listed as PasswordEnabled.

Anyone else notice at the end of the install when you click Yes to restart the server, it doesn't restart it? Or maybe thats not what the message says since I blindly clicked Yes all 3 times that I've installed this already...? heh. I had to restart the servers manually on each time, though.

My recollection is that BES Setup (whether SP, HF or RTM) only offers to start the BES services, not Windows. In my cases, it's always started them.

Thats after the reboot, though (for the SPs, in my experience). Which it does work on that. I'm talking about the installation itself for the SP. There's a giant Yes/No box that pops up that I keep forgetting to read prior to clicking the Yes button.

Also, can you all check the database for the BESVersion under the ServerConfig table? Mine just reset this server to 4.0.0.0 as the reported version, even though Add/Remove and BlackBerry Manager show 4.0.2.8 (or Bundle 11 in A/R). It was showing 4.0.1.x prior to the upgrade.

Installed on Windows 2003 without SP1 and (knock on wood) have had no complaints as of yet. I did this in test first and then production and the only issues I had during the upgrade was that I had to run createdb on the SQL dbase since the regular setup\upgrade would not update the dbase. Also, it is recommended from RIM that a BESMigration.exe be run on the BES for the databases with over 200 users on it - this does a "mock" migration to ensure the users can be migrated, once the test completes you remove the -p and run it again and it migrates the users to the new dbase.

BESMigration -p -s MAPIName OLDBES NEWBES -d DBServerName DBName