[ethlax18]

Hello All.

I was wondering if anyone else was having problems pushing the Enterprise Messenger client down to the 8800 devices. I was even unable to load it on using the USB cable and Desktop Manager until I upgraded to 4.2 Service Pack 1 (as per RIMs advice, was receiving an "no application exists" error with the previous version, was able to load it using javaloader before downloading newest DM version). This solution is getting me by for now, but would really like the ability to push this wirelessly in the future.

Thanks.

[ethlax18]

Fixed this issue. Apparently, the device.xml file that was on the BES (located in C:\Program Files\Common Files\Research In Motion\AppLoader) did not have info on the 8800. Simply copying and pasting an updated version of this file to this location resolved the issue (I got mine from my PC which has the newest Desktop Manager and device software). I did run an apploader.exe /reindex just to make sure, but I don't know if this was necessary or not.

Hope this info helps anyone else running into this problem

E

[alan_kelly]

ethlax18

Thanks for the info. I have a followon question

In my BES environment we have 5 BES servers, do we need to replace the Device.xml on every server ?

Al.

[pharkett@ntlworld.com]

I had a similar problem with the DST Patch . You need to make sure the device.xml in the Fileshares under
\Program Files\Research In Motion\BlackBerry Enterprise Server\PackageCache

is the latest version. Just delete any File shares you have under this directory and they will be rebuilt after the next Policy update (Every 4 hrs)

[hayabusa]

if every server is pushing software to the handhelds you will need to replicate that device.xml file to every server to enable them to see the 8800 and push the app to them

[MJDW]

I am so glad I found this post .. I was on with RIM for 2 hours.. They finally told me to stop the Policy service and delete the folder packageCache..
( I just renamed it) then wait 4 hours it will be recreated. then see if the software pushes to the 8800...

I have the same problem with the 7520 and the 8703.... Weird because I pushed it to the 8700c and the 7250 without problems..

Now i have to wait till tonight to see if this works...

MJ

[MJDW]

So I deleted the PackageCache folder.. it did recreated but the BES is still not pushiing out MS live communicator to the 8800 7520 or 8703.

Guess I am back on the phone with T support.. Any suggestions out there!

MJ

[autsoldnow]

Originally Posted by ethlax18

Hello All.

I was wondering if anyone else was having problems pushing the Enterprise Messenger client down to the 8800 devices. I was even unable to load it on using the USB cable and Desktop Manager until I upgraded to 4.2 Service Pack 1 (as per RIMs advice, was receiving an "no application exists" error with the previous version, was able to load it using javaloader before downloading newest DM version). This solution is getting me by for now, but would really like the ability to push this wirelessly in the future.

Thanks.

Well this maybe of some interest. I was running BES 4.0.4.5 when a customer came to us asking if their new 8800 would work, after the talked with the carrier "Rogers" I was told I'd need up apply some patch to my BES to make it work.

So I applied 5a, then 6 to our BES and I have had nothing but a head ache with getting our new 7290's EA'n with our BES (we have 30 new BBs). After seeing you post I told the client it was going to be a hit and miss but that we could try it.

The clients 8800 sync'd to BES without any problems and its running fine, uhm.. makes me wonder why the 7290's aren't working the same way... sigh

Andrew