Skip to main content
Version: 10.2.4

Health check messages

The document lists health check messages received via API. For more information on health checks, see Configuration and health check

Control Tower​

Component nameMessage typeMessage text
AUTOML-SERVICESErrorBase automation URL is empty, define the secure automl.services.endpoint properties.
GeneralError%component_name does not respond. Check if it is accessible via the URL.
Database connectionErrorDatabase validation failed. Error: %s. Use 'liquibase validate' to see details.
Database connectionErrorDatabase validation failed. %s change sets have not been applied. Use 'liquibase status' to see details.
Database connectionErrorImpossible to call the stored procedure. Make sure that the "ct.datasource.username" ControlTower user has appropriate permissions
Database connectionErrorFailed to connect to database. Reason: %s (an error from the MS SQL driver)
NexusErrorThe Nexus repository username or password is empty. Please define the secure nexus.user and nexus.password properties.
NexusInfoFound %number artifact(s) in the Nexus repository. "nexus.url"
OCRErrorThe OCR URL is empty. Please define the ocr.api.base_url property.
OCRWarningThe JWT issuer or secret are not set. Please define the secure jwt.issuer, jwt.secret properties to enable correct operation of the ocr-plugin.
S3WarningThe secure s3.access-key or s3.secret-key properties are not set. The S3 file storage might be not accessible. Please define the secure s3.access-key or s3.secret-key property.
TableauWarningTableau secure properties for Dashboard and Automation do not match. Dashboard reports might not be displayed. Please check that secure properties match as follows:
  • tableau.dashboard.host equals tableau.automation.host
  • tableau.dashboard.username equals tableau.automation.username
  • tableau.dashboard.password equals tableau.automation.password.
TableauWarningTableau:Automation is not configured. You should specify following parameter(s): tableau.automation.host,tableau.automation.username,tableau.automation.password"
SSOErrorError parsing the identity provider’s (IdP) metadata file %wf.sso.SSO.idp.file.metadata for Single Sign On Authentication. %Error message%
SSOErrorThe Service Provider ID property is not set for Single Sign On. Please define the secure wf.sso.SSO.sp.metadata property.
SSOErrorThe secure username attribute property is not defined for Single Sign On. Please define the secure wf.sso.SSO.username.attribute=username property. If you do not have the username attribute, contact your Security Administrator.
SSOErrorIdentity Provider (IdP) metadata file does not exist for Single Sign On. Please request the IdP metadata file from your Security Administrator and copy the file to configured path: %wf.sso.SSO.idp.file.metadata.
LDAPErrorUsers and groups base directories for LDAP server are not set. Please, define the ldap.group.base and ldap.user.base properties for searching the users and groups.
LDAPErrorUser or groups filters for LDAP server are not set. Please, define the ldap.user.filter, ldap.group.filter filters for searching the users and groups.
LDAPErrorUser filter for LDAP server is not set. Please, define the "ldap.user.filter" property for searching the users.
LDAPWarningUser groups are not found at LDAP server. Users can not log in. Please, setup the ldap.group.base or ldap.group.filter properties correctly.
LDAPInfoCredentials for the LDAP server system user are not set. Please define the secure ldap.bind.password or ldap.bind.dn properties.
LDAPErrorError loading the user groups from LDAP server. Please check the ldap.server.url, ldap.bind.dn, ldap.bind.password secure connection properties.
LDAPErrorThe URL property for LDAP server is not set. Please define the secure ldap.server.url property.
LDAPErrorLDAP Server URL %URL is invalid. Please define the secure ldap.server.url property correctly.
LDAPInfoLDAP Integration without groups\roles is enabled.
LDAPInfoLDAP Integration with groups is enabled
ImageMagickWarningThe ImageMagick image conversion library is not found. The OCR pre-processing step cannot be executed correctly. Please, setup the ImageMagick library.
GhostScriptWarningThe GhostScript image conversion library is not found. The OCR pre-processing step cannot be executed correctly. Please, setup the GhostScript library.

GhostScript is a secondary tool used for OCR. This warning can be ignored in case either OCR or GhostScript capabilites are not used by the designed Business Process.

LicenseWarningThe %s license is inactive. Manual tasks are not possible to publish with this license.
LicenseErrorThe problem with the '%s' license (%s) occurred. Error: %s
RPAWarningRPA Bot Manager host is empty, please define the property rpa.bot.manager.base.url.

Workspace​

