Known Issues

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 login to config db of the on premise environment open the message queue handler workspace open the handler name web service handler update the dispatch method name to handlewebservicemessage 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 log in to open the configuration console go to integration tools > data import connections > ivanti neurons connector –device validate the test connection and proceed till the final screen 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 log in to itsm as an administrator click more and search for inbox business object and open it or from the configuration console, select email configuration > mail boxes select any protocol except imap4 set the following options to move to folder action to perform on processing success action to perform on processing error 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 log in to itsm as an administrator click more and search for inbox business object and open it or from the configuration console, select email configuration > mail boxes 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 log in to itsm as an administrator click more and search for inbox business object and open it or from the configuration console, select email configuration > mail boxes select the protocol as imap4 set the following options to move to folder action to perform on processing success action to perform on processing error enter some value in the archive mailbox name field 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 2021 2 release bug 845546 docid prmiijuu 3ahphzpuou4 when upgrading from 2021 1 to 2021 2, the application throws an error bug 811955 docid prmiijuu 3ahphzpuou4 request offerings do not display in alphabetical order when the global constant enableukenglishlocalization is set to true issue details bug 845546 bug 811955 issue request offerings do not display in alphabetical order when the global constant enableukenglishlocalization is set to true details log in to neurons for itsm open the configuration console > global constants > set the enableukenglishlocalization option as true open languages and add english uk culture if it is already added, remove and re add open the service desk console > request offerings the list of request offerings are in alphabetical order 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 2021 1 release bug 822605 docid prmiijuu 3ahphzpuou4 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 install 2021 1 on windows 2019 and sql 2019 provision report on ssrs 2019 select custom authentication for microsoft ssrs authentication type under service account , select use built in account and network service from the drop down list 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 2020 4 release bug 774221 docid prmiijuu 3ahphzpuou4 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 2020 3 release bug 739326 docid prmiijuu 3ahphzpuou4 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 setup a machine with window authentication download the ivanti service and asset manager installer and run as administrator select the product you want to install, that is ism, itam, or itxm 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 2020 2 release bug 697328 docid prmiijuu 3ahphzpuou4 after session timeout clicking on received notification it redirects to home page of ssm user in android and ios device bug 700504 docid prmiijuu 3ahphzpuou4 enable biometric authentication checkbox is not displaying in android device which has face id bug 701732 docid prmiijuu 3ahphzpuou4 while renewing session using password, it throws time stamp exception in android device bug 702094 docid prmiijuu 3ahphzpuou4 navigating to ivanti cloud workspace throws an error bug 703679 docid prmiijuu 3ahphzpuou4 translation japanese administrator chat configuration "seconds" is mistranslated as "2nd" bug 711161 docid prmiijuu 3ahphzpuou4 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 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 login to ism mobile app as ssm role in android or ios device wait for session timeout (configure session time out in admin ui) in desktop create an incident to get notification in the mobile device click on the newly received notification 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 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 install latest ism app in android device which has face id enabled in the device launch the app and access the url 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 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 login to ism using passowrd in android device wait for session timeout click on any workspace in the "you were logged out would you like to continue working?" pop up click the yes button 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 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 login to ism as administrator open ivanti cloud workspace 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 bug 703679 issue translation japanese administrator chat configuration "seconds" is mistranslated as "2nd" actual result login to the tenant as administrator go to the chat configuration workspace 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 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 log in to with the administrator role open the configuration console under security controls, select security and sessions under concurrent session, change the value of named user, privileged user, and non privileged user to 0 save the changes and refresh the page and re validate the values are changed now you can install 2020 2 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 2020 1 release bug 670687 docid prmiijuu 3ahphzpuou4 ism sso session renew fails for openid and saml okta for android device bug 670665 docid prmiijuu 3ahphzpuou4 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 bug docid prmiijuu 3ahphzpuou4670661 docid prmiijuu 3ahphzpuou4 ism sso after session timeout while renewing the session, application opens default external authentication login page in different browser in ios device bug docid prmiijuu 3ahphzpuou4636223 docid prmiijuu 3ahphzpuou4 ivanti cloud transfer blank record is getting created in hardware workspace for device bug 648276 docid prmiijuu 3ahphzpuou4 software asset creation has intermittent issues bug 671029 docid prmiijuu 3ahphzpuou4 username and roles are not visible as the text is in white color by default bug 431449 docid prmiijuu 3ahphzpuou4 on premise installation of metric server for the first time fails bug 678308 docid prmiijuu 3ahphzpuou4 on premise unable to login to tenant once scw completed for itam/ixm/ism clean windows authentication bug 676494 docid prmiijuu 3ahphzpuou4 default value of request offering text field set to current user function (primary phone) is not reflecting in service catalog issue details 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 ism android mobile app using openid or saml okta as external authentication provider wait for more than 1 minute click on any one of the workspace the message " you were logged out would you like to continue working? " is displayed 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 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 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 bug 636223 issue ivanti cloud transfer blank record is getting created in hardware workspace for device workaround no workaround is available 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 bug 671029 issue username and roles are not visible as the text is in white color by default details login to ism with admin role 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 bug 431449 issue on premise installation of metric server for the first time fails with db connection error steps install the latest 2020 1 build on windows 2014 r2 or any os 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 bug 678308 issue on premise unable to login to tenant once scw completed for itam/ixm/ism clean windows authentication steps set up itam clean windows authentication 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 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 login to the application as admin or service owner create a new request offering go to design request form and add a text field edit the field and set the default value to function and select current user primary phone from the drop down list publish the request offering and save 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 2019 3 release bug 636223 docid prmiijuu 3ahphzpuou4 ivanti cloud transfer blank record is getting created in hardware workspace for device bug 648276 docid prmiijuu 3ahphzpuou4 software asset creation has intermittent issues issue details bug 636223 issue ivanti cloud transfer blank record is getting created in hardware workspace for device workaround no workaround is available 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 2019 3 release bug 616198 docid prmiijuu 3ahphzpuou4 heat mobile app may crash when ios is upgraded from version 12 3 1 to 13 1 bug 610706 docid prmiijuu 3ahphzpuou4 post 2019 2 upgrade, audit history is not updated based on the relationship link for frs approval business object bug 615685 docid prmiijuu 3ahphzpuou4 ivanti cloud (uno) login app v1 & v2 integration does not work on ism tenant which has pre mct database bug 620323 docid prmiijuu 3ahphzpuou4 duplicate entries for workflow and task on creating a service request from a backup database bug 635269 docid prmiijuu 3ahphzpuou4 ip whitelisting shows "invalid ip" for all frsheat integration api requests when session key from "authenticate user" is used bug 644185 docid prmiijuu 3ahphzpuou4 the application throws an error when trying to link new and edit existing records in telemetry logging configuration tab in config db tenant bug 70551 docid prmiijuu 3ahphzpuou4 embedding content using iframe in html ui control is not working as expected bug 518404 docid prmiijuu 3ahphzpuou4 request offering is not getting created in the tenant, when imported via the release tool patch file bug 632194 docid prmiijuu 3ahphzpuou4 ip whitelisting integration trusted host is not allowing any ip to send/receive request, when the load balancer ip is configured issue details 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 bug 610706 issue post 2019 2 upgrade, audit history is not updated based on the relationship link for frs approval business object actual results upgrade to version 2019 2 log in to with admin user role open the configuration console navigate to business objects > service request > relationships > servicereqassociatedfrs approval select the relationship is audited check box save and exit create a service request that generates an approval, for example, mailbox quota request save the service request and exit re open the service request and click the audit history tab 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 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 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" 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 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 log in to a config db tenant of with admin user role open a tenant record and navigate to telemetry logging configuration tab 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 bug 70551 issue embedding content using iframe in html ui control is not working as expected bug 518404 issue request offering is not getting created in the tenant, when imported via the release tool patch file 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 2019 2 release release version 2019 1 and earlier given below is the list of known issues in 2019 1 and earlier releases bug 476581 docid prmiijuu 3ahphzpuou4 configuration fails if the app server cache does not have trusted host information of database server bug 492307 docid prmiijuu 3ahphzpuou4 on premise re branding is pending in the itam application as it still refers to "ivanti service manager" bug 492520 docid prmiijuu 3ahphzpuou4 ssrs configuration with custom authentication and domain credentials may throw the 1326 error sometimes bug 492643 docid prmiijuu 3ahphzpuou4 ops console is not re branded for ivanti, it still shows heat brand names bug 333924 docid prmiijuu 3ahphzpuou4 configure openidconnect auth provider for ms azure ad bug 341934 docid prmiijuu 3ahphzpuou4 \[request for information] report distribution option "download" bug 505677 docid prmiijuu 3ahphzpuou4 multiple records are displayed on the home page search for a single request bug 502699 docid prmiijuu 3ahphzpuou4 ssrs configuration fails while trying to add the provision report in scw bug 504840 docid prmiijuu 3ahphzpuou4 there is a browser compatibility issue for self service mobile, in the ui price list/ cost panel showing zero(0) bug 383101 docid prmiijuu 3ahphzpuou4 japanese characters are shown as ? in the frs surveyanswer bug 359153 docid prmiijuu 3ahphzpuou4 logout from the self service mobile ui takes users to the ism login instead of the auth provider login bug 508376 docid prmiijuu 3ahphzpuou4 "frontrange solution" installer certificate is not trusted by microsoft anymore bug 519086 docid prmiijuu 3ahphzpuou4 upgrading 2019 1 directly from 2018 1 1 does not work bug 522220 docid prmiijuu 3ahphzpuou4 unable to create new ci due to the asset processor configuration bug 525479 docid prmiijuu 3ahphzpuou4 login page not loading by throwing timestamp error while internal services user is disabled bug 522214 docid prmiijuu 3ahphzpuou4 config db/tenant db metadata version field left blank during upgrade/install bug 431449 docid prmiijuu 3ahphzpuou4 on premise installation of metric server for the first time fails bug 526262 docid prmiijuu 3ahphzpuou4 upgraded ism 2018 3 1 to 2019 1 and post upgrade accessing the below workspaces as licensemanager role throws exception bug 485595 docid prmiijuu 3ahphzpuou4 the sting "self" is unloc shown under self service user my items > benefits package claim bug 235039 docid prmiijuu 3ahphzpuou4 the service request review and submit page displays the incorrect employee details if the login ids are similar bug 533210 docid prmiijuu 3ahphzpuou4 2019 1 premise installer seems to silently exit or crash after installing one of the pre req modules bug 576301 docid prmiijuu 3ahphzpuou4 errors on form and grid for bo authenticationprincipal when upgrading from 2018 3 1 to 2019 1 0 premise issue details 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) 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 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 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 bug 333924 issue {"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" "andrejs\@synergy lt","upn" "andrejs\@synergy lt","uti" "zmsljpcsleqe3kbp8qkdaa","ver" "1 0"} 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 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 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 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 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 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 login as an admin go to the request offerings workspace and import a rof file, publish, and save switch to the self service (old ui) role go to service catalog and open this offering select desktop type, then a desktop and a quantity notice that the price list looks correct for the selection 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 switch to the self service mobile ui go to service catalog and open this offering select desktop type, then a desktop and a quantity observe that the price list looks correct for the selection 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 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/ open frs surveyanswer# go to field questiontext or answertext change type to unicode, 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 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 set up the environment with saml authentication set up a logout url as seen in the screenshot log in as admin with the role of self service mobile 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 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 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 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 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 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 pre requisite this issue can only be reproduced on ootb(ixm) so to reproduce ootb(ixm) environment is required login to the application 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 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 login to ism as the admin role open employee workspace and search for "internal services" user 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 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 install & upgrade any of the above application 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 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 install the latest 2018 1 1 build on windows 2014 r2 or any os 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 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 bug 485595 issue the sting "self" is unloc shown under self service user my items > benefits package claim steps to reproduce log in to ism and change the role to self service user open the my items workspace select benefits package claim 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 "自我" 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 bug 533210 issue 2019 1 premise installer seems to silently exit or crash after installing one of the pre req modules steps to reproduce run installer exe as an admin click install to installer pre reqs a dialog box will appear, "extracting ivanti service asset manager msi follow the wizard to where you select sm / am / both 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 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 close scw restore the application db back to 2018 3 1 go to the adminui and import the “globalid contract identity metadatapatch” package re launch scw 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 after installing 2019 1 0 and before walking through the scw, launch adminui import the “globalid contract identity metadatapatch” package walk through scw and the customer should be able to upgrade db