I have a script entry for my own Windows EXE using InstallShield Premium 2012. However, my EXE ultimately relies on presence components provided by Microsoft EXE called AccessDatabaseEngine.exe.
To run this executable file AccessDatabaseEngine.exe with my installation, I added it as an embedded binary resource, then used the custom action wizard to launch AccessDatabaseEngine.exe as “Delayed execution in the system context” as the “After publishing” Exec Sequence installation. This worked as expected: AccessDatabaseEngine.exe starts after my installation completes most of its work.
However, as soon as I see the UI for AccessDatabaseEngine.exe and confirm its user interface prompts, I see "Error 1500," which says that another installation is in progress.
I understand that two MSI packages cannot work at the same time unless you configure the registry to allow it, which I don’t want to do on my client workstations, which are 32-bit Windows 7 machines.
I would like to successfully implement one of the following options:
OPTION ONE: Run the Setup.exe program, which at some point will launch Microsoft AccessDatabaseEngine.exe without generating an error message. I just don’t know how to do this without causing error 1500 ...
OPTION TWO: - Setup.exe Microsoft AccessDatabaseEngine.exe EXE, EXE Setup.exe, , AccessDatabaseEngine.exe.
, OPTION TWO .bat() , EXE EXE, , .
?