Troubleshoot Data Services

For information about how to administer data services, see Managing Data Services. For information about managing access to data services, see Controlling Access in Loftware Enterprise SP.

Important! Whenever you add a new device, data service, integration, or facility, you must ensure that the service is activated on all Loftware Application Servers on which it should be available to run and started on at least one. In an environment with only one Loftware Application Server, these types of services are automatically activated and started when they are created. For more information, see High Availability with Distributed Services.

Important! In an environment with distributed services, to permit a user to perform administrative tasks related to services you must assign Read and Write permissions for Servers. These permissions must be assigned for each server in Access Control . Examples of administrative tasks related to services include creating a data service, a device connection, an integration, or a facility. Core services can only be configured by the SuperAdmin or SystemAdmin user.

Important! If you delete a custom parameter from a JDBC data service, the parameter is automatically removed from any Database data sources associated with that data service.

Note: The maximum length for a string parameter is 4,000 characters.

Symptom	Resolution
An error message occurred when attempting to run a query for the first time.	The data service is not running. Save and start the data service before attempting to run a query.
Changing a JDBC data service does not produce any change in the label data.	A Database data source contains a copy of the configuration in the JDBC data service rather than a link to it. For more information about the behavior to expect, see Managing Data Service Parameters.
Deleting a custom parameter from a JDBC data service causes the parameter to vanish from existing Database data sources.	If the Data Service Administrator deletes a custom parameter in the JDBC data service, that parameter is automatically removed from the associated data sources. For more information about the behavior to expect, see Managing Data Service Parameters.
A JDBC data service will not run and the following message is displayed: No suitable driver.	To enable Loftware Enterprise SP to connect to most types of databases, you must install a third-party Java Database Connectivity (JDBC) API driver on the Loftware Application Server. For more information, see Add a JDBC Driver.
A Channel disconnected error is displayed when retrieving data by using a data entry form that points to a data source.	This message may be displayed during an attempt to use a data source if the data service has failed and is not load balanced by using distributed services in Loftware Enterprise SP. If the data service is configured to fail over to another Loftware Application Server, this message may still be displayed because there is a brief interruption during failover. Use one of the following approaches to resolve the issue: Eliminate the potential for this error by using distributed services to configure the data service to be load balanced. If the data service is configured to fail over to another Loftware Application Server by using distributed services, instruct the user to click OK to close the error message, wait for a few seconds so that the service can fail over, and try again to use the form again.
Problems are occurring with a Serial Number Data Service.	To troubleshoot a Serial Number Data Service, add the following logger to your log4j2.xml file found in <LOFTWARE_HOME>\product\conf. For more information, see Event (Application) Logging. <Logger name="com.loftware.services.dataservices.implementations.lifecycles.SerialNumberDataService" level="DEBUG"/>