Summary This article provides, and details how to apply the hotfix patch that was created for Workflow Manager 2017. Synopsis This article provides, and details how to apply the hotfix patch that was created for Workflow Manager 2017. Discussion This patch addresses the following issues: IOJ-1763363 - Request for additional report with click through feature on dashboard page IOJ-1841457 - Conflict with ?Application Upload? and ?AdminStudio Package Upload? data elements in the same workflow IOJ-1841493 - AdminStudio import integration steps should support adding transforms for MSI packages IOJ-1847133 - Same package cannot be distributed to different SCCM environments IOJ-1863285 - Unable to access links from WFM when using single sign on IOJ-1874263 - Approval Task step not working as expected IOJ-1856893 - System out of memory exceptions You can download the attached ?Patch 06-Jul-2018.zip?. To apply the patch please do the following steps: Extract the contents of the .zip to your server Run the ?WFM 2017 Update 1.exe? Once you get to the setup complete dialog you will see a button that says, ?Configure Database? instead of finish. Instead of clicking this please use the ?X? on the title bar to close the install. Since the install completed this will have no negative impact on the patch After the install is complete take the ?1700UpgradeWFM.sql? from the SQL Scripts folder Once the database has been updated please perform an iisrest ... View more

Summary This article covers how to apply the second update patch created for Workflow Manager 2017. Synopsis This article details how to apply the second update that was created for Workflow Manager 2017. This update includes all the fixes found in the first update. Discussion This update addresses the following issues: Update 2: IOJ-1883923 - Click through capability for 'Open Issues' IOJ-1872509 - Issue with auto assignment from FNMS IOJ-1850036 - Give Consumer users access to the Properties tab IOJ-1876585 - Fix Typo ?Click here to go to dasboard page? IOJ-1883742 - Add Cummins' Hot Fix items to WFM 2017 code stream IOJ-1835626 - Corrupt Database With Duplicate ItemRole Values for an ItemID Associated with WFMinorItemID IOJ-1857638 - When new roles are added after the template is created, Users Without Edit Permission to the new role are Able to Advance Workflow. IOJ-1800604 - Customer template does not rollback IOJ-1860738 - Time Off Administration Screen Needs to Allow Setting the Times for a Request IOJ-1883926 - Custom Table Editor view IOJ-1884368 - Request Detail report breaks after making SLA tracking changes in the template IOJ-1885894 - Creation of Project based of Template is Out of Sync for ItemRole and TemplateRole tables. Update 1: IOJ-1763363 - Request for additional report with click through feature on dashboard page IOJ-1841457 - Conflict with ?Application Upload? and ?AdminStudio Package Upload? data elements in the same workflow IOJ-1841493 - AdminStudio import integration steps should support adding transforms for MSI packages IOJ-1847133 - Same package cannot be distributed to different SCCM environments IOJ-1863285 - Unable to access links from WFM when using single sign on IOJ-1874263 - Approval Task step not working as expected IOJ-1856893 - System out of memory exceptions You can download the attached ?WFM_Update_2.zip?. To apply the patch please do the following steps: 1: Extract the contents of the .zip to your server 2: From an administrative command prompt execute: iisreset /stop 3: Once IIS is stopped, copy the ?wwwroot? folder from the .zip to ?AdminStudioWebComponents_2017?. Confirm to merge existing folders and overwrite existing files. 4: Once this is complete you will need to take the ?1700UpgradeWFM.sql? and ?WFM-6370.sql? from the ?wwwroot\SQL Scripts? folder, and run this against your SQL database. 5: From an administrative command prompt execute: iisreset ... View more

Summary This article will cover how to use Windows Active Setup feature to repair user settings Synopsis This article will cover how to use Windows Active Setup feature to repair user settings Discussion The Windows Installer service will install the user-specific data only for the profile of the account under which the application is being installed. So, if another user logs into the machine, that user data is unavailable to the new user. It is typically recommended to use advertised shortcuts as an entry point to trigger the repair. A Windows Installer advertised shortcut causes Windows to verify that all of the application's component key paths are in place before launching the application. If a key path is missing, Windows Installer will try to repair the application before launching the program. This method works well for repairing user-specific data if the application has shortcuts, but this will not always be the case. For these cases, Windows offers the Active Setup feature through some registry keys. There are two registry keys that Windows uses to decide whether an application is installed for a user as they are logging into Windows. The concept here is that you will create a per-machine registry key in HKEY_LOCAL_MACHINE and then compare that key with a similar key in HKEY_CURRENT_USER. If the version information in the keys is different, then Windows runs a command specified in the HKEY_LOCAL_MACHINE key and updates the version data so that the command does not run again. To set this up with your install you will need to add some registry data into your InstallShield project. The installer will need to write to the following registry key: HKEY_LOCAL_MACHINE\Software\Microsoft\Active Setup\Installed Components\[ProductCode] With the following value: "@"=[ProductName] "StubPath"="msiexec.exe /fou [ProductCode] /qb" "Version"="1,0,0" Once these are added in InstallShield it should look something like: Once this is setup when the end user logs into the computer Active Setup will compare the registry data in HKLM with the corresponding key in HKCU, and if he version in HKCU is less than the one in HKLM or the HKCU key does not exist, Windows will copy some of the values from the HKLM key to the HKCU key and then execute the command in the "StubPath" value. At some point the original user that did the initial install will need to log off and log back onto the computer. In this case the Active Setup may run a repair under this user even though it is not necessary. To get around this you will want to also add a registry key and value under the HKCU hive. This would be in the following key: HKEY_CURRENT_USER\Software\Microsoft\Active Setup\Installed Components\[ProductCode] With the following value: "Version"="1,0,0" Once this is added in InstallShield it should look something like: Once this is done the user that did the first time install should be able to log off and back on without triggering the repair. Any other user should see the Windows Installer repair dialog once they login, and Windows has determined that the Active Setup should be run. The last thing to note will be to ensure that the Windows Installer will be able to locate the source media to complete the repair. If Windows Installer needs the source media, but cannot find it, the end user will be prompted to browse to the source media. To get around this you can place the source media where you would like, for example on a network share, and then specify this location in the SOURCELIST property in your installer. If you do not have network access in your environment you can copy the source to a common accessible location on the machine, for example a location like: [CommonAppDataFolder]\[Manufacturer]\[ProductName] Which should resolve to something like: C:\ProgramData\MyCompany\Active Setup Sample Related Documents SOURCELIST property Registry View ... View more

