MonitorWare Knowledge Base

When installing Monitorware 1.2 Final on one of our servers, I got a message saying that a file that needs updating was in use by another application (and listed the app). How can I find out exactly what is going to be updated? I dont want to damage the other application.

Thanks.

Hi Bob,

first let me mention that we user the latest Windows Installer and InstallShield Developer 8 for our installation files.

There is no known way I can tell to find out what exactly is going to be updated. It depends on the version that was installed before.

Lets assume, you had MW Agent 1.1 installed.
In this case, the only thing being updated by 1.2 would be the MW Agent Service, the Client (+ its language xml) and the manual file. These are the files changed between between 1.1 and 1.2.

The Installfile contains a lot of components which are needed as well. But these components were already installed during the MWAgent 1.1 installation. So you see, there are no files updated which are related to other applications.

Regarding the message you got, as the MW Agent Client is written in Visual Basic, the Installer automatically checks if there is an applications running that uses VisualBasic runtime components. If such an application is found, it queries you to close it before. This is just some kind of precautionary measure which the Installer does automatically.

I can post a list with components that are installed by the MW Agent if you like.

The application that the Installer flags is also a Visual Basic app. So the conflict is likely something to do with the VB runtime. I note that there is an "ignore" conflict button. I will try to install Monitorware and take that option and see if all goes well (will let you know).

Actually, I would like to add a rant on Windows installer technology... Sure, it is an improvement over what was there before, but it is - to say the least - not very transparent.

When we build setup programs, we need to merge-in so-called merge modules (e.g. for the VB runtime) and it is not really under our control what is being delivered. Also, the Installer does - in phase 0 of the setup - first check it's own version and eventually update itself first. This can even involve a reboot request... Again, no way around this. And, yes, sure MSI files are more or less required under Windows now, so there is no real way around that, too.

HOWEVER, if you are just interested in running the agent and do not need the client on a specific machine, you can do so without any pain. The full instructions are under the "engine only install" in the manual. In short, all you need to do is copy a single file (I think mwagent.exe), call it with the -i switchto install it and then import a configuration via a registry file. And voila, you are done. No reboots, no system file updates, just plain fun .

I am not sure if it applies here, but it definitely is a life-safer for larger rollouts.

Just my two cents (spiced up a little with my frustration about installer issues...)

Rainer