Description When attempting to delete a beacon in disabled status in the Beacons view, a red bar error occurs. The beacon remains undeleted.   Workaround Change the beacon status before attempting to delete. Or Run the query below on the compliance database with the name of the beacon that needs to be removed. DELETE FROM Beacon WHERE BeaconName = '<nameofbeacon>'     ... View more

Description If an inventory is updated with a nondefault role, the inventory does not consume any license. This is due to an incorrectly populated flag in the database. This can be confirmed with the query below: select * from ComplianceComputerRole where DefaultValue='<EnterRoleNameHere>' If ManageLicenses does not have value of 1, the device with this role will not consume licenses.   Workaround Run the query below to enable consumption on the the devices with the custom role. update ComplianceComputerRole Set ManageLicenses=1 where DefaultValue='<EnterRoleNameHere>' A reconcile is needed after to calculate consumption.   Resolution The issue will be fixed by Engineering with bug  IOJ-2094595. ... View more

Symptoms: When navigating to Inventory Evidence tab of the discovered device record, there is no evidence showing. The source of the inventory was from agent. Diagnosis: There is an incorrect connection string to the Inventory Database. Solution: Confirm that the registry value below is correctly pointed to the Inventory Database on both the web and batch server: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageSoft corp\ManageSoft\Reporter\CurrentVersion\InventoryDatabaseConnectionString Confirm that the Server and DatabaseName column from the query result is correct. Please execute on the Compliance Database. SELECT * from ComplianceConnection where SourceType='ManageSoft' ... View more

Symptoms: When importing source data with Microsoft Office format data, the error message below appears: "The MicrosoftAce.OLEDB.12.0 provider is not registered on the local machine" Diagnosis: A prerequisite for the software is missing. Solution: Download and install the 32bit version of Microsoft Access Database Engine 2010 Redistributable. https://www.microsoft.com/en-us/download/details.aspx?id=13255 ... View more

Symptoms: With SCCM import, the reconcile fails with an error similar to the one below: Failed to execute Reader 'GetUniversalApplicationInstalledInstallerEvidence-CreateIndexes' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Reader\sms\InstallerEvidence.xml, at step line 2 Error: Operation failed. The index entry of length 910 bytes for the index 'IX_InstallerEvidence' exceeds the maximum length of 900 bytes. Warning! The maximum key length is 900 bytes. The index 'IX_UniversalInstalledInstallerEvidence' has maximum length of 1056 bytes. For some combination of large values, the insert/update operation will fail. Warning! The maximum key length is 900 bytes. The index 'IX_InstallerEvidence' has maximum length of 1056 bytes. For some combination of large values, the insert/update operation will fail. The statement has been terminated. Diagnosis: This is due to  the combined string of the installer evidence, version, and publisher being too long. This usually occurs if the any of the above values are modified or the installation was repackaged. Solution: This issue has bee resolved in FNMS 2019 R2.3. Workaround: The queries below can be used on the SCCM database to identify which entry and machine this evidence is coming from. If possible, please remove the evidence. If it is modified from the default value, there is a high chance this will not map to any existing entry in the library. SELECT DATALENGTH(DisplayName0) + DATALENGTH(Version0) + DATALENGTH(Publisher0), c.name00, arpd.* FROM dbo.v_GS_ADD_REMOVE_PROGRAMS AS arpd LEFT OUTER JOIN Computer_System_data AS c ON c.MachineID = arpd.ResourceID WHERE DATALENGTH(DisplayName0) + DATALENGTH(Version0) + DATALENGTH(Publisher0) > 900 SELECT DATALENGTH(DisplayName0) + DATALENGTH(Version0) + DATALENGTH(Publisher0), c.name00, arpd.* FROM dbo.v_GS_ADD_REMOVE_PROGRAMS_64 AS arpd LEFT OUTER JOIN Computer_System_data AS c ON c.MachineID = arpd.ResourceID WHERE DATALENGTH(DisplayName0) + DATALENGTH(Version0) + DATALENGTH(Publisher0) > 900 ... View more

Summary On the Project Assignment view, no imported users show up for selection. Symptoms When trying to assign an user to a workflow through the AdminStudio Process Assistant, none of the imported users show up. As a result, the process cannot be completed. Cause Setting in the web.config file is hiding all the users in the Project Assignment view. Steps To Reproduce 1. Launch the AdminStudio IDE and click on the Process Assistants tab. 2. Right click in the left window pane and choose "Create a new project". The New Workflow Project Wizard appears. 3. Click Next on the Welcome dialog. 4. Choose a Workflow template and click Next. 5. Leave the Source Package field blank and click Next. 6. Leave the Target Directory and Target Filename blank and click next. 7. On the Project Assignment screen, the list of "AdminStudio Application Catalog Users" is blank and the Finish button is disabled. Resolution In the Web.config file located in the wwwroot subfolder of the Workflow Manager installation , change the value of "ShowOnlyAssignedUsersInAS" to "0". The file is located at C:\WorkflowManager\wwwroot by default. ... View more

