MSI package question

Hello,
This is not really a SCCM question, but I don't really know where to post this question and I thought a lot of MSI geeks are in this forum too.
In my company an in-house tool was developed and is available as a MSI package. The package requires .NET 4.5.
When I deploy this MSI in my environment without any switch I'm receiving this error message.
"This advertised application will not be installed, because it might be unsafe. Contact your administrator to change the installation user interface option of the package to basic"
If I run the MSI with the switch msiexec  /I product.msi /qb /norestart, the installation will start but gives back an error during the installation. Error 1001: Some or all identity reference could not be translated".
I'm clueless what is going on. I have seen the installation went fine with computers which are in production for a longer time. I perform the tests mainly on computers which were freshly imaged. Even I cannot install the tool with a fresh image computer
which have only the OS and .NET 4.5 installed.
Our OS is Windows 7 SP1 64bit ENG with the DE MUI installed.
Do you have an idea what the problem could be? I googled a bit for the error messages but I have not found real help for my issue.
Thanks,
Edy from Switzerland

this is not the exact error but check this out
https://support.microsoft.com/kb/941209?wa=wsignin1.0
1. Create a new local user group with name "Network Service"
2. Add the localized network service account to the recently created "Network Service" group. Here's a mapping:
German - NT-AUTORITÄT\NETZWERKDIENST
French - AUTORITE NT\SERVICE RÉSEAU
Italian - NT AUTHORITY\SERVIZIO DI RETE
Spanish - NT AUTHORITY\SERVICIO DE RED
maybe this might fix it?

