Data Platform Error Codes
This section lists and describes the error codes you may encounter when administering Data Platform.
Error codes are grouped by component:
Publish Component Error Codes
Find the error text in the table below to learn more about it.
| Error Type | Error Text | When can it occur? | Resolution | Category/Stage |
|---|---|---|---|---|
| Informational to Fatal | Error occurred. System.Exception: Updater: Expecting 0. [return:2] [Error : No such as Action.[ERROR]] at BDNA.Agent.NBR.FlowItem.SynUpdateFiles.ExecuteFlowItem() 2024-02-12 06:02:28,553 0 ERROR System.Exception: Updater: Expecting 0. [return:2] [Error : No such as Action.[ERROR]] at BDNA.Agent.NBR.FlowItem.SynUpdateFiles.ExecuteFlowItem() at BDNA.Agent.NBR.FlowItem.BaseFlowItem.Execute() | Occurs if there are any exceptions while executing database store procedures. This includes import, mapping and publish stages. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | Data at the root level is invalid. Line 1, position 1. | While importing from xsf file, there are some scenarios where the xml import file within the xsf file is invalid. This error occurs when the import file being provided is invalid. | This error is caused when the xml import file inside the XSF being provided is invalid. Re-evaluate and try importing again. In Case the import file is in correct format, Please contact Flexera with the logs and relevant details. | XSF |
| Informational | No *.xsf files found under <Configured Path> | When process is created to import from xsf file, we configure the input folder location from where the file is picked up for the imports. If this folder is empty when the process is run, this error occurs. | Check the import folder (configured in the process) has the import file and then restart the task. | XSF |
| Fatal | DISC_GUID create temp index DISC_GUID_GID | When import is run, the data gets dumped into publish database which is then used in for the report. In order to import effectively, we use something called indexing, that help process large data. This error occurs if there are any issue with the indexing of a table. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | ERROR Line <Exception Details> insert DISC_GUID <Exception details> | While importing, there are times when the product faces issues in inserting data into a database table. This issue occurs when that happens. This occurs usually due to a faulty input value, or a mismatched value. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | ERROR ENABLE_CAT_TABLES_CONSTRAINTS Line | While importing, there are some tables which are created dynamically. Each time few constraints needs to be set for the tables. This occurs when one such constraints setting fails. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | ERROR PUBLISH_MATCH_INV_TASK Line | Error occurred due to internal issue | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | ERROR Line <Exception Details> insert into DISC_HOSTS <Exception details> | When one imports, there are times when the product faces issues in inserting data into a database table. This issue occurs when that happens. This occurs usually due to a faulty input value, or a mismatched value. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | ERROR Line <Exception Details> DISC_ALL_OS create temp index DISC_HOSTS_T <Exception details> | When one import is run, the data gets dumped into publish database which is then used in for the report. In order to import effectively, we use something called indexing, that help process large data. This error occurs if there are any issue with the indexing of a table. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | task_id cannot be NULL, please provide valid task_id | Every process has a task id associated with it. When an import process is triggered, this task id is automatically passed to the underlying logic. If for some reason, this is not passed, maybe due to faulty process creation, this error occurs. | Try to remove the process in question. And add it again. If this doesn't fix the issue, make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | SUBSCRIPTION_ID is null | This possibly occurs when subscription ID is not being passed or is invalid. | Check with the process configurations and if possible the data being imported. Contact Flexera technical support with the details | Publish |
| Fatal | failed to get name_prefix,task_id | Every process has a task id associated with it. When an import process is triggered, this task id/inventory id is automatically passed to the underlying logic. If for some reason, this is not passed, maybe due to faulty process creation, this error occurs. | update the extractor file with valid prefix and try again. | Publish |
| Fatal | ERROR ENABLE_CAT_TABLES_CONSTRAINTS Line | While importing, there are some tables which are created dynamically. Each time few constraints needs to be set for the tables. This occurs when one such constraints setting fails. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | Name Prefix not properly fetched | Every import configuration comes with an extractor. This file contains mapping of different tables along with the prefix. This error occurs due if this extractor has some errors or not configured properly. | Update the extractor file with valid prefix and try again. | Publish |
| Fatal | ERROR Line <Exception Details> CREATE [VW_MATCH_HOST_SW_INSTANCE_ | As a part of publish process, the logic creates some database elements such as VW_MATCH_HOST_SW_INSTANCE view. This error occurs if the creation of the view fails. This occurs if either inventory id is not passed properly or something similar. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | ERROR Line <Exception Details> error creating TMP_CAT_SW_REL table | As a part of publish process, the logic creates some database elements such as temporary tables and views. This error occurs if the creation of such elements fails. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | ERROR Line <Exception Details> error creating TMP_MAJOR_VERSION table | As a part of publish process, the logic creates some database elements such as temporary tables and views. This error occurs if the creation of such elements fails. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | ERROR Line <Exception Details> failed to create TMP_MAJOR_VERSION_IDX on TMP_MAJOR_VERSION | When one import is run, the data gets dumped into publish database which is then used in for the report. In order to import effectively, we use something called indexing, that help process large data. This error occurs if there are any issue with the indexing of a table. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | ERROR Line <Exception Details> error creating TMP_CAT_SW_REL2 table | As a part of publish process, the logic creates some database elements such as temporary tables and views. This error occurs if the creation of such elements fails. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | ERROR Line <Exception Details> failed to create TMP_CAT_SW_REL2 on TMP_CAT_SW_REL2 | As a part of publish process, the logic creates some database elements such as temporary tables and views. This error occurs if the creation of such elements fails. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | ERROR Line <Exception Details> error creating TMP_TAX table | As a part of publish process, the logic creates some database elements such as temporary tables and views. This error occurs if the creation of such elements fails. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | ERROR Line <Exception Details> error creating TMP_PROD table | As a part of publish process, the logic creates some database elements such as temporary tables and views. This error occurs if the creation of such elements fails. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | ERROR Line <Exception Details> error creating TMP_PR table | As a part of publish process, the logic creates some database elements such as temporary tables and views. This error occurs if the creation of such elements fails. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | ERROR Line <Exception Details> error Inserting Mapped but no subscription for Manufacturer (TMP_PR) | When one imports, there are times when the product faces issues in inserting data into a database table. This issue occurs when that happens. This occurs usually due to a faulty input value, or a mismatched value. | Check with the process configurations and if possible the data being imported. Contact Flexera technical support with the details | Publish |
| Fatal | ERROR Line <Exception Details> error Inserting Mapped but no subscription for Taxonomy (TMP_PR) | When one imports, there are times when the product faces issues in inserting data into a database table. This issue occurs when that happens. This occurs usually due to a faulty input value, or a mismatched value. | Check with the process configurations and if possible the data being imported. Contact Flexera technical support with the details | Publish |
| Fatal | ERROR Line <Exception Details> error Inserting Mapped but no subscription for SW Product (TMP_PR) | When one imports, there are times when the product faces issues in inserting data into a database table. This issue occurs when that happens. This occurs usually due to a faulty input value, or a mismatched value. | Check with the process configurations and if possible the data being imported. Contact Flexera technical support with the details | Publish |
| Fatal | ERROR Line <Exception Details> insert MATCH_HOST_SW_PROD_ALL | When one imports, there are times when the product faces issues in inserting data into a database table. This issue occurs when that happens. This occurs usually due to a faulty input value, or a mismatched value. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | ERROR Line <Exception Details> UPDATE L3 | As a part of publish process, the logic creates some database elements such as temporary tables and views. This error occurs if the creation of such elements fails. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | ERROR Line <Exception Details> MATCH_HOST_SW_PROD_DET create index MATCH_HOST_SW_PROD_ALL_SW_IDX | When one import is run, the data gets dumped into publish database which is then used in for the report. In order to import effectively, we use something called indexing, that help process large data. This error occurs if there are any issue with the indexing of a table. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | ERROR Line <Exception Details> create TMP_AR_ADDREMOVE | As a part of publish process, the logic creates some database elements such as temporary tables and views. This error occurs if the creation of such elements fails. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | ERROR ENABLE_CAT_TABLES_CONSTRAINTS Line | As a part of publish process, the logic creates some database elements such as tables and constraints related to them. This error occurs when there is a technical error while doing the same. | Make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | Export normalize statistics file error: | When the normalize results are ready, Data Platform exports it to a file such as exporting unmatched data etc. If there are any issues related to the operation on files, this error occurs. | Clean up the folder before running normalize. And Ensure that the directory to which the export is configured to has been given access to the service account operating Data Platform. | Publish |
| Fatal | Can't found subscription_id | This occurs when Data Platform is unable find the subscription details. | Contact Flexera technical support with the details of the exception. | Publish |
| Fatal | Name Prefix not properly fetched | An error occurred in Data Platform on the database side. This occurs if a prefix fetched is empty or invalid. | Contact Flexera technical support with the details of the exception. | Publish |
| Fatal | Can’t get publish schema name. InventoryID = | An error occurred in Data Platform on the database side. This occurs if a prefix fetched is empty or invalid. | Contact Flexera technical support with the details of the exception. | Publish |
| Fatal | An error has occurred during Insert, Retry | An error occurred while pushing data to the import table in Data platform. This error occurs if there are some error related to the data being imported. | Recheck the data being imported based on the data error details and retry. | Publish |
| Fatal | DISC_ALL_OS create temp index DISC_HOSTS_T | As a part of publish process, the logic creates some database elements such as temporary tables and views. This error occurs if the creation of such elements fails. | Make sure that the version is up to date. If an update does not fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | Write data to database error: | As a part of publish process, the logic creates some database elements such as temporary tables and views. This error occurs if the creation of such elements fails. | Make sure that the version is up to date. If an update does not fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | Invalid column name | As a part of publish process, the logic creates some database elements such as temporary tables and views. This error occurs if the creation of such elements fails. | Make sure that the version is up to date. If an update does not fix the issue, contact Flexera technical support with the details. | Publish |
| Fatal | ERROR ENABLE_CAT_TABLES_CONSTRAINTS Line | As a part of publish process, the logic creates some database elements such as temporary tables and views. This error occurs if the creation of such elements fails. | Make sure that the version is up to date. If an update does not fix the issue, contact Flexera technical support with the details. | Publish |
Patch Update Component Error Codes
Find the error text in the table below to learn more about it.
| Error Type | Error Text | When can it occur? | Resolution | Category/Stage |
|---|---|---|---|---|
| Informational | Could not read version information from "<LOCATION>patchsetversion.txt". File doesn’t exist. | Error occurs while Technopedia synchronization is running before patch upgrade in Data Platform | No action is required | none |
| Fatal | System.NullReferenceException: Object reference not set to an instance of an object. at bms.Server.Service.SynchronizeService.GetPatchsetMd5FromCache(Dictionary`2 md5Dict, String patchPath, String workFolder) | The exception occurs within the method, indicating that the parameter is null. This suggests that the dictionary object you are passing to the method is not initialized i.e it's null. | Should ensure that the dictionary is properly initialized before passing it to the method. | none |
| Fatal | System.Exception: Specified file does not exist. at BDNA.Agent.NBR.FlowItem.AddNoramlizeTask.MoveFileToWorkFolder(ZipFileSource zipFileSource) at BDNA.Agent.NBR.FlowItem.AddNoramlizeTask.CreateMashupOrPOProcessTask(BaseJobProcess process, InventoryCfg inventoryCfg) at BDNA.Agent.NBR.FlowItem.AddNoramlizeTask.CreateProcessTask(BaseJobProcess baseJobProcess, InventoryCfg inventoryCfg) at BDNA.Agent.NBR.FlowItem.AddNoramlizeTask.ExecuteFlowItem() at BDNA.Agent.NBR.FlowItem.BaseFlowItem.Execute() | The file path provided to the method might be (incorrect \incomplete) or If multiple processes or threads are accessing the file concurrently, it's possible that one process deletes or moves the file while another process is still trying to access it. | Verify that the file exists at the specified path before attempting to move it. You can use file existence checks to ensure the file is available before performing operations on it. | none |
Import Component Error Codes
Find the error text in the table below to learn more about it.
| Error Type | Error Text | When can it occur? | Resolution | Category/Stage |
|---|---|---|---|---|
| Fatal | Exception: Get ILMT Connection token failed. | This exception will occur while testing ILMT connection. If the entered API URL, UserName, Password in Admin Console UI are incorrect, we throw this exception. | Check Username and Password, API URL entered. This error can also occur in the Admin Console UI component. | Import, Admin Console UI |
| Informational | ERROR ------> Parse Exception Newtonsoft.Json.JsonReaderException: Error reading JObject from JsonReader. Current JsonReader item is not an object: Null. Path '', line 1, position 4. | Exception while parsing the ILMT response during Normalize Import process. | Check the ILMT response, Contact Flexera support to identify the problematic record from ILMT response | Import |
| Informational | ERROR ------> Parse Exception Flatten JSON | Exception while parsing the ILMT response during Normalize Import process. | Check the ILMT response, Contact Flexera support to identify the problematic record from ILMT response | Import |
| Fatal | Request to "API URL" failed with status code "Status code" and content: "API response content | This exception could occur while getting ILMT token, BigFix about, or other status calls | Check if the logged API URL is available and accessible | Import |
| Informational | JSON handling error exceed max count. | Exception while reading the API response JSON data during Normalize Import process. | Check the ILMT response, Contact Flexera support to identify the problematic record from ILMT response | Import |
| Informational | ERROR [BMCFlow] [EndpointClient] [ByTypeParser] parse response in json failed. Cannot deserialize the current JSON array (e.g. [1,2,3]) into type 'BDNA.API.BMC.ApiVersion1_0.Response.ActionResponse' because the type requires a JSON object (e.g. {"name":"value"}) to deserialize correctly. To fix this error either change the JSON to a JSON object (e.g. {"name":"value"}) or change the deserialized type to an array or a type that implements a collection interface (e.g. ICollection, IList) like List<T> that can be deserialized from a JSON array. JsonArrayAttribute can also be added to the type to force it to deserialize from a JSON array. | Exception while deserializing the BMC response during Normalize Import process. This could occur if a field in the API response is of array type and expected is string type. | Check the BMC response, Contact Flexera support to identify the problematic record from BMC response | Import |
| Fatal | ERROR [BMCFlow] [EndpointClient] [Request] request endpoint failed. BDNA.Common.API.HttpResponseException: service response an error for the request ---> BDNA.Common.API.FrontException: MessageStatus: {"StatusCode":400,"ReasonPhrase":"Bad Request"} MessageBody: { "code": 400, "message": "Invalid token", "transient": false } | Invalid API token while testing the connection in Admin Console UI | Check Token, API URL entered. This error can also occur in the Admin Console UI component. | Import, Admin Console UI |
| Fatal | no result retrieved from GetHostAssetCount request | While testing connection we check number of assets, If request fails here, it throws exception | Import | |
| Fatal | BMCAPIVersions is not supported. | While testing the connection or during import we check if the BMC version is supported. We throw this exception when in case of unsupported BMC version | Check Flexera DataPlatform BMC datasource documentation for supported versions list and take action. This error can also occur in the Admin Console UI component. | Import, Admin Console UI |
| Fatal | Invalid input folder path | This exception occurs while testing the Tanium connection. If the provided input path is not a valid path, We throw this exception. | Tanium input JSON path is invalid, check the input path. | Import |
| Fatal | No JSON files in input folder | This exception occurs while testing the Tanium connection. If there no input files in input folder, we throw this exception. | Please check for JSON input files in input folder. | Import |
| Fatal | Check file name for " + wrongfilenames + " from instruction guide or invalid file | This exception occurs while testing the Tanium connection. If the input files inside input folder doesn't match with predefined names, we throw this exception. | Please check Flexera DataPlatform Tanium documentation for list of predefined JSON input file names | Import |
| Fatal | Not enough permission to access input folder | This exception occurs while testing the Tanium connection. If the provided input path is not accessible, we throw this exception. | Tanium input JSON path is not accessible, check if user is having permission to access the input folder. | Import |
| Fatal | get InventoryId failed with ProcessId: | Every process has a InventoryId associated with it. When an import process is triggered, this task id is automatically passed to the underlying logic. If for some reason, this is not passed, maybe due to faulty process creation, this error occurs. | Try to remove the process in question. And add it again. If this doesn't fix the issue, make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Import |
| Fatal | get TaskId failed with ProcessId: | Every process has a task id associated with it. When an import process is triggered, this task id is automatically passed to the underlying logic. If for some reason, this is not passed, maybe due to faulty process creation, this error occurs. | Try to remove the process in question. And add it again. If this doesn't fix the issue, make sure that the version is up to date. And if the update didn’t fix the issue, contact Flexera technical support with the details. | Import |
| Fatal | the path is not accessible | This error occurs while importing data from ServiceNow datasource. We throw this exception when Export folder of ServiceNow is not accessible. | Check if Export folder of ServiceNow is accessible | Import |
| Fatal | endpoint execute failed. and fallback is not success. fallback is not execute as the rules is not resolved. | This error occurs while importing data from ServiceNow datasource. We try to get status code from Import, can_inport, export, can_export endpoints and check if mid server is accessible. If any of these pre-checks fails during import process we throw this exception | Check the error, and make necessary changes in ServiceNow environment or mid-server configuration. If it's not resolved yet, Please contact Flexera Support | Import |
| Informational | source parse failed. possible error section from response in raw is -----> | Exception while parsing the API response during Normalize Import process. | Check the API response, Contact Flexera support to identify the problematic record from API response | Import |
| Fatal | ERROR [SNOWFlow] [DownloadFlowHandler] processing ServiceNow [export] failed. System.Exception: ServiceNow status: [can_export] API return:. exception in [filter list] not catch(ed) from message. [errors] = 0. [catch list]=[]. [config list]=["TimeoutException","HttpRequestException","\"StatusCode\":50"]. [message list]=SYSTEM.EXCEPTION [SUCCESS] IS NOT READ FROM SERVICENOW [CAN_EXPORT]. RESPONSE: {"MESSAGE":"A NEW EXPORT CANNOT BE STARTED. PLEASE CHECK APPLICATION LOGS FOR DETAILS.","STATUS":FALSE} | This exception occurs in the import step, if can_export, export, can_import, import APIs from ServiceNow return false. | Check ServiceNow instance and correct these API responses. | Import |
| Fatal | ERROR System.Exception: MessageStatus: {"StatusCode":500,"ReasonPhrase":"Internal Server Error"} MessageBody: {"message":"TypeError: Cannot convert null to an object."} [cause]: endpoint execute failed. and fallback is not success. fallback is not execute as the rules is not resolved. ---> System.AggregateException: One or more errors occurred. ---> System.Exception: MessageStatus: {"StatusCode":500,"ReasonPhrase":"Internal Server Error"} MessageBody: {"message":"TypeError: Cannot convert null to an object."} [cause]: endpoint execute failed. and fallback is not success. fallback is not execute as the rules is not resolved. | This exception occurs in the import step. | Check if the Mid Server is selected under export targets in ServiceNow. And check if the Export folder is correctly added in ServiceNow. | Import |
| Fatal | QUALYSAPIVersions is not supported. | This exception occurs during Test connection. | Check if Qualys version is supported. This error can also occur in the Admin Console UI component. | Import, Admin Console UI |
| Fatal | SNOWVersions is not supported. | This exception occurs during Test connection. | Check if ServiceNow version is supported. This error can also occur in the Admin Console UI component. | Import, Admin Console UI |
| Informational | An error occurred processing row <>. Error is <>. Will try to continue.. | Data Platform imports data from different types of data sources. Fetching each row and pushing it to data platform. If an issue occurs during processing such rows, this error occurs. | Check if the data being imported are valid. Along with the source database process is pointing to. The error will provide further details on what error occurred. This will help further investigate the same. | Import |
| Fatal | An error occurred while importing task[...] | Data Platform imports data from different types of data sources. Fetching each row and pushing it to data platform. If an issue occurs during processing such rows, this error occurs. | This usually occurs when there are issues with the source. Check the data source and retry again. If that does not fix the issue, contact Flexera technical support with the exception details. | Import |
| Fatal | ERROR insert into PRC_DYNAMIC_METADATA | Data Platform imports data from different types of data sources. Fetching each row and pushing it to data platform. If an issue occurs during processing such rows, this error occurs. | This usually occurs when there are issues with the source. Check the data source and retry again. If that does not fix the issue, contact Flexera technical support with the exception details. | Import |
Zip, CSV, Mashup Error Codes
Find the error text in the table below to learn more about it.
| Error Type | Error Text | When can it occur? | Resolution | Category/Stage |
|---|---|---|---|---|
| Fatal | Error: System.Exception: Unable to find queries.txt. The input file may be corrupted. ---> System.Exception: queries.txt file absent. | Exception Occurs When user tries to do a Normalize for Zip File imported without queries.txt file | Zip File should contain queries.txt file while doing the Normalize. | none |
| Fatal | Error: System.Exception: Invalid zip file. Part of the file is missing.System.csv | Exception Occurs When user tries to do a Normalize for Zip File imported without system.csv file | Zip File should contain system.csv file while doing the Normalize. | none |
| Fatal | ERROR The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. System.InvalidOperationException: The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. | Exception Occurs When User tries to import a csv without Microsoft.ACE.OLEDB.12.0 installed on server. | running platform is missing Microsoft Office, “Microsoft Access Database Engine” driver needs to be installed on machine before running this extractor. This driver can be downloaded from below url: (Install 64 bit) https://www\.microsoft\.com/en\-us/download/details\.aspx?id=13255 | none |
| Fatal | ERROR System.Exception: Object [Manufacturer] does not support mapping field. Match key not found. | Exception Occurs while adding CSV as a Mashup DataSource. | Appropriate Mashup Type should be selected based on the csv uploaded. | none |
Admin Console UI Error Codes
Find the error text in the table below to learn more about it.
| Error Type | Error Text | When can it occur? | Resolution | Category/Stage |
|---|---|---|---|---|
| Fatal | Exception: Get ILMT Connection token failed. | This exception will occur while testing ILMT connection. If the entered API URL, UserName, Password in Admin Console UI are incorrect, We throw this exception. | Check Username and Password, API URL entered. This error can also occur in the Import component. | Import, Admin Console UI |
| Fatal | ERROR [BMCFlow] [EndpointClient] [Request] request endpoint failed. BDNA.Common.API.HttpResponseException: service response an error for the request ---> BDNA.Common.API.FrontException: MessageStatus: {"StatusCode":400,"ReasonPhrase":"Bad Request"} MessageBody: { "code": 400, "message": "Invalid token", "transient": false } | Invalid API token while testing the connection in Admin Console UI | Check Token, API URL entered. This error can also occur in the Import component. | Import, Admin Console UI |
| Fatal | BMCAPIVersions is not supported. | While testing the connection or during import we check if the BMC version is supported. We throw this exception when in case of unsupported BMC version | Check Flexera DataPlatform BMC datasource documentation for supported versions list and take action. This error can also occur in the Import component. | Import, Admin Console UI |
| Fatal | QUALYSAPIVersions is not supported. | This exception occurs during Test connection. | Check if Qualys version is supported. This error can also occur in the Import component. | Import, Admin Console UI |
| Fatal | SNOWVersions is not supported. | This exception occurs during Test connection. | Check if ServiceNow version is supported. This error can also occur in the Import component. | Import, Admin Console UI |
| Fatal | Specified file does not exist. | This exception will occur while testing ServiceNow WorkFolder connection if the entered folder path doesn't exist. | Check if the folder path exists. | Admin Console UI |
| Fatal | The network path was not found. | This exception will occur while testing ServiceNow WorkFolder connection if the entered folder path is not found. | Check if the folder path is accessible. | Admin Console UI |
| Fatal | Invalid username or password. Please try again. | This exception will occur while testing ServiceNow WorkFolder connection if the entered Username and Password are not valid. | Check the Username and Password entered. | Admin Console UI |
| Fatal | Data Platform failed to connect to Normalize database. | This occurs when Data Platform fails to connect with the data source. | Check the data source’s password and connections and retry the process. | Admin Console UI |
| Fatal | Cancel Inventory failed, Analyze return false | This occurs when process is canceled in the middle of the critical task. | Retry cancellation after some time. | Admin Console UI |
| Fatal | Purge Inventory in Analyze failed, inventory id= <> | This occurs when purging an inventory is attempted when the inventory is busy. | Retry purge after some time. If that does not work, restart the Data Platform service, and retry purge. | Admin Console UI |
| Fatal | TestConnection in errors, skipped as IsSkipRequestExecute=[true] | This occurs when user attempts Test connection on an invalid data source. | Verify the credentials and retry Test connection | Admin Console UI |
Mapping Component Error Codes
Find the error text in the table below to learn more about it.
| Error Type | Error Text | When can it occur? | Resolution | Category/Stage |
|---|---|---|---|---|
| Warning | Connection timeout caught, retry after 2 minutes. | Data Platform communicates with the databases in order to move the data around. There are times when there is a disconnect causing Data Platform to wait for a response. | Check if the database is online and the credentials are configured properly. If not rerun Data Platform Configuration Wizard and retry. Check the data source configuration if database is working fine. | Mapping |
| Informational | User canceled Mapping | Occurs when the user cancels process at the mapping stage. | Retry by starting process again. | Mapping |
| Fatal | System.Exception: One or more errors occurred. | When Data Platform encounters an error with the imports on data base level, this error occurs. | Retry by starting process again after reconfiguring data platform and user console. If that doesn't work, contact Flexera technical support with the details. | Mapping |