[mirmujahed]

Hi,

We have installed BES 5.0.3 with windows server 2008 and Exchange 2007 sp2 .

Recently, we have configured deployment of ocs client for blackberry wireless deployment from the BES serever.

It worked fine for old devices and if we deploy on new devices ( OS 6.0or above ) , it is not working. The deployment status is always showing "Ready to run" and does not change.

When we click the user, under software configuration it shows "The associated device information has not been completely downloaded. Reconciliation information will not be available until the download has been completed."

I also tried to update the vendor.xml and device.xml manually but stil no success.

Appreciate your help in this matter.

Thank you.

[freakinvibe]

In the WebAdmin console if you click on one of those devices, do you see the long list of modules in the "Modules" tab, or is it empty?

Normally, after the Enterprise Activation, the device sends all its properties to the BES (Device model, software version, installed programs and modules etc.). If these properties are for any reason not there, the app cannot be wirelessly sent.

[mirmujahed]

Where can I find the modules tab. The devices were activated successfully. There was no problem in wireless enterprise activation.

[freakinvibe]

Go to the user in question and click on the Blackberrry PIN number.

[mirmujahed]

Yes, I can see a long list of applications under modules...

[freakinvibe]

Please have a look at this KB article:

KB24806-Software configuration applied to users show warning "The associated device information has not been completely downloaded. Reconciliation information will not be available until the download has been completed"

How did you ensure that the device.xml is up-to-date?

[mirmujahed]

The server does not have internet access due to security policies. But I have updated all the device.xml and vendor.xml on the server manually but still no success. :(

[freakinvibe]

Manually updating the device.xml and vendor.xml on BES 5.0 does not help as BES 5.0 is reading the info from the config database. You need to have internet access, see

KB22777-How to update the device.xml and vendor.xml files manually in BlackBerry Enterprise Server 5.0

To ensure security, you can limit internet access to the URLs given in the article.

[Tweedle]

Try to resend service books to that user and check is everything is ok

[freakinvibe]

Re-sending service books will not help if the device.xml information in the config DB is not up-to-date (which is obviously the case, as the BES does not have internet access at all).

[fadmin]

The only other way to do it is to download from time to time and place those two files in the folders on the local intranet website if you have one and change path in sql to go there instead of going out to the RIM:
Device.xml
http://intranet.local/Desktop/Download/XML/Device.xml
Vendor.xml
http://intranet.local/Desktop/Download/XML/Vendor.xml

[mirmujahed]

This is to update you that we have already requested network team to give access to above mentioned URLS on blackberry server.
But I have one confusion. WE have our bb configuration database on central sql server. So I am now confused whether these urls are accessed by blackberry server or sql server. Then in this case who shoudl have access to these urls sql serve or bes server ????

Thanks.

[freakinvibe]

No, the SQL server doesn't need access to the internet.

Just the server which the BAS service runs on needs internet access. This is your BES server if you haven't installed BAS on a separate server.

[mirmujahed]

OK. Thanks for the clarification.
But is there any link between DB and updating of vendor.xml / device.xml files as you earlier mentioned that the config db is not up to date.

[freakinvibe]

Yes. The BAS service (running on the BES) is downloading the latest versions of those files and then it writes that info to the config database, which is residing on the SQL server.

[mirmujahed]

Thanks for the confirmation brother. So it seems the only option is to have internet access allowed to above mentioned links.

Just a thought, does applying the latest patch of maintenance release solve this problem of updating vendor.xml and device.xml files???

[mirmujahed]

Waiting for your reply guyz !!!
Thanks in advance .

[freakinvibe]

No, the behaviour is still the same, you need internet access.

[mirmujahed]

Just wanted to inform you guys that the problem is now resolved. As advised, we had requested access to above mentioned links on the BES server and once that was done, the files were automatically updated to new version and software was deployed to the devices without any issue.
Thanks for the help and support.