Summary How to remove integration between App Portal and FNMS Synopsis If integration between App Portal and FNMS is removed from App Portal, you may find that you are unable to check out catalog items that have an ARL specified. When attempting to add an item to the cart, an error stating "<title> can not be added to the cart at this time.....". Discussion Even if you remove the integration between App Portal and FNMS, there will still be a mapping in the App Portal DB which indicates that that catalog item is still licensed. It will be necessary to remove this mapping in order to avoid the error. To remove the mappings from the DB run the following query against the App Portal DB. UPDATE WD_WebPackages SET FUID=NULL WHERE FUID is not NULL You will no longer see an error for those CI's at checkout Note: Always backup your database before making any changes. ... View more

Summary ISEXP: fatal error -7219: Failed to verify digital signature of <> Error -2147467259: Automation error Symptoms This build error usually occurs due to expired, corrupt or missing root certificates on your machine. ISDEV: fatal error -7210: Failed to verify digital signature ISDEV : fatal error -7219: Failed to verify digital signature of C:\Program Files\InstallShield\VERSION\System\IsUiServices.dll Cause The Build Machine Does Not Have Latest currently used root Certificates This is related to the operating system and is generally seen if building on an offline machine or a machine missing the latest root certificate update. Resolution Ensure your Windows Trusted root certificates are up to date: https://support.microsoft.com/en-gb/kb/293781 If your certificate has expired or become corrupted, verify if this is the case by right clicking on C:\Program Files (x86)\InstallShield\VERSION\System\ISUIServices.dll to view the properties - if there is a Warning triangle this needs to be updated replaced. The current certificate is VeriSign Class 3 Public Primary Certification Authority -G5 The certificate is no longer publicly downloadable from VeriSign Website, this particular site no longer exists, since they were aquired by Symantec. Workaround In order to obtain an updated certificate for this Goto https://www.websecurity.digicert.com/theme/roots Locate Root 3 Name: VeriSign Class 3 Public PCA - Generation 5 (G5) Serial Number: 18 da d1 9e 26 7d e8 bb 4a 21 58 cd cc 6b 3b 4a Operational Period: Tue, November 08, 2006 to Wed, July 16, 2036 Certificate SHA1 Fingerprint: 4e b6 d5 78 49 9b 1c cf 5f 58 1e ad 56 be 3d 9b 67 44 a5 e5 Change the extension to cer, double click on the file to open the certificate, and click the install button. You should install this certificate to the Trusted Root Certificate Authorities Store. Symantec SHA256 TimeStamping Signer Certificate - G1 Download and install the certificate at the below link: https://symantec.tbs-certificats.com/vsign-universal-root.cer Double click on the file to open the certificate and click the install button. You should install this certificate to the Trusted Root Certificate Authorities Store. Additional Information Symantec - Licensing and Use of Root Certificates https://www.symantec.com/page.jsp?id=roots See also: Windows 8 and Windows Server 2012: How to Open the Certificates Console http://social.technet.microsoft.com/wiki/contents/articles/11497.how-to-open-the-certificates-console-in-windows-8-and-windows-server-2012.aspx Related KB Articles Error -7210</> ... View more

Summary Delete a certificate from the InstallShield project to prevent error extracting digital information from file ISDEV : error -6258 Synopsis If you no longer require signing and your project previously had signing enabled. ISDEV : error -6258: An error occurred extracting digital signature information from file "C:\InstallShield Projects\My Project Name-1\Product Configuration 1\Release 1\DiskImages\DISK1\My Project Name-1.msi". Make sure the digital signature information provided in the IDE is correct. You should be able to disable the signing and remove the certificate information in the project. Discussion If you no longer require signing and your project previously had signing enabled disable the signing and remove the certificate information on the signing tab of the release settings. There are a number of ways to disable certificate settings. 1) Using the Releases view using the Signing tab of the Release settings delete all the entries and set the sign files option to 'No'. Reference image immediately below for example 2) Using the Project Assistant view on the Build Installation page verify Digitally sign setup check box is not enabled Related KB Articles Build Error 6258 (1) Build Error 6258 (2) Error 6259, 6258, and 6003 while attempting to sign installers ... View more

