[freakinvibe]

For testing purposes, I have installed BES 5.0.1 (Bundle 70) on Win2003R2 server. I am now trying to distribute an application (Bloomberg) wirelessly to a test device. This worked flawlessly on BES 4.1.6.

I see that the distribution of applications has changed quite a bit with the upgrade to 5, so I started from scratch. Here is what I did:

1) Create a Share on the BES: c:\program files\common files\besapplications and give it full access rights for the BB service user.

2) Blackberry Solution topology > Blackberry Domain > Component view > BlackBerry Administration Service: Set the "BlackBerry Administration Service application shared network drive" to \\bbserver1\besapplications.

3) Create a .zip file with my .alx and .cod files

4) Software > Applications > Add or update applications: Browse to the .zip file created in step 3 and click Next

5) The applications is read from the .zip file and listed on the screen. Now click Publish Application. It automatically gets written to the share and is indexed.

6) Software > Create a software configuration: I give it the name Bloomberg and Save it.

7) Click on the newly created software configuration "Bloomberg", click on the "Applications" Tab and click "Edit software configuration"

8) Click "Add applications to software configuration", then choose the Bloomberg application with a disposition of "Required". The deployment type is set to "Wireless" and the App control policy is "Standard Required"

9) Then click "Add to software configuration". Bloomberg is now listed under "Required Application Name"

10) Now click "Save all". The last step is now to assign this software config to a user.

11) User > Manage users: Select an activated user

12) Click on the "Software configuration" tab and then "Edit user"

13) Choose the Bloomberg software configuration and click Add and then Save all. The software configuration is now listed as "User assigned" under the user.

My expectation was now that (after some time), a job would be created that distributes the app to the device, but that didn't happen. While assigning IT Policies to the user works, assigning software configs doesn't.

What's also strange is that if I click "View resolved applications" for that user, everything is empty.

Has anybody in this forum successfully deployed apps wirelessly with BES 5.0.1? If so, do I miss an additional step? Do you see your applications under "View resolved applications"?

I have rebooted the server and I have re-activated the device, but nothing helps.

Thanks for any information you can give.

[noname]

Complete steps for BES 5.0 listed in KB03748 - How to create a software configuration to deploy third-party applications to BlackBerry smartphones wirelessly from the BlackBerry Enterprise Server.

Link: View Document.

[freakinvibe]

Thank you for this document. I had everything done as described in this document. But I can't complete Task 7 as the job never appears in the Job list. It appears that the applications reconciliation doesn't finish and a job is never created.

[mifa]

Hi,

I am just trying the same. Did all the configuration as described and it will work for some Users but not for all.

There is simply no job created, as far as I can see for users with an 9700 only. On a 9000 Bloomberg is distributed quite quickly...

Any suggestions?

BES = v5.0.1
Bloomberg v1.9.12.14

Bold 9000 with 4.x FW
Bold 9700 with 5.x FW

[noname]

Do a search for the file device.xml on the BES, open it with a notepad and see if you can see entry for 9700 model as follow:-

<!-- 9700 -->
<os model="9700" radio="UMTS-WLAN" series="Onyx" Colour="True" Theme="Normal" JVMLevel="1.0" Camera="True" VideoRecorder="True" VoiceNotes="True" pttApp="True" Memory="Large" KeyboardType="Qwerty" Sound="Tunes8700g" SystemSize="normal" Bluetooth="True" MMS="True" GPS="True" ThemeSupport="Enhanced" VAD="True" JPN_Input="True" WLAN="True" VPN="True" UMA="True">0x04001507</os>

Otherwise, get the latest file from:
Link: https://www.blackberry.com/Desktop/D...XML/Device.xml

[surajd]

Originally Posted by mifa

Hi,

I am just trying the same. Did all the configuration as described and it will work for some Users but not for all.

There is simply no job created, as far as I can see for users with an 9700 only. On a 9000 Bloomberg is distributed quite quickly...

Any suggestions?

BES = v5.0.1
Bloomberg v1.9.12.14

Bold 9000 with 4.x FW
Bold 9700 with 5.x FW

Am having the exact same problem. Deployment to 9000 and other devices are fine, but not to 9700. Device.xml is updated. Is there any impact with vendor.xml?

Suraj

[knottyrope]

IIRC BES 5.0 was supposed to self update device.XML.

[freakinvibe]

Bloomberg v1.9.12.14

Is Bloomberg for Blackberry supposed to run on the OS 5.0 platform (9700)? Has Bloomberg confirmed this?

I know that this is most probably not the cause of your problem as the jobs are not even created.

[laribum]

Hi,

I am trying exactly the same as you, but I cannot "upload" (Add or update applications) the zip file (all.zip).

error message: The multiple alx files in the publishable bundle give conflicting information.

Any ideas how to handle this? Where can I download the latest zip bundle?

BES 5.0.1

Cheers
laribum

[fadmin]

ops

[freakinvibe]

Bloomberg contains two alx files. Remove the all.alx and then zip again.

[perpetual]

Originally Posted by surajd

Am having the exact same problem. Deployment to 9000 and other devices are fine, but not to 9700. Device.xml is updated. Is there any impact with vendor.xml?

Suraj

Suraj - having the same software deployment issues on 9700. Devices.xml & vendor.xml upgraded as per RIM's suggestions. Did you get this resolved?

[jtritton]

i am in the same please

have you checked the globalsettings table in sql and look at the devicexml field. is it the same version as the device.xml on your bes server.

mine isnt - new device.xml on bes but old device.xml refresnced in sql table.

thinking if i update the sql table it will work.
going to phone RIM on how to do it though !

[jjbova]

I don't know how helpful it will be, but here is my 2 cents. I did all the same steps as you, over and over. I was trying to push out Google maps. I tried everything, even going to the SQL tables and trying to manually update the device.xml table (I can't remember the name of the table, but it holds all the device and vendor XML file info).

The fix I found was upgrade. I was on 5.0.1 MR1, and upgraded to 5.0.2 (SP2). This seemed to fix a few issues we were having, but RIGHT after the upgrade finished and I rebooted, google maps started pushing. I wish I would have came up with an actual solution, but you know how being an admin is, sometimes, the best answer is a reboot, an upgrade, or a reimage...... and live forever wondering what the fix really was.

Edit: We are using the BB 9000, and they have 4.6 os installed. our next venture is to push out a new device OS

[andrezinh0]

Hi everyone. I am not sure if you guys solved the issued but we had the same problem here.

While we were looking into it we found out that even though the files (device.xml and vendor.xml) were up to date, what really matters to BAS is the the SQL table called Globalsettings that jtritton mentioned before.

Our problem was that we moved our BAS to a separate server that did not have access to the Internet and could not download these files every 4 hours like it should. So we just needed to configure IE proxy settings and a few hours later the information in the table was updated and we could push software to 9700 devices.

[jgudnas]

Originally Posted by freakinvibe

What's also strange is that if I click "View resolved applications" for that user, everything is empty.

when you click view resolved apps, and it's empty, click the other configured applications tab. That tab will show the apps that the BES is NOT pushing, for whatever reason.

clicking the little eye icon will then give you the reason for the failure.
if it's "unknown device" then the device.xml is the culprit (or possibly that user needs to be re-activated if the bes simply didn't do a capture of the device info, happens rarely)
if it's some other error, like "device memory full"... well. troubleshoot.