Error code 2732
I created an install in VS .NET 2003 and my installed program didn't run correctly - it got an error when I called my first method in the vendor's dll I am using. Then I read the vendor doc and found out I needed merge modules. So I added them and rebuilt the install and now the install won't even run. I am getting
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2732.
I went back and looked at my build process, and I had these warnings
WARNING: Unable to find module dependency with signature 'OLEAUT32.8C0C59A0_7DC8_11D2_B95D_006097C4DE24'
WARNING: Unable to find module dependency with signature 'Psplog.9BBCFD04_FFD6_11D3_8865_00D0B717743C'
Does anyone know how to resolve this?
Please help. Thanks.
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2732.
I went back and looked at my build process, and I had these warnings
WARNING: Unable to find module dependency with signature 'OLEAUT32.8C0C59A0_7DC8_11D2_B95D_006097C4DE24'
WARNING: Unable to find module dependency with signature 'Psplog.9BBCFD04_FFD6_11D3_8865_00D0B717743C'
Does anyone know how to resolve this?
Please help. Thanks.
0 Comments
[ - ] Hide Comments

so that the conversation will remain readable.
Answer this question
or Comment on this question for clarity
Answers
Don't think there are much people using WinINSTALL but they are going for Wise or InstallShield.
Have you tried to go to the vendor of WinINSTALL for help?
But basically what "Unable to find module dependency with signature" means is that the merge module you included requires (module dependency) other merge modules noted by the "signature".
Have you tried to go to the vendor of WinINSTALL for help?
But basically what "Unable to find module dependency with signature" means is that the merge module you included requires (module dependency) other merge modules noted by the "signature".
Please log in to comment
I am not using WinINSTALL either! Sorry about that - I didn't realize it was a vendor product, I thought it was Microsoft.
Anyway, I didn't find a solution but rather a workaround. Instead of adding the merge modules, there was an alternative way I could install the vendor's ocx and dll's I need.
And I think we will be using Wise!
Thank you.
Anyway, I didn't find a solution but rather a workaround. Instead of adding the merge modules, there was an alternative way I could install the vendor's ocx and dll's I need.
And I think we will be using Wise!
Thank you.
Please log in to comment
Comments