[pemurray]

Greetings all,

We are on 5.0.2.

Our application vendor created several versions of applications with different module names. And as far as I can tell, that has prevented us from doing upgrades to install the new versions of the applications.

I think it is because they share some modules.

I have had people at RIM support tell me that I should set the old version of the application to OPTIONAL in the software configuration. And then assign a new software configuration for the latest version as REQUIRED.

This does not seem to have the desired effect.

I have also tried creating a new software configuration for the old application and setting it to DISALLOW. But this does not remove the old application.

What is frustrating here is that I have several versions of the applications with different names. Some are the same, some are not.

For instance, I have some users that have FTLJava version 1.0.0.10. I want them to have FTLJava 1.0.0.18. But somehow, I cannot overwrite what is there.

When I check the POLC logs, it shows that BES is busy pushing down FTLJava 1.0.0.16. I don't see that this version is assigned all to the users. So I am wondering if these are some OLD configurations that BES just keeps trying and trying to push down.

Is there a way to clear this out?

Thanks,

Paul

[cyclmpc]

Paul -

It sounds to me like it's time to get a new vendor to work with.

I know that may not be feasible, but I think you have some legitimate points with their software not being an easy thing to update or remove.

I don't think there is an 'easy' way out of this. You have the right information on how to go about removing software configurations, however, from your description, it appears your vendor has done some sloppy work.

I do not know how many users are affected by this, but it appears you'll need to have your users manually remove the software from their devices and try a new software configuration to get the new version to their device. Sorry, I wish there was another way, but I don't think there is.