Wise Installation Development | Forum profile

You need to look in the application event log using the event viewer, as this will report the GUID of the component(s) that require(s) repair. You have also used the file extension abc and abs in your original posting. Are you working with two file extensions, or was one of them a typo? If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Hi EdT. Thank you so much for quick reply. I run it from AutoRun.inf file, and the line inside of this file is : [autorun] open=msiexec.exe /i MyInstall.msi /L*v C:\MyInstall.log. Do you have an idea if there is a way to pass the date in here?

Seems like a repair is triggered each time the entrypoint (file association) is triggered. Check the event viewer for which component that is found broken and fix it.

Hi, please let me explain: The original problem happened on W2K8 R2. There a custom action written in WiseScript had the problem. The trace mentioned here (Action645) has been done on W2K8, but the problem happens only, if I enable PageHeap for msiexec. So it looks for me, that in this action dynamically allocated memory is overwritten. Best Regards Alfred

See  https://www-secure.symantec.com/connect/forums/how-do-i-automate-password-prompt-digital-signature#comment-3338441  

I don't know what happened there, SORRY, but .... I have a weird situation. We have some Custom Actions that fire .exe's stored in the install package (Execute Program from Installation in the Wise Installation Studio world). On XP, we're good in that when the .exe's launch any forms or message boxes from the .exe, they are in front of Windows Installer or Installation dialogs. During some testing on newer OSs --Win 7 and...

Okay so I just figure out it out with a little help from your comment.  Our build on .net was set up for AnyCPU which by default on a 64 bit OS looks in the 64bit portion of the OS.  I changed it to build as x86 and then when it runs on a 64bit, it looks in the new 32 bit registry portion.  Now our app works fine. Thanks for pointing me in the right direction.

Thanks for the follow-up Ed. This is being run as an admin on XP, so no worries on the UAC prompt. There are indeed some UILevel items that we've set but I didn't see anything that made itself obvious but I will keep looking.  As far as PUBLIC properties, I had a look through the UI Sequence but again, didn't see anything that popped.   There's a lot to go through though so...

There has clearly changed something in Windows 7, because we also have an application (now I am not talking about the installation) that has a splash screen at startup. During startup (when the splash screen is visible) a dialog might be shown. In Windows XP, this dialog always was shown above the splash. In Windows 7, it is behind, and there is no way for the user to see it, without entering Alt-Tab. I will check if the problem has been...

You can set a property and use that property in LaunchCondition. You can also use vbscript function to call IDABORT Function ExitSetup()    Const IDABORT = 3    ExitSetup=IDABORT End Function With this your script can write to the log, event viewer, or display a message to the installing user.