I have problems repackaging a program called Meridian 2006 PowerUser from Cyco Software.

It's an Installshield installation. At first I tried wrapping it with a Wisescript. After I succeeded in installing it with an setup.iss, I then tried uninstall it using another uninstall answerfile. But it won't uninstall properly and leaves files and entries behind.

Waiting for reply from the manufacturer, I decided to repackage the program.
However what ever I do with the resulting MSI, upon starting any Meridian executable, I get the message: This application has failed to start because the application configuration is incorrect. Reinstall the application may fix this problem.

I am using Wise, and I have tried our old Wise Packaging Studio v4.6, trial v5, v5.5 and beta 7 and our new version 6.
I also tried doing only a snapshot, snapshot with smartmonitor, only smartmonitor.
Registring all the program's dlls did not work either.

When I use VirtualOS, the diffirent WPS versions give me strange errors like: "error installing ikernel.exe: (0x10000)".

When repacking with old AdminStudio 7 trial and fresh downloaded AdminStudio 7.5 trial version, the resulting MSI works fine.
I can not find any diffirences that might explain the behaviour of the packages.

Can someone give me some tips about rpacking this perticular program or fixing the above errors?

TIA, Jem.

P.s. I have to use Wise to repackage this program (company policy...)
0 Comments   [ + ] Show 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.


An update for other Meridian 2006(b) repackagers...

The reason I couldn't capture Meridian 2006 Poweruser was because it does several installations (4) (also llok at AMM2006b-Setup????.log within c:\Windows):

1. Check if Windows Installer is version 3.0? If not install Windows Installer 3.0
2. Install Microsoft XML 4.0
3. Install Meridian Prerequisites
4. Install Meridian PowerUsers

a. First do an administrative install with: Setup.exe /a
b. Before reboot, copy WindowsInstaller-Kb884016-v2-86.exe, vc80rdst.msi and xml4inst.msi from c:\documents and settings\your username\Local Settings\Temp\{9e16cb6e-823e-473f-b49a-d5b57b492c8d}
c. Restore computer to pre-admin setup state
d. install Windows Installer and reboot (this is only needed if your desktop don't have Windows 3.0 yet)
e. Install Xml4inst.msi
f. Install Vc80rdst.msi
g. reboot computer
h. Now start the capture and choose Smartmonitor (ONLY!!!!!), if you don't do this you'll get some systemfile error within your capture!
i. Edit and customize your WSI/MSI

When ready, create a wrapper with:
1. WindowsInstaller-Kb884016-v2-86.exe /quiet /norestart
2. msiexec.exe /i vc80rdst.msi /quiet /norestart
3. msiexec.exe /i xml4inst.msi /quiet /norestart
(xml4inst.msi creates error 2762 in Eventvwr, so I later replaced this with the msxml.msi (Microsoft XML 4.0 SP2 )
you can download this from the Microsoft website)
4. msiexec.exe /i meridian2006b.msi /quiet /norestart (your captured installation)

Before installing Windows Installer 3.0, please check if Windows 3.1 is not alreeady installed. Installing Windows Installer 3.0 over Window Installer 3.1 WILL break Windows Installer. However this can be repaired by uninstalling bot 3.0 and 3.1 and reinstalling version 3.1.

For Microstation V8 files viewing, you need to install Advanced Viewer 2006b (using version 2006 you need to install several patches/fix to get it to work).
To get a normal view you need to change the default viewer for .DGN files to AdvViewer. Prior to version 2006b the resulting view stayed the same as the default viewer-plugin.
Version 2006b of Adv. Viewer incorporate all the fixes to biew DGN files properly with Adv.Viewer.
One other thing: Adv.Viewer 2006b or 2006 with fixes will NOT work when using a RDP-session, so please use Dameware or another tool if you need to verify the Adv.Viewer with DGN-files.
Answered 01/10/2007 by: Jemboy2004
Senior Yellow Belt

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