OPC Data Logger Errors

Error

Description

Asynchronous Read results received from the Server are BAD (cannot be trusted) because the MasterError = '...'

The Data Logger issued an asynchronous read request, and the results of that request were received with errors. This means that all of the data within that update are all of bad quality.

Cannot complete startup on '<project>'

The specified project could not start up and initialize. Further details of the reason will be embedded within this message.

Cant generate mappings from Groups because no groups exist

An attempt to automatically generate the Table Mode mappings could not be made because no Groups have been defined. Verify your configuration.

Connection Failed: '...'

The connection to the specified component failed. This usually indicates a problem with the Data Collection engine. The reason for the failure will be available elsewhere within the text.

Connection to Server closed. Server status '...'

This error is typically thrown by the Data Collection component. The error is likely because the data source is no longer connected. You may need to re-initialize the application if your configuration is not set to automatically revive lost connections.

Could not open Configuration file

An error occurred while opening the configuration file (*.DataLogger). Perhaps the file does not exist or the data is corrupted.

Data Storage '...' encountered Exception '...'

The specified Data Storage component encountered a problem unexpectedly. The details of the error will be available elsewhere within the text.

Engine not specified

Means that an attempt was made to connect to a Data Collector or Data Store, but the underlying interface has not been specified. Verify your configuration is setup correctly.

Error shutting down DataLogger Service: '...'

An attempt was made to shut down the Service which failed. The reason for the failure will be specified elsewhere within the message.

Error starting DataLogger Service: '...'

An attempt was made to start the Service which failed. The reason for the failure will be specified elsewhere within the message.

Evaluation expired '...'

The specified component is running as a demo. The application will need to be restarted.

Filename invalid

Indicates that an attempt was made to specify a file whose name is not legal, i.e. not compatible with the underlying Operating System.

No Group specified

An attempt was made to read or subscribe to Items, but no Group was specified. This indicates that the Project does not contain any groups. Check your configuration.

No Items specified within the Group

An attempt was made to read or subscribe to Items, but the specified Group does not contain any items. Verify your project configuration.

No Plugins were found at '...'

The application could not find any components at the specified location. This would indicate that the files have been deleted or not installed. Re-installing the product should fix this problem.

Not enough disk space

This error may be thrown by the Text File logger which contains a fail-safe method which causes it to stop logging if the remaining disk space goes below a specified required disk space. Check your hard disk space.

<null> value received

This error is typically thrown by the Data Collection engine. This error means that the value received is null, consequently meaning that the data is bad. If you see this message, it usually indicates that an OPC Server is not truly OPC Compliant.

'<project>' does not have a Data Collector

The specified Project cannot start logging because no Data Collection engine has been specified. Verify your configuration settings.

Registration Failed. No response detected.

While attempting to register the software online, the call to register the software failed with no response from the internet. Make sure that your computer is connected to the internet. You may need to temporarily close your firewall or allow the application to pass through firewall.

Table configuration incompatible. There are required fields that have not been mapped yet.

The database Table configured for logging data to requires values for specific fields, and the current configuration does not provide a value for all of these required fields. This means that there is no possibility of logging data until this issue is corrected. The solution will be to open the Database Properties, go to the Mappings tab and to verify the settings in there.

Table Schema Changed

This error is thrown by a Database Logging component. While initializing the project for data collection the engine will query the schema of the Table or Stored Procedure that will be used for logging data. If that schema differs from what the configuration remembers then this error will be thrown. The solution will be to open the Database Properties, go to the Mappings tab and to verify the settings in there.

There are no active data stores in: '<project>'

The specified Project cannot start logging because all of the Data Stores associated with the project are disabled. Open the project properties and then go to the Log to tab and enable at least 1 data store.

Unable to add group, error '...'

This error is typically thrown by the Data Collection component. The error is likely because the data source rejected the request, typically seen in OPC Servers. The solution is check the error code and to consult the OPC Server documentation for possible reasons that might cause this.

Unable to add items to group, error '...'

This error is typically thrown by the Data Collection component. The error is likely because the data source rejected the request because the specified items do not exist. You will need to verify that your configuration contains Items (within the Group properties) which are valid and do exist within your data source.

Unable to connect to Service. No connection could be made because the target machine actively refused it.

This is not a serious problem. The error is thrown because either the Configuration GUI or the Notification Icon was unable to establish a socket connection to the Windows Service. This may be because:

• The service is not running

• Firewall configuration is blocking the applications

Unable to load Plugin

Careful attention to the details of this message will specify the reason behind the failure. This kind of problem usually occurs as a result of a required dependency file (*.dll) that cannot be found in the product installation directory.

Unable to register online: '...'

While trying to register the software online, the transaction failed. The reason for the failure will be present elsewhere within the text. Make sure that you do have a connection to the internet. Also make sure that the information you have entered is 100% identical to the information provided at the time of purchase.

Unable to validate items. Error '...'

This error is typically thrown by the Data Collection component. The error is likely because the items within the configuration are not valid, i.e. perhaps the names are incorrect or the items simply do not exist at the data source. Verify your configuration settings.