OTA upgrades no being performed.
For those of you who are having issues with upgrades not being performed; you shouold really take a look at the BES policy logs. If the application status is "Upgrade required" then every 4 hours (default timer for the polling cycle)your policy service should be queueing the application up for delivery. Do a grep or a find on the log for the PIN# in question and post the results here. There really are a ton of reasons why the application might be failing to isntall on the device. If you have the log level turned up to 4 or 5 though, you should be able to follow whats happening. It should go something like:
(very roughly)
The polling interval runs and determines that app needs to be deployed to the device. The app gets loaded into memory. The app gets sent. The device sends back a status, ie.. app recieved, The device reports back an installation status ie, app installed successfully or app rejected by handheld. *Prior to the app bein sent the Policy service will queue up and send the IT Policy, app policy, and/or any other policy related requests before processing the app (password changes, sevice books etc.) Only after these have processed successully will it queue the app to be sent down.
There is also an ITadminqueue table in your BES database that will show everything queued up to be sent to the handhelds in your system. You should look for you PIN# there and see if the app had been queued previously. You'll sometimes see that the app (or another transaction for that pin#) has a status of 6, or 7 which means that the previous attempt had failed. If this is the case, that pin# will be skipped when the polling process runs. To get around this I routinely clear out records with a status of 6 or 7 to force the Policy service to resend.
|
