DST Upgrades
 

As you have found out the handheld patches have been released.
BlackBerry

Please note: the patch is a PATCH MANAGER once it applies, the handheld will need MDS connection service or MDS(4.0) running to download the actual fix. MDSS IS NOT REQUIRED
The following KB walks through setting up a software configuration.
BlackBerry Search Results
Please ignore step 1: On the host computer, install the BlackBerry Device Software for the BlackBerry devices that will receive the DST upgrades.

These articles will show you what else needs to be upgraded:
Please note that the 4.1.3 and 4.0.6 DST upgrades are really only required for FUTURE changes to the DST tables.

GroupWise

Domino

Exchange

Here is an article with pretty pictures (applies to BES for Exchange 4.0)
http://www.blackberry.com/select/dst...007_Update.pdf

I will be updating this post with the Frequently asked questions.

• Known issues with wireless application push:
  Wireless application delivery fails when resending an application
• If you do not use the MDS or MDS Connection Service you will need to change the default browser to the BlackBerry Internet Service to download the patch.
• If your Handheld software isn't listed here then there isn't a patch available yet.

Edited by Jibi (on behalf of a knowledgeable user):

Patch Not Found error
DST2007Query shows errors 0x87 and 0x88.
Fix: Make sure you are using Patch Manager 2.3 and/or disable MDS for the user, delete the Desktop [IPPP] service book, and reset the BlackBerry.

Error Installing Patch
DST2007Query shows error 0x8D.
Fix: Set the Application Control Policy on the Application Software level to <none> and set the ACP on the DST Patch level to the desired ACP.

Error 406 when trying to download and install the patch manually over the air.
Fix: Set the "Disallow Third Party Applicaiton Downloads" IT Policy entry to False (setting to default may not correctly overwrite a True setting on the handheld)

DSTQuery shows users are Awaiting Patch or have an Error status but the handheld says the patch is applied.
Fix: Use DST2007Query tool 4.1.2.12 and run the -invokesync switch

Thanks Mr. Pipes. :-)

I suspect a policy setting may be reason I am getting "2007 DST Patch Manager is running...Patch not found : Trying again at"

Heck if I can figure out what that setting is. I'm now allowing 3rd party application downloads. Could it be that I only allow browsing ability through the BES, or something else? Any ideas, anyone?

(We are not pushing from our BES. Users will point devices to the website to get patch.)

oops
 

My apologies -- you answered my question before I posted it...

I do not use the MDS or MDS Connection Service and so will need to change the default browser to the BlackBerry Internet Service to download the patch.

Thanks again for posting this. n_n

Thanks for posting this!

Is there any way to shorten the time it takes for the software config to pushed to the device? One place I read it could take 4 hours, and in this document it says it could take 24 hours.

What is the advantage of pushing the software vs. sending the OTA download link to all of my 4.x handheld users?

There is a registry hack but I'd have to find it again, It could crash your server so I'd just go ahead and be patient.

After yesterday I don't need my server to crash...again. I'll try the patience route....although it's not my best virtue.

Patch is applying on the Cingular 8100 (current firmware) via a 4.1 SP2 Hotfix 3 Lotus Notes Server.

However once applied it won't let me delete any applications off of the handheld. I have tried it both Required and Optional. But it always gives an IT Policy message when trying to delete an application. If I remove the policy I can delete apps.

Any ideas?

ts937km, this is a known issue for the Pearl, I believe (better damn well be, since I've reported it). for now, once the DST patch has been applied, set the Software configuration to <None> for that user.

I'll call tSupport this morning, also. Let you know if they admit it. And see what I can find out.

Thanks for your help.

Anyone? I'm just curious what the advantage is pushing vs. OTA download. We have MDS enabled and all of my users could do the OTA download.....

I still need to apply the patch to the BES, though, right?

Pushing means you don't have users ignoring their email, it's just less user intervention.

You shouldn't need the BES patch but check the document for your mail platform in the First Post.

Thanks!

I have pushed the patch manager to my handheld as a test:

a 7290 with HH software 4.1.0.256 on platform 1.8.0.143.

It is pushed to my handheld and is trying to get the patch, however it fails:

"patch not found: trying again at: <date/time>"

The MDS (running on besx 4.1.2) shows these HTTP errors:

My device tries to go to the following page: GET /DST2007/patches/0x20400430/4.1.0.256/1.8.0.143/patch.txt HTTP/1.1> on BlackBerry

It then receives a http 404 error (file does not exist) which is correct as I my desktop browser also reports a 404 error.

When I visit the site with my BlackBerry handheld manually, I get redirected to the correct patch. So it seems the patch manager is pointing to the incorrect URL on the BlackBerry site to download the patch.

Anybody seen this before? Any ideas?

EDIT: I opened up a case at RIM. Will report any updates.

They supposedly reported it up to the Development group for further research. No SDR was ever assgined, to my knowledge. RQST00003216830 was my ticket number, in case you want to reference it to whomever you speak to. It's no longer listed in my Remedy queue, which typically means it's been resolved, but perhaps they can pull up some history... :)

So, tell me why I need to roll out this upgrade to our users? Don't we get our time/date updated automatically from Cingular?

Rather, we DO get our phone time/date upgraded from Cingular. Won't the time just update on the day?

Nope the time isn't sent down as the current time, it's sent down as GMT or somesuch and the handheld has to compensate for the timezone that it is in.

I've got a user with an 8700g and this as the status from DST2007Query.exe:
4.1.0.284,2.0.0.120,N/A,Error,0x88,0x00,200

The patch is installed on his device. Lovely. Others show '1.5' instead of 'Error', while others show 'Applied'.

Why didn't RIM make the error code definitions available to us? I'd like to know what 0x88 meant, ya know? Unless I'm just missing something, that is :)

FYI. If anyone receives the following when looking at a user in the BES after patches have been pushed to the device:

Configuration Name: DST 2007
Status Check Time:
Configuration Status: Device state invalid

The Handheld is just off w/ dead battery or such. No biggie.