[jibi]

FWIW, here's an explanation of the 0x88 error code I and some others have been receiving.

http://www.blackberryforums.com/bes-...planation.html

[x14]

Originally Posted by centrekin

My appointments are doing the same, correct on berry, but 1hr ahead on outlook/exchange.. I assume this is because the DST for exchange is not applied yet.

We found the Microsoft DST patch installed on the workstation is causing this. Opened my calendar from a workstation without the DST patch and it showed up fine.

[centrekin]

What is the name of the dst patch on the workstation?

[centrekin]

So, if the BES Manager is reporting:

Configuration Name: DST2007
Status Check Time:
Configuration Status: Ok
System Status: Up to date
Application Status: Install Required

I can assume that the user needs to reboot their device?

[|||||||]

Originally Posted by centrekin

So, if the BES Manager is reporting:

Configuration Name: DST2007
Status Check Time:
Configuration Status: Ok
System Status: Up to date
Application Status: Install Required

I can assume that the user needs to reboot their device?

You need to wait 4 hours or ensure that the delivery is set to wireless.

[noname]

For everybody's benefits here, I have gathered and summarize all the things that you need to take note for applying the DST2007 patch wirelessly via the Patch Manager:

Caution #1: It is recommended that you deploy the RIM DST 2007 patch manager to an initial group of 100 users and record the impact upon system performance. Use that initial deployment as a benchmark to gauge the size of subsequent deployment groups.

Caution #2: It is recommended that you deploy the RIM DST 2007 patch during off-peak hours but not overnight.

Caution #3: Allow your BlackBerry devices to download third party applications and access external servers for at least 24 hours after the last group of BlackBerry devices is configured to receive the RIM DST 2007 patch. (Source: KB12286 - Proxy server is restricting access to DST 2007 upgrades)


DST2007 Patch Manager can be downloaded here:-
http://www.blackberry.com/DST2007/patch/

Note: Look for "If you are an IT Administrator and would like to wirelessly push this patch to your BlackBerry users..."


Additional Information:
1. Once the upgrade files have been installed on a BlackBerry device, it must be reset before the changes take effect. This reset could take 15 to 30 minutes to complete. (Source: KB12258 - BlackBerry device user is prompted to restart after installing the 2007 DST upgrade)

2. If the RIM DST 2007 patch manager download the update file after into User Mode, allowing the BlackBerry to download the patch manually Options > 2007 DST Patch.

3. RIM is providing an application called DST2007Query.exe that is designed to let IT administrators verify that all BlackBerry devices have been updated. The application will send a query to the Configuration database and report how many devices have and have not been updated.

4. If the device is reporting "2007 DST patch applied", trust the device. I was informed that the DST2007Query.exe is not reporting as it should be as devices may not be able to acknowledge over-the-air back to the BES that the patch has successfully been applied.

On how to use the DST2007Query.exe tool see : KB12333 - Using the DST2007Query.exe tool .


Important Readings:
1. Impact of North American Daylight Saving Time changes in 2007 on BlackBerry smartphone users
2. Reference: Daylight Saving Time 2007: Reference Guide For Deploying the DST 2007 Update
3. Reference: Updating your BlackBerry Environment to Support DST 2007 Changes
4. Documented KB articles related to DST2007 issues


Known Issue:
1. Windows DST Hotfix KB928388 causing calendar appointment to be 1 hour ahead in Outlook/Exchange. <- Thanks to x14 for sharing his testing result


Post Update Remarks:
1. Include RIM KB article - "KB12333 - Using the DST2007Query.exe tool".
2. Include MS Windows patch "KB928388 - 2007 time zone update for Microsoft Windows operating systems"

Cheers!

[x14]

Originally Posted by centrekin

What is the name of the dst patch on the workstation?

It's the Windows DST Hotfix KB928388

[jglass38]

Worked perfectly here with my handheld. I figured I would be the guinea pig before rolling it out to the users. It pushed and prompted me to restart the device. After the restart under options it shows it successfully applied and the dstquery does as well. Good luck to everyone!

[thomas.fischer]

Hi,

we try to poll the DST Patcher to our devices wireless but got a problem.
We´ve configured the software configuration as described from RIM and the Config File is also fine and assignable to users.

We´re using BES 4.1.1 SP2 and get the following error messeage in the POLC Log:

[40000] (02/19 10:24:08.034):{0x1E40} RequestHandler::PollForMissingApps: Starting Poll For Missing Apps.
[20000] (02/19 10:24:08.143):{0x1E40} Syntax error in vendorxml line 0, column 0. Reason: XML document must have a top level element.
[20000] (02/19 10:24:08.143):{0x1E40} Syntax error in devicexml line 0, column 0. Reason: XML document must have a top level element.
[40000] (02/19 10:24:08.143):{0x1E40} RequestHandler::PollForMissingApps: Completed Poll For Missing Apps, elapsed time 0 seconds.

Does anybody got a solution or a tip what the problem is ?

Thank you very much and cheers,

Thomas

[x14]

Support on this issue is rediculous. Just got an email from support asking for handheld model, software version, carrier, etc. I already sent them a DSTQuery result when I opened the ticket.

I'm begining to wonder If they are not doing anything about fixing the DST results and are trying to hold back the flood of phone call until March 11.

[CRWJumper]

Originally Posted by ustreetcub

I have been testing the DST deployment for 2 days now and have had about 95% success rate at pushing the software to the device and having the devices do what they are supposed to do. I have multiple OS versions in my enterprise.

