This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Flexera Community
- :
- AdminStudio
- :
- AdminStudio Forum
- :
- I know how to do this
Subscribe
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
Macromedia Studio MX
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When trying to build an MSI from the ISM file for studio MX I get the following unspecified error...
Tuesday, July 29, 2003 10:14:01AM
Starting conversion
Creating Developer project: C:\Packages\macromedia\Shockwave Flash.ism
Reading repackager output file
Loading registry entries
An unknown error occurred
Conversion completed with 0 warning(s).
Output file:
Log file created: C:\Packages\macromedia\Build Log.txt
Any ideas :confused: :rolleyes:
Tuesday, July 29, 2003 10:14:01AM
Starting conversion
Creating Developer project: C:\Packages\macromedia\Shockwave Flash.ism
Reading repackager output file
Loading registry entries
An unknown error occurred
Conversion completed with 0 warning(s).
Output file:
Log file created: C:\Packages\macromedia\Build Log.txt
Any ideas :confused: :rolleyes:
‎Jul 29, 2003 04:27 AM
(4) Replies
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
To get more debug level log do the following:
Create a registry key as follows:
[HKEY_LOCAL_MACHINE\SOFTWARE\InstallShield]
"DebugFile"="C:\\Inc2msi.log"
"DebugRepackager"="5"
[HKEY_LOCAL_MACHINE\SOFTWARE\InstallShield\AdminStudio]
"DebugLogLevel"="3"
The Inc2msi.log will tell you the where it failed.
Create a registry key as follows:
[HKEY_LOCAL_MACHINE\SOFTWARE\InstallShield]
"DebugFile"="C:\\Inc2msi.log"
"DebugRepackager"="5"
[HKEY_LOCAL_MACHINE\SOFTWARE\InstallShield\AdminStudio]
"DebugLogLevel"="3"
The Inc2msi.log will tell you the where it failed.
‎Jul 29, 2003 09:59 AM
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Aug 02, 2003 03:14 PM
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Since the conversion from INC to ISM/MSI failed the ism will be not have the information as to why it failed. You can send me the log file at praveenl@installshield.com
‎Aug 04, 2003 09:56 AM
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Subscribe
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
MX studio is already in a MSI format from Macromedia
this is what i did to make it work. Using Repackager will not work
1- I first ran a standard setup from the cd-rom so that the source files would be extracted to a sub-directory in my %Temp% directory. While running this install, I also used RegMon from SysInternals to get where the Dreamweaver registration information was being written in the registry. I exported this registry info for later reference
2- Prior to canceling the setup, I copied the source files from the %Temp% directory to my server share
3- I canceled setup.
4- I created a setup.iss file by running setup -r at the server share location where the extracted install source files were copied in step 2
5- I copied the setup.iss file from the %Winnt% directory to where my source files are located.
6- I created a vbs script to use for the deployment so that I can kill my anti virus software or whatever else needs to be done prior to iniating the software install.
7- I added code in the script to create the HKLM\Macromedia\Dreamweaver\6\Registration structure. I created and populated the following string items with the info I exported during step 1:
First Name, Last Name, Organization, Register, Serial Number, Validation
8-After creating the registration information in the registry setup -s runs totally silent.
this is what i did to make it work. Using Repackager will not work
1- I first ran a standard setup from the cd-rom so that the source files would be extracted to a sub-directory in my %Temp% directory. While running this install, I also used RegMon from SysInternals to get where the Dreamweaver registration information was being written in the registry. I exported this registry info for later reference
2- Prior to canceling the setup, I copied the source files from the %Temp% directory to my server share
3- I canceled setup.
4- I created a setup.iss file by running setup -r at the server share location where the extracted install source files were copied in step 2
5- I copied the setup.iss file from the %Winnt% directory to where my source files are located.
6- I created a vbs script to use for the deployment so that I can kill my anti virus software or whatever else needs to be done prior to iniating the software install.
7- I added code in the script to create the HKLM\Macromedia\Dreamweaver\6\Registration structure. I created and populated the following string items with the info I exported during step 1:
First Name, Last Name, Organization, Register, Serial Number, Validation
8-After creating the registration information in the registry setup -s runs totally silent.
‎Aug 04, 2003 10:08 AM
Related Content
