Hi All,

Does anybody already tried to use MST for their MSI which the msi needs ADMIN RIGHTS to be install on the PC. By the way, the workstation uses elevated previliges / elevated user.

Thanks

knight
More power to MSI repackagers[:)]
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Two questions:

1) Does your msi requires Isscript9.msi? Does it call it internally to install Isscript9.msi first?

2) Have you already checked for the custom actions?

Hope this helps
Answered 11/04/2005 by: slb
Purple Belt

Please log in to comment
0
It doesnt requires the Isscript9.msi. It has a custom action which is on execute immediate.

thanks
Answered 11/04/2005 by: knight
Orange Senior Belt

Please log in to comment
0
Just about all of my packages are done that way. What's the problem you're having?
Answered 11/04/2005 by: VikingLoki
Second Degree Brown Belt

Please log in to comment
0
Here is the log file I got when I tried to install the app.

MSI (c) (80:14): Transforming table CustomAction.
MSI (c) (80:14): Creating MSIHANDLE (12) of type 790542 for thread 1044
PDINSTALL: Function CheckForSMP: 'Uniprocessor machine'
DEBUG: Error 2769: Custom Action CheckForSMP.B391C186_6953_11D4_82CB_00D0B72E1DB9 did not close 1 MSIHANDLEs.
Internal Error 2769. CheckForSMP.B391C186_6953_11D4_82CB_00D0B72E1DB9, 1
MSI (s) (24:6C): Transforming table CustomAction.
MSI (s) (24:6C): Creating MSIHANDLE (1) of type 790542 for thread 1388
PDINSTALL: Function InstallNTParService: 'Installed service successfully.'
DEBUG: Error 2769: Custom Action InstallNTParService.B391C188_6953_11D4_82CB_00D0B72E1DB9 did not close 1 MSIHANDLEs.
Internal Error 2769. InstallNTParService.B391C188_6953_11D4_82CB_00D0B72E1DB9, 1
Action 09:05:41: MakeVDDRegEntry.B391C188_6953_11D4_82CB_00D0B72E1DB9.
MSI (s) (24:6C): Executing op: CustomActionSchedule(Action=MakeVDDRegEntry.B391C188_6953_11D4_82CB_00D0B72E1DB9,ActionType=3073,Source=BinaryData,Target=MakeVDDRegEntry,)
MSI (s) (24:6C): Creating MSIHANDLE (3) of type 790536 for thread 1388
PDINSTALL: Function MakeVDDRegEntry: 'Added entry successfully.'
DEBUG: Error 2769: Custom Action MakeVDDRegEntry.B391C188_6953_11D4_82CB_00D0B72E1DB9 did not close 1 MSIHANDLEs.
Internal Error 2769. MakeVDDRegEntry.B391C188_6953_11D4_82CB_00D0B72E1DB9, 1
Action start 09:05:44: ScheduleReboot.
Action ended 09:05:44: ScheduleReboot. Return value 1.
PDINSTALL: Function StartParallelDriver: 'Called ScheduleReboot standard action, returned error code 0.'
PDINSTALL: Function StartParallelDriver: 'Unable to start parallel driver, setting SSDREBOOTREQUIRED property.'
DEBUG: Error 2769: Custom Action StartParallelDriver.B391C188_6953_11D4_82CB_00D0B72E1DB9 did not close 3 MSIHANDLEs.
Internal Error 2769. StartParallelDriver.B391C188_6953_11D4_82CB_00D0B72E1DB9, 3
PDINSTALL: Function CopyUSBINF: 'Using INSTALLDIR.B391C186_6953_11D4_82CB_00D0B72E1DB9 property for INF location.'
PDINSTALL: Function CopyUSBINF: 'Sucessfully deleted any existing OEM*.INF files.'
PDINSTALL: Function CopyUSBINF: 'PnP driver update failed with error code 5.'
PDINSTALL: Function CopyUSBINF: 'Reboot property after INF deletion is 0.'
DEBUG: Error 2769: Custom Action CopyUSBINF.B391C186_6953_11D4_82CB_00D0B72E1DB9 did not close 4 MSIHANDLEs.
Internal Error 2769. CopyUSBINF.B391C186_6953_11D4_82CB_00D0B72E1DB9, 4
MSI (c) (80:14): Doing action: SetupCompleteSuccess
Action start 09:05:45: SetupCompleteSuccess.
MSI (c) (80:14): Transforming table CustomAction.

