Jun 04, 2010
12:09 PM
I would suggest using [PersonalFolder]word1.doc to set the element content. PersonalFolder is a Windows Installer system folder property that will resolve to the My Documents folder of the current user. System Folder Properties http://msdn.microsoft.com/en-us/library/aa370905(v=VS.85).aspx#system_folder_properties You can take a look at LogonUser and USERNAME properties if you are just interested in the user name: User Information Properties http://msdn.microsoft.com/en-us/library/aa370905(v=VS.85).aspx#user_information_properties Please check the XML File Changes help to see how to set up this view to update the xml file and element that you are looking to do. -Ajay
... View more
Jun 03, 2010
11:39 AM
Hi Bruno, App-V packages are not truly OS independent. This is because the App-V client does not simulate an entire OS - App-V can't be used for OS application compatibility. The client sometimes gives a virtual application a virtual resource, and sometimes gives it the actual physical OS resource. If an application installed physically on a Win 7 machine will not work, then most likely, an App-V package for this app will also not work on Win 7. To debug the issue you are seeing, I suggest trying a couple different approaches: 1. Try copying the DLLs that can't be located in your 32-bit system folder in the physical machine to see if this resolves the problem (just to get a feel for the scope of the problem). 2. Try including the File system diagnostic tool and rebuilding the App-V package. Then you can use the AppVLauncher to launch the Virtual File System tool and get a feel for the file structure seen by the virtual package. You could go to the 32-bit system folder and verify that the MFC DLL is present (if it is supposed to be there). 3. You can try running a recent copy of Process Monitor tool available from Microsoft. Run this tool on the physical machine with the command line switch /externalcapture. Then it will also report registry accesses within the virtual bubble. Look for mfc42.dll in the report and check to see where it was searched for and determine why it was not there. -Ajay
... View more
Jun 01, 2010
06:21 PM
In general I would recommend against using the professional logging option because our setup technology agnostic Installation Monitoring and Snapshot technologies should be perfectly capable of capturing the system changes made by the setup. I believe we are considering either deprecating this option or else at least not selecting it by default in the Repackaging wizard. Regards, Ajay
... View more
May 27, 2010
04:10 PM
Hi DBrewer, Although the Repackaging Wizard suggests to use the Professional Logging method, I recommend that you do not use this method during the repackaging. Our standard Snapshot mode or Install Monitoring mode should be fully capable of capturing the system changes made by the InstallScript setup that you are Repackaging. Please try not using the Professional logging option and let me know how it goes. Regards, -Ajay
... View more
May 26, 2010
03:24 PM
Hi Tim, #1 - Instead of a traditional install package, you would need the virtual package itself (basically a binary proprietary file that contains the application payload and settings). #2 - Since application virtualization technologies do a good job of fooling applications into thinking that they are actually running in the physical environment, normally not much tweaking is needed to the application itself to get it to work virtually. #3 - Most application virtualization technologies (such as App-V and ThinApp) have built-in support for interaction between virtual packages. App-V has a feature called dynamic suite composition (DSC) that supports specifying dependencies between virtual packages. #4 - The system changes made by the package installation need to be captured with a capture tool such as Repackager and then converted into the binary format of the virtualization technology that you are interested in. With InstallShield, you can directly convert from ISM and MSI formats to an App-V package - in some cases it would be necessary to repackage a MSI package before conversion to an App-V package. I hope that helps to clarify some things for you.
... View more
May 25, 2010
11:23 AM
Any custom action that makes a system change should be of type "Deferred execution in system context." Only these types of custom actions are run with elevated privileges. I am not sure whether elevated privileges are required for starting and stopping services, but I suspect that they may be. Also, if you are planning on making the registry change in your custom action as well, then this definitely would be considered a system change. Hope this helps, Ajay
... View more
May 19, 2010
01:29 PM
Hi Jakob, Unfortunately, in recent releases of AdminStudio, running Repackager remotely with an evaluation version is not supported. So you will not be able to evaluate the remote Repackager functionality. Instead please consider installing the full AS eval on the machine where you want to repackage to evaluate the Repackager. I know that this approach is against best practices because installing AS dirties the machine, but you should be able to evaluate the Repackager functionality this way. You can deselect most of the other features besides Repackager to install a smaller footprint (I think you can deselect all but Distribution Wizard and Repackager). Hope this helps! -Ajay
... View more
May 19, 2010
01:23 PM
I agree with Robert that your approach to addressing the ICE03 validation error is valid. Leaving this issue in the MSI package shouldn't cause any issues on systems supporting long file names - which is just about every system out there these days. We have an issue reported for this with issue number 1-AWE2X. Regards, Ajay
... View more
May 19, 2010
12:07 PM
The best single reference for Windows Installer conditional statements can be found in the following link: Conditional Statement Syntax http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx
... View more
May 19, 2010
12:05 PM
Hi, I see that you are not able to use the workaround I presented because you have the LANDesk limited edition which does not come with InstallShield Editor. I think you may be able to workaround this issue by directly editing the INC file. This is a text file that you can open with Notepad. At the bottom of the file you will find the Links (shortcuts) section that lists all of the shortcuts along with their icon information. Here is an example line: CreateLink('BusinessObjects','%ProgramFilesFolder%\Business Objects\BusinessObjects 5.0\BUSOBJ.EXE','','%WindowsFolder%\Installer\{2B989026-FE29-4EE6-AC98-46816D43A32F}\IconFF937CC6.exe,2','%WindowsVolume%Documents and Settings\All Users\Start Menu\Programs\BusinessObjects 5.1.6','BusinessObjects','') You can see that IconFF937CC6.exe is the icon file with an index of 2. So this could be altered here before building the Repackager project. I would verify whether the icon EXE (Icon_CoWriter.exe) that is presenting the error for you is really an EXE file. If it is really an ICO file, then you may want to make a copy of the EXE file with the extension ICO in the same folder as the EXE. Then modify the CreateLink command to use the ICO file instead and rebuild. You can also just pick one of the actual executables in your project as the source of the icon. Hopefully, you will be able to workaround this problem. -Ajay
... View more
May 19, 2010
11:50 AM
You are correct that it is possible to have 10 versioned files in one component and create a patch that only updates one of these files and only contains the binary delta for this one file. However, including multiple versioned files in one component is against best practices. It may make it difficult for you to update some of the versioned keyfiles without also updating the keyfile. Basically putting the versioned files in separate components will help you avoid headaches in the future. Also, you can't take full advantage of the Windows Installer resiliency or Auto-Repair functionality which can trigger a repair if the keyfile has been deleted. -Ajay
... View more
May 18, 2010
11:30 AM
Hi, Windows Installer makes a determination on whether to install a component or not based on its keyfile. Then if it decided that the component will be installed, then it individually checks each file in the component to see if it will be installed or not. If a component has a versioned keyfile, then MSI will mark the component to be installed if the version of the file is equal or greater than an existing file version. If a component has no keyfile or an unversioned keyfile, then the component will always be flagged to be installed. Later on in the InstallFiles action, MSI will follow its normal file versioning rules to decide whether to install each file in components marked to be installed. File Versioning Rules http://msdn.microsoft.com/en-us/library/aa368599(VS.85).aspx -Ajay
... View more
May 18, 2010
11:18 AM
I suspect that you are running into expected Windows Installer major upgrade behavior when the RemoveExistingProducts action is sequenced after InstallFinalize. In this situation, the updated key file is installed during the InstallFiles action (as it would have been if you were using a minor upgrade), and then at the end of the install MSI is determining that this component does not need to be removed because it is still present in the new version of the product. Your possible work-around options include the following: 1. Sequence RemoveExistingProducts action in the InstallShield default location of after InstallValidate action (You can also change this same setting in Upgrades View - Upgrade Windows Installer Setup - Major Upgrade Settings. OR 2. Use the RemoveFile table to remove the files no longer in the component (this approach works in a minor upgrade, so I suspect that it will also work in this case). OR 3. Use a custom action to delete the files no longer included in the component. Hope this helps, Ajay
... View more
May 10, 2010
11:21 AM
The 1920 error unfortunately does not narrow down the cause of the failure with starting the service. Here are some things you can look into to try to get to the bottom of this: 1. Check the ServiceInstall and ServiceControl tables in the built MSI. Compare with the documentation for these tables and also check to see if these tables were being used in the original install (before repackaging) to see how they were populated before. 2. Verify that all dependencies for the service EXE (CentralDICOMServer.exe) are present. 3. Verify that the correct internal name of the service (not necessarily the display name) is being used as the key of the Service* tables above. 4. Try to remove the ServiceControl table entries, then install the MSI, and then manually try to get the service to start-up successfully. Once you determine what the problem was, then you can correct it in the MSI (you could use ProcessMonitor, do a file diff with the original install, etc). Hope this helps! -Ajay
... View more
May 05, 2010
05:49 PM
Glad to hear that reconversion worked with the hotfix! It is technically possible to manually edit the captured INC and ISR or NIR files to ensure that backslashes and double quotes appearing within registry value names or Ini key names are escaped with a backslash. But it could be time consuming for large packages that may have multiple entries with this problem. The registry data can be found in any ISR or NIR files, and the Ini data can be found in the INC file. You may find that it is easiest do the reconversion. Or else, you may be able to figure out some way to quickly identify unescaped backslashes or double quotes in the Repackager project files. -Ajay
... View more
Latest posts by Ajay_Ladsaria
Subject | Views | Posted |
---|---|---|
1474 | May 24, 2017 05:26 PM | |
633 | May 08, 2017 05:53 PM | |
826 | May 08, 2017 05:51 PM | |
1474 | May 08, 2017 05:42 PM | |
1716 | Jul 22, 2015 10:49 AM | |
1716 | Jul 17, 2015 07:46 PM | |
907 | Feb 27, 2012 03:50 PM | |
690 | Dec 16, 2011 04:19 PM | |
676 | Dec 01, 2010 07:57 PM | |
1100 | Oct 06, 2010 07:26 PM |
Activity Feed
- Posted Re: Start Menu Icons Missing After Converting to .MSI on AdminStudio Forum. May 24, 2017 05:26 PM
- Posted Re: Automated Application Converter Icon problem on AdminStudio Forum. May 08, 2017 05:53 PM
- Posted Re: AdminStudio 2016 - Shortcuts blank after application has been repackaged on AdminStudio Forum. May 08, 2017 05:51 PM
- Posted Re: Start Menu Icons Missing After Converting to .MSI on AdminStudio Forum. May 08, 2017 05:42 PM
- Posted Re: "C:\Program Files (x86)" captures incorrectly as "C:\Program Files" with App-V on InstallShield Forum. Jul 22, 2015 10:49 AM
- Posted Re: "C:\Program Files (x86)" captures incorrectly as "C:\Program Files" with App-V on InstallShield Forum. Jul 17, 2015 07:46 PM
- Posted Re: Installshield App-V Build Server on InstallShield Forum. Feb 27, 2012 03:50 PM
- Posted Re: App-V Sequencing to another drive than Q on AdminStudio Forum. Dec 16, 2011 04:19 PM
- Posted Re: Repackager does not transfer registry settings from .msi to .sft on AdminStudio Forum. Dec 01, 2010 07:57 PM
- Posted Re: Problem with Repackager on AdminStudio Forum. Oct 06, 2010 07:26 PM
- Posted Re: Problem with Repackager on AdminStudio Forum. Oct 04, 2010 11:54 AM
- Posted Re: convert from setup to MSI leaves out files on AdminStudio Forum. Sep 22, 2010 08:23 PM
- Posted Re: Bug in Repackager? Directories containing square brackets. on AdminStudio Forum. Sep 16, 2010 01:27 PM
- Posted Re: Custom Action Error crashes installer on InstallShield Forum. Jul 15, 2010 11:27 AM
- Posted Re: ICE 33 resolution on AdminStudio Forum. Jul 15, 2010 11:22 AM
- Posted Re: Where do I find the RemoveFile Table? on InstallShield Forum. Jul 13, 2010 12:08 PM
- Posted Re: RemoveExistingProducts rollback on InstallShield Forum. Jul 13, 2010 12:06 PM
- Posted Re: Managed Custom Action on InstallShield Forum. Jul 12, 2010 06:52 PM
- Posted Re: Managed Custom Action on InstallShield Forum. Jul 12, 2010 11:23 AM
- Posted Re: Display a message box on dialog initialization on InstallShield Forum. Jul 12, 2010 11:17 AM