Known Issues

Release Version 2024.2

No known issues this release.

Release Version 2023.4

Bug ID: 1369214

Issue

When using HTTP - unable to create incident due to console errors while creating an issue in Self Service Mobile UI V3.
Workaround Use HTTPS.

Bug ID: 1369214

Issue

Inbound web service request fails with null reference object error and the message is stuck in Dispatched state.

Workaround

 

Verify and update the dispatch method name for the type Web Service Handler to HandleWebServiceMessage.

1.Login to Config DB of the on-premise environment.

2.Open the Message Queue Handler Workspace.

3.Open the handler name Web Service Handler.

4.Update the Dispatch method name to HandleWebServiceMessage.

5.Restart the Ivanti Message Queue Service.

In case the Dispatch Name is HandleMessage, then incoming web service will not work.

Release Version 2023.3

No known issues in this release.

Release Version 2023.2

Issue

Whenever Asset Processor displays the message "SQL Error 245: Data Access Error. Conversion failed".
Workaround Under CI Business Object select the field PercentFreeDiskspace and set Precision as 2 and save. Run the device sync again for failed Asset Processor.

Release Version 2023.1

Bug: 1041094:

Issue

ICDP web.release.configfile has 2 endpoints which has the same contract name and binding configuration. Due to this the files generated by SCW for OnPrem has 2 nodes with incorrect addresses that causes software messages to timeout.
Details

1.Log in to Neurons for ITSM.

2.Open the Configuration console.

3.Go to Integration Tools > Data Import Connections > Ivanti Neurons Connector –Device.

4.Validate the test connection and proceed till the final screen.

5.Click Run now.
Expected Result The status message in the Integration queue is displayed as Timed out.
Actual Result The status message in the Integration queue should be displayed as Completed
Workaround Remove the redundant entry that includes the actual hostname and update the "localhost" entry in the web.config file to specify the port number as 7200.

Release Version 2022.3

No known issues in this release.

Release Version 2022.2

No known issues in this release.

Release Version 2022.1

Bug: 923520:

Issue

When the Archive Mailbox Name has uppercase text, the email services do not work.
Details

6.Log in to ITSM as an Administrator.

7.Click more and search for Inbox Business Object and open it.

or

8.From the Configuration console, select Email Configuration > Mail Boxes.

9.Select any Protocol except IMAP4.

10.Set the following options to Move to Folder:

•Action To Perform On Processing Success

•Action To Perform On Processing Error

11.Enter the value as Absolute in the Archive Mailbox Name field.
Expected Result Email services should work.
Actual Result Email Service do not work.
Workaround

Enter only lowercase letter in the Archive Mailbox Name field.

Bug: 923520:

Issue

Email services do not work for IMAP4 Protocol when the Action To Perform On Processing Success and Action To Perform On Processing Error options are set to Move to Folder.
Details

1.Log in to ITSM as an Administrator.

2.Click more and search for Inbox Business Object and open it.

or

3.From the Configuration console, select Email Configuration > Mail Boxes.

4.Set the following options to Move to Folder:

•Action To Perform On Processing Success

•Action To Perform On Processing Error

Expected Result Email services should work.
Actual Result Email Service do not work.
Workaround

Delete the Inbox settings record and create a new one. Ensure the following options are set to Delete:

•Action To Perform On Processing Success

•Action To Perform On Processing Error

Bug: 923520:

Issue

Email services do not work when the Action To Perform On Processing Success and Action To Perform On Processing Error options are changed from Move to Folder to Delete without deleting the data in the Archive Mailbox Name field.
Details

1.Log in to ITSM as an Administrator.

2.Click more and search for Inbox Business Object and open it.

or

3.From the Configuration console, select Email Configuration > Mail Boxes.

4.Select the Protocol as IMAP4.

5.Set the following options to Move to Folder:

•Action To Perform On Processing Success

•Action To Perform On Processing Error

6.Enter some value in the Archive Mailbox Name field.

7.Without deleting the data in the Archive Mailbox Name, change the following options to Delete.

•Action To Perform On Processing Success

•Action To Perform On Processing Error

Expected Result Email services should work.
Actual Result Email Service do not work.
Workaround

Before changing the following options to Delete, ensure to delete the data from the Archive Mailbox Name field.

•Action To Perform On Processing Success

•Action To Perform On Processing Error

Release Version 2021.4

No known issues in this release.

Release Version 2021.3

No known issues in this release.

Release Version - 2021.2

Following known issue is in Ivanti Neurons for ITSM 2021.2 release:

  1. Bug 845546: When upgrading from 2021.1 to 2021.2, the application throws an error.
  1. Bug 811955: Request Offerings do not display in alphabetical order when the Global Constant EnableUKEnglishLocalization is set to True.

Issue Details

  1. Bug: 845546:
Issue

When upgrading from 2021.1 to 2021.2, the application throws an error.

Details

The upgrade from 2021.1 to 2021.2 is not successful. The new items introduced in the Configuration Item (CI) Business Object are not imported automatically.
Expected Result The upgrade should be successful without an errors.
Workaround

