In the following text, we will use ASP as an example. But the method described here works for ASP,ASP.NET or in general as a method for controlling iMacros from a very restricted user account.
Problem:
The problem of running iMacros from an ASP page is that by default all programs started by an ASP page have only the rights of the ASP user, which is a very restricted account. An ASP account is significantly more restricted than even the "Guest" user of a machine. However, iMacros needs at least the rights of a "Guest" account or "Limited account" in order to work correctly.
Solution:
Start the "iimRunner.exe" module inside the account, that you want to use iMacros with. In the following, we assume that is a regular user account called "user1". You can use for example the Windows task scheduler for this purpose: Select the option to start iimRunner.exe as soon as the computer boots.
Inside your ASP script you only need to tell iimInit to use iimRunner to start iMacros.exe. This is done by adding the flags "-asp -authorizeAll" (the same flags are used with ASP.NET, PHP or any other scripting language that wants to start iMacros.exe via iimRunner.
i= iim1.iimInit("-asp -authorizeAll")
This is all that you need to do. Now the iMacros Browser can be controlled as before via iimPlay, iimExit etc.
Limit the number of running instances: As a special feature of iimRunner.exe, it can control the number of iMacros instances that are allowed to run in parallel. This is done by changing the MaxNumberOfInstances paramenter in the simple.config file. If the max. number is reached, iimInit returns a -7 error code.