Installing converted MSI packages

Hello friends, I used
two different tools to convert exe applications
msi format for the last
tool I used was EMCO MSI
Package Builder Enterprise.
When I test the msi packages
created, trying to install on a
Windows 7 x86, the error message
appears or lack of permission stating that
another installation is already happening and
this has to be closed first.
I'm tired of redoing the packages and test,
always appear the same mistakes, what can I
do to solve this?
Thank you!
Ivanildo Teixeira Galvão

Hi,
I am just writing to check the status of this thread. Was the information provided in previous reply helpful to you?
Do you have any further questions or concerns? Please feel free to let us know.
If you have any feedback on our support, please click
here
Roger Lu
TechNet Community Support

Similar Messages

Acrobat XI Pro Install via CCP Packager for Enterprise unuseable - tips for the unitiated

Well, after at least six weeks of trying to script and package Acrobat XI via the CCP packager for enterprise (Windows 7 X64) I have learnt many home truths which I thought I would share with the unitiated. This process, from the point of view of an IT admin who has to mass deploy this application to 680 PC's as part of an updated SOE has been the most painful scripting process I have ever found of any package (we successfully deploy Office, and Autodesk apps!). Not only that, but our entire State technical colleges have all purchased the same version. This will be affecting IT staff across a huge area, perhaps worldwide. Below are some some facts relating to this that I will share so others do not have to trawl the minefiled of dead-ends and confusion that is Adobe forums/official documentation. Apologies for not finding direct links to all of the below just yet but I've run out of time as we now have MANUALLY install Acrobat XI on all of these machines. When I get time I will post some of the links:
Facts:
Acrobat XI and Lightroom are NOT "CC" packages. Therefore they rely on a spearate serial numbers to install standalone without another major Adobe product (eg Photoshop) to be installed and then run first. Otherwise they will run in trial mode. If your organistaion is wanting to install these products I highly recommend seeing if Adobe can provide you with these.
Without the use of serial number for Acrobat XI this almost renders the Customisation Wizard effectively useless, none of the silent install switch will work with "Offline Exception"
Yes, one Adobe employee notes that you must install a major package before Acrobat but as the aoplogies for not fixing this were posted last August, we are still in the quandry of not having any useable fix except for the ridiculous "Exceptions" file and Exceptions installer.
If you run the Build and/or execeptions msi's it installs Acrobat twice, gold Adobe, gold.
http://forums.adobe.com/message/6039529#6039529 - look at this for a working script for Photoshop etc, it's great.Thanks to http://forums.adobe.com/people/PetriRiihikallio for posting this. However, alas, it cannot silently install Acrobat correctly (thus far).
It appears that the msi builder for CCP for enterprise is fatally flawed. I have never had as much problem with installing msi's - ever. For example, I have had to re-package the msi multiples times and many times simply running the msi will fail.
The idea that all major installs have to install the 32 bit version AND the 64 bit version is riduclous, enough said.
http://blogs.adobe.com/acrolaw/2013/02/acrobat-xi-deployment-guide-for-large-firms/ this guide may be useful for people who have been given a separate serial number.
http://helpx.adobe.com/acrobat/kb/known-issues-acrobat-xi-reader.html another useful link
I think for the time being I have now wasted enough time trying to tear my hair out with this. I will be waiting for Adobe to announce Acrobat and Lightroom CC. this will enable the correct deployment of a single app without having the bloat my SOE with unnecessary applications that most staff rarely use. Ahhh, I love a good manual install via VNC/RDP, don't you?

Hi Waltpenner and others, yes it can be very confusing and writing script after script got me even more confused.
Now, the story continues, after 6+ hours on the phone with Adobe Support...
When you install Adobe Acrobat XI it asks you to install the C++ Redistributable package and this is where the msi will STOP INSTALLING. even though the MSI says "complete"
Now you think to yourself, OK, I'll write a script to install this msi package no problems, solved.
Nope, the msi for Acrobat Pro XI will Still Halt even if you write this into the script along with halt no err or something similar in your code.
So what do you do?
When you create your msi in Cloud Packager, even though this feels completely against your better judgement tick the box under conflicting Process entitled "Ignore Conflicts and Continue installations" This will (finally) allow you to run the msi. Please see the wonderful deployment script above, which you may still need to edit to your needs (I did) - which I post once it's working perfectly.
You could then install the C++ redist from Microsoft at a later date ----> On that note however (thanks Microsoft for this gem) the Visual C++ redist is an msi for download, but it's actually a zip file calling an exe inside it. I suggest using the App Deploy Repackager to help you change registry entries if you need to install this, but choose your favourite tool (and no I'm not talking about that work colleague you don't like
Note: You will need to install this for certain features of Acro Pro XI to function, most of which relates to sever functions of Acrobat. I will post the exact reasons when I find them. Under pressure to get this deployed, I have not deployed this pckage as yet. Also, I'm unsure how Visual C++ will affect other major apps across my enterprise just yet.
Things to still consider
Acrobat still installs twice in the program directory (1.7GB nd 1.8GB respectively)
As all of the other CC packages are quite easy to install, Adobe needs to provide better service to it's enterprise customers by creating a proper version of Acrobat and Lightroom which is Acrobat CC and Lightroom CC, not version numbers tacked onto their new Cloud Service.
As for the above point I would still recommend creating the smallest msi packages you can, as large msi's that install a number of Apps (eg all of the web/image editing apps) take forever and quite often exhibit install errors
The amount of time I've spent on this is ridiculous, and we've had to package everything from Office to Autocad.
The amount of bandwidth I've chewed up is excessive, with package re-creation (download) of all the products probably about 100GB - however the ability to edit these packages with updates with the CCP is a good step forward.
Using the CCP through a proxy is horrendous, and complicated with the amount of exception through the servers you have to prvide (even then it rarely works).
The MSI packager still needs quite alot of work. As Petri states why he had to write a script like this when Adobe could have done the same thing is beyond him.
Adobe needs to trawl it's forum posts and take out the many false leads and dead ends provided by it's experts.
When I Think of anything else, or wite more scipts I'll let you all know.
Cheers,

