Data Platform Error Codes

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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

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.

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

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

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.