Summary This article shows you how to enable Windows Feature(s) during an installation, that may be required for your Product, but maybe disabled by default on target systems Synopsis InstallShield Premier Edition:Suite Project has built-in support for enabling several Windows Features during an installation. This may be required as some Windows functionality is disabled by default on target systems. This guide will help you to enable the required feature(s) during your installation Discussion Some Windows functionality is disabled by default on target systems. In addition, some end users, or perhaps IT administrators, may choose to disable some Windows functionality. InstallShield has built-in support for enabling several Windows Features: ? Internet Information Services ? PowerShell ? .NET Framework 3.x InstallShield also lets you specify additional Windows roles and Features that a package requires. Only available in the Suite Project which is available with InstallShield Premier. In a Suite UI, To specify a Windows role or Feature that you want to enable, 1. Click Packages, in the View List under Organization. 2. In the Packages explorer, click the package that you want to configure. 3. On the Common tab, in the Windows Features setting, click the Add New Windows Feature button, and then click one of the available Feature options For example IIS: InstallShield adds a new Windows Feature row under the Windows Features setting, This is not available in the Professional edition of InstallShield with the Advancesd UI project, which may be assumed from the wording in the Online documentation http://helpnet.flexerasoftware.com/installshield21helplib/helplibrary/SteWindowsFeat.htm Support for scheduling actions to occur at run time on target systems is Not Available in Avanced UI projects whereas it is in a Suite UI projects. What you would have to do instead for the Non Premier Version is use a Custom Action in your msi to enable the required feature using Deployment Image Servicing and Management (DISM.exe) tool. DISM is the inbox utility included with Win7/2008 R2 installations, To install IIS 7.5 on Windows 7, you use DISM.exe to target the running operating system (using the /Online switch) and use the /Enable-Feature option to enable individual IIS features DISM /online /enable-feature /featurename:<name of feature> You could run this from a EXE type custom action or a batch file see attached sample bat as an example Related Documents Enabling Windows Roles and Features During a Suite/Advanced UI Installation Advanced UI Projects vs. Suite/Advanced UI Projects Deployment Image Servicing and Management (DISM) DISM - Deployment Image Servicing and Management Technical Reference for Windows Enable or Disable Windows Features Using DISM ... View more

Summary If source files are stored on a Network or mapped drive Installshield cannot access Symptoms This issue can occur on Windows Vista and above with UAC enabled, Installshield cannot get access to Networked drives. Cause This error is due to the way Windows Vista and Windows 7 onwards works if UAC is enabled. Windows treats members of the Administrators group as standard users. When you run an application as an Administrator, you are then provided an Administrator access token for that action. When network shares are mapped during login, they are linked to the current logon session for the current access token (Linked to the "standard user" token even if logged in as an Administrator) Since InstallShield makes use of the Administrator token, you will then lose access to the mapped network location due to the change in the security token - ie: no longer using the standard user access token. Resolution To work around this problem, configure the EnableLinkedConnections registry value. This value enables Windows Vista and Windows 7 to share network connections between the filtered access token and the full administrator access token for a member of the Administrators group. To configure the EnableLinkedConnections registry value Click Start, type regedit in the Start programs and files box, and then press ENTER. Locate and then right-click the registry subkey HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System. Point to New, and then click DWORD Value. Type EnableLinkedConnections, and then press ENTER. Right-click EnableLinkedConnections, and then click Modify. In the Value data box, type 1, and then click OK. Exit Registry Editor, and then restart the computer. Workaround For issue Workaround refer to Microsoft Technet article below. Some Programs Cannot Access Network Locations When UAC Is Enabled ... View more

Summary Failed to extract file setup.inx. Error = 0 Intermittent errors known to occur with a Basic msi using a .rul file for custom actions Symptoms An error can occur at install time using a Basic MSI with .rul file for InstallScript custom actions.The Script File when using InstallScript cannot be extracted to Temp Folder. The result is Failed to extract file setup.inx. Error = 0 This is expected to be a generic error with evidence there is an environmental issue. Cause Possible causes Antivirus product blocks the extraction of some files. This occurs when the anti virus scanners flag them as viruses. Insufficient privileges to the temp folder, or not enough free space on the target machine to extract the files. Installing over a slow network connection. Resolution Test installing with the antivirus disabled, particularly real time scanning to see if this is the issue. Ensure that you have Write privileges to the Temp folder and that there is also sufficient space. If there is a slow network connection, try installing from a local directory ... View more