Similar Messages

  • Error while deploying MSI package -- Insufficient memory

    Hi,
    While importing the MSI package I am getting below error:
    What is the reason for this error?
    Thanks, Girish R. Patil.

    Check the disk space on C: drive. Sometime ago I had this issue, I just restarted the server and resumed the installation. So do the following:
    Check the disk space; ensure you have enough free space.
    If you have enough space, then close this installation and restart it again, as worked in my case try restarting the server and resume the installation.
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

  • Adobe Reader 9.3.2 silent install package questions, please ...

    Hello:
      I am a network and Desktop Support person for a higher education facility.  I was asked to take over automating software application
    installs.
      I have a script process, created by Auto-It (Scite script editor), that has been working well for Adobe Reader 9.1 with updates to 9.1.1, 9.1.2 and 9.1.3 (found on the Internet) -
    msiexec /i \\<server>\<path>\AcroRead.msi TRANSFORMS=\\<server>\<path>\AcroRead_10132009.mst /passive /norestart /update \\<server>\<path>\AdbeRdrUpd911_all_incr.msp;\\<server>\<path>\AdbeRdrUpd912_all_incr.msp; \\<server>\<path>\AdbeRdrUpd913_all_incr.msp
      My questions:
    Is there a similar process for installing Adobe Reader 9.3 silently and then updating to 9.3.2?
    If so, what are the steps, ex. expand/extract the initial 9.3 .EXE, then create a transform using Orca/<transform making of choice>, etc.?
    With having read of some issues in this forum regarding Adobe Reader 9.3.2, should I continue using 9.1.3 and wait?
      Thank you for your time.

    Well we have a wiki where I work, and here is then entry I have created on how to deploy Adobe Reader. See if any of this helps, if not, we'll take it from there.
    Deployment
    It is HIGHLY recommended that you read and follow the directions of the deployment guide provided by Adobe located at http://www.adobe.com/devnet/acrobat/pdfs/deploying_reader9.pdf. The documentation located here is simply for a quick reference for those who have already read the guide.
    The rights to distribute Adobe Reader must be obtained by filling out the form found at http://www.adobe.com/products/reader/rdr_distribution1.html. After filling out the form and being accepted to distribute Adobe Reader, you will receive an email with a link to download the redistributable version of Adobe Reader. You will be prompted to download a .exe package containing the Reader MSI file. The general form of the command to convert a Nosso-compressed file to an MSI package is:
    <path to>\AdbeRdr90_en_US.exe [<switches>...]
    Switch
    Description
    -nos_ne
    Do not execute any file after installation (overrides the -e switch) This switch should be used if user only wants to extract the installer contents and not run the installer.
    -nos_o
    Specifies the name of folder where the contents of the expanded package are to be placed. The folder name should be enclosed in quotation marks. It is best if you do not use an existing folder, and there should be no space following the “-nos_o”.
    For example:<path to>\AdbeRdr90_en_US.exe -nos_o”TestFolder” -nos_ne
    Using the extracted MSI, create an Administrative Installation Point (AIP) using the command-line:
    msiexec /a <path to>\AcroPro.msi transforms=<path to>\AcroPro.mst
    The AcroPro.mst transform file is created by the Adobe Customization Wizard 9
    You can apply any patches that may have been released since the major version release. Use the command-line:
    msiexec /a <path to>\AcroPro.msi /p <path to>\AdbeRdrUpd931.msp;<path to>\AdbeRdrUpd932.msp
    Once all this is complete, you can fully deploy the software by running the command-line:
    <path to>\AcroRead.msi transforms=<path to>\AcroRead.mst /qb
    More information can also be found in the Enterprise Administration Guide

  • 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:  

  • MOVED: MSI-6378 Question please....

    This topic has been moved to AMD SocketA based board.
    MSI-6378 Question please....

    I am sorry I am being so slow to respond to these questions: I'm at work and will look at the post properly when at home.
    However, I have seen this Crucial RAM being advertised. Is it compatible with this Motherboard can anyone tell me??
    Begins:
    Virtually BRAND NEW opened and tested Crucial 512MB ECC Registered SD-RAM!!!
    Module Details:
    * Module Size: 512MB
    * Package: 168-pin DIMM
    * Feature: SDRAM, PC133
    * Configuration: 64Meg x 72
    * DIMM Type: Registered
    * Error Checking: ECC
    * Speed: 133MHz
    * Voltage: 3.3V
    * Memory Timings: CL=3
    Selling on Cricial.com/uk for over £90!!!!! LOW starting bid! Cricial part no. CT64M72S4R75
    PLEASE ONLY BID if you KNOW and UNDERSTAND that this is ECC REGISTERED RAM and does NOT work in most standard Motherboards, as this RAM is designed for servers.
    ECC stands for Error Correction - this ram can correct certain memory paging faults itself, which is why servers normally run ECC to keep them stable. Ends:
    I'd appreciate all and any help with this as I have some irons in the fire which will be helped immensly by increasing the RAM.
    God Bless & Thank you for looking ( even if you are unable to help )
    Hackbridge

  • 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

  • The "Adobe Reader 11.0.08 security update - All languages" is not working with "Adobe Reader 11.0 - Multilingual (MUI) installer" using msiexec when creating an msi package. is there going to be a release of Adobe Reader 11.0.08 update - Multilingual (MUI

    Is it possible to create an msi package if the product you are upgrading is Multilingual (MUI) and the update(msp) you are applying is not Multilingual (MUI) but "All languages"?

    Please download the latest Adobe Reader patch from the below mentioned location, it will work with MUI installer.
    ftp://ftp.adobe.com/pub/adobe/reader/
    ~Deepak

  • Error 1603 in deploying Office 2003 by creating an application object using its MSI package!

    Hello,
    I got the error of 1603 when I ran Office 2003 MSI package through NAL. I
    have no idea how to resolve this problem. Even though I enabled logging in
    Office 2003 installation, I still could not figure out what went wrong and
    what caused the error.
    I have used Snapshot to create an application object for a long time with
    little problem. However, I could not successfully deploy any MSI package
    created by an application object. I knew ZenWork Managing Application has
    the feature, but I don't know how to make it work in our environment.
    Do I have to know more about Microsoft Window Installer ?
    Appreciate your comments and experience in advance
    Thanks
    Joe Liu
    email: [email protected]

    [email protected],
    > I got the error of 1603 when I ran Office 2003 MSI package through NAL
    >
    Start here:
    http://support.novell.com/techcenter...tation&x=0&y=0
    Yes, understanding MSI helps. FWIW I have deployed 2003 this way.
    - Anders Gustafsson, Engineer, CNE6, ASE
    NSC Volunteer Sysop
    Pedago, The Aaland Islands (N60 E20)
    Novell does not monitor these forums officially.
    Enhancement requests for all Novell products may be made at
    http://support.novell.com/enhancement
    Using VA 5.51 build 315 on Windows 2000 build 2195

  • 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

  • .air to exe or an MSI package?

    Is it possible to convet an .air file into an MSI package? or even an .exe? My developers have created this app with Air and would like to roll it out companywide. We have about 300 users and don't want to install one by one manualy. Can some one help with a solution?

    We have been successful in deploying our AIR app via an MSI in our corporate environment.  The users can launch the app via a desktop shortcut or from Program Files.  However, we can't launch the AIR application from a browser (badge) if we've deployed via the MSI.
    The badge thinks that the application hasn't been installed and therefore displays 'Install' as button label.  If we do install the application by clicking 'Install' we can then launch via the badge....but we need to install via the MSI.
    e.g.
    And the HTML ....
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
         <head>
              <title>eRevenue</title>
              <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
              <script type="text/javascript" src="swfobject.js"></script>
              <script type="text/javascript">
                   var flashvars = new Object();
                   flashvars.airVersion = "1.5";
                   flashvars.applicationID = "eRevenue94.0.2.3";
                   flashvars.applicationURL = "file:///Z:/IT&T/FLEX/AIR Installer Files/eRevenue94.0.2.3-dev.air";
                   flashvars.publisherID = "00B5DD753DA2312E245FAD63894B9C283A29B6E9.1";
                   swfobject.embedSWF("Badge.swf", "divBadge", "100", "50", "9.0.0", null, flashvars);
              </script>
         </head>
         <body>
              <div id="divBadge">
                   <p>Alternative Content</p>
              </div>
         </body>
    </html>
    To generate the MSI we install the AIR app normally on a PC, then we package up the MSI from the installed files the AIR app deploys.
    The AIR installer must do something else with the Publisher ID that the MSI doesn't know about - which is why the badge doesn't seem to recognise the application is installed.
    Any ideas?
    Thanks,
    Dave

  • 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.

  • Distributable MSI package issue

    Platform: Windows XP SP3 Finnish
    Flash version: 10.1.53.64
    Format: MSI package
    The latest distributable Flash plugin (for other browsers than IE) MSI installation fails with an error message:
    Error 2753. The file 'FP_PL_MSI_INSTALLER.exe' is not marked for installation.
    Anyone else having this problem and has a solution?

    The problem seems to relate to a failure to remove the previous version leading
    to a stuck MSI install. It can be cleared using the Microsoft MSI cleanup utility.
    BUT!!
    Microsoft have removed the MSI cleanup tool from their download site as they seem to say it can cause damage to other parts of the system. The tool is still available from various download sites but useing it has to be at your own risk.

  • 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

Maybe you are looking for