[Joluth]

I'm trying to push the BlacKBerry Enterprise Messenger app to a device and it keeps failing. Device is a Sprint 8830 with 4.2.2.123 firmware. I've sent the apps to tons of other handhelds with no problems, inlcuding other handhelds of the same device and firmware that this one has but this one just won't go. I found this in the policy logs.

[40000] (02/22 20:17:49.353):{0xFBC} {***.***@***.com, PIN=********, UserId=***}RequestHandler::PollForMissingApps - Transaction Id already queued for package BlackBerry Enterprise Messenger.
[30000] (02/22 20:17:58.353):{0xFBC} Either the vendor ID 0x69 or hardware ID 0x4000e04 is not supported.
[30000] (02/22 20:17:59.447):{0xFBC} Either the vendor ID 0x69 or hardware ID 0x4000b04 is not supported.
[30000] (02/22 20:17:59.447):{0xFBC} Either the vendor ID 0x69 or hardware ID 0x4000b04 is not supported.
[30000] (02/22 20:18:02.260):{0xFBC} Either the vendor ID 0x6a or hardware ID 0x4000e04 is not supported.
[30000] (02/22 20:18:02.260):{0xFBC} Either the vendor ID 0x6a or hardware ID 0x4000e04 is not supported.

First off, where is it getting the vendor ID from? The vendor.xml file on the BES says that 0x69 is Verizon and 0x6a is AllTel (for what its worth, Sprint is 0x68, but that isn't referenced in any of the logs for this user). Is it possible to 'trick' the BES into thinking its supported by editing the XML file and making up entries for those vendor ID with the Hardware ID listed (the hardware IDs from the log don't show up at all in the vendor.xml file)?

[Ugg]

I've no idea about this bit:

Originally Posted by Joluth

[30000] (02/22 20:17:58.353):{0xFBC} Either the vendor ID 0x69 or hardware ID 0x4000e04 is not supported.

But I'm guessing that this:

Originally Posted by Joluth

Transaction Id already queued for package BlackBerry Enterprise Messenger.

is that it's already tried to push once already and has failed, or been somehow changed before the actual push could take place. A resolution for that is in KB04221 here:

BlackBerry Search Results

I'd fix that first, and then if you still get issues with Vendor ID check the ALX file to make sure that there isn't anything "odd" in there.

[Inphektion]

you need an updated device.xml.
someone keeps one updated on these servers but otherwise you can grab it from the handheld software that came with the device.

[hdawg]

Thank you Jibi

[penguin3107]

Originally Posted by Inphektion

you need an updated device.xml

I might have agreed with this had it not been for this statement by the OP:
"I've sent the apps to tons of other handhelds with no problems, inlcuding other handhelds of the same device and firmware that this one has"

If the OP was able to push apps to an equivalent model device with equivalent firmware... then the device.xml file is likely not the issue. Of course... we're taking the OP's word for it that they did indeed successfully push apps to those equivalent devices.

[Joluth]

Cross my heart its worked for same device/firmware in other cases--I'm going to try the article Ugg suggested and see if that does the trick.

Thanks all!

[Joluth]

Thanks Ugg for that article--that was what I had to do to get it to go for this particular device.