My problem is with the DST2007Query.exe tool not reporting correct information. in one case, the device got the patch, installed it, and asked to be reset. but, DST2007Query.exe says the user errored for some reason. In other cases, DST2007Query.exe says the device is "awaiting patch" when in fact it has received the patch and reset properly. I have asked rim why this is, and they want me to put the device log in debug mode PRIOR to pushing the software to it, gathering tons of information, push the software, then stop logging, export it and send it up. a whole lot of work. unfortunately, it does not look like DST2007Query.exe is rely-on-able for reporting proper information.

We are experiencing an unrelated issue (All appointments disappear for one day then return later or the next day on the device) and RIM has made me send them SO MUCH stuff (Logs, individual appointment ID's both before and after the issue, backups of affected devices, and LOTS more without providing any resolution other than "Install the newest GroupWise client on the BES - (Unsupported FTF version) and we hope this will fix it.
I'm pretty unhappy that they are making me do all of the legwork instead of trying to recreate the issue on thier side. Sounds alot like what they are doing for (to) you in this case.

[noname]

Originally Posted by thomas.fischer

Hi,

we try to poll the DST Patcher to our devices wireless but got a problem.
We´ve configured the software configuration as described from RIM and the Config File is also fine and assignable to users.

We´re using BES 4.1.1 SP2 and get the following error messeage in the POLC Log:

[40000] (02/19 10:24:08.034):{0x1E40} RequestHandler::PollForMissingApps: Starting Poll For Missing Apps.
[20000] (02/19 10:24:08.143):{0x1E40} Syntax error in vendorxml line 0, column 0. Reason: XML document must have a top level element.
[20000] (02/19 10:24:08.143):{0x1E40} Syntax error in devicexml line 0, column 0. Reason: XML document must have a top level element.
[40000] (02/19 10:24:08.143):{0x1E40} RequestHandler::PollForMissingApps: Completed Poll For Missing Apps, elapsed time 0 seconds.

Does anybody got a solution or a tip what the problem is ?

Thank you very much and cheers,

Thomas

Thomas, seems like your BES' vendor.xml and device.xml may be corrupted. Do you have another BES 4.1.2? Try copy and replace them, restart POLC service and try again.

[mahoward]

CRWJumper - I am also getting reports that people's future calendar appt's are disappearing after the update. One device I know ran out of memory so I am guessing the appts were deleted to free up space. There are several others I have not investigated yet, however they appear to have plenty of memory.

Can you verify that the appts do come back eventually? This is a very big deal and could prevent us from pushing out the patch.

[mahoward]

I have verified 2 different devices, an 8700 and 7290, that I know of out of a 100 device test deployment that were missing all appts between 3/11 and 3/31. Disabling / re-enabling cal synch fixed it however this is a big deal for those large deployements (like me) out there.

[thomas.fischer]

Originally Posted by noname

Thomas, seems like your BES' vendor.xml and device.xml may be corrupted. Do you have another BES 4.1.2? Try copy and replace them, restart POLC service and try again.

Thank you but we´ve found the problem. It was a security problem. We have to add the BES Admin Account to the Host where the Shared Files are.

Cheers,

Thomas

[CRWJumper]

Originally Posted by mahoward

CRWJumper - I am also getting reports that people's future calendar appt's are disappearing after the update. One device I know ran out of memory so I am guessing the appts were deleted to free up space. There are several others I have not investigated yet, however they appear to have plenty of memory.

Can you verify that the appts do come back eventually? This is a very big deal and could prevent us from pushing out the patch.

Yes, they always come back.

However, this is in no way related to the patch. We noticed this about 30 days ago and RIM has been working on it with us ever since. (More like we have been working on it for them)

[CRWJumper]

Originally Posted by mahoward

I have verified 2 different devices, an 8700 and 7290, that I know of out of a 100 device test deployment that were missing all appts between 3/11 and 3/31. Disabling / re-enabling cal synch fixed it however this is a big deal for those large deployements (like me) out there.

PLEASE open a ticket with RIM on this. They have repeatedly told me that we (Tampa Electric) are the only ones having this problem. If others start reporting it, perhaps they will get it in gear and provide a fix . . . .

[CRWJumper]

Anyone else seeing the amazing disappearing appointment trick on thier user's devices - either related to this patch or not?

[DarthBBerry]

To be honest with ya'll... this DST '07 patch/upgrade/fiasco is scarin' the hell out of me. I've been working on some procedures for my environment and I sure hope they work. Please take a look and let me know what you think.

Current Status
Windows Server 2003
Lotus Domino 6
BES 4.0.4
NO Desktop Software installed ANYWHERE! All devices are activated and synchronized wirelessly. (only cable the user ever has to plug in is AC power) Therefore, no desktop downloading/upgrading/patching. Everything needs to be completed OTA.

Procedure

1. Windows Server '03 Patch - COMPLETED
2. Upgrade to BES 4.0.6 HF2
3. Download .COD & .ALX
4. loader.exe \Index .COD & .ALX
5. Share files from PF\Common Files.... \DST Upgrade location
6. Create software configuration
7. Set / apply Application Control Policy
8. Wait 4+ hours
9. Wish really hard the darn thing works
10. Run query tool and hope for good results!

Thanks for the help.

BTW - Just think, we're are gonna have to "undo" all of this in 5 years.

[x14]

Originally Posted by DarthBBerry

To be honest with ya'll... this DST '07 patch/upgrade/fiasco is scarin' the hell out of me. I've been working on some procedures for my environment and I sure hope they work. Please take a look and let me know what you think.

We are suppose to start our first batch 50 production users tomorrow. I'm thinking of postponing.