Component nameMessage typeMessage text
LDAP authenticationErrorUsers and groups base directories for LDAP server are not set. Please define ldap.group.base and ldap.user.base for searching the users and groups.
SSOErrorIdentity Provider (IdP) metadata file does not exist for Single Sign On. Please request the IdP metadata file from your Security Administrator and copy the file to configured path: %ws.sso.SSO.idp.file.metadata.
SSOErrorService Provider ID property not defined for Single Sign On. Please define the secure ws.sso.SSO.sp.metadata property.
SSOErrorSecure username attribute property is not defined for Single Sign On. Please define the secure ws.sso.SSO.username=mail attribute property. If you do not have the username attribute, contact your Security Administrator.
SSOErrorIdentity Provider (IdP) metadata file does not exist for Single Sign On. Please request IdP metadata file from your Security Administrator and copy file to configured path: %ws.sso.SSO.idp.file.metadata.
SSOErrorError during parsing identity provider's metadata file.
LDAPErrorUsers and groups base directories for LDAP server are not set. Please define ldap.group.base and ldap.user.base properties for searching users and groups.
LDAPErrorError loading the user groups from LDAP server. Please check the ws.secure.ldap.server.url, ws.secure.ldap.bind.dn, ws.secure.ldap.bind.password secure connection properties.
LDAPErrorUsers and groups base directories for LDAP server are not set. Please define ldap.group.base and ldap.user.base properties for searching users and groups.
LDAPTBD InfoCredentials for the LDAP server system user are not set. Please define the ws.secure.ldap.bind.password or ws.secure.ldap.bind.dn secure properties.
LDAPWarnOne or more groups are not found at LDAP server. Please, setup the ldap.group.base or ldap.group.filter properties correctly.
LDAPErrorUser groups defined in the application properties are not found at LDAP server. Users cannot log in. Please setup the ldap.group.base or ldap.group.filter properties correctly.
LDAPErrorUser or groups filters for LDAP server are not set. Please, define the ldap.user.filter, ldap.group.filter filters for searching the users and groups properties.
LDAPErrorUser filter for LDAP server are not set. Please, define the ldap.user.filter filter for searching the users.
Database connectionErrorDatabase validation failed. Error: %s. Use 'liquibase validate' to see details.
Database connectionErrorDatabase validation failed. %s change sets have not been applied. Use 'liquibase status' to see details.
Database connectionErrorDatabase connection error occurred. Please, check the database endpoint, security settings and connections number limits.
Database connectionErrorDatabase access error occurred. Please, check that the ws.datasource.username or ws.datasource.password secure database credentials are correct.
Database connectionErrorDatabase access error occurred. Connection to database does not exist.

OCR​

Component nameType of issueMessage Text
Microsoft SQL ServerErrorMS SQL check failed: + e.getMessage()
Possible causes:
  1. OCR could not connect to Microsoft SQL Server.
  2. Microsoft SQL Server is down.
  3. The Microsoft SQL Server node is not reachable from ocr-rest.
  4. OCR Service is not operational.
Remedy:
Make sure:
  1. Microsoft SQL Server is up.
  2. The network between Microsoft SQL Server node and ocr-rest node is operational.
S3ErrorFailed loading a file: + e.getMessage()
Possible causes:
  1. S3 is not reachable from ocr-rest.
  2. OCR Service is not operative.
Remedy:
Make sure S3 is up.
S3ErrorSave operation failed during a storage test: + e.getMessage()

Possible causes:
  1. S3 or MS SQL (depending on the active profile in configuration) is not reachable from ocr-rest.
  2. The connection is not configured correctly.
  3. MS SQL is down.
  4. OCR Service is not operational.
Remedy:
Make sure:
  1. S3 is up.
  2. The connection is configured properly.
RabbitMQErrorReceive operation failed with an error during MQ test: ", e
Possible causes:
  1. RabbitMQ or MS SQL (depending on the active profile in configuration) is not reachable from ocr-rest or ocr-worker.
  2. RabbitMQ or MS SQL is down.
  3. ocr-worker is down.
  4. OCR Service is not operational.
Remedy:
Make sure:
  1. RabbitMQ or MS SQL is up.
  2. The network between RabbitMQ or MS SQL node and ocr-rest node is operational.
RabbitMQErrorA bad message payload was received, expected='" + expectedPayload + "' actual='" + actual + "'"
Possible causes:
  1. An incompatible version of ocr-worker is deployed.
  2. Message Queue for Health Check has incorrect custom configurations.
  3. OCR Service is not operational.
Remedy:
Make sure:
  1. Compatible version if ocr-worker is deployed.
  2. ocr-worker is up and has the correct connection settings to RabbitMQ.
  3. Message Queue for Health Check is configured properly and consistent between ocr-rest and ocr-worker.
RabbitMQErrorA message was not received during MQ testing, expected='" + expectedPayload + "', workers supposedly are not handling messages in MQ".
Possible causes:
  1. RabbitMQ or MS SQL (depending on the active profile in configuration) is not reachable from OCR-worker
  2. OCR-worker is not operational.
  3. Wrong version of ocr-worker is deployed.
  4. Message Queue for Health Check has incorrect custom configurations.
  5. OCR Service is not operational.
Remedy:
Make sure:
  1. RabbitMQ or MS SQL is up.
  2. ocr-worker is up and has the correct connection settings to RabbitMQ or MS SQL.
  3. Message Queue for Health Check is configured properly and consistent between ocr-rest and ocr-worker.
RabbitMQErrorFailed sending a message to RabbitMQ. Please, check that RabbitMQ is up and running. Refer to Installation Guide.
ocr-workerErrorNo reports from OCR-workers are found or the reports have expired. Please check number of the OCR-workers operating on the server and of the OCR-workers number is less then required start required OCR-worker number. Refer to WorkFusion OCR Guide.
ocr-workerErrorNumber of workers without errors is below the error threshold: " + counts[3])
Possible causes:
  1. MS SQL is not reachable from OCR-workers.
  2. OCR-workers are not operational.
  3. OCR Service might handle the requests slowly or be non-operational.
ocr-workerWarningNumber of well operational OCR-workers is below warning threshold: " + okCount
ocr-workerInfoNumber of well operational OCR-workers: " + okCount
ocr-workerErrorOCR-worker where reports exceeded expiration threshold (" + errorTtl + " seconds): " Make sure these ocr-workers are up and can access MS SQL.
LicenseInfoRemaining number of pages to be processed under the current OCR license: + volumeRemaining
LicenseWarningRemaining number of pages to be processed under the current license is below warning treshold: + volumeRemaining. Contact Workfusion support team to obtain a new license.
LicenseWarningYour OCR license is about to expire. Less than 10% of pages left. You will need to purchase a new license in order to continue using OCR.
LicenseErrorYour OCR license has expired. You have to purchase a new license in order to continue using OCR.
LicenseErrorOCR license is not found. Please, check that the OCR license is activated.
LicenseErrorFailed to load the OCR license. Please, check the access permissions for it.