[mahoward]

You do not need the device to show up there to push to all devices. You need an updated device.xml in your apploader directory in the same sharepoint were the DST patch is located.

[Andi]

Thanks - I think we have that correct then. We have never pushed apps from the BES and we are dead in the water. We're escalated with T-Support and calling in reinforcements.... It just seems like we are missing something in the basic software configuration

[centrekin]

Thanks for the confirmation.. I appreciate your help guys!!

[rpfeffer]

I updated my configuration check status and the status is:

Configuration Name: DST2007
Configuration: OK
System Status: Up to date
Application Status: Install required

However, my device has not yet prompted me to install the update. Does it just take a while?

[CentexChris]

We are running BES 4.1, Domino Enviroment. We cant seem to push the patch down to users that have nothing listed under Network Type. When you click on the persons name in BES Manager you should get there device info but a few do not display and we cant get these users updated. The patch fails to loads. Anyone ever seen this problem before??

[Andi]

I have a few users like that (missing device info) and I know some of them had issues with Enterprise Activation completing - I assume those will fail the BES push and I'll have to update manually or OTA.

[rpfeffer]

Ok well....

I just tested pushing the update to my device (8100c) via the software configuration on our server and our BES stopped being able to send email. No error messages, just warnings in the event log and no one is able to send. Currently rebooting and hoping that it fixes it...otherwise t-support here I come.

edit: reboot fixed it, but what the heck? If pushing to one device brings the server down, what is going to happen when I push it to 40?

However, application status reads up to date now as well, but my device never prompted me to do anything at all. Also, under options it does list "2007 DST Patch" and when you click on it it says "2007 DST Patch Manager is running..."

[rpfeffer]

just came across this in Blackberry manager...our server is not set as a push server...did I skip a critical step here?

[JPenrose]

Originally Posted by jibi

Okay, so any luck on figuring out this whole mess?

DST2007Query_SERVER.csv:
1.5,Error,0x88,0x00,200

DST2007Query_Log.txt:
'Time Zone Patch' DB found for [14] [user@domain.com]
...but no 'Time Zone Patch' is patched based on Tag 3 [1.0] entry

[20000] (02/14 15:11:48.948):{0xFA8} Summary of results:
[20000] (02/14 15:11:48.948):{0xFA8} Total number of users: 16
[20000] (02/14 15:11:48.948):{0xFA8} Total number of users requiring patch: 14
[20000] (02/14 15:11:48.948):{0xFA8} 4 upgraded
[20000] (02/14 15:11:48.948):{0xFA8} 10 not upgraded [8 errors]
[20000] (02/14 15:11:48.948):{0xFA8} (10 helper installed)
[20000] (02/14 15:11:48.948):{0xFA8} (4 helper not installed)
[20000] (02/14 15:11:48.948):{0xFA8} Total number of users not requiring patch: 1
[20000] (02/14 15:11:48.948):{0xFA8} 1 upgrade not required
[20000] (02/14 15:11:48.948):{0xFA8} 0 no device info
[20000] (02/14 15:11:48.948):{0xFA8} (0 helper installed)
[20000] (02/14 15:11:48.948):{0xFA8} (1 helper not installed)
[20000] (02/14 15:11:48.948):{0xFA8} Total number of users with unsupported device code: 1

Device:
2007 DST patch applied.

So according to the device, the patch IS applied. According to DST2007Query, it's not. According to DST2007Query, the patcher (not the patch) has been installed on the device.

Now the thing that REALLY pisses me off is that the damn thing won't retry, it appears, because it thinks it's installed.

I just removed the patch from a user's device, enabled MDS, pushed the application back to the user, and now it's reporting as installed/applied in DST2007Query.

For the record, it sucks that MDS is pushing out a service book and applying itself as the default browser and MDS browser even though the damn service is disabled in Windows services, in BlackBerry Manager at the top-level, and for the individual users. I guess it just doesn't get the point that I don't want to use it!

I can tell you that 0x88 is EVENT_ERROR_CONTACTING_WEBSITE_TRANSPORT but the other codes aren't listed. Information from Updating your BlackBerry Environment to Support DST 2007 Changes [Document ID: 11415718 Version 7]

All I seem to get is the Patch Not Found error which seems to indicate that my deices are going to the wrong place. Can anyone confirm this? I only have 1 policy which disallows Web on 51 of my 53 devices. Is this going to FUBAR this patch push?

-J

[rehilliard]

Question rephrased:

Can the device updates be applied in conjunction with the client updates? Or does that confuse an already confusing scenario.

PC updates are being pushed immediately, but based on docs on RIM, I need to get the devices updated before running the CDO and calendar updates. Obviously, the lag between client updates and the calendar update leaves room for new meetings getting created and then set back an hour by the update tool. If I could go ahead with the device updates concurrent with the client updates, then I could do CDO and calendar tool a little quicker.

Thanks for any info.

[rpfeffer]

For the wireless push to work, does our BES need to be set as a push server? I tried a test push yesterday and it caused all of my users not to be able to send email from their devices, despite the fact I only pushed it to my device. Ever since yesterday under options it says that the DST 2007 patch manager is running...is that all it is supposed to say?

[rizenbone]

It seems like I have the same issues as many others. I deployed the DST2007 update via Blackberry Enterprise Server 4.1. BES shows the DST2007 configuration status as OK with system status of OK and application status of up to date for each of my clients.

Yet, DST query shows:

(2) users applied successfull
(4) users with Error,0x43,0x00,503
(1) user with helper not installed

All units are Blackberry Pearl 8100's

I see the DST2007 on the BLackberry 8100 itself.

So, what does this mean? Did the patch apply ok on all or not? BES and the handheld seem to indicate it did, dst query seems to indicate it did not.

Is there any other way to verify?

[x14]

We pushed out our 1st batch of 50 production users last night at 9PM EST. First time I've ever seen a 503 HTTP Response and 0x043 Error.

Pushing it out over night might not of been a good idea. Most of my testing has been during the day so the next batch I'm doing it during the day.

[rizenbone]

I didn't push it out overnight.

As a matter of fact I had 5 of the devices sitting on my desk during the process.

[zip]

I tried pushing to devices last night and got the same 0x43/http 503 errors logged. First time I have seen these. Anyone know if RIM had an issue on the server side? On hold waiting for tsupport... again... daily ritual at this point.

-zip

[rpfeffer]

Originally Posted by zip

I tried pushing to devices last night and got the same 0x43/http 503 errors logged. First time I have seen these. Anyone know if RIM had an issue on the server side? On hold waiting for tsupport... again... daily ritual at this point.

-zip

Ask them if there was a large scale outtage yesterday. Our BES stopped allowing email to be sent from devices around 4pm, right around the time I set the test push. I've heard of at least one other report of the same, so I don't know if my test push caused the server screw up or not.

[zip]

According to them there was no issue last night, but I'm still working with them to identify the problem.

-zip

[rizenbone]

I pushed to 2 devices flawlessly on Mondey, then pushed to 5 more devices immediately after on Monday and 5 of the next group give the Error,0x43,0x00,503.

[JGonzalezGUS]

Same problem here (8703e, 4.1.0.344).
Applied to 1 last week, no problem. Applied to another Monday, no problem. I did 6 yesterday afternoon and all sit this morning with Error, 0x43, http 503 from DST2007Tool.
Web site down?

[rizenbone]

I thought it was supposed to time out after 18 hours and revert to manual as well. Mine have been in the 503 status for roughly 36 hours now. The first 2 applied great, the next 5 all are nopw stuck at 503 saying the patch manager is running with no other status.