[jibi]

Just got off the phone with RIM. I'm sure most of you have noticed that in most (if not all) of these cases of this particular error (maybe others), the device goes through a reboot. Per RIM, it appears that the successful acknowledgement/notification slated to be reported to the BES server is being lost/dropped during the reboot, thus resulting in an error status.

All in all, if the device says that the patch is installed, it's supposedly safe to assume that the patch is, in fact, installed.

On a side note, if you are a TSupport customer, the representative I spoke to said they were compiling cases right now for further research on the issue. He was unsure if there would be an updated patch released to correct the issue, though. Needless to say, if you would like to call in and report your issue, it could potentially help out with their research. Just beware that hold times are quite lengthy during standard business hours. Since it's the weekend, I'm not really sure if they will be any better (I'm sure they have less staffing, but maybe not). So, if you have some time to blow and want to help with a potential fix to the issue, please call in and use your TSupport customer code to report the issue (some troubleshooting will likely be required, though). Otherwise, if you are simply concerned with pushing the patch down and it being applied successfully, it appears that it is safe to install the patch that has been provided to us already, error (0x88) or not.

-J

[mahoward]

Thanks for the update. Were you able to determine what error x87 and x44 are as well?

Also it seems that the 8700's w/ 4.1.0.346 apply very quickly and without error for most of my users. Other models / os versions have some issues.

[x14]

The error code I'm getting is 0x44 on 7290. Not sure if it's different error code for different models.

[mahoward]

I also received my 0x44 on a 7290 version 4.0.2.49 1.8.0.142.

My 0x87 errors are on various models and I have a single 0x41 error.

Overall, assuming that all the 0x88's errors are spurious and really have applied properly, and assuming all the "Awaiting Patch" devices will eventually work, then my "success" rate is at over 90%. Big assumptions, I know...

[mahoward]

On one of my 8700 devices I received the 0x87 error. Turns out the sw downloaded, but would not grab the patch itself. Error was "Patch cannot be downloaded". Strange.

[jibi]

Not sure on the other errors, just the 0x88 one. It appears that RIM's rule of thumb is that 'if the device says it's applied, then it is, in fact, applied.' That may actually prove to be true.

[noname]

Have you guys actually download and read the document "Updating your BlackBerry Environment to Support DST 2007 Changes" (Document ID: 11415718 Version 7)?

There is a table of device event ID error and "0x87" means "EVENT_ERROR_NO_TRANSPORT_AVAILABLE".

There is a further explanation for the device options > "2007 DST Patch"; if the status is "2007 DST patch cannot be downloaded", this means that there was a "A connectivity issue has occurred or the user account is not configured correctly". I have learnt that the patch manager requires the BES MDS-CS (4.1) or the MDS (4.0) to have unrestricted access to (upload/download???) the patch to device. If your MDS-CS | MDS is configured using proxy server, you will need to reconfigure your proxy server to allow the access.

Source: KB12286 - Proxy server is restricting access to DST 2007 upgrades

Hope this info helps! I guess we need to do a lot of read-ups for a successful DST2007 patching !!!

[noname]

Further to my post earlier:

1. 0x41 means "EVENT_WARNING_DOWNLOAD_FAILED"
=> I believe the patcher manager has attempted to download the patch but for some reasons, it failed.

2. 0x44 means "EVENT_WARNING_NOT_ENOUGH_SPACE_DOING_FLASH_RECOVER Y"
=> I believe the handheld is running out of free flash memory. I think your needs to remove any unused applications or housekeep the handheld to free up some space.

Of course, you needs to diagonse together with the status for DST2007 Patch on the handheld too.


Good luck guys!

[mahoward]

Thanks noname for the info. I did read that doc earlier but just assumed that error code table only applies to the device event log, not the DST query tool.

Turns out the 0x87 device had a misconfigured MDS on the device, which jives with the error message description. I had just moved him to a different server, and I have noticed in the past that MDS is broken after an account move between servers until the device is hard reset.

[noname]

Originally Posted by mahoward

Thanks noname for the info. I did read that doc earlier but just assumed that error code table only applies to the device event log, not the DST query tool.

Turns out the 0x87 device had a misconfigured MDS on the device, which jives with the error message description. I had just moved him to a different server, and I have noticed in the past that MDS is broken after an account move between servers until the device is hard reset.

No worries, mahoward. Thanks for letting us know the cause of your issue. Yeah sometimes a hard reset is required to "re-initialize" the service books for the device after moving from one BES to another.