Exchange 2003 SP2 and Mobile Devices

Posted on 2006-05-11
Medium Priority
Last Modified: 2012-05-05
Hi :)

First of all:
I am running an Exchange 2003 Environment with a RIM Blackberry Enterprise Server attached.
Yesterday, I applied ExchSrv2003 SP2. The Server Properties (or the Store.exe itself) are now on V. 6.5 (Build 7638.2).

In this KB Article http://support.microsoft.com/kb/895949/EN-US/ under the CAUSE section it states that the issue (Problems with Sending Mails from Mobile Devices like f.e. Blackberry) http://support.microsoft.com/kb/912918/EN-US/ may occur if you are running SP2 with a Store.exe version that is equal to or later than version 7650.23. The servers are running SP2, but my Store.exe version is at 7638.2.

How can it be, that i'm running an older store.exe with SP2 and what means that to me regarding above mentioned MS issue? I don't know if i should apply the patch (which is not downloadable but has to be ordered from MS) or just leave it.

Thx and regards

Question by:OliG
  • 3
  • 2
LVL 104

Expert Comment

ID: 16659663
If you installed SP2 yesterday, then you don't have the latest updates.
On Tuesday night, Microsoft released a hot fix for Exchange through Automatic Updates. That makes the change to the store that causes the problems outlined in 912918.

What Microsoft have done is put the change in to all hotfixes for Exchange after a certain version, and the update that came out earlier in the week was the first once that forced the behaviour change on everyone.

RIM have a KB article on their web site here:

this is the LONG version of the above URL:


Author Comment

ID: 16660163
Thanks for quick answer.

>If you installed SP2 yesterday, then you don't have the latest updates.
On Tuesday night, Microsoft released a hot fix for Exchange through Automatic Updates. That makes the change to the store that causes the problems outlined in 912918.

But Tuesday night was before. I updated the machine yesterday evening (that's Wednesday evening).
I do not see KB895949 in Windows Updatehistory and there's no remaining Patch to be applied. Is it possible, that MS revoked KB895949 in the meantime?

Still unclear (for me) is the exchange version 7638.2 which should be 7650.23 (?). Any idea?

LVL 104

Accepted Solution

Sembee earned 2000 total points
ID: 16660407
The update that was released on Tuesday is covered by


On my home Exchange server I have 7638.2

The information I have is that you need to make the Send As change when deploying Tuesday's hotfix. That would indicate that the behaviour has been changed within Exchange by that update.

I haven't deployed the hotfix on 895949 and as far as I am aware it hasn't been released via any of the updates mechanism.


Author Comment

ID: 16660530
That's interesting.
I deployed KB916803 just before installing SP2, that was KB916803 for Exch.2003 SP1.
After that, i deployed KB916803 again - but this time for Exch.2003 SP2. Didn't recognize that.

Will review the Send As change (even if users didn't report any problems so far).

Thanx much for quick help.
LVL 104

Expert Comment

ID: 16661085
Due to Microsoft's support policy, we are effectively running with two versions of Exchange 2003 - SP1 and SP2.
Patches for SP1 may not be in SP2. Remember service pack 2 is now almost 12 months old. If you apply a fix released for SP1 after July 2005, then it will not be service pack 2.


Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This month, Experts Exchange sat down with resident SQL expert, Jim Horn, for an in-depth look into the makings of a successful career in SQL.
This article will help to fix the below errors for MS Exchange Server 2016 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses
Course of the Month16 days, 13 hours left to enroll

864 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question