[i5g]

we're having the same problem in our environment and i've been waiting for rim to get back to me but they havn't. Could someone please provide me the Hot Fix. This will be appreciated.

[Malkier]

Anyone know if this has been fixed with 4.1.5? dont have a 2007 sp1 environment to test with atm.

Also dont see any mention at all about OOF in the 4.1.5 Documents, would be nice if they mentioned if it was fixed or not....

[awharton]

I am installing the sp5 today so will post once done.

[bechard]

Originally Posted by Malkier

Anyone know if this has been fixed with 4.1.5? dont have a 2007 sp1 environment to test with atm.

Also dont see any mention at all about OOF in the 4.1.5 Documents, would be nice if they mentioned if it was fixed or not....

I had asked RIM and was told it is NOT in 4.1.5 but will be in 4.1.5sp1. I don't know this for a fact though but I'm not going to try testing until sp1 is out.

[hdawg]

Originally Posted by bechard

I had asked RIM and was told it is NOT in 4.1.5 but will be in 4.1.5sp1. I don't know this for a fact though but I'm not going to try testing until sp1 is out.

4.1.5 = 4.1 SP5

the next release after that would likely be 4.1 SP1 MR1 ... yup, SPs for SPs ... heh, silly RIM.

[awharton]

No, The 4.1.5.26 does not fix this issue.

[Malkier]

Thanks, guess we'll have to wait for 4.1.5 MR1 or higher....

Why wasn't this listed as a Known Issue in the 4.1 SP5 Release Notes, would have saved a lot of time...

[bechard]

Originally Posted by hdawg

4.1.5 = 4.1 SP5

the next release after that would likely be 4.1 SP1 MR1 ... yup, SPs for SPs ... heh, silly RIM.

sorry, yah I meant its "supposed" to be in 4.1.5mr1

[kapasaca]

We have this escallated within RIM as well and yes they say it won't be fixed until 4.1.5mr1

as a work around they provide the following KB article, but i'm not sure this will work reading the problems here.

BlackBerry Search Results

Can some admins here confirm the issue still exists when the OOO is enabled from outlook and not updated from the blackberry?

[dcwilly]

I checked with RIM on Friday and MR1 for 4.1 SP 5 is not available yet. In the past I had entered an SDR 145355 to request a repair to this problem. This was prior to the release of SP5. When I spoke with RIM on Friday they indicated that there is a new SDR 162722 which covers this problem.

They did not give an ETA on MR1.

There is still a problem and editing the OOO from OWA 2007 does not fix the problem.

[jalcala]

Just to shed a little more light on this, you should experience this issue if you have the following environment:

1) Exchange 2007
2) BES Server
3) Outlook 2003

If you have these criteria your SOL. Blackberry is aware of this and working on the issue. When I spoke with the tech they (development) are working to get their Exchange 2007 environment together. Glad to know they are ahead of the curve on this.

However, if you have Outlook 2007 instead of 2003, their is a work around you can do. However, since I do not have 2007 I did not inquire as to what it was.

[dcwilly]

I hope that this helps save you a little frustration. I have wasted a lot of time on this one. Exchange 2007 introduces some new OOF features. OOF sets a MAPI field called PR_OOF_STATE on all of the clients (Outlook 2003, OWA 2003, Outlook 2007, OWA 2007 and BES). Unfortunately, to accomodate the new features, they changed the location in MAPI for the template for the OOF message. The old location was IPM.Note.Rules.OOFTemplate.Microsoft and the new locations is IPM.Note.Rules.ExternalOOFTemplate.Microsoft. The BES is not able to handle the new location. If you set it using OWA2007 or Outlook 2007 it will work for about 20 minutes to 2 hours and then it will either disable or it will revert back to a previous OOF message.

If you want to see the MAPI Profiles you can download the MFCMapi utility from Microsoft and you can watch this occur.

I hope that this helps. I am a T Support subscriber and I am checking periodically with Rim about the MR1 Patch. They keep saying that it will be out soon but it is not out yet.

I hope that this helps.

[jalcala]

I got the patch from Will yesterday and we will be applying the patch next week and see if it fixes the issue. I first need to take a snapshot of my Blackberry VM in case it blows up.

I will keep you all posted on the outcome.

[WillFulmer]

A VM Snapshot is a great idea. Remember for this fix, all you're doing it RENAMING (not overwriting) two files and starting the services. You could always just replace the original files. Or worst case scenario, take 10 mins (depending on speed of the VM), install BES and repoint to the DB.

[quintex]

We only have the Blackberry Professional Software ver 4.1.4 with Exchange 2007 SP1. We are having the same issues with OOF. Does anyone know if RIM is updating the Blackberry Professional as well as the Enterprise versions?

[coslau]

Originally Posted by jalcala

I got the patch from Will yesterday and we will be applying the patch next week and see if it fixes the issue. I first need to take a snapshot of my Blackberry VM in case it blows up.

I will keep you all posted on the outcome.

Dear,
We have the same issue, exept that OOF is working with some users. don't andertand why...
OOF do not work anymore with BES server down... ???

Does the patch you tried fix this issue ?

Thanks
Laurent

[jalcala]

Originally Posted by coslau

Dear,
We have the same issue, exept that OOF is working with some users. don't andertand why...
OOF do not work anymore with BES server down... ???

Does the patch you tried fix this issue ?

Thanks
Laurent

Laurent,

I have not yet had an opportunity to take care of this. I did get an IM from another member who tried the patch in the UK in his VM environment and it was working. That was last week sometime when I heard from them.

[Azmere]

Just add my 2cents on this I added the patch on the 4.1.4 in the test lab and it worked fine. However we were told in no uncertain terms that RIM would not support us if this change caused issues. Also we were required to change to 4.1.5 to support the features in 4.5 handheld software. My understanding was that the changes are lost with the SP5 install (which makes sense). So we didn't go ahead with this in production.

However RIM were initially telling us June/July on this fix and that has now blown out to December. Is anyone else getting this feedback from RIM? This is a major issue for us as we have to hold our BES users in a separate 2003 environment.

This is not even quoted as a know issue in the SP5 release notes and I think as more people convert to Exchange 2007 they are going to be asking why were they not made aware of this issue?

[nzdude]

Someone on another forum [RE: BES 4.1.x, Exchange 2007 SP1 and OOF] posted that if you use OWA to specify a start and end time range for the Out of Office Assistant, then the problem doesn't occur. I'm testing this at the moment, but feedback from other environments would be useful, and might even help BlackBerry narrow down where the corruption occurs and speed up delivery of a fix.

It's crazy that this isn't listed as a known issue in 4.1 SP5 as it would save everyone time and aggravation.

Does anyone have access to the text of SDR162722 that they can post here?

UPDATE: this workaround did not work for me on Exchange 2007 SP1 using either OWA or Outlook 2007 SP1 to set the OOF with a specified time range.

[jalcala]

Originally Posted by nzdude

UPDATE: this workaround did not work for me on Exchange 2007 SP1 using either OWA or Outlook 2007 SP1 to set the OOF with a specified time range.

Yeah I tried this too and it failed for me as well.