The latest ITAM delta upgrade package introduces the CI.ivnt_MedicalDevice new member objects in CI.

After applying the delta upgrade package, the new fields introduced in the CI base business object are not automatically inherited in the new member objects.

To force the field synchronization, so that missing fields are copied from the CI base object, you need to perform the following steps:

1.Go to one of the Existing Business object for example CI.ivnt_infrastructure create a boolean field.

To create a Boolean field:

a. From the Configuration console > Business Object > open the respective Business Object > Fields.
b. Click Add new Field, select the Field Type as Boolean.
c. Enter a name and click Save.

2.Go to the new member object - CI.ivnt_MedicalDevice and create a boolean field with same name created for the CI.ivnt_infrastructure business object.

3.Remove the field that you just added. First remove from CI.ivnt_infrastructure and then from CI.ivnt_MedicalDevice.

This workaround will fix the link between all the CI Group and the base business object.
  1. Bug: 811955:
Issue

Request Offerings do not display in alphabetical order when the Global Constant EnableUKEnglishLocalization is set to True.

Details

1.Log in to Neurons for ITSM

2.Open the Configuration console > Global Constants > set the EnableUKEnglishLocalization option as True.

3.Open Languages and add English UK Culture. If it is already added, remove and re-add.

4.Open the Service Desk console > Request Offerings. The list of Request Offerings are in alphabetical order.

5.Edit one of the offering except the first one from list, save and exit the page.
Actual Result The recently edited offering is on the top of the list.
Expected Result The Request Offerings should still be displayed in alphabetical order.

Release Version - 2021.1

Following known issue is in Ivanti Neurons for ITSM 2021.1 release:

Bug 822605: - Provisioning report on SSRS 2019 for custom authentication throws a 401 unauthorized error.

Issue Details

Bug: 822605:

Issue

Provisioning report on SSRS 2019 for custom authentication throws a 401 unauthorized error.
Details

Steps:

1.Install 2021.1 on windows 2019 and sql 2019.

2.Provision report on SSRS 2019.

3.Select Custom Authentication for Microsoft SSRS Authentication Type.

4.Under Service Account, select Use built-in account and Network Service from the drop down list.

5.Click Next and provide the necessary information and click Provision Report Now.
Actual Result The application throws a 401 error.
Expected Result Report provision should be successful.
Workaround Stop and start the Report Server Configuration Manager (SSRS) and provision the report again.

 

Release Version - 2020.4

Following known issue is in Ivanti Neurons for ITSM 2020.4 release:

Bug 774221: - Enabling chat fails.

Issue Details

Bug: 774221:

Issue

Enabling chat fails.
Details

Enabling chat fails with the error message - "Unable to register in chat" or "Login prompted".
Expected Result Chat feature should be enabled without any errors.
Workaround Review the Redis configuration inside AppServer directory of the installation and restart the Redis service.

Release Version - 2020.3

Following known issue is in Ivanti Neurons for ITSM 2020.3 release:

Bug 739326 - When trying to install Ivanti Service and Asset Manager, the installer automatically closes without installing upon clicking the Install button.

Issue Details

Bug: 739326

Issue

When trying to install Ivanti Service and Asset Manager, the installer automatically closes without installing upon clicking the Install button.

Details

1.Setup a machine with Window authentication.

2.Download the Ivanti Service and Asset Manager installer and run as Administrator.

3.Select the product you want to install, that is ISM, ITAM, or ITxM.

4.Follow the next steps and finally click the Install button.
Actual Result The installer closes automatically.
Expected Result The product should be installed.
Workaround Run the installer again.

Release Version - 2020.2

Following is the list of known issues in Ivanti Neurons for ITSM 2020.2 release:

1.Bug 697328 - After session timeout clicking on received notification it redirects to Home page of SSM user in Android and iOS device.

2.Bug 700504 - Enable Biometric Authentication checkbox is not displaying in Android device which has Face ID.

3.Bug 701732 - While renewing session using password, it throws time stamp exception in Android device.

4.Bug 702094 - Navigating to Ivanti Cloud Workspace throws an error.

5.Bug 703679 - TRANSLATION-Japanese-Administrator-Chat Configuration-"Seconds" is mistranslated as "2nd".

6.Bug 711161 - While upgrading from 2020.1, SCW throws an error if the value for Privileged User is set as 1 under Concurrent User section.

Issue Details

  1. Bug: 697328
Issue

After session timeout clicking on received notification it redirects to Home page of SSM user in Android and iOS device.
Details

Prerequisite:

•Ensure ISM application is configured to receive push notifications on your device.

1.Login to ISM mobile app as SSM role in Android or IOS device

2.Wait for session timeout (configure session time out in Admin UI)

3.In desktop create an incident to get notification in the mobile device

4.Click on the newly received notification

5.It redirects to Login page, enter valid credential to login.
Actual Result After successful login it redirects to Home page of SSM user.
Expected Result After successful login it should redirect to Notification Corner.
Workaround After landing on the home page, user can click on the bell icon on top right to navigate to notification corner to view notification.
  1. Bug: 700504