Summary Skinned dialogs show overlapped text after files in use Symptoms If a ?Files in Use? dialog is presented during an InstallScript/MSI install that is using any other themes besides the default (none) text on the progress dialog will be overlapped. Cause The exact cause of this issue is not known, but this issue is currently being tracked under the work orders IOJ-1621607 and IOJ-1624889 as a bug. Workaround To work around this issue you can do one of the following: Add MSIRESTARTMANAGERCONTROL to the Property Manager and set its value to ?Disable? (no quotes). Modify the OnRMFilesInUse event to disable the status dialog (usually STATUSEX) before calling SdRMFilesInUse and then re-enable it after the dialog call. Additional Information For more information on on the property and events mentioned in the work around please refer to the following: OnRMFilesInUse STATUSEX MSIRESTARTMANAGERCONTROL property ... View more

Summary Access is denied errors are most commonly caused by antivirus Symptoms Running a pure InsatllScript based installation you see a File Error, ?Access is denied? during the actual installation of the files. Cause This error can occur when third party software, mainly anti-virus, hold the .tmp files in use, causing the InstallScript engine to not have access to them. The .tmp files are coming from the InstallScript engine. What actually occurs during installation is a .tmp file is created within the installation location, and then the .tmp file is renamed or expanded to become the target file. Some anti-virus solutions will either hold these files in use, and in some cases delete these files. This behavior also appears to be most common with installations that contain a large number of files. Workaround There are a few ways that this could ultimately be addressed. The first way would be to alter the default OnFileError event to contain logic that will automatically retry accessing the file. This can add some additional time to the install, but should address the access is denied error. You can refer to the OnFileError_Retry.txt attached to this KB for an example of this modified event. Another longer term solution would be to migrate to a Windows Installer based project type, with Basic MSI being preferred. Since the MSI based installers are processed by Windows Installer the files should not be locked by anti-virus at installation time. Additional Information If you are experiencing this error and it has been determined that it is caused by anti-virus, then you will want to contact the anti-virus vendor. Ultimately the issue is with how these third-party applications handle the .tmp files, and would require the vendors to address this with their software. In this regard it is best for you as the customer of the anti-virus to contact the vendor for support, and request them to address the problem. ... View more

Summary Long delays in the signing process and missing time stamps is a sign of a connection issue Synopsis When you build an installer and have specified it to be signed it will take a very long time to sign the package. Once the build is complete you might also notice that the time stamp information is missing from the signature on the package. Discussion When you see this long of a delay, and the time stamp is missing from the signed package, this is an indicator that there is a communication problem between the signing process and the time stamp server. This could be caused by an unstable internet connection, or if the communication is being blocked by a proxy, firewall, or other security measures in your environment. Workaround You will want to work with your IT department to ensure that no communication is being blocked during the signing process, and if it is work with them to resolve the problem. ... View more

Summary A delay can be seen while installing an MSI Synopsis On newer or fully updated operating systems you may see a delay during the installation of an MSI package. Discussion When installing an MSI on newer or fully updated operating systems the installer may take several minutes longer to install than expected. You may also notice the delay in the installer in the log in lines like the following: MSI (s) (1C:48) [18:27:33:263]: SECREPAIR: New Hash Database creation complete. MSI (s) (1C:48) [18:35:36:219]: Transforming table Property. Over the past few years Microsoft has made some security improvements with Windows Installer. Since these security enhancements have been added there can be some delays seen during the installation of an MSI. Since this is related to security updates it would not be recommended to remove any updates as a workaround to the delay. This behavior is also something that InstallShield will have no influence over as it is related to Windows Installer itself. Additional Information Two of the common updates associated with this behavior are the following: MS15-074: Vulnerability in Windows Installer service could allow elevation of privilege MS14-049: Description of the security update for Windows Installer Service ... View more

Summary The UAC icon cannot be changed for a Basic MSI project. The interaction between msiexec.exe and the UAC cause the generic icon. Synopsis When uninstalling a Basic MSI installation from ?Programs and Features? you will notice that the icon on the UAC dialog is a generic icon. Discussion This is caused by the UAC being displayed by the application that is triggering the UAC prompt. In this case Windows Installer (msiexec.exe) is what is making the request to the UAC. As a result of this the generic icon is coming from the interaction of msiexec.exe and the UAC. Workaround Since this is an interaction between msiexec.exe and the UAC there are not going to be any ways to alter this through your Basic MSI project. ... View more