Installing a .deb package in Arch

Maybe I'm becoming something uncool (xD), but I not could find a way to install/convert a package from a .deb to a pacman package. The thing is that we are talking about cedega an it is a .deb, then obviosly I don't have the code to make a PKGBUILD by myself (well, we have the CVS but I don't like it), so if anybody helps me I will be really grateful.
Thank you so much

aur/cedega 6.0.2-1
A program that lets you play Windows games in Linux
aur/cedega-cvs 20060907-1
Cedega CVS

App-V SP3 Sequenced Packages Fail to Install via MSI with Error

I upgraded my sequencer machine and 2 client machines to App-V SP3 and proceeded to sequence 2 new packages. I then attempted to install the new packages on the client PCs using the automatically created MSI and got the following errors during install. Note
I am logged into the PC with an Admin user. Screen shot 1 pops up during the install, then screenshot 2 shows up right after. I have also included the event log error. Note that packages sequenced using SP2 install fine via their MSI on the SP3 client machine.
Both a Win7 and Win81 client with SP3 give this error, and I have tried reinstalling the clients on both PCs. If I add and publish the packages via powershell they work fine. Any assistance is appreciated.
AppV Error Code: 0300000102
Event ID:10
If you found this post helpful, please give it a "Helpful" vote. If it answered your question, remember to mark it as an "Answer".

OK, fond the issue in the msi file. Do the following steps to fix the issue:
Download the mst that fixes the issue: http://www.notmyfault.ch/downloads/AppV5_SP3Fix.zip
Extract the mst file and copy it into the same folder as your msi file
Run the following command: msiexec /i YourAppvPackage.msi TRANSFORMS=AppV5_SP3Fix.mst
If you want to run it unattended, add /qb as parameter. Make sure your current directory is the one that contains the msi/mst or just add the full path to your msi and mst. Don't rename your msi, use the original name that has been created by the sequencer.
Let me know if that fixes your issue.
Regards, Michael - http://blog.notmyfault.ch -

Install firefox gpo msi package

Hello,
How to install and upgrade firefox automaticaly on more than 100 computers in corporate invoirment.
(users without administrative permissions and very limited internet connections)
Can we expect original firefox msi packages in the future, to install with Microsoft domain GPO?
Is there any other solution for my problem?
Best regards
Marko Rotar

See e.g. http://www.frontmotion.com/Firefox/index.htm

Adobe Professional MSI package not installing

Hello, I have downloaded the Adobe Professional MSI package from the Creative Cloud Packager but the application will not install. I have tried both 32bit and 64 bit versions to no avail.
Here are some errors from the PDApp.Log File
Any help that could be provided would be greatly appreciated.

Download, install,then run and remove Adobe Reader 6 using the Windows Installer CleanUp Utility. Now try the 9.2 installation again.

Can not install a second product using Adobe .msi packages

Hi,
We install our Adobe products using .MSI packages (made with the Adobe CCPLaucher tool)
The first package is installed correctly, but the second always fails...
Does anyone have a solution to install multiple applications using Adobe MSI packages?
Thank you

Hi Ashish,
I found the PDApp.log for the second .MSI package that doesn't work but i don't understood why...
The MSI package works when I install it for the first time but if I try to install it after another one, it doesn't work anymore.
I have the problem with all the MSI Adobe's package, I can only install one but impossible to install another.
Here below the PAApp.log if you can indicate me what's the problem...thank you very much !
Thanks

Assigned .msi package does not install app

This should be trivial but it does not work - I have created GPO with software installation at computer configuration and linked it to an OU containing test Windows 7 computer. Having assigned new .msi package that resided on shared folder to a computer
I did gpupdate /force on test computer, restarted it and nothing happened. There were no application logs related to MsiInstaller and of course application was not installed on test computer. How to troubleshoot this? gpresult /r on client computer retrieves
info that GPO with software installation was applied but strangely application is not installed.

Hello,
additional GPO question please ask in
http://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverGP&filter=alltypes&sort=lastpostdesc
Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://blogs.msmvps.com/MWeber
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
Twitter:

Install Oracle with a .msi package

Hello, someone know how to install an Oracle client through a package .msi?
Thanks

Thanks for the help...
I read this web, but I don´t know how to create create the .msi package. So I click in "Connecting to an Instance of Oracle and Running SQL Scripts", and I followed the instructions but I am stop in the step 3 because I can´t Open the Oracle Instant Client installation project in InstallShield.
Can you help me in this step?
Thank you very much!!!!

I need step by step guide to install MSI package through group policy

I need step by step guide to install MSI package through group policy its about.
I tried a lot using software deployment with GPO but its not happening may be I am doing mistake I am not getting.
help.
Thanks,
Mohan

Hi,
Maybe we could refer to the following Microsoft KB article for
detailed information about how to use Group Policy to remotely install software.
How to use Group Policy to remotely install software in Windows Server 2008 and in Windows Server 2003
http://support.microsoft.com/kb/816102
Hope this helps.
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

MSI package for Oracle Calendar Client

It would make the deployment/upgrades of the Oracle calendar much easier if it was distributed as a microsoft installer package .msi file so that I could install it automatically on my windows clients by group policy.
The former product "Steltor/CorpoateTime" used to be available as an .msi in addition to a .exe format.
Any suggestions?

the best way is to make a snapshot of the oracle calendar setup and convert it into a msi package. wise for windows installer (http://www.wise.com/wfwi.asp) is a reliable and easy to use software to make such msi packages from installation snapshots.
cheers,
sebastian

Debtap - A script to convert .deb packages to Arch Linux packages

I wrote this script in my free time to help people who, for any reason, want to convert a .deb to an Arch Linux package. It works in a similar way with alien (which converts .deb packages to .rpm packages and vice versa), but, unlike alien, it is focused on accuracy of conversion, trying to translate Debian/Ubuntu packages names to the correct Arch Linux packages names and store them in the dependencies fields of the .PKGINFO metadata in the final package. In other words, it won't only create an Arch package with the data of the original .deb package, but also it will try to create a valid and as accurate as possible .PKGINFO metadata file in the converted package. It uses pkgfile and pacman utilities to achieve this accuracy. The final package can be installed like any local Arch Linux package. Debtap is now available on AUR!
FAQ
Q: What "debtap" stands for?
A: DEB To Arch (Linux) Package
Q: Isn't better to download an official package or write a PKGBUILD in case I need to compile a package or convert a .deb package to an Arch Linux package?
A: Sure it is, and I truely encourage you to do so. Debtap was written to create packages that either cannot be compiled (closed source packages) or cannot be built from AUR for various reasons (error during compiling or unavailable files), as a quick 'n' dirty solution and an extra option for creating Arch Linux packages for Arch Linux users.
Q: So debtap will help me only in case I need to convert specific .deb packages to Arch Linux packages?
A: No. In case you need to write a new PKGBUILD for a package that already exists in the Debian/Ubuntu distributions, by converting its .deb package to Arch package with debtap, thanks to the packages names translator function inside the script, it can help you determine which dependencies are needed for the package you write the PKGBUILD for and complete the necessary fields.
Q: What are the minimum requirements to run this script?
A: You need to have installed these dependencies: bash, binutils (provides ar utility for extracting .deb package), pkgfile, and fakeroot. You must run at least once (preferably recently) "debtap -u" to create/update pkgfile and debtap database (you do this with root privileges).
Q: Debtap needs a lot of time to convert a package. So, why this is happening?
A: Like I said, debtap is focused on accuracy. It won't just unpack a .deb package and then repackage its data to an Arch Linux package, ignoring metadata. Depending on the speed of your processor and the package itself, conversion can take from a few seconds to several minutes.
Q: During conversion I get several warning messages, why?
A: Debtap cannot be 100% accurate for several reasons, the main reason for this is the complexity of packages names. If you want to check the freshly generated .PKGINFO and .INSTALL (this is optional file) metadata files or even fix the untranslated packages names inside .PKGINFO, debtap offers you the option to edit these files before compressing the final package.
Q: How do I use debtap?
A: The syntax is quite simple actually: debtap [option] package_filename
For example: debtap world-of-goo-demo_1.0_i386.deb
Any recommendations or questions for debtap are welcomed!
Last edited by helix (2015-05-21 22:54:17)

Hi helix. I've had trouble trying to use your script with ubuntu software from The Open University
debtap OpenUniversity-ubuntu-0.1.3.20130104.deb
==> Extracting package data...
==> Fixing possible directories structure differencies...
==> Generating .PKGINFO file...
debtap OpenUniversity-ubuntu-0.1.3.20130104.deb
==> Extracting package data...
==> Fixing possible directories structure differencies...
==> Generating .PKGINFO file...
:: Enter Packager name:
NewPepper2013
:: Enter package license (you can enter multiple licenses comma seperated):
closed
:: If you want to edit .PKGINFO file, press (1) For vi (2) For nano (3) For a cu stom editor or any other key to continue:
==> Generating .MTREE file...
==> Creating final package...
xz: unrecognized option '--1-any.pkg.tar'
xz: Try `xz --help' for more information.
mv: cannot stat â*.xzâ: No such file or directory
==> Removing leftover files...
==> Package successfully created!
The software is called NewPepper 2013 but i've not been able to find it online except on the ou website.

Basic MSI package.

Hi people,
I am trying to create a .MSI file from a product called Chart Reader.
However it is not capturing .ocx registrations in the registry.
Any help would be great
Thanks
Pete
Wednesday, March 23, 2005 07:59:40PM
Starting conversion
Creating Developer project: C:\Packages\ChartR2\Chart Reader.ism
Reading repackager output file
Loading registry entries
Creating components for the files captured
Mapping registry information to the Advertising tables
Mapping typelib data from registry information to the TypeLib
table
Mapping COM data from registry information
Undefined CLSID '{0968e258-16c7-4dba-aa86-462dd61e31a3}': no component
exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
CLSID
'{0968e258-16c7-4dba-aa86-462dd61e31a3}' will remain in the Registry table
because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
list. This may result in ICE33 warnings.
Undefined CLSID '{32B533BB-EDAE-11d0-BD5A-00AA00B92AF1}': no component
exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
CLSID
'{32B533BB-EDAE-11d0-BD5A-00AA00B92AF1}' will remain in the Registry table
because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
list. This may result in ICE33 warnings.
Undefined CLSID '{3dd53d40-7b8b-11D0-b013-00aa0059ce02}': no component
exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
CLSID
'{3dd53d40-7b8b-11D0-b013-00aa0059ce02}' will remain in the Registry table
because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
list. This may result in ICE33 warnings.
Undefined CLSID '{54c37cd0-d944-11d0-a9f4-006097942311}': no component
exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
CLSID
'{54c37cd0-d944-11d0-a9f4-006097942311}' will remain in the Registry table
because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
list. This may result in ICE33 warnings.
Undefined CLSID '{79eac9e0-baf9-11ce-8c82-00aa004ba90b}': no component
exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
CLSID
'{79eac9e0-baf9-11ce-8c82-00aa004ba90b}' will remain in the Registry table
because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
list. This may result in ICE33 warnings.
Undefined CLSID '{79eac9e2-baf9-11ce-8c82-00aa004ba90b}': no component
exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
CLSID
'{79eac9e2-baf9-11ce-8c82-00aa004ba90b}' will remain in the Registry table
because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
list. This may result in ICE33 warnings.
Undefined CLSID '{79eac9e3-baf9-11ce-8c82-00aa004ba90b}': no component
exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
CLSID
'{79eac9e3-baf9-11ce-8c82-00aa004ba90b}' will remain in the Registry table
because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
list. This may result in ICE33 warnings.
Undefined CLSID '{79eac9e4-baf9-11ce-8c82-00aa004ba90b}': no component
exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
CLSID
'{79eac9e4-baf9-11ce-8c82-00aa004ba90b}' will remain in the Registry table
because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
list. This may result in ICE33 warnings.
Undefined CLSID '{79eac9e5-baf9-11ce-8c82-00aa004ba90b}': no component
exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
CLSID
'{79eac9e5-baf9-11ce-8c82-00aa004ba90b}' will remain in the Registry table
because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
list. This may result in ICE33 warnings.
Undefined CLSID '{79eac9e6-baf9-11ce-8c82-00aa004ba90b}': no component
exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
CLSID
'{79eac9e6-baf9-11ce-8c82-00aa004ba90b}' will remain in the Registry table
because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
list. This may result in ICE33 warnings.
Undefined CLSID '{79eac9e7-baf9-11ce-8c82-00aa004ba90b}': no component
exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
CLSID
'{79eac9e7-baf9-11ce-8c82-00aa004ba90b}' will remain in the Registry table
because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
list. This may result in ICE33 warnings.
Undefined CLSID '{79EAC9F1-BAF9-11CE-8C82-00AA004BA90B}': no component
exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
CLSID
'{79EAC9F1-BAF9-11CE-8C82-00AA004BA90B}' will remain in the Registry table
because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
list. This may result in ICE33 warnings.
Undefined CLSID '{79eac9f2-baf9-11ce-8c82-00aa004ba90b}': no component
exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
CLSID
'{79eac9f2-baf9-11ce-8c82-00aa004ba90b}' will remain in the Registry table
because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
list. This may result in ICE33 warnings.
Undefined CLSID '{7b8a2d94-0ac9-11d1-896c-00c04Fb6bfc4}': no component
exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
CLSID
'{7b8a2d94-0ac9-11d1-896c-00c04Fb6bfc4}' will remain in the Registry table
because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
list. This may result in ICE33 warnings.
Undefined CLSID '{7b8a2d95-0ac9-11d1-896c-00c04Fb6bfc4}': no component
exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
CLSID
'{7b8a2d95-0ac9-11d1-896c-00c04Fb6bfc4}' will remain in the Registry table
because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
list. This may result in ICE33 warnings.
Undefined CLSID '{8f6b0360-b80d-11d0-a9b3-006097942311}': no component
exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
CLSID
'{8f6b0360-b80d-11d0-a9b3-006097942311}' will remain in the Registry table
because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
list. This may result in ICE33 warnings.
Undefined CLSID '{B15B8DC0-C7E1-11d0-8680-00AA00BDCB71}': no component
exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
CLSID
'{B15B8DC0-C7E1-11d0-8680-00AA00BDCB71}' will remain in the Registry table
because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
list. This may result in ICE33 warnings.
Undefined CLSID '{c733e4af-576e-11d0-b28c-00c04fd7cd22}': no component
exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
CLSID
'{c733e4af-576e-11d0-b28c-00c04fd7cd22}' will remain in the Registry table
because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
list. This may result in ICE33 warnings.
Mapping Application IDs from registry information and writing to
the AppId table
Mapping ProgIDs from registry information
Writing to the Class table
Mapping file extensions and MIME types from registry information
to the Extension and Mime tables
Mapping shell extension verbs from registry information to the
Verb table
Writing to the ProgId table
Mapping application paths from registry information
Mapping environment variables from registry information to the Environment
table
Processing .INI file changes and writing to the IniFile table
Scanning for ODBC drivers and writing to the ODBCSource and ODBCDriver
tables
Applying merge modules
Including merge module 'Microsoft (R) C Runtime Library'
Including merge module 'Microsoft OLE 2.40 for Windows
NT(TM) and
Windows 95(TM) Operating Systems'
Including merge module 'Windows Common Controls ActiveX Control
DLL'
Including merge module 'CMDialog ActiveX Control DLL'
Including merge module 'Visual Basic Virtual Machine'
Including merge module 'Microsoft Component Category Manager
Library'
Including merge module 'MCI OLE Control DLL'
Creating directory folders and writing to the CreateFolders table
Writing unmapped registry information to the Registry table
Writing information to the RemoveRegistry table
Creating shortcuts and writing to the Shortcut table
A non-advertised shortcut must be created for Embedding In A Web
Page.pdf in
folder [ProgramMenuFolder]i2\Chart Reader 6\Documentation. Autorepair
cannot be enabled for this shortcut.
A non-advertised shortcut must be created for User Guide.pdf in folder
[ProgramMenuFolder]i2\Chart Reader 6\Documentation. Autorepair cannot be
enabled for this shortcut.
Building .msi package
Created release folders
AdminExecuteSequence table successfully built
AdminUISequence table successfully built
AdvtExecuteSequence table successfully built
AdvtUISequence table successfully built
InstallExecuteSequence table successfully built
InstallUISequence table successfully built
Directory table successfully built
Feature table successfully built
FeatureComponents table successfully built
Component table successfully built
Loading File table
Building File table
Merging modules...
Merging Microsoft Component Category Manager Library: C:\Program
Files\InstallShield\AdminStudio\6.0\Repackager\COM CAT.MSM
Merging Windows Common Controls ActiveX Control DLL: C:\Program
Files\InstallShield\AdminStudio\6.0\Repackager\COM CTL32.MSM
Merging CMDialog ActiveX Control DLL: C:\Program
Files\InstallShield\AdminStudio\6.0\Repackager\COM DLG32.MSM
Merging MCI OLE Control DLL: C:\Program
Files\InstallShield\AdminStudio\6.0\Repackager\MCI 32.MSM
Merging Visual Basic Virtual Machine: C:\Program
Files\InstallShield\AdminStudio\6.0\Repackager\MSV BVM60.MSM
Merging Microsoft (R) C Runtime Library: C:\Program
Files\InstallShield\AdminStudio\6.0\Repackager\MSV CRT.MSM
Merging Microsoft OLE 2.40 for Windows NT(TM) and Windows 95(TM) Operating
Systems: C:\Program
Files\InstallShield\AdminStudio\6.0\Repackager\OLE AUT32.MSM
File table successfully built
Building MsiFileHash table
MsiFileHash table successfully built
Class table successfully built
Extension table successfully built
ODBCDataSource table successfully built
ODBCDriver table successfully built
ActionText table successfully built
AppSearch table successfully built
BindImage table successfully built
CCPSearch table successfully built
Condition table successfully built
AppId table successfully built
ISDEV : warning -6261: The property ALLUSERS is defined in the property
table. This may result in a setup that is always installed per-machine
when
it has been advertised as a per-user install. It is recommended that the
ALLUSERS property not be defined in the Property table.
Property table successfully built
BBControl table successfully built
Billboard table successfully built
Binary table successfully built
CompLocator table successfully built
Complus table successfully built
ControlCondition table successfully built
ControlEvent table successfully built
CreateFolder table successfully built
CustomAction table successfully built
Error table successfully built
DrLocator table successfully built
DuplicateFile table successfully built
Environment table successfully built
EventMapping table successfully built
FileSFPCatalog table successfully built
Font table successfully built
IniFile table successfully built
IniLocator table successfully built
IsolatedComponent table successfully built
Verb table successfully built
LaunchCondition table successfully built
LockPermissions table successfully built
MIME table successfully built
MoveFile table successfully built
MsiAssembly table successfully built
MsiAssemblyName table successfully built
MsiDigitalCertificate table successfully built
MsiDigitalSignature table successfully built
ODBCAttribute table successfully built
ODBCSourceAttribute table successfully built
ODBCTranslator table successfully built
PatchPackage table successfully built
ProgId table successfully built
PublishComponent table successfully built
Registry table successfully built
RegLocator table successfully built
RemoveFile table successfully built
RemoveIniFile table successfully built
RemoveRegistry table successfully built
ReserveCost table successfully built
SelfReg table successfully built
ServiceControl table successfully built
ServiceInstall table successfully built
SFPCatalog table successfully built
Shortcut table successfully built
Signature table successfully built
TextStyle table successfully built
TypeLib table successfully built
UIText table successfully built
Upgrade table successfully built
_Validation table successfully built
Searching project for extract-at-build components...
Validating Custom Action sequencing
Dialog AdminChangeFolder for language English (United States) built
Dialog AdminNetworkLocation for language English (United States) built
Dialog AdminWelcome for language English (United States) built
Dialog CancelSetup for language English (United States) built
Dialog CustomSetup for language English (United States) built
Dialog CustomSetupTips for language English (United States) built
Dialog CustomerInformation for language English (United States) built
Dialog DatabaseFolder for language English (United States) built
Dialog DestinationFolder for language English (United States) built
Dialog DiskSpaceRequirements for language English (United States) built
Dialog FilesInUse for language English (United States) built
Dialog InstallChangeFolder for language English (United States) built
Dialog InstallWelcome for language English (United States) built
Dialog LicenseAgreement for language English (United States) built
Dialog MaintenanceType for language English (United States) built
Dialog MaintenanceWelcome for language English (United States) built
Dialog OutOfSpace for language English (United States) built
Dialog PatchWelcome for language English (United States) built
Dialog ReadyToInstall for language English (United States) built
Dialog ReadyToRemove for language English (United States) built
Dialog SQLBrowse for language English (United States) built
Dialog SQLLogin for language English (United States) built
Dialog SetupCompleteError for language English (United States) built
Dialog SetupCompleteSuccess for language English (United States) built
Dialog SetupError for language English (United States) built
Dialog SetupInitialization for language English (United States) built
Dialog SetupInterrupted for language English (United States) built
Dialog SetupProgress for language English (United States) built
Dialog SetupResume for language English (United States) built
Dialog SetupType for language English (United States) built
Dialog SplashBitmap for language English (United States) built
Resolving strings...
Language English (United States) built
Building CAB files...
Data1.cab built
Files built
Media table successfully built
Performing Upgrading and Patching Validation
Automatic update notification disabled
Product1\Release1 - 0 error(s), 1 warning(s)
Finished successfully.
Conversion completed with 20 warning(s).
Output file: C:\Packages\ChartR2\Chart Reader.msi

Peter Norris wrote:
> Hi people,
>
> I am trying to create a .MSI file from a product called Chart Reader.
>
> However it is not capturing .ocx registrations in the registry.
>
>
> Any help would be great
>
> Thanks
>
> Pete
>
> Wednesday, March 23, 2005 07:59:40PM
> Starting conversion
> Creating Developer project: C:\Packages\ChartR2\Chart Reader.ism
> Reading repackager output file
> Loading registry entries
> Creating components for the files captured
> Mapping registry information to the Advertising tables
> Mapping typelib data from registry information to the TypeLib
> table
> Mapping COM data from registry information
> Undefined CLSID '{0968e258-16c7-4dba-aa86-462dd61e31a3}': no component
> exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
> CLSID
> '{0968e258-16c7-4dba-aa86-462dd61e31a3}' will remain in the Registry table
> because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
> list. This may result in ICE33 warnings.
> Undefined CLSID '{32B533BB-EDAE-11d0-BD5A-00AA00B92AF1}': no component
> exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
> CLSID
> '{32B533BB-EDAE-11d0-BD5A-00AA00B92AF1}' will remain in the Registry table
> because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
> list. This may result in ICE33 warnings.
> Undefined CLSID '{3dd53d40-7b8b-11D0-b013-00aa0059ce02}': no component
> exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
> CLSID
> '{3dd53d40-7b8b-11D0-b013-00aa0059ce02}' will remain in the Registry table
> because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
> list. This may result in ICE33 warnings.
> Undefined CLSID '{54c37cd0-d944-11d0-a9f4-006097942311}': no component
> exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
> CLSID
> '{54c37cd0-d944-11d0-a9f4-006097942311}' will remain in the Registry table
> because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
> list. This may result in ICE33 warnings.
> Undefined CLSID '{79eac9e0-baf9-11ce-8c82-00aa004ba90b}': no component
> exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
> CLSID
> '{79eac9e0-baf9-11ce-8c82-00aa004ba90b}' will remain in the Registry table
> because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
> list. This may result in ICE33 warnings.
> Undefined CLSID '{79eac9e2-baf9-11ce-8c82-00aa004ba90b}': no component
> exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
> CLSID
> '{79eac9e2-baf9-11ce-8c82-00aa004ba90b}' will remain in the Registry table
> because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
> list. This may result in ICE33 warnings.
> Undefined CLSID '{79eac9e3-baf9-11ce-8c82-00aa004ba90b}': no component
> exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
> CLSID
> '{79eac9e3-baf9-11ce-8c82-00aa004ba90b}' will remain in the Registry table
> because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
> list. This may result in ICE33 warnings.
> Undefined CLSID '{79eac9e4-baf9-11ce-8c82-00aa004ba90b}': no component
> exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
> CLSID
> '{79eac9e4-baf9-11ce-8c82-00aa004ba90b}' will remain in the Registry table
> because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
> list. This may result in ICE33 warnings.
> Undefined CLSID '{79eac9e5-baf9-11ce-8c82-00aa004ba90b}': no component
> exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
> CLSID
> '{79eac9e5-baf9-11ce-8c82-00aa004ba90b}' will remain in the Registry table
> because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
> list. This may result in ICE33 warnings.
> Undefined CLSID '{79eac9e6-baf9-11ce-8c82-00aa004ba90b}': no component
> exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
> CLSID
> '{79eac9e6-baf9-11ce-8c82-00aa004ba90b}' will remain in the Registry table
> because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
> list. This may result in ICE33 warnings.
> Undefined CLSID '{79eac9e7-baf9-11ce-8c82-00aa004ba90b}': no component
> exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
> CLSID
> '{79eac9e7-baf9-11ce-8c82-00aa004ba90b}' will remain in the Registry table
> because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
> list. This may result in ICE33 warnings.
> Undefined CLSID '{79EAC9F1-BAF9-11CE-8C82-00AA004BA90B}': no component
> exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
> CLSID
> '{79EAC9F1-BAF9-11CE-8C82-00AA004BA90B}' will remain in the Registry table
> because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
> list. This may result in ICE33 warnings.
> Undefined CLSID '{79eac9f2-baf9-11ce-8c82-00aa004ba90b}': no component
> exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
> CLSID
> '{79eac9f2-baf9-11ce-8c82-00aa004ba90b}' will remain in the Registry table
> because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
> list. This may result in ICE33 warnings.
> Undefined CLSID '{7b8a2d94-0ac9-11d1-896c-00c04Fb6bfc4}': no component
> exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
> CLSID
> '{7b8a2d94-0ac9-11d1-896c-00c04Fb6bfc4}' will remain in the Registry table
> because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
> list. This may result in ICE33 warnings.
> Undefined CLSID '{7b8a2d95-0ac9-11d1-896c-00c04Fb6bfc4}': no component
> exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
> CLSID
> '{7b8a2d95-0ac9-11d1-896c-00c04Fb6bfc4}' will remain in the Registry table
> because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
> list. This may result in ICE33 warnings.
> Undefined CLSID '{8f6b0360-b80d-11d0-a9b3-006097942311}': no component
> exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
> CLSID
> '{8f6b0360-b80d-11d0-a9b3-006097942311}' will remain in the Registry table
> because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
> list. This may result in ICE33 warnings.
> Undefined CLSID '{B15B8DC0-C7E1-11d0-8680-00AA00BDCB71}': no component
> exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
> CLSID
> '{B15B8DC0-C7E1-11d0-8680-00AA00BDCB71}' will remain in the Registry table
> because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
> list. This may result in ICE33 warnings.
> Undefined CLSID '{c733e4af-576e-11d0-b28c-00c04fd7cd22}': no component
> exists for file '%SystemFolder%\urlmon.dll'. COM registry entries for
> CLSID
> '{c733e4af-576e-11d0-b28c-00c04fd7cd22}' will remain in the Registry table
> because file '%SystemFolder%\urlmon.dll' was not listed in the .inc file
> list. This may result in ICE33 warnings.
> Mapping Application IDs from registry information and writing to
> the AppId table
> Mapping ProgIDs from registry information
> Writing to the Class table
> Mapping file extensions and MIME types from registry information
> to the Extension and Mime tables
> Mapping shell extension verbs from registry information to the
> Verb table
> Writing to the ProgId table
> Mapping application paths from registry information
> Mapping environment variables from registry information to the Environment
> table
> Processing .INI file changes and writing to the IniFile table
> Scanning for ODBC drivers and writing to the ODBCSource and ODBCDriver
> tables
> Applying merge modules
> Including merge module 'Microsoft (R) C Runtime Library'
> Including merge module 'Microsoft OLE 2.40 for Windows NT(TM)
> and
> Windows 95(TM) Operating Systems'
> Including merge module 'Windows Common Controls ActiveX Control
> DLL'
> Including merge module 'CMDialog ActiveX Control DLL'
> Including merge module 'Visual Basic Virtual Machine'
> Including merge module 'Microsoft Component Category Manager
> Library'
> Including merge module 'MCI OLE Control DLL'
> Creating directory folders and writing to the CreateFolders table
> Writing unmapped registry information to the Registry table
> Writing information to the RemoveRegistry table
> Creating shortcuts and writing to the Shortcut table
> A non-advertised shortcut must be created for Embedding In A Web
> Page.pdf in
> folder [ProgramMenuFolder]i2\Chart Reader 6\Documentation. Autorepair
> cannot be enabled for this shortcut.
> A non-advertised shortcut must be created for User Guide.pdf in folder
> [ProgramMenuFolder]i2\Chart Reader 6\Documentation. Autorepair cannot be
> enabled for this shortcut.
> --------------------------
> Building .msi package
> Created release folders
> AdminExecuteSequence table successfully built
> AdminUISequence table successfully built
> AdvtExecuteSequence table successfully built
> AdvtUISequence table successfully built
> InstallExecuteSequence table successfully built
> InstallUISequence table successfully built
> Directory table successfully built
> Feature table successfully built
> FeatureComponents table successfully built
> Component table successfully built
> Loading File table
> Building File table
> Merging modules...
> Merging Microsoft Component Category Manager Library: C:\Program
> Files\InstallShield\AdminStudio\6.0\Repackager\COM CAT.MSM
> Merging Windows Common Controls ActiveX Control DLL: C:\Program
> Files\InstallShield\AdminStudio\6.0\Repackager\COM CTL32.MSM
> Merging CMDialog ActiveX Control DLL: C:\Program
> Files\InstallShield\AdminStudio\6.0\Repackager\COM DLG32.MSM
> Merging MCI OLE Control DLL: C:\Program
> Files\InstallShield\AdminStudio\6.0\Repackager\MCI 32.MSM
> Merging Visual Basic Virtual Machine: C:\Program
> Files\InstallShield\AdminStudio\6.0\Repackager\MSV BVM60.MSM
> Merging Microsoft (R) C Runtime Library: C:\Program
> Files\InstallShield\AdminStudio\6.0\Repackager\MSV CRT.MSM
> Merging Microsoft OLE 2.40 for Windows NT(TM) and Windows 95(TM) Operating
> Systems: C:\Program
> Files\InstallShield\AdminStudio\6.0\Repackager\OLE AUT32.MSM
> File table successfully built
> Building MsiFileHash table
> MsiFileHash table successfully built
> Class table successfully built
> Extension table successfully built
> ODBCDataSource table successfully built
> ODBCDriver table successfully built
> ActionText table successfully built
> AppSearch table successfully built
> BindImage table successfully built
> CCPSearch table successfully built
> Condition table successfully built
> AppId table successfully built
> ISDEV : warning -6261: The property ALLUSERS is defined in the property
> table. This may result in a setup that is always installed per-machine
> when
> it has been advertised as a per-user install. It is recommended that the
> ALLUSERS property not be defined in the Property table.
> Property table successfully built
> BBControl table successfully built
> Billboard table successfully built
> Binary table successfully built
> CompLocator table successfully built
> Complus table successfully built
> ControlCondition table successfully built
> ControlEvent table successfully built
> CreateFolder table successfully built
> CustomAction table successfully built
> Error table successfully built
> DrLocator table successfully built
> DuplicateFile table successfully built
> Environment table successfully built
> EventMapping table successfully built
> FileSFPCatalog table successfully built
> Font table successfully built
> IniFile table successfully built
> IniLocator table successfully built
> IsolatedComponent table successfully built
> Verb table successfully built
> LaunchCondition table successfully built
> LockPermissions table successfully built
> MIME table successfully built
> MoveFile table successfully built
> MsiAssembly table successfully built
> MsiAssemblyName table successfully built
> MsiDigitalCertificate table successfully built
> MsiDigitalSignature table successfully built
> ODBCAttribute table successfully built
> ODBCSourceAttribute table successfully built
> ODBCTranslator table successfully built
> PatchPackage table successfully built
> ProgId table successfully built
> PublishComponent table successfully built
> Registry table successfully built
> RegLocator table successfully built
> RemoveFile table successfully built
> RemoveIniFile table successfully built
> RemoveRegistry table successfully built
> ReserveCost table successfully built
> SelfReg table successfully built
> ServiceControl table successfully built
> ServiceInstall table successfully built
> SFPCatalog table successfully built
> Shortcut table successfully built
> Signature table successfully built
> TextStyle table successfully built
> TypeLib table successfully built
> UIText table successfully built
> Upgrade table successfully built
> _Validation table successfully built
> Searching project for extract-at-build components...
> Validating Custom Action sequencing
> Dialog AdminChangeFolder for language English (United States) built
> Dialog AdminNetworkLocation for language English (United States) built
> Dialog AdminWelcome for language English (United States) built
> Dialog CancelSetup for language English (United States) built
> Dialog CustomSetup for language English (United States) built
> Dialog CustomSetupTips for language English (United States) built
> Dialog CustomerInformation for language English (United States) built
> Dialog DatabaseFolder for language English (United States) built
> Dialog DestinationFolder for language English (United States) built
> Dialog DiskSpaceRequirements for language English (United States) built
> Dialog FilesInUse for language English (United States) built
> Dialog InstallChangeFolder for language English (United States) built
> Dialog InstallWelcome for language English (United States) built
> Dialog LicenseAgreement for language English (United States) built
> Dialog MaintenanceType for language English (United States) built
> Dialog MaintenanceWelcome for language English (United States) built
> Dialog OutOfSpace for language English (United States) built
> Dialog PatchWelcome for language English (United States) built
> Dialog ReadyToInstall for language English (United States) built
> Dialog ReadyToRemove for language English (United States) built
> Dialog SQLBrowse for language English (United States) built
> Dialog SQLLogin for language English (United States) built
> Dialog SetupCompleteError for language English (United States) built
> Dialog SetupCompleteSuccess for language English (United States) built
> Dialog SetupError for language English (United States) built
> Dialog SetupInitialization for language English (United States) built
> Dialog SetupInterrupted for language English (United States) built
> Dialog SetupProgress for language English (United States) built
> Dialog SetupResume for language English (United States) built
> Dialog SetupType for language English (United States) built
> Dialog SplashBitmap for language English (United States) built
> Resolving strings...
> Language English (United States) built
> Building CAB files...
> Data1.cab built
> Files built
> Media table successfully built
> Performing Upgrading and Patching Validation
> Automatic update notification disabled
> Product1\Release1 - 0 error(s), 1 warning(s)
> Finished successfully.
> Conversion completed with 20 warning(s).
> Output file: C:\Packages\ChartR2\Chart Reader.msi
Forgot to say that I am using Admin Studio 5 (Zen) and now 6 Demo...
Thanks

MSI-Packages to deploy SDK via LAN with Windows Server

On the net you can find decriptions how to make and alter MSI-Packages for JRE.
But no reliable ones for the JSDK.
Does the SUN-Webpage contain information or descriptions how to make a MSI-Package for JSDK?
Thanks a lot.
Volkhard

Welcome to the forums !
Do you need the full client ? Or will the Instant Client suffice ? See these related threads -
multiple client installs
Install Oracle with a .msi package
HTH
Srini

Clean Install - use MSI System Drivers?

I have a question regarding a clean install.
Install operating system -> MSI Chipset Drivers then update on top using ATI Catalyst 8.4?, Realtek Audio Drivers and finally Realtek PCI-E Lan Drivers.
What is difference between the MSI Drivers and the Catalyst suite? They same to be the same:
Catalyst Control Centre
ATI Install Manager
North Bridge Filter Driver
ATI Display Manager
IDE Driver
Microsoft Visual C++
ATI Unified Stream Driver
except the MSI Drivers adds Avivo64 Driver
Also, I thought it was always best to unistall all ATI drivers before upgrading? - at least that is the concensus on the AMD forum.
Any advice is appreciated.
Vista x64 Premium
Antec P182B Case
MSI K9A2CF BIOS ver 1.5B1
AMD Phenom 9500
Thermaltake ToughPower 750w
ATI Radeon 2900XT
OCZ PC2-6400 800Mhz 2 x 1024
Seagate 500GB 16MB cache SATA-2 HD
Mitsumi 1.44 internal 3.5 floppy / 6 in 1 card reader
Samsung 206BW

I guess that's where I'm confused.
It dosen't appear that the MSI system drivers are any different than the ATI catalyst drivers. The only difference is that the MSI drivers wanted to install Avivo64 on my system. Going to the ATI Catalyst site, it offers Avivo64 as a seperate download, but "Avivo Video Converter will only work with X1000 series products." http://game.amd.com/us-en/drivers_catalyst.aspx?p=vista64/common-vista64 I have a 2900XT.
The Realtek audio and PCIe Ethernet drivers to install from the MSI site are in this case up to date and make sense.
So to ask in a different way, is there a problem with: OS first -> then the ATI Catalyst Suite (system drivers and display driver) - NOT install the MSI system drivers which appear to be outdated and the same as the ATI Catalyst Suite- then the Realtek Audio Driver, and finally the Realtek PCIe Ethernet driver.
Thanks
Vista x64 Premium
Antec P182B Case
MSI K9A2CF BIOS ver 1.5B1
AMD Phenom 9500
Thermaltake ToughPower 750w
ATI Radeon 2900XT
OCZ PC2-6400 800Mhz 2 x 1024
Seagate 500GB 16MB cache SATA-2 HD
Mitsumi 1.44 internal 3.5 floppy / 6 in 1 card reader
Samsung 206BW

Installing converted MSI packages

Similar Messages

Maybe you are looking for