Issue

Enable Biometric Authentication checkbox is not displaying in Android device which has Face ID.
Actual Result

Prerequisite:

•Ensure Biometric authentication is enabled on your device.

1.Install latest ISM app in Android device which has Face ID enabled in the device.

2.Launch the App and access the url.

3.In the login page observe for Enable Biometric Authentication check box.
Expected Result Enable Biometric Authentication checkbox is not displayed to the user.
Actual Result Enable Biometric Authentication checkbox should be displayed to the user.
Workaround Use Phone PIN to login or enable fingerprint authentication on your mobile device.
  1. Bug: 701732
Issue

While renewing session using password, it throws time stamp exception in Android device.
Actual Result

Prerequisite:

•Session timeout value should be set in the Admin UI. e.g – set the value to 1 minute.

1.Login to ISM using passowrd in Android device.

2.Wait for session timeout.

3.Click on any workspace.

4.In the "You were logged out. Would you like to continue working?" pop up click the Yes button.

5.In the login page enter password and click the login button.
Expected Result It throws time stamp exception.
Actual Result It should login successfully to ISM mobile app.
Workaround Close the app, relaunch and login again.
  1. Bug: 702094
Issue

Navigating to Ivanti Cloud Workspace throws an error.
Actual Result

Note: This workspace newly added in 2020.2 and was not present in previous releases.

1.Login to ISM as Administrator.

2.Open Ivanti Cloud workspace.

3.In the login page enter password and click the login button.
Expected Result Workspace doesn’t load and displays error.
Actual Result Workspace should load without any error.
Workaround No workaround available.
  1. Bug: 703679
Issue

TRANSLATION-Japanese-Administrator-Chat Configuration-"Seconds" is mistranslated as "2nd".

Actual Result

1.Login to the tenant as Administrator.

2.Go to the Chat Configuration workspace.

3.Click UI under Session Configuration Settings.
Expected Result "Seconds" is translated as 2nd in time.
Actual Result Seconds should be properly translated.
Workaround No workaround available.
  1. Bug: 711161
Issue

While upgrading from 2020.1, SCW throws an error if the value for Privileged User is set as 1 under Concurrent User section.

Workaround

1.Log in to Neurons for ITSM with the Administrator role.

2.Open the Configuration console.

3.Under Security Controls, select Security and Sessions.

4.Under Concurrent Session, change the value of Named User, Privileged User, and Non Privileged User to 0.

5.Save the changes and refresh the page and re-validate the values are changed.

6.Now you can install 2020.2 Neurons for ITSM.

7.After installation is complete, you can change the concurrent users values as it was earlier.

Note: The user session information is stored in Frs_system_settings in case of sql update.

Release Version - 2020.1

Following is the list of known issues in Ivanti Neurons for ITSM 2020.1 release:

1.Bug 670687 - ISM SSO: Session renew fails for OpenID and SAML OKTA for Android device.

2.Bug 670665 - ISM SSO: After session timeout user is redirected to different browser while default authentication is activated if user don't want to work in Android device.

3.Bug 670661 - ISM SSO: After session timeout while renewing the session, application opens default external authentication login page in different browser in iOS device.

4.Bug 636223 - Ivanti cloud transfer: Blank record is getting created in Hardware workspace for device.

5.Bug 648276 - Software Asset creation has intermittent issues.

6.Bug 671029 - Username and roles are not visible as the text is in white color by default.

7.Bug 431449 - On-premise : Installation of Metric server for the first time fails.

8.Bug 678308 - On-premise: Unable to Login to Tenant once SCW completed for ITAM/IxM/ISM clean windows authentication.

9.Bug 676494 - Default value of Request Offering text field set to Current User Function (Primary Phone) is not reflecting in Service Catalog.

Issue Details

  1. Bug: 670687
Issue

ISM SSO: Session renew fails for OpenID and SAML OKTA for Android device.
Details

Prerequisite:

•Set any one of the external authentication as default. And set timeout session as 1 minute in Admin UI for validation purpose.

1.ISM Android Mobile App using OpenID or SAML OKTA as external authentication provider.

2.Wait for more than 1 minute.

3.Click on any one of the workspace.

4.The message "You were logged out. Would you like to continue working?" is displayed.

5.Click Yes.
Actual Result The same message "You were logged out. Would you like to continue working?" is displayed.
Expected Result The session should renew without any error.
Workaround No workaround available.
  1. Bug: 670665
Issue

ISM SSO: After session timeout user is redirected to different browser while default authentication is activated if user don't want to work in Android device.
Actual Result

On timeout of your session, if you select No button for the "You were logged out. Would you like to continue working?" the application redirects to different browser and opens default authentication login page in different browser and application continues loading in Android Mobile App.
Expected Result The application should logout the user session from the Android app.
Workaround No workaround available.
  1. Bug: 670661
Issue

ISM SSO: After session timeout while renewing the session, application opens default external authentication login page in different browser in iOS device.
Actual Result

Scenario 1: When Yes button is clicked for the timeout session message, default authentication provider login page opens in different browser and in mobile app ISM keeps loading.

