Known Issues and Breaking Changes

Known Issues

Media control does not function in Desktop WebView

The Media control does not function reliably in Desktop WebView. It may or may not play a video that works in Silverlight. We are aware of the issue and will try to improve it in a future version.

New security groups may need to be reset in DataHub v9

DataHub v9 includes two new security groups (Admin and RemoteConfig), which help with configuring new user access credentials. After upgrading to v9, you may not see these new user groups in the Configure Permissions window. To add these new groups, you can close the Configure Permissions window and click on the ‘Reset Default Users and Groups’ button.

No WebSocket support in Windows 7

Microsoft does not support WebSockets in Windows 7.  So when using Remote Config, Desktop WebView or the Vine Excel Add-in, you will need to configure a TCP connection to the DataHub, rather than the default WebSocket connection.

Upgrade from DataHub v7 while running as a service

If you are running DataHub v7 as a Windows service and you plan to upgrade to DataHub v8, then you should follow these steps.

  1. Stop the DataHub service in the Service Manager program;
  2. Perform the upgrade to version 8;
  3. Run the DataHub as a service again from the Service Manager program.
Running DataHub as a service in Windows 10 and Server 2016

We use a program called the Service Manager to help you run the DataHub as a Windows service. With Windows 10 and Server 2016, Microsoft have removed keyboard and mouse support from the service console 0.  Although you can still use the Service Manager to run DataHub as a service, you can no longer use the service console to change the DataHub configuration.

DataHub v9 introduces the Remote Configuration feature which makes it easy to configure and work with the DataHub while it is running as a Windows service.  Using the Remote Configuration feature also allows you to configure a DataHub running on a remote network computer.

To make changes to DataHub v7 or v8 (in Windows 10/Server 2016), you must do the following:

  1. Stop the DataHub service in the Service Manager program;
  2. Run the DataHub as a normal Windows user and save the configuration changes;
  3. Close down the DataHub; and
  4. Run the DataHub as a service again from the Service Manager program.
Windows XP support for LDS

If you install the DataHub in Windows XP with Service Pack 2, then the DataHub will run but the UA Server will not be able to register with the Local Discovery Server. The work-around for this problem is to simply copy the DataHub UA server Endpoint URL and paste it into the UA client configuration.

Failed authentication causes a disconnection

In version 7, the authentication mechanism follows an escalation process, where the connection initially has anonymous permissions, then upgrades to TCP permissions, then to Mirror permissions. If the user then authenticates then the connection upgrades to the permissions of the user. If the user authentication fails, the connection remains open and the permission for that connection remains at the permissions for Mirror.

In version 8, the same escalation process occurs. However if the user attempts to authenticate and the authentication fails, the connection is immediately disconnected instead of remaining open with the permissions of Mirror.

Data model not always transmitted

Version 8 no longer sends the data model over a tunnel during initialization when the user selects “Get all values from the master”. In version 7 the slave would send its model even when it knew that it was not authoritative on the data set. This could cause a slave to mangle the model on the master, even though the master is supposed to be correct.

Breaking Changes

DataHub v9 is a 64-bit application

DataHub v9 is a 64-bit application so it will not run on 32-bit operating systems.

DataHub v9 does not support Windows XP and Server 2003

DataHub V9 requires .NET 4.6.1, which is only available on Windows 7 and later.  Windows XP and Server 2003 are not supported.

DataHub v9 uses 64-bit ODBC drivers

ODBC support in DataHub v9 now uses 64-bit drivers.  All existing DSNs will fail to load. You need to create the DSNs as 64-bit instead of 32-bit.  To open the 64-bit DSN editor, you can choose “Open DSN Administrator” from the DataHub database action configuration dialog.

Changes to OPC-UA certificate handling

DataHub v9 changes the way DataHub deals with OPC-UA certificates by removing a dependency on the windows machine certificate store that was stopping DataHub from registering with the LDS if the user permissions did not permit reading that store. We are not aware of any side-effects from this.

Changes to DataHub Web Server folders

The DataHub Web server document root, default certificate file and log folders have all changed.  The tunnel/Mirror default certificate file has changed.  When DataHub starts, it looks for a configuration that was default for version 8 and automatically adjusts that to reasonable values for version 9.

Binary tunnel connections between DataHub v9 and v8

Binary tunnel connections between DataHub v8 programs (DataHub, DataSim, DataPid) and version 9 programs will fail. They appear to succeed but no data values are delivered. The event log may contain error messages depending on the direction of the connection. This is made necessary by a change in the timestamp representation from 32 to 64 bits. Text connections (non-binary) are compatible between v8 and v9.

DataHub v9 start up parameter now on by default

In DataHub v9 the installer now sets the default value of “Allow only one running instance” to TRUE.

Old Web Server demo pages removed in DataHub v9

The demonstration pages for the built-in web server have been removed in DataHub V9.  The special URLs supporting AJAX and streaming AJAX application have been removed. The AJAX paths (/points and /ajax) are unauthenticated and represent a potential information leak. Streaming AJAX is no longer a useful technology.

Specifically, the following paths no longer exist:

  • /points
  • /ajax
  • /stream
  • /socketIn
  • /socket

For web applications that need to interact with DataHub you have 2 options:

  • use a WebSocket connection
  • create your own ASP page to generate custom JSON or XML content that your web application can poll.
Scripts need to be moved after upgrade to DataHub v9

After upgrading to DataHub version 9, the scripting tab may refer to scripts in the C:\Program Files (x86)\… folder. These scripts should be moved to another folder. We recommend creating a folder within the DataHub configuration folder and moving them there, typically:

C:\Users\<Windows Login>\AppData\Roaming\Cogent DataHub\scripts

where <Windows Login> is the user name you used to log in to Windows.