/build/static/layout/Breadcrumb_cap_w.png

MsiProvideComponentFromDescriptor is returning: 0

Hi,

I can't figure out what this means, googled it and the few solutions I found that worked for others where already in place.

Problem is that this vendor MSI (we install as is, no MST) doesn't install correctly the first time. Doing a repair afterwards fixes it most of the time, sometimes two repairs are required. Also sometimes it installs fine the first time.

The difference in the log file when it doesn't install correctly compared to a log file where it does are these extra lines.

MSI (s) (84:28) [14:15:08:646]: Entering MsiProvideComponentFromDescriptor. Descriptor: nnPl(}XP9?_,O3?,aFS^>M5KDYSUnf(HA*L[xeX)y, PathBuf: 244F340, pcchPathBuf: 244F33C, pcchArgsOffset: 244F294
MSI (s) (84:28) [14:15:08:678]: MsiProvideComponentFromDescriptor called for component {997FA962-E067-11D1-9396-00A0C90F27F9}: returning harcoded oleaut32.dll value
MSI (s) (84:28) [14:15:08:693]: MsiProvideComponentFromDescriptor is returning: 0
MSI (s) (84:28) [14:15:08:709]: Entering MsiProvideComponentFromDescriptor. Descriptor: nnPl(}XP9?_,O3?,aFS^>M5KDYSUnf(HA*L[xeX)y, PathBuf: 244F2EC, pcchPathBuf: 244F2E8, pcchArgsOffset: 244F240
MSI (s) (84:28) [14:15:08:740]: MsiProvideComponentFromDescriptor called for component {997FA962-E067-11D1-9396-00A0C90F27F9}: returning harcoded oleaut32.dll value
MSI (s) (84:28) [14:15:08:756]: MsiProvideComponentFromDescriptor is returning: 0
MSI (s) (84:38) [14:15:08:912]: Executing op: ActionStart(Name=writeTnccDepFile.B83FC53B_8462_497C_A98D_E6BEEEFC14EC,,)

All custom actions return a value of 0 or 1 and the exit code is also 0. 

Thanks for your help.

Gizsha

 

 


0 Comments   [ + ] Show comments

Answers (0)

Be the first to answer this question

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