Scenario 2: On clicking the external authentication hyperlink, the external authentication login page is opened in different browser instead of opening within the mobile app.
Expected Result The application should open in the ISM app.
Workaround No workaround available.
  1. Bug: 636223
Issue

Ivanti cloud transfer: Blank record is getting created in Hardware workspace for device.

Workaround

No workaround is available.
  1. Bug: 648276
Issue

Software Asset creation has intermittent issues.

For example, when a software is installed on different system, after sometime the same software asset is created twice.
Workaround

No workaround is available.
  1. Bug: 671029
Issue

Username and roles are not visible as the text is in white color by default.
Details

1.Login to ISM with Admin role.

2.Verify the logged in username and role.

Actual Result The username and role are not visible as the text is in white color.
Expected Result The logged in username and role should be visible.
Workaround

Navigate to the Configuration console > Style Editor and change the role text’s color to black.
  1. Bug: 431449
Issue

On-premise - Installation of Metric server for the first time fails with db connection error.

Steps:

  1. Install the latest 2020.1 build on Windows 2014 R2 or any OS.

  2. Select the Metric Server configuration in SCW.
Actual Results

The application fails to create the Metric Server database after the "Create" action though the db test connection is successful.
Expected Results The application should create the Metrix Server database.
Workaround

Recreate works fine.

  1. Bug: 678308
Issue

On-premise: Unable to Login to Tenant once SCW completed for ITAM/IxM/ISM clean windows authentication.

Steps:

1.Set up ITAM clean windows authentication.

2.Once SCW completed open tenant enter valid credentials to login to tenant.
Actual Results

The application throws an error.
Workaround

Re-run the SCW and try to login.
  1. Bug: 676494
Issue

Default value of Request Offering text field set to Current User Function (Primary Phone) is not reflecting in Service Catalog.

Prerequisite:

•Add Phone number to the current user.

Steps:

1.Login to the application as Admin or Service Owner.

2.Create a new Request Offering.

3.Go to Design Request form and add a text field.

4.Edit the field and set the default value to Function and select Current User: Primary Phone from the drop down list.

5.Publish the Request Offering and save.

6.Open the created Request Offering in Service Catalog and verify the current user phone number is populated.
Actual Results

Current User Phone number is not displayed in the service catalog.
Workaround

This is specific to 2019.1.0 OOTB onwards. No workaround available.

Release Version - 2019.3.1

Following is the list of known issues in Ivanti Neurons for ITSM 2019.3 release:

1.Bug 636223 - Ivanti cloud transfer: Blank record is getting created in Hardware workspace for device.

2.Bug 648276 - Software Asset creation has intermittent issues.

Issue Details

  1. Bug: 636223
Issue

Ivanti cloud transfer: Blank record is getting created in Hardware workspace for device.

Workaround

No workaround is available.
  1. Bug: 648276
Issue

Software Asset creation has intermittent issues.

For example, when a software is installed on different system, after some time the same software asset is created twice.
Workaround

No workaround is available.

Release Version - 2019.3

Following is the list of known issues in Ivanti Neurons for ITSM 2019.3 release:

1.Bug 616198 - Heat Mobile app may crash when iOS is upgraded from version 12.3.1 to 13.1.

2.Bug 610706 - Post 2019.2 upgrade, Audit History is not updated based on the relationship link for FRS_Approval business object.

3.Bug 615685 - Ivanti Cloud (UNO) Login App V1 & V2 integration does not work on ISM tenant which has Pre-MCT database.

4.Bug 620323 - Duplicate entries for workflow and task on creating a service request from a backup database.

5.Bug 635269 - IP Whitelisting shows "Invalid IP" for all FRSHeat integration API requests when session key from "Authenticate User" is used.

6.Bug 644185 - The application throws an error when trying to link new and edit existing records in Telemetry Logging Configuration tab in config db tenant.

7.Bug 70551 - Embedding content using iFrame in HTML UI Control is not working as expected.

8.Bug 518404 - Request Offering is not getting created in the tenant, when imported via the Release Tool patch file.

9.Bug 632194 - IP whitelisting - Integration trusted host is not allowing any IP to send/receive request, when the load balancer IP is configured.

Issue Details

1.Bug: 616198

Issue

After upgrading iOS version from 12.3.1 to 13.1, some users may experience crashing of the Heat Mobile app.

Workaround

Un-install and re-install the Heat Mobile app.

2.Bug: 610706

Issue

Post 2019.2 upgrade, Audit History is not updated based on the relationship link for FRS_Approval business object.
Actual Results
  1. Upgrade Neurons for ITSM to version 2019.2.
  2. Log in to Neurons for ITSM with Admin user role.
  3. Open the Configuration console.
  4. Navigate to Business Objects > Service Request > Relationships > ServiceReqAssociatedFRS_Approval.
  5. Select the Relationship is Audited check box.
  6. Save and exit.
  7. Create a Service Request that generates an approval, for example, Mailbox Quota Request.
  8. Save the Service Request and exit.
  9. Re-open the Service Request and click the Audit History tab.
  10. No link to the Approval record is added in the Audit History.