Summary Error 7354 occurs when building MSI project with entries in the MoveFile table. Symptoms Error 7354 occurs when building MSI project with entries in the MoveFile table using Installshield. ISDEV : error -7354: The English (United States) value for string 'ID_STRING2' does not contain a legitimate value for table MoveFile column SourceName Cause The SourceName column in the MoveFile table should be a Text data type and should not be validated. There is a bug in IS2016 that is trying to validate the value. Steps To Reproduce Create BMSI Add a sample file in Files and Folder view Navigate to MoveFile table Add "SampleKey" for FileKey file Add "AllOtherFiles" for Component_ Add "SourceFile.exe" for SourceName column Add "SOURCE~1|SourceFile.exe" for DestName column Add "INSTALLDIR" for SourceFolder column Add "INSTALLDIR2" for DestFolder column Add "1" for Options column Build project Resolution Backup the ISWIBuild.dll file at C:\Program Files (x86)\InstallShield\2016\System\ Extract the attached file to that location Restart InstallShield and try building again Additional Information The issue is tracked internally under the Work-Order# IOJ-1774403 and the hotfix issued will be included in the future releases of InstallShield. The download of InstallShield 2016 was updated on 9/8/2016 to include this hotfix, the updated version number for ISWIBuild.dll is 23.0.0.290 ... View more

Summary Error 7354 occurs when building the MSI project Symptoms The build error 7354 occurs while referencing a string that does not have the correct value in MSI projects. The issue may occur with a new project or a migrated project. The error will reference the string as well as the table using the string. For example, the error can be displayed as: ISDEV : error -7354: The <LANGUAGE NAME> value for string <STRING_ID> does not contain a legitimate value for table <TABLE NAME>column <COLUMN NAME>. OR ISDEV : error -7354: The English (United States) value for string 'ID_STRING4' does not contain a legitimate value for table Shortcut column Name Cause This error is known to occur when a destination filename column needs to be in the shortfilename format as documented at the following link. MSDN: Filename data type For example, the following two strings are valid: status.txt projec~1.txt|Project Status.txt We introduced additional string validation with InstallShield 2016, therefore a project successfully built in previous versions may exhibit this error when built using InstallShield 2016. Resolution Check the requirements of the table mentioned in the error. Use Direct Editor to navigate to the table and press key F1 will bring out the HelpDoc for the table. Clicking on the link for the Type column will bring up an article about field requirements. For example, the FileName column of the RemoveFile table requires a FileName data type. This data type will need a short file name. Adding a short file name will fix the issue. For Express projects there is no direct access to the tables. The string entries can be exported in the Project > Export String Entries option. The modified strings can then be imported back to the project after being fixed. Additional Information Additional information: To include a long file name with a short file name, separate it from the short file name with a vertical bar (|). For example, the following two strings are valid: Eshwar.txt Projec~1.txt|Project Scripting.txt Short and long file names must not contain the following characters: \ ? | > < : / * " In addition, short file names must not contain the following characters: + , ; = [ ] Short file names may not include a space, although a long file name may. No space is allowed preceding the vertical bar (|) separator for the short file name/long file name syntax. If a space exists after the separator, then the long file name must have a space at the beginning of the file name. No full-path syntax is allowed. This error is documented briefly in the helpnet article Build Errors and Warnings. Also reference: Error 7354 when building MSI with MoveFile Table Entry ... View more

Summary How to set Product Name during runtime for InstallScript Project Synopsis This article describes how to set the Product Name during runtime for InstallScript Projects. Discussion There are several properties to change to make sure all appearances of the product name is changed. Modifying IFX_PRODUCT_DISPLAY_NAME should change the value that the placeholder %P uses in the dialogs. Modifying UNINSTALL_DISPLAYNAME should change the product name being displayed in the Control Panel. Modifying IFX_SETUP_TITLE should change the product name in the title bars of the dialogs. All the properties can be changed in OnBegin() Additional Information If the string being used for the Product Name is non-ANSI, the string will have to be set in the String Editor before assigning to the product name properties. The syntax is below where ID_STRING is the identifier of the string editor entry containing the new product name. IFX_PRODUCT_DISPLAY_NAME = @ ID_STRING ... View more

Summary How to modify text font, size, and color Synopsis Text in InstallShield can be changed to use preset font, color, and size in the TextStyle Table. Discussion InstallShield will use a preset font provided in the the Text Style field for each text object. Additional Information These presets are stored in the TextStyle table in the Direct Editor. Modification and addition of presets can be created there. The MSDN article below contain additional information on what needs to be provided for each field. http://msdn.microsoft.com/en-us/library/windows/desktop/aa372074(v=vs.85).aspx ... View more