This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Uninstall shortcut broken
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 08, 2010
09:58 AM
Uninstall shortcut broken
I am using IS 2010, and I create an uninstall shortcut in the start menu group for my app. The shortcut target is [SystemFolder]msiexec.exe in the IS project, but when I run the installer and try to click the uninstall shortcut, it searches for missing file msiexec.exe. So I checked the properties for the shortcut and it's this C:\PROGRA~1\COMMON~1\MICROS~1\OFFICE12\msiexec.exe /x {896A27B1-9320-4D17-B2C6-E5EEADA9ED9A}
Why is IS creating this shortcut when [SystemFolder]msiexec.exe is defined in the project before building?
Why is IS creating this shortcut when [SystemFolder]msiexec.exe is defined in the project before building?
(12) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 19, 2010
10:31 AM
Hello? A little help please...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 20, 2010
01:58 PM
Bump, bump, bump
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 21, 2010
06:39 PM
If you create an MSI log file, do you see anything that's changing the value of [SystemFolder]?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 22, 2010
12:47 PM
RobertDickau wrote:
If you create an MSI log file, do you see anything that's changing the value of [SystemFolder]?
How will I know if a log file is created?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 22, 2010
02:15 PM
If neither the installer nor the target system's policy settings are set up to create one automatically, you'll do it by hand with a command like:
msiexec.exe /i installer_name.msi /L*v everything.log
msiexec.exe /i installer_name.msi /L*v everything.log
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 22, 2010
02:50 PM
RobertDickau wrote:
If neither the installer nor the target system's policy settings are set up to create one automatically, you'll do it by hand with a command like:
msiexec.exe /i installer_name.msi /L*v everything.log
I'm creating a single exe image, so can I still create a log file for msi?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 22, 2010
03:12 PM
Please see the InstallShield help for details ("Setup.exe and Update.exe Command-Line Parameters", for example); you can pass switches through setup.exe to msiexec.exe with the /v switch, as in:
setup.exe /v"/L*v C:\everything.log"
setup.exe /v"/L*v C:\everything.log"
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 22, 2010
03:41 PM
RobertDickau wrote:
Please see the InstallShield help for details ("Setup.exe and Update.exe Command-Line Parameters", for example); you can pass switches through setup.exe to msiexec.exe with the /v switch, as in:
setup.exe /v"/L*v C:\everything.log"
Ok I got the log file and this is in it...
Property(S): SystemFolder = C:\PROGRA~1\COMMON~1\MICROS~1\OFFICE12\
Why is this happening?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 22, 2010
03:44 PM
Also found this...
MSI (s) (DC:0C) [15:34:54:451]: Doing action: SetODBCFolders
Action 15:34:54: SetODBCFolders. Initializing ODBC directories
Action start 15:34:54: SetODBCFolders.
MSI (s) (DC:50) [15:34:54:467]: Generating random cookie.
MSI (s) (DC:50) [15:34:54:467]: Created Custom Action Server with PID 3776 (0xEC0).
MSI (s) (DC:C8) [15:34:54:514]: Running as a service.
MSI (s) (DC:C8) [15:34:54:514]: Hello, I'm your 32bit Impersonated custom action server.
MSI (s) (DC:0C) [15:34:54:514]: LocalSQLInstallDriverEx returned 1 in remote context.
ODBC driver Microsoft Access Driver (*.mdb, *.accdb) forcing folder SystemFolder to C:\PROGRA~1\COMMON~1\MICROS~1\OFFICE12\
MSI (s) (DC:0C) [15:34:54:561]: PROPERTY CHANGE: Modifying SystemFolder property. Its current value is 'C:\WINDOWS\system32\'. Its new value: 'C:\PROGRA~1\COMMON~1\MICROS~1\OFFICE12\'.
MSI (s) (DC:0C) [15:34:54:561]: SystemFolder folder has been set to 'C:\PROGRA~1\COMMON~1\MICROS~1\OFFICE12\'
MSI (s) (DC:0C) [15:34:54:561]: Note: 1: 2205 2: 3: ODBCTranslator
MSI (s) (DC:0C) [15:34:54:561]: Note: 1: 2228 2: 3: ODBCTranslator 4: SELECT `ComponentId`,`Description`,`Directory_`, `ActionRequest`, `Installed`, `Attributes` FROM `ODBCTranslator`, `Component` WHERE `ODBCTranslator`.`Component_` = `Component` AND (`ActionRequest` = 1 OR `ActionRequest` = 2)
Action ended 15:34:54: SetODBCFolders. Return value 0.
MSI (s) (DC:0C) [15:34:54:451]: Doing action: SetODBCFolders
Action 15:34:54: SetODBCFolders. Initializing ODBC directories
Action start 15:34:54: SetODBCFolders.
MSI (s) (DC:50) [15:34:54:467]: Generating random cookie.
MSI (s) (DC:50) [15:34:54:467]: Created Custom Action Server with PID 3776 (0xEC0).
MSI (s) (DC:C8) [15:34:54:514]: Running as a service.
MSI (s) (DC:C8) [15:34:54:514]: Hello, I'm your 32bit Impersonated custom action server.
MSI (s) (DC:0C) [15:34:54:514]: LocalSQLInstallDriverEx returned 1 in remote context.
ODBC driver Microsoft Access Driver (*.mdb, *.accdb) forcing folder SystemFolder to C:\PROGRA~1\COMMON~1\MICROS~1\OFFICE12\
MSI (s) (DC:0C) [15:34:54:561]: PROPERTY CHANGE: Modifying SystemFolder property. Its current value is 'C:\WINDOWS\system32\'. Its new value: 'C:\PROGRA~1\COMMON~1\MICROS~1\OFFICE12\'.
MSI (s) (DC:0C) [15:34:54:561]: SystemFolder folder has been set to 'C:\PROGRA~1\COMMON~1\MICROS~1\OFFICE12\'
MSI (s) (DC:0C) [15:34:54:561]: Note: 1: 2205 2: 3: ODBCTranslator
MSI (s) (DC:0C) [15:34:54:561]: Note: 1: 2228 2: 3: ODBCTranslator 4: SELECT `ComponentId`,`Description`,`Directory_`, `ActionRequest`, `Installed`, `Attributes` FROM `ODBCTranslator`, `Component` WHERE `ODBCTranslator`.`Component_` = `Component` AND (`ActionRequest` = 1 OR `ActionRequest` = 2)
Action ended 15:34:54: SetODBCFolders. Return value 0.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 22, 2010
03:45 PM
Possibly related to the ODBC System DSN that's created?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 09, 2010
01:19 PM
Bump... desperately need help!!!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 10, 2010
10:26 AM
I don't have any firsthand experience with this issue, but yes, the "forcing" part of the log suggests the action is responsible.
ODBC driver Microsoft Access Driver (*.mdb, *.accdb) forcing folder SystemFolder to C:\PROGRA~1\COMMON~1\MICROS~1\OFFICE12\For testing, presumably the shortcut works if you remove the DSN? Does this happen on every system? Does anything else in the installer point to that directory? Is the driver already installed somewhere else on the target system?