Expected Results A link to the Approval record should be added in the Audit History.

3.Bug: 615685

Issue

Ivanti Cloud (UNO) Login App V1 & V2 integration does not work on ISM tenant which has Pre-MCT database.
Workaround

Upgrade the pre-MCT tenant using MCT migration tool before performing IvantiCloud (UNO) Integration.

4.Bug: 620323

Issue

Duplicate entries for workflow and task on creating a service request from a backup database.
Workaround

Note: The issue is re-producible when you restore the 2019.3 OOTB database from any existing tenant.

You need to run a clean up script to remove the unwanted entries from specific table so that no duplicate workflow is triggered.

Run the below query in the restored tenant database and "isvisble=0" condition is mandatory. Make sure the workflow service is stopped before running this script and start after running.

"select * from Frs_def_businessrules where isvisible = 0"

5.Bug: 635269

Issue

IP Whitelisting shows "Invalid IP" for all FRSHeat integration API requests when session key from "Authenticate User" is used.

Workaround

Use the SID (from ISM application > Developer Tools) to authenticate API requests.

6.Bug: 644185

Issue

The application throws an error when trying to link new and edit existing records in Telemetry Logging Configuration tab in config db tenant.
Actual Results
  1. Log in to a config db tenant of Neurons for ITSM with Admin user role.
  2. Open a tenant record and navigate to Telemetry Logging Configuration tab.
  3. Click Link > select a service record to link > Add or Edit button.

The application displays an error message.
Expected Results

The selected service record should be linked to the Telemetry Logging Configuration.

Workaround

Go to the Telemetry Logging Configuration workspace, add new service records or existing records here. The updated services will be visible in the Telemetry Logging Configuration tab of the tenant page which you can now link.

7.Bug: 70551

Issue

Embedding content using iFrame in HTML UI Control is not working as expected.

8.Bug: 518404

Issue

Request Offering is not getting created in the tenant, when imported via the Release Tool patch file.

9.Bug: 632194

Issue

IP whitelisting - Integration trusted host is not allowing any IP to send/receive request, when the load balancer IP is configured.

Release Version - 2019.2

There are no known issues in Ivanti Neurons for ITSM 2019.2 release.

Release Version - 2019.1 and earlier

Given below is the list of known issues in Ivanti Neurons for ITSM 2019.1 and earlier releases.

  1. Bug 476581 - Configuration fails if the App server cache does not have trusted host information of database server.
  2. Bug 492307 - On-premise - Re-branding is pending in the ITAM application as it still refers to "Ivanti Service Manager".
  3. Bug 492520 - SSRS configuration with custom authentication and domain credentials may throw the 1326 error sometimes.
  4. Bug 492643 - Ops console is not re-branded for Ivanti, it still shows HEAT brand names.
  5. Bug 333924 - Configure OpenIDConnect Auth Provider for MS Azure AD.
  6. Bug 341934 - [Request for Information] Report: Distribution option "Download".
  7. Bug 505677 - Multiple records are displayed on the home page search for a single request.
  8. Bug 502699 - SSRS configuration fails while trying to add the provision report in SCW.
  9. Bug 504840 - There is a browser compatibility issue for Self Service Mobile, in the UI price list/ Cost panel showing Zero(0).
  10. Bug 383101 - Japanese characters are shown as ? in the FRS_SurveyAnswer.
  11. Bug 359153 - Logout from the Self Service Mobile UI takes users to the ISM login instead of the Auth provider login.
  12. Bug 508376 - "FrontRange Solution" installer certificate is not trusted by Microsoft anymore.
  13. Bug 519086 - Upgrading 2019.1 directly from 2018.1.1 does not work.
  14. Bug 522220 - Unable to create new CI due to the Asset Processor Configuration.
  15. Bug 525479 - Login page not loading by throwing Timestamp Error while Internal Services user is disabled.
  16. Bug 522214 - Config db/tenant db metadata version field left blank during upgrade/install.
  17. Bug 431449 - On-premise : Installation of Metric server for the first time fails.
  18. Bug 526262 - Upgraded ISM 2018.3.1 to 2019.1 and post upgrade accessing the below workspaces as LicenseManager role throws exception.
  19. Bug 485595 - The Sting "Self" is UNLOC shown under Self Service User - My Items > Benefits Package Claim.
  20. Bug 235039 - The Service Request Review and Submit page displays the incorrect employee details if the login IDs are similar.
  21. Bug 533210 - 2019.1 premise installer seems to silently exit or crash after installing one of the pre-req modules.
  22. Bug 576301 - Errors on Form and Grid for BO AuthenticationPrincipal when upgrading from 2018.3.1 to 2019.1.0 premise.

Issue Details

