BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 09-10-2010, 01:21 PM   #1 (permalink)
New Member
 
Join Date: Mar 2010
Model: 9600
PIN: N/A
Carrier: Sprint
Posts: 4
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default Push Deployment Job - Not Ready To Deliver

Please Login to Remove!

Hi Everyone,

Interesting problem I have here. We are trying to deploy Enterprise Messenger for OCS 2007. I have successfuly created the software configurations and published the applications. I checked the network drive share which is - Program Files\Research In Motion. Permissions are set to full control. The applications are there and the pkgdbcache.xml and the specification.pkg files are there as well.

However, looking at the deployment job tasks, I'm getting "not ready to deliver" on the application tasks. Not sure what this means. I know it means that the BAS service can not currently deploy the tasks, but I that's not very helpful.

I called RIM and created a ticket, we went through deleting and recreating the software configurations, deleting and repubilshing the applications, etc... But, it's still the same "not ready to deliver". He said that everything looks to setup OK, and to check back in a few hours.

However, I was wondering if anyone had any information or can point me in the right direction. Please help! Thank you all in advance.

Mike
Offline  
Old 09-10-2010, 01:33 PM   #2 (permalink)
BlackBerry God
 
penguin3107's Avatar
 
Join Date: Jan 2005
Model: iOS 5
Carrier: VZW
Posts: 11,701
Post Thanks: 1
Thanked 237 Times in 219 Posts
Default

What version of BES?
What version of Enterprise Messenger?
What model handheld and what OS version?
Does this affect all handhelds, or just some?
Have you updated the device.xml and vendor.xml files on BES?
__________________
BCSA
BES 5.0.3 MR4 :-: Exchange 2007 SP3 RU3
http://port3101.org
Offline  
Old 09-10-2010, 03:15 PM   #3 (permalink)
New Member
 
Join Date: Mar 2010
Model: 9600
PIN: N/A
Carrier: Sprint
Posts: 4
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

The BES version is 5.0.0.137, I have a software configuration for Enterprise Messenger 2.1 and a software configuration for Enterprise Messenger 2.5. We use 8830s (EM 2.1 OS 4) and 9630s (EM 2.5 OS 5). This push issue is happening on all the 9630s that I've tested (I've only tested a few).

No, I haven't updated the device.xml or vendor.xml files? Why is this needed? Where are they located?

Thanks for the help.

Mike
Offline  
Old 09-10-2010, 03:25 PM   #4 (permalink)
New Member
 
Join Date: Mar 2010
Model: 9600
PIN: N/A
Carrier: Sprint
Posts: 4
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Just tested a 8830 with EM 2.1. Same thing, not ready to deliver.

Mike
Offline  
Old 09-11-2010, 05:22 AM   #5 (permalink)
BlackBerry Extraordinaire
 
noname's Avatar
 
Join Date: Sep 2005
Location: Congested Islet of "Foreign Talents" (> 45% of workforce) - Singapore.
Model: Z10
OS: 10.0.0
PIN: NUKE(PAP)
Carrier: Singtel
Posts: 1,504
Post Thanks: 6
Thanked 9 Times in 9 Posts
Default

RIM never help review the BAS logs? Good to check if there is exceptions. Also try reducing the jobs deployment delay to 1 minute from the default 15 to try again. I've heard cases where modifying this may helped.
Posted via BlackBerryForums.com Mobile
Offline  
Old 10-21-2010, 11:17 AM   #6 (permalink)
New Member
 
Join Date: Aug 2010
Model: 8800
PIN: N/A
Carrier: Verizone
Posts: 5
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Has anyone found any resolution to this? We are seeing "Not Ready to Deliver" trying to push device software wirelessly under BES 5. That error is very vague and I can't seem to find any more detail in the logs. Has anyone else run across this?
Offline  
Old 10-21-2010, 11:39 AM   #7 (permalink)
Talking BlackBerry Encyclopedia
 
RadHaz75's Avatar
 
Join Date: Feb 2006
Location: Philadelphia
Model: 9650
OS: 6.0.0.524
PIN: BALL
Carrier: Verizon Wireless
Posts: 456
Post Thanks: 2
Thanked 4 Times in 4 Posts
Default

usually things are not ready to deliver because of dependent tasks that have not yet been marked as complete (or failed). any of those tasks that say not ready to deliver probably has a dependent task listed for it.

i have been running into this problem a lot lately with policy. i find that even though the user has gotten the policy successfully, sometimes the task is not updated to "completed" and stays in a "pending result" state. any task that is not in a completed or failed state will cause any subsequent tasks for that user to be set to "not ready to deliver" until those dependent tasks are completed or failed.

the easy way around this is to find those dependent tasks and manually fail them which will then turn the most recent tasks from "not ready to deliver" to "ready to deliver." I believe the BAS will automatically fail any pending tasks in 30 days.
__________________
Two months ago, I saw a provocative movie on cable TV. It was called The Net, with that girl from the bus.

Last edited by RadHaz75 : 10-21-2010 at 11:40 AM.
Offline  
Old 10-22-2010, 06:12 PM   #8 (permalink)
Knows Where the Search Button Is
 
Join Date: Mar 2010
Model: 8310
PIN: N/A
Carrier: AT&T
Posts: 18
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hello, Our BES has been a big MESS since we installed 5.0.2. We have a bunch of tasks sitting in the 'Not ready to deliver state'.

RedHaz75, can you tell me the best way to find these dependent tasks and how to fail them?

Thanks!!

Paul
Offline  
Old 10-24-2010, 08:36 PM   #9 (permalink)
Talking BlackBerry Encyclopedia
 
RadHaz75's Avatar
 
Join Date: Feb 2006
Location: Philadelphia
Model: 9650
OS: 6.0.0.524
PIN: BALL
Carrier: Verizon Wireless
Posts: 456
Post Thanks: 2
Thanked 4 Times in 4 Posts
Default

Quote:
Originally Posted by pemurray View Post
Hello, Our BES has been a big MESS since we installed 5.0.2. We have a bunch of tasks sitting in the 'Not ready to deliver state'.

RedHaz75, can you tell me the best way to find these dependent tasks and how to fail them?

Thanks!!

Paul
if any task that is not ready to deliver is dependent on another pending task, then it will list that task number in one of the columns in the search results, then just search for that task id. dont forget to set the created after date to something a long time ago so you can actually find the results
__________________
Two months ago, I saw a provocative movie on cable TV. It was called The Net, with that girl from the bus.
Offline  
Old 10-25-2010, 09:11 AM   #10 (permalink)
Talking BlackBerry Encyclopedia
 
cyclmpc's Avatar
 
Join Date: Nov 2008
Location: DC
Model: 9800
OS: 6.0.0.141
PIN: N/A
Carrier: ATT
Posts: 217
Post Thanks: 2
Thanked 2 Times in 2 Posts
Default

Just an FYI, the BAS does not reflect immediate changes. I believe RIM has told me that it can take 15-20 minutes to accurately show status. I had some issues with deployments too, though I have begun to look into the logs themselves to figure what's going on.
__________________
I'm actually lost...
Offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





Copyright 2004-2014 BlackBerryForums.com.
The names RIM and BlackBerry are registered Trademarks of BlackBerry Inc.