MSA and MTA, when installed on the same host, and are locking the tracking database (4281081)

When using the Agent Host feature in QMM 8.7 and higher, it is possible to place the MSA and MTA on the same computer. However it has been observed that the performance if the agents will be affected, because they will have to wait when the tracking database is being locked by another agent.

The following entries can be seen in the MSA or MTA log file:

4/27/2011 12:40:31 PM FileResource::CMutex::IsLocked TraceMsg 4300 Waiting for the resource to be unlocked.
4/27/2011 12:50:29 PM SyncMachine::ReleaseDB TraceMsg 2204 Unlocking tracking database 'E:\emwst.dat'.
4/27/2011 12:50:30 PM SyncMachine::Init TraceMsg 2203 Locking tracking database 'E:\emwst.dat'.
4/27/2011 12:50:30 PM FileResource::CMutex::IsLocked TraceMsg 4300 Waiting for the resource to be unlocked.
4/27/2011 1:04:51 PM SyncMachine::ReleaseDB TraceMsg 2204 Unlocking tracking database 'E:\emwst.dat'.
4/27/2011 1:04:52 PM SyncMachine::Init TraceMsg 2203 Locking tracking database 'E:\emwst.dat'.

This happens because MSA ad MTA are designed to use a tracking database with the same name "emwst.dat"

An enhancement request has been submitted to Development for consideration in a future release for Migration Manager for Exchange. An official Change Request has been created CR#77605.

As a workaround one could use another (separate) host for those agents.

If this issue is causing a real problem, eg. the agents must be located on the same machine or time and performance do matter then please contact Quest Support and reference the workaround mentioned in SOL59160. This workaround will allow to specify different databases directly in the config.ini for each agent, but if this is not implemented via Additional Parameters for all agents then this change can be easily overwritten when opening and closing with OK the properties, which makes the workaround less desirable.