1.

  • Bug: 476581

    • Issue

    Configuration fails if App server cache does not have trusted host information of database server

    1. Install or upgrade ISM application to latest build version of 2018.1.1

    2. Install or upgrade the reporting service

    3. Provision the report as part of configuration

    Use Custom Authentication method for SSRS configuration and SQL authentication for database connection type.
    Workaround

    There is a timing issue on provisioning. If the application cache is not rebuilt after updating the Trusted Host Entry in the config database (central config webapp), then provisioning of reports will fail as post config calls fails (Exception to access config service). Hence, it is advised to make sure Trusted Host Address are already added in the config database and IIS is reset (or wait for 15 mins to rebuild cache).

    2.

  • Bug 492307

    • Issue

    On-premise - Re-branding is pending in the ITAM application as it still refers to "Ivanti Service Manager".

    Steps to reproduce

    Install ITAM application and check the product version and other branding-related information.
    Actual Results

    Expected Results Currently, the 2018.3.1 on-premise version is built on top of the ISM platform and continues to refer ISM in many places. This needs to be fixed.
    Workaround

    No application functionality should be lost.

    3.

  • Bug 492520

    • Issue

    SSRS configuration with Custom Authentication may fail sometimes if the domain user credentials provided is working. You will see the 1326 error.

    Steps to reproduce

    Configure SSRS with Custom Authentication with Domain credentials.
    Actual Results

    SSRS configuration with Custom Authentication is shown below:
    Expected Results Provided domain credentials should work and users should be able to proceed.
    Workaround

    Use Custom authentication with the User in-built account type "Network Service" to proceed.

    4.

  • Bug 492643

    • Issue

    2018.3.1 ops console is not re-branded for Ivanti, it still shows HEAT brand names.

    Steps to reproduce

    Login to ops console by accessing the following path: http://10.16.228.14/OpsConsole/User
    Actual Results

    5.

  • Bug 333924

    • Issue

    When configuring OpenIDConnect Authentication Provider for MS Azure AD and making "Test Authentication", he follwoing message appears: "Use Sub as external login as e-mail is not available at this step."

    Azure AD does not return "email" claim in response and there is no "email" in "Extracted JWT token".

    Instead of returning email in "email" claim, Azure returns an email in "upn" claim:

    {"typ":"JWT",

    "alg":"RS256",

    "x5t":"z44wMdHu8wKsumrbfaK98qxs5YI",

    "kid":"z44wMdHu8wKsumrbfaK98qxs5YI"}.{"aud":"022c4d20-1d56-4a73-a421-86b2b423f344",

    "iss":"https://sts.windows.net/23afecaf-6440-44aa-a6f2-b6e38bd02ba9/",

    "iat":1517385849,

    "nbf":1517385849,

    "exp":1517389749,

    "aio":"Y2NgYGi+6xjp02/t1/erTNy+LKVPa8dC4+/TP3xennmSm1+8+z4A",

    "amr":["pwd"],

    "family_name":"Sandyrov",

    "given_name":"Andrej",

    "ipaddr":"88.119.194.198",

    "name":"Andrej Sandyrov",

    "oid":"83f1b61f-1e77-4ce5-85ad-c76bed5a1247",

    "onprem_sid":"S-1-5-21-1293440551-2949271503-1314497110-1132",

    "sub":"qX_OE8OkmVyYRXYI7chX4qqSWPyCQLVRl8CU_YtYOY8",

    "tid":"23afecaf-6440-44aa-a6f2-b6e38bd02ba9",

    "unique_name":"[email protected]",

    "upn":"[email protected]",

    "uti":"ZmsLjPCsLEqe3Kbp8qkDAA",

    "ver":"1.0"}

    The following errors occur:

    User not found for external login qX_OE8OkmVyYRXYI7chX4qqSWPyCQLVRl8CU_YtYOY8. Try to use auto-provisioning

    ...

    Value is missing for 'email'

    System.ArgumentException: Value is missing for 'email'

    ?? at HEAT.Authentication.Sso.Oidc.OidcResultHandler.GetDictStringValue(IDictionary`2 dict, String

    ...

    Authentication failed unexpected error
    Actual Results

    Configuration to install Ivanti SM handler to use "upn" instead of "email.

    6.

  • Bug 341934

    • Issue

    When choosing the "Download" option in Distribution Information of the report from the homepage dashboard or report list, download is not happening.
    Expected Results

    Reports should be downloaded from homepage dashboard or report list.

    7.

  • Bug 505677

    • Issue

    In self-service mobile, when searching with the string "optional software" in the home page search box, multiple records that are displayed for a single record and the request offerings are in the "Design" state.

    Steps to reproduce

    1. Log in to ISM in the "Self Service Mobile" role.

    2. On the home page, search for "optional software".

     
    Actual Results

    The system displays multiple records for a single request that is in design state.
    Expected Results A single record should get displayed for a single request that are in the "Published" state.

    8.

  • Bug 502699

    • Issue

    SSRS configuration fails while trying to add the Provision report in SCW.

    Steps to reproduce

    1. Configure the Reporting service configuration.

    2. Click on "Provision report now".
    Actual Results

    Error message appears as shown above.
    Expected Results There should be no error and the URL should be accessible.

    9.

  • Bug 504840

    • Issue

    There is a browser compatibility issue (in Firefox and Microsoft Edge) for Self Service Mobile, in the UI price list/ Cost panel showing Zero(0).

    If a user selects an item, for example, Desktop, which is $595 when he submits the request, the cost panel shows $0. Hence, the severity must be kept to 2. In addition, customer bugs (which are linked) are getting blocked and hence, the priority should be set to 2.

    Steps to reproduce

    1. Login as an Admin.
    2. Go to the Request Offerings workspace and import a .ROF file, publish, and save.
    3. Switch to the Self Service (old UI) role.
    4. Go to Service Catalog and open this offering.
    5. Select Desktop type, then a Desktop and a Quantity. Notice that the price list looks correct for the selection.
    6. Without submitting or saving, go back and select Laptop type, a Laptop and a Quantity. Observe that the Costs panel is still correct and the originally selected Desktop item is removed.
    7. Switch to the Self Service Mobile UI.
    8. Go to Service Catalog and open this offering.
    9. Select Desktop type, then a Desktop and a Quantity. Observe that the price list looks correct for the selection.
    10. Without submitting or saving, go back and select Laptop type, a Laptop and a Quantity. Notice that the Costs panel retains the previously selected Desktop even though it should not.
    Actual Results

    The Cost panel shows zero even if the product is selected.

    This is working fine in Chrome, but not working in Firefox and Microsoft Edge.
    Expected Results The Cost panel should display the correct value for the selected type.

    10.

  • Bug 383101

    • Issue

    Japanese characters are shown as ? in the FRS_SurveyAnswer

    Steps to reproduce

    This error can be replicated in Demo 2017.3.1 and 2018.1 tenant: https://tenant-dev2.saasitpilot.com/.

    1. Open FRS_SurveyAnswer#
    2. Go to field QuestionText or AnswerText
    3. Change type to unicode,
    4. Save.
    Actual Results

    Error: Unhanded system exception: The given key was not present in the dictionary.

    Expected Results Possibility to set this field to be unicode text.

    11.

  • Bug 359153

    • Issue

    Logout from the Self Service Mobile UI takes users to the ISM login instead of the Auth provider login.

    Steps to reproduce

    1. Set up the environment with SAML authentication.
    2. Set up a logout URL as seen in the screenshot.
    3. Log in as admin with the role of Self Service Mobile.
    4. Log out later using the logout button.
    Actual Results

    Users are taken back to the ISM login page for only Self Service Mobile role.
    Expected Results Users should be taken back to the SAML login page.

    12.

  • Bug 508376

    • Issue

    The certificate issued for installer is "FrontRange Solution" and Publisher name is "Ivanti Inc." since the last couple of releases. The Windows certificate trust store never questioned the authenticity of the certificate earlier. However, somehow it is prompting the certificate trust question now on Windows OS like 2016, 2012 etc.

    Steps to reproduce

    1. Take the latest installer and install on vanilla OS (Win2016, 2012)
    Actual Results

    Expected Results Issue a new certificate to installer with "Ivanti Inc."
    Workaround Accept the certificate to add to MS trust store.

    13.

  • Bug 519086

    • Issue

    If a user tries to directly upgrade from 2018.1.1 to 2019.1.0 or the latest version, the upgrade will fail.

    This is because SCW fails to launch the post installer update due to the missing registry key for ProductType. This entry should be retained during the upgrade, which is currently not working. 2018.1.1 build: 2018.1.1000.2018103001 @ 10/29/2018 2019.1.1 build: 2019.1.1000.2019030701

    The supported upgrade paths for 2018.1.1 to 2019.1.0 application version must be 2018.1.1 > 2018.3.1 > 2019.1.0.

    Steps to reproduce

    1. Upgrade the existing 2018.1.1 on-premise version to the 2019.1.0 on-premise version by skipping the 2018.3.1 upgrade path.
    Actual Results

    Expected Results The product reg key must be created during an upgrade and SCW should launch without any error.

    14.

  • Bug 522220

    • Issue

    Unable to create new CI due to the Asset Processor Configuration.

    After installing the GatewayDC(Discovery), Gateway CI is not getting generated and getting error message as "Unable to create new CI due to the Asset Processor configuration". This is can be found only on OOTB(IxM) on 2019.1 Builds Onwards.

    Steps to reproduce

    1. Pre-requisite: This issue can only be reproduced on OOTB(IxM). SO to reproduce OOTB(IxM) environment is required.

    2. Login to the application.

    3. Go to the Admin UI and download the GatewayDC/StandardGateway and install with proper credential on the above mentioned kind on tenants environment.
    Actual Results

    Gateway is not getting created in under Gateway workSpace and Highlighted Error will comes in Message Queue Journal.
    Expected Results -

    15.

  • Bug 525479

    • Issue

    When Internal Services user is disabled in a tenant, then login page is not loading by throwing timestamp error.

    It is a regression issue as the 2018.3.1 environment login page is loading successfully if an Internal Services user is disabled. After 2019.1 deployment to FFT and NVD PLT landscapes where few customers login page is not loading by throwing the Timestamp Error. On Analyzing, ops team found Login "Internal Services" were disabled in those tenants. After enabling the login, they were able to login to the Tenant without any issues.

    Steps to reproduce

    1. Login to ISM as the Admin role.

    2. Open Employee workspace and search for "Internal Services" user.

    3. Disable "Internal Services" user and close the browser or try to logout.
    Actual Results

    The system is throwing the Timestamp error while loading the login page.
    Expected Results After disabling "Internal Services" user, login page should be loaded properly without throwing any timestamp error.
    Workaround To work properly, we need to enable the "Internal Services" user.

    16.

  • Bug 522214

    • Issue

    After installation or upgrade of ISM/AM/IXM application, the metaRevision field is not updated. Regression: NO as it is observed in 2018.3.1 or an earlier version.

    Steps to reproduce

    1. Install & upgrade any of the above application

    2. Check the MetaRevision version of the application tenant in configuration.
    Actual Results

    Expected Results MetaRevision should be updated or should retain the old value (in case of no system table upgrade) as it is a mandatory field.
    Workaround User should manually enter "670" in this field and save it. This is a workaround only for 2019.1.

    17.

  • Bug 431449

    • Issue

    Version: 2018.1.1 On-premise

    OS: Windows 2016 SP1 & IIS version 10.0.14393.0

    Installation of Metric server for the first time fails with db connection error, however subsequent attempt of "recreate" works fine.

    Steps to reproduce

    1. Install the latest 2018.1.1 build on Windows 2014 R2 or any OS.

    2. Select the Metric Server configuration in SCW.
    Actual Results

    The application fails to create the Metric Server database after the "Create" action though the db test connection is successful. However, subsequent attempt on "recreate' works fine.

    Expected Results -

    18.

  • Bug 526262

    • Issue

    Upgraded ISM 2018.3.1 to 2019.1.0 and post upgrade accessing the below workspaces as LicenseManager role throws exception.

    Steps to reproduce

    Upgrade ISM 2018.3.1 to 2019.1.0.
    Actual Results

    LicenseManager home page fails to load.

    Accessing the Software Inventory, Software Product, Software Family and other workspaces as a LicenseManager throws error in UI.
    Expected Results The above mentioned modules should not be exposed to LicenseManager role.

    19.

  • Bug 485595

    • Issue

    The Sting "Self" is UNLOC shown under Self Service User - My Items > Benefits Package Claim.

    Steps to reproduce

    1. Log in to ISM and change the role to Self Service User.
    2. Open the My Items workspace.
    3. Select Benefits Package Claim.
    4. Under Item Details, there is one unloc sting "Self" from "PATIENT INFORMATION".
    Actual Results

    The Sting "Self" is UNLOC shown under Self Service User - My Items > Benefits Package Claim.
    Expected Results The UNLOC string should translated as "自我".

    20.

  • Bug 235039

    • Issue

    Upgraded ISM 2018.3.1 to 2019.1.0 and post upgrade accessing the below workspaces as LicenseManager role throws exception.

    Steps to reproduce

    Upgrade ISM 2018.3.1 to 2019.1.0.
    Actual Results

    LicenseManager home page fails to load.

    Accessing the Software Inventory, Software Product, Software Family and other workspaces as a LicenseManager throws error in UI.
    Expected Results The above mentioned modules should not be exposed to LicenseManager role.

    21.

  • Bug 533210

    • Issue

    2019.1 premise installer seems to silently exit or crash after installing one of the pre-req modules.

    Steps to reproduce

    1. Run installer exe as an admin.
    2. Click Install to installer pre-reqs. A dialog box will appear, "Extracting Ivanti Service Asset Manager.msi.
    3. Follow the wizard to where you select SM / AM / both.
    4. Select any installation type, click next, then again next, select Complete, click next, and then click install. Just after the VC 2013 redist x64 finishes installing the installer exits silently.
    Actual Results

    Just after the VC 2013 redist x64 finishes the installing process, the installer exits silently.
    Expected Results Installer should progress normally.
    Workaround Re-run the installer EXE.

    22.

  • Bug 576301

    • Issue

    During Update System on Update Application Database in SCW, the system receives a notification that it was updated with visible errors.

    Example: Patch 'AuthenticationPrincipal' has 5 error(s) Error during metadata commit operation for seq = 12482: System.Exception: Nom de colonne non valide : 'GlobalId'.

    Workaround

    If a customer receives the error for GlobalID and/or AuthenticationPrincipal, then:

    1.Close SCW.

    2.Restore the Application DB back to 2018.3.1.

    3.Go to the AdminUI and import the “GlobalID_Contract_Identity.MetadataPatch” package.

    4.Re-launch SCW.

    5.Re-validate and re-select upgrade. The customer should be able to upgrade ISM DB with no errors.

    Optimally, the customer should run through the following steps so they do not have to wade through a failing upgrade and then have to restore the 2018.3.1 Application DB, thus saving possibly hours of time.

    1.After installing 2019.1.0 and before walking through the SCW, launch AdminUI.

    2.Import the “GlobalID_Contract_Identity.MetadataPatch” package.

    3.Walk through SCW and the customer should be able to upgrade DB.