Action 09:05:45: SetupCompleteSuccess. Dialog created
Action ended 09:05:46: SetupCompleteSuccess. Return value 2.
Answered 11/07/2005 by: knight
Orange Senior Belt

Please log in to comment
0
The log file I got on Uninstallation


MSI (s) (D4:C4): Creating MSIHANDLE (6) of type 790542 for thread 708
PDINSTALL: Function RemoveOldDriver: 'Older driver version detected.'
PDINSTALL: Function RemoveOldDriver: 'CONFIRMUPGRADE property is not set, uninstallation of old driver has been skipped.'
DEBUG: Error 2769: Custom Action RemoveOldDriver.B391C18A_6953_11D4_82CB_00D0B72E1DB9 did not close 2 MSIHANDLEs.
Internal Error 2769. RemoveOldDriver.B391C18A_6953_11D4_82CB_00D0B72E1DB9, 2
Action 09:10:02: RemoveVDDRegEntry.B391C188_6953_11D4_82CB_00D0B72E1DB9.
MSI (s) (D4:C4): Executing op: CustomActionSchedule(Action=RemoveVDDRegEntry.B391C188_6953_11D4_82CB_00D0B72E1DB9,ActionType=3073,Source=BinaryData,Target=RemoveVDDRegEntry,)
MSI (s) (D4:C4): Creating MSIHANDLE (9) of type 790536 for thread 708
PDINSTALL: Function RemoveVDDRegEntry: 'Removed entry successfully.'
DEBUG: Error 2769: Custom Action RemoveVDDRegEntry.B391C188_6953_11D4_82CB_00D0B72E1DB9 did not close 1 MSIHANDLEs.
Internal Error 2769. RemoveVDDRegEntry.B391C188_6953_11D4_82CB_00D0B72E1DB9, 1

Thanks..[;)]
Answered 11/07/2005 by: knight
Orange Senior Belt

Please log in to comment
0
The problem you're having is in a custom action, which is an added piece of custom code that can do just about anything. The issue isn't with MST per se, it's getting that custom action working.

Check the context that the CA is running in. It's either USER or SYSTEM context. The caveat with each is that USER is limited by user security and SYSTEM has full system level security but doesn't have a full user interface available. Ignoring the error code will only help if your CA suceeds but spits out an error code anyway.
Answered 11/07/2005 by: VikingLoki
Second Degree Brown Belt

Please log in to comment
0
I tried to install the commercial application w/o using mst on admin workstation and it works fine. And I tried to install it on elevated workstation and it did not install. Using the MST I created removing only the one install condition "AdminUser" = "You must have administrative access rights to install this driver!" and the application install creating a log file above.

I tried to install the commercial app on the admin account and I think the only difference is on the start parallel driver.

MSI (s) (08:E0): Doing action: StartParallelDriver.B391C188_6953_11D4_82CB_00D0B72E1DB9
Action start 23:11:05: StartParallelDriver.B391C188_6953_11D4_82CB_00D0B72E1DB9.
MSI (s) (08:E0): Creating MSIHANDLE (5) of type 790542 for thread 3040
PDINSTALL: Function StartParallelDriver: 'Service was successfully started!'
DEBUG: Error 2769: Custom Action StartParallelDriver.B391C188_6953_11D4_82CB_00D0B72E1DB9 did not close 1 MSIHANDLEs.
Internal Error 2769. StartParallelDriver.B391C188_6953_11D4_82CB_00D0B72E1DB9, 1
PDINSTALL: Function CopyUSBINF: 'Successfully completed SetupCopyOEMInf.'
PDINSTALL: Function MarkDevicesForReinst: 'Enumeration completes'
PDINSTALL: Function MarkDevicesForReinst: 'Enumeration completes'
PDINSTALL: Function CopyUSBINF: 'Reboot property after INF deletion is 0.'
DEBUG: Error 2769: Custom Action CopyUSBINF.B391C186_6953_11D4_82CB_00D0B72E1DB9 did not close 7 MSIHANDLEs.
Internal Error 2769. CopyUSBINF.B391C186_6953_11D4_82CB_00D0B72E1DB9, 7

Thanks...[8|]
Answered 11/08/2005 by: knight
Orange Senior Belt

Please log in to comment
Answer this question or Comment on this question for clarity