Troubleshooting
If you have problems with your installation or deployment, check this section first.
Error Messages
•Login Errors
•Backup Error
Login Errors
Error Message
Error upon executing commands: The following error occurred when authenticating with the tenant <tenantUrl>.
Status: TenantNotFoundPossible Cause
The tenant that you specified is invalid.
Solution
Ensure that the tenant URL and tenant ID are valid.
Error Message
Error upon executing commands: The following error occurred when authenticating with the tenant <tenantUrl>.
Status: AccessDeniedPossible Cause
You entered an invalid user name or password.
Solution
Ensure that the user name and password are valid.
Error Message
Error upon executing commands: The following error occurred when authenticating with the tenant APPSERVER.
Status: InvalidRolePossible Cause
You do not have administrator rights.
Solution
Ensure that you have administrator rights. See About Roles.
Error Message
Error upon executing commands: Could not establish trust relationship for the SSL/TLS secure channel with authority '<IP_address>'.Possible Cause
You did not connect to the Service and Asset Manager application server using HTTPS.
Solution
Configure the Service and Asset Manager application server to use SSL. See Optional SSL Configuration. Enter the URL for the Service and Asset Manager application server that is configured to use SSL.
Error Message
Failed to execute applyPatch: The remote server returned an unexpected response: (400) Bad Request.Possible Cause
The database version is not up to date.
Solution
If the system table upgrade fails, review the log files and fix any metadata issues. Then upgrade the system table.
Problem
Cannot view the login dialog box. A message says:
Please use your subdomain when accessing the application, for example https://yourname.saas.heatsoftware.com
Possible Cause
The web.config file parameter "RequireTenantIdInURL" value is set to true.
Solution
1.Go to C:\Program Files\HEAT Software\HEAT\AppServer\ and open the web.config file.
2.Search for the parameter "RequireTenantIdInURL" and change its value to false.
3.Save and close the web.config file.
Upgrade Errors
Problem
After upgrading to the latest version of Service and Asset Manager, the list of tenants in the Operations Console is empty.
Possible Cause
During the upgrade, the system updated the connection strings for the landscape with the incorrect name for the data source.
Solution
In the Operations Console, edit each landscape to update the data source to the correct database server name. See Upgrading Service and Asset Manager from an Earlier Release for more information on how to do this.
Error Message
Failed to execute applyPatch: The request channel timed out while waiting for a reply after 00:59:59.7741622. Increase the timeout value passed to the call to request or increase the SendTimeout value on the binding. The time allotted to this operation may have been a portion of a longer timeout.
Possible Cause
By default, the upgrade tool is set to wait for one hour for a response from the Service and Asset Manager application server. This message indicates that the Service and Asset Manager application server is still applying the patch or package. The patch can be completed at any time.
Solution
Check the status of the upgrade tool later by looking at the patch log in the Configuration Database.
Backup Error
Error Message
No database backup location specified in configuration database. Please contact support.
Backup failed for Server 'db_server'.Possible Cause
•The backup location is not set in the configuration database.
•The backup failed to execute because of permissions issues.
Solution
Ensure that you have set the backup location and ensure that you have the correct permissions.
Database Migration Errors
Error Message
Error during metadata commit operation: System.Exception: The following errors were encountered when synchronizing the schema...:
Possible Cause
This indicates a serious problem in business object metadata and is a synchronization schema error. The system cannot synchronize the database schema change with the business object definition. If you get this error, the system usually stops upgrading the metadata.
Solution
If this happens in your production environment, restore the database from a backup that was made before the upgrade. Then contact Ivanti support so that they can look into the error. See How to Contact Us.
Error Message
Error during metadata commit operation: DataLayer.SaaSDbException: Invalid object name 'Frs_ITFM_Account_Status'. ---> System.Data.SqlClient.SqlException: Invalid object name 'Frs_ITFM_Account_Status'.
Possible Cause
Part of the database is corrupt.
Solution
Contact Ivanti Software support. See How to Contact Us. They may suggest that you restore the database from a backup that was made before the upgrade.
Error Message
Error during metadata commit operation: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
Possible Cause
Part of the database is corrupt.
Solution
Contact Ivanti Software support. See How to Contact Us. They may suggest that you restore the database from a backup that was made before the upgrade.
Microsoft SQL Execution Errors
Error Message
An error occurred when applying patch named <some_filename>.sql in package <some_package>.MetadataPackage to tenant <tenantUrl>. Unable to execute SQL due to Invalid column name 'IPCMUrlPort'.: update FRS_IPCM_Integration set IPCMUrlPort = 2323 where IPCMUrlPort is null Unable to execute SQL due to Invalid column name 'IPCMUrl'.: update FRS_IPCM_Integration set IPCMUrl = 'http://' + IPCMServerHost + ':' + convert(varchar(6), IPCMUrlPort) where IPCMUrl is null and IPCMServerHost is not null
Possible Cause
An embedded Microsoft SQL statement is corrupt.
Solution
Review the Microsoft SQL statements.
Update Key Not Found Warnings
Error Message – Business Object
Error during metadata update operation. MetadataType: BusinessObject, ID: Frs_AuthenticationProvider# SaaS.StandardizedMetadata.UpdateKeyNotFoundException: Update key not found: key = Rel2s at SaaS.StandardizedMetadata.MetadataExtensions.Patch(XElement element, XElement differences) at DataLayer.MetadataPatch.ApplyGroupedActions(IMetadataProvider provider, ISessionContext sessionContext, IEnumerable`1 definitionGroup) in c:\depot\Eng\SaaS\main\Platform\AppServer\MetadataServices\MetadataPatch.cs:line 1034
Possible Cause
There is a problem updating the metadata and the system did not update the business object.
Solution
Review the business object to make sure it was updated.
Error Message – Form
Error during metadata update operation. MetadataType: Form, ID: Task.WorkOrder System.Exception: Update key not found: key = Details at SaaS.StandardizedMetadata.MetadataExtensions.Patch(XElement element, XElement differences) in c:\depot\Eng\SaaS\main\Platform\StandardizedMetadata\MetadataExtensions.cs:line 1377 at SaaS.StandardizedMetadata.MetadataExtensions.Patch(XElement element, XElement differences) in c:\depot\Eng\SaaS\main\Platform\StandardizedMetadata\MetadataExtensions.cs:line 1359 at DataLayer.MetadataPatch.ApplyGroupedActions(IMetadataProvider provider, ISessionContext sessionContext, IEnumerable`1 definitionGroup) in c:\depot\Eng\SaaS\main\Platform\AppServer\MetadataServices\MetadataPatch.cs:line 1016
Error Message – Dashboard
Error during metadata update operation. MetadataType: Dashboard, ID: 8e2cce05-c593-4545-bf4d-5f719a9bd5a5 System.Exception: Update key not found: key = OLA Target Compliance ( e94a602f-959e-4cf1-9c07-be4d5eb0da68 ) at SaaS.StandardizedMetadata.MetadataExtensions.Patch(XElement element, XElement differences) in c:\depot\Eng\SaaS\main\Platform\StandardizedMetadata\MetadataExtensions.cs:line 1377 at SaaS.StandardizedMetadata.MetadataExtensions.Patch(XElement element, XElement differences) in c:\depot\Eng\SaaS\main\Platform\StandardizedMetadata\MetadataExtensions.cs:line 1359 at DataLayer.MetadataPatch.ApplyGroupedActions(IMetadataProvider provider, ISessionContext sessionContext, IEnumerable`1 definitionGroup) in c:\depot\Eng\SaaS\main\Platform\AppServer\MetadataServices\MetadataPatch.cs:line 1016
Error Message – Validation Data
Error during metadata update operation. MetadataType: ValidationData, ID: Justification# System.Exception: Update key not found: key = Justification#_culture#pt-BR at SaaS.StandardizedMetadata.MetadataExtensions.Patch(XElement element, XElement differences) in c:\depot\Eng\SaaS\main\Platform\StandardizedMetadata\MetadataExtensions.cs:line 1377 at SaaS.StandardizedMetadata.MetadataExtensions.Patch(XElement element, XElement differences) in c:\depot\Eng\SaaS\main\Platform\StandardizedMetadata\MetadataExtensions.cs:line 1359 at SaaS.StandardizedMetadata.MetadataExtensions.Patch(XElement element, XElement differences) in c:\depot\Eng\SaaS\main\Platform\StandardizedMetadata\MetadataExtensions.cs:line 1359 at DataLayer.MetadataPatch.ApplyGroupedActions(IMetadataProvider provider, ISessionContext sessionContext, IEnumerable`1 definitionGroup) in c:\depot\Eng\SaaS\main\Platform\AppServer\MetadataServices\MetadataPatch.cs:line 1016
Error Message – Rule
Error during metadata update operation. MetadataType: Rule, ID: Incident# System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary. at System.Collections.Generic.Dictionary`2.get_Item(TKey key) at SaaS.StandardizedMetadata.MetadataExtensions.Patch(XElement element, XElement differences) in c:\depot\Eng\SaaS\main\Platform\StandardizedMetadata\MetadataExtensions.cs:line 1386 at SaaS.StandardizedMetadata.MetadataExtensions.Patch(XElement element, XElement differences) in c:\depot\Eng\SaaS\main\Platform\StandardizedMetadata\MetadataExtensions.cs:line 1359 at DataLayer.MetadataPatch.ApplyGroupedActions(IMetadataProvider provider, ISessionContext sessionContext, IEnumerable`1 definitionGroup) in c:\depot\Eng\SaaS\main\Platform\AppServer\MetadataServices\MetadataPatch.cs:line 1016
Possible Cause
There is a problem updating the metadata.
Solution
You do not need to do anything.
Workflow Warnings
Error Messages
Error during metadata delete operation. MetadataType: Workflow, ID: 69d31c7248b54f92bc1bff415cd29e0f System.Exception: Could not deactivate workflow definition RecId: 69d31c7248b54f92bc1bff415cd29e0f ---> System.Exception: Error updating existing active workflow definition to inactive, RecId 69d31c7248b54f92bc1bff415cd29e0f at SaaS.WebUI.WorkflowMetadataServices.WorkflowMetadataUpdate.Delete(MetadataType metadataType, String id) in c:\depot\Eng\SaaS\main\Platform\AppServer\BPE\src\WorkflowMetadataServices.cs:line 409 Error during metadata insert operation. MetadataType: Workflow, ID: 871d9466c4754fa19ffb03de179cd057 System.Exception: Inactive definition exists with the same RecId: Name:LDAP Sync_LC_133k134k135k13k14k15k16k17k18k19k, ObjectType:ScheduleEntry, Definition RecId 871d9466c4754fa19ffb03de179cd057 at SaaS.WebUI.WorkflowMetadataServices.WorkflowMetadataUpdate.CreateWorkflowDefinition(String name, String objectType, String defRecId, String typeRecId, XElement workflow) at SaaS.WebUI.WorkflowMetadataServices.WorkflowMetadataUpdate.Insert(MetadataType metadataType, XElement workflow) at SaaS.StandardizedMetadata.MetadataProvidersContainer.Insert(MetadataType metadataType, XElement definition) at DataLayer.MetadataPatch.ApplyGroupedActions(IMetadataProvider provider, ISessionContext sessionContext, IEnumerable`1 definitionGroup)
Possible Cause
There is a problem updating the workflows.
Solution
You do not need to do anything.
Software Problems
•Application redirects the user from http://localhost/HEAT to https://localhost on the machine where SSL is not setup.
Problem
Discovery cannot detect assets on the network.
Possible Causes
•Service Center Configuration Manager (SCCM) service is stuck in starting mode.
•You are using a domain account for running all Service and Asset Manager services but the domain account has insufficient rights.
Solution
Use your local system account and restart Service and Asset Manager.
Problem
System cannot search.
Possible Cause
Full-text search is disabled.
Solution
Enable full-text search. See Enabling Full-Text Search.
Problem
The Service and Asset Manager demo database does not load properly.
Possible Cause
Full-text search is disabled.
Solution
Enable full-text search. See Enabling Full-Text Search.
Problem
Web servers do not work correctly.
Possible Cause
In multi-server environments, each Service and Asset Manager web server must meet the system requirements.
Solution
Refer to the System Requirements and Compatibility Matrix for Service and Asset Managerfor more information.
Problem
Provision report now returns an exception: Cannot Decrypt the Symmetric Key.
Possible Cause
The Service and Asset Manager reporting server cannot use the symmetric key to access the data from the report server database.
Solution
1.Click OK, but do not close the System Configuration Wizard.
2.Start the Reporting Services Configuration Manager and connect to your Microsoft SRSS instance.
3.Select Encryption Keys from the list in the left panel.
4.Click Delete and then click Yes at the confirmation message.
5.Return to the wizard and click Provision Report Now.
Problem
Dashboard and report controls (such as charting, pivoting, and copy/paste) and the Service Catalog attachment control do not work.
Possible Cause
Browser does not have, or does not support, Adobe Flash.
Solution
•Install Adobe Flash. Go to https://get.adobe.com/flashplayer/.
•If your current browser does not support Adobe Flash, upgrade the browser.
Problem
Cannot download or edit reports in Chrome.
Possible Cause
The Chrome ClickOnce extension is not installed.
Solution
Install the ClickOnce extension for Chrome. Navigate to https://chrome.google.com/webstore/detail/eeifaoomkminpbeebjdmdojbhmagnncl# and download the extension.
Problem
Cannot download or edit reports in Firefox.
Possible Cause
The Firefox Microsoft .NET framework assistant extension is not installed.
Solution
Install the Microsoft .NET framework assistant extension. Navigate to https://addons.mozilla.org/en-US/firefox/addon/9449 to download the extension.
Problem
Cannot download files or run controls in Internet Explorer.
Possible Cause
Scripting is disabled.
Solution
Set properties in Internet Explorer as follows:
1.Go to the Tools > Internet Options > Security > Custom level page.
2.Set the following options to enable:
•Run ActiveX controls and plug-ins
•File download
•Scripting > Active scripting
Problem
Cannot open websites in Internet Explorer.
Possible Cause
You have not set Service and Asset Manager to be a trusted site.
Solution
Set properties in Internet Explorer as follows:
1.Go to the Tools > Internet Options > Security page.
2.Highlight Trusted sites and click Sites.
3.Click Add.
Problem
Logging into a tenant using Internet Explorer fails.
Internet Explorer displays this message: You cannot login to the system now. Please contact your administrator. Additional information is available in the logs.
Possible Cause
Internet Explorer does not accept cookies if the host name of the DNS server or the server NetBIOS names contain an underscore '_'.
Solution
•Change the host name of your DNS server or its NetBIOS names so they no longer contain an underscore '_'
•Use a Chrome or Firefox browser.
Problem
Unable to use integrated components, such as Voice.
Possible Cause
You must use the Microsoft Windows operating system when you use integrated components.
Solution
Change to the Microsoft Windows operating system. Refer to the System Requirements and Compatibility Matrix for Service and Asset Managerfor more information.
Problem
When trying to access the Configuration Database, the application redirects the user from http://localhost/HEAT to https://localhost on the machine where SSL is not setup.
Possible Cause
There is a known limitation in the 2018.3.1 release with respect to FedRamp requirements related to the URL redirect configuration.
Solution
To resolve this, there is a need to update an entry in the web.config file. Set the parameter highlighted below to ‘false’ and restart IIS. Once the process is completed, try to access Configuration Database.
</rule>
<rule name="HTTP to HTTPS redirect" stopProcessing="true">
<match url="(.*)">
</match>
<conditions>
<add input="" pattern="^localhost$" negate="true">
</add>
<add input="" pattern="off" ignoreCase="true">
</add>
</conditions>
<action type="Redirect" url="https:///{R:1}" redirectType="Permanent">
</action>
</rule>
