Archived:File in use error when re-installing an MTM (Known Issue)

Comments

(no comments yet)

Log in or Join to leave comments.

Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

The article is believed to be still valid for the original topic scope.

Article Metadata

---

Compatibility

Platform(s): Series 80 2nd Edition, S60 1st Edition, S60 2nd Edition, Feature Pack 1, Feature Pack 2, Feature Pack 3, S60 3rd Edition

---

Article

Created: User:Technical writer 1 (July 7, 2006, updated September 7 ,2006)

Last edited: hamishwillee (21 Jun 2012)

Overview

Re-installing an MTM: file in use error.

Description

On S60 and Series 80 platforms there may be problems when re-installing an existing MTM. This concerns only MTM installations that try to handle uninstalling manually after the same MTM has recently been used.
The actual problem arises from a resource file being locked as "in use" even after the MTM group is unregistered. This is usually due to the SendAs capability of other applications running on the device. The applications may have the MTM stored in their list of supported MTMs and thus keep the files locked. This problem should be overcome by removing the MTMs sending capability (KUidMtmQueryCanSendMsg), thus having it be removed by all SendAs clients - and by closing the messaging centre application before uninstalling the MTM.
This problem can be encountered on all S60 platforms, including S60 3rd Edition, and on Series 80 2nd Edition.