Hi, I am trying to install MarcEdit 4.6a in a Windows XP Pro SP2 virtul machine and MarcEdit is freezing. What seems to happen is that first MarcEdit installs the MarcEdit bootloader and once complete launches the MarcEdit installer to install Marcedit. It is at this point that I think the MarcEdit bootloader should have quit because it installed sucessfully and laucned that MarcEdit install but what is happening is that it just freezes while MarcEdit continues to install. When I end the MarcEdit bootloader install AppDeploy Repackager 1.2 Beta 3 says that MarcEdit has succesfully install and that it is time to scan for changes made to the system.

The windows error report has the following information
Error signature
szAppName : is-QOBC4.tmp szAppVer : 0.0.0.0 szModName : hungapp
szModVer : 0.0.0.0 offset : 00000000

Technical information about the error report
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\WER2da0.dir00\is-QOBC4.tmp.mdmp
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
After completing the process the package seems to install but throws some error messages. Clicking ignore to these message MarcEdit appears to be installed fine and working.

Product: MarcEdit -- Error 1406. Could not write value VersionMinor to key \Products\42611719BF2D21A4B9DF1B1DDDF3838C\InstallProperties. System error . Verify that you have sufficient access to that key, or contact your support personnel.
Product: MarcEdit -- Error 1406. Could not write value VersionMinor to key \Software\Microsoft\Windows\CurrentVersion\Uninstall\{91711624-D2FB-4A12-9BFD-B1D1DD3F38C8}. System error . Verify that you have sufficient access to that key, or contact your support personnel.
Answered 01/19/2010 by: BW~Merlin
Third Degree Green Belt

Please log in to comment
0
Did you perform a capture with AppDeploy Repackager?
Seems to be an MSI you've re-captured in that case, if so use the original MSI.
Answered 01/20/2010 by: AngelD
Red Belt

Please log in to comment
0
The original file is a exe file that doesn't have a silent install switch which is why I tried to capture the install process and turn it into a MSI file using AppDeplpy Repackager.
Answered 01/20/2010 by: BW~Merlin
Third Degree Green Belt

Please log in to comment
0
You've captured more then you need and in this specific case Windows Installer metadata.

Run the exe manually and when the first (MSI) dialog turns up then take a pause, find the extracted MSI and use that instead.
Answered 01/21/2010 by: AngelD
Red Belt

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