LoggerNet versions

v4.4 [Apr 8, 2016]
Toolbar Bug Fix - Fixed an issue with a hard-coded file path of C:\Campbellsci. With certain video settings, the toolbar would sometimes create files in this directory. This would cause the toolbar to fail, if LoggerNet was installed on a different drive such as the D:\ drive.
Setup Screen Bug Fix - Fixed a problem where the Setup Screen would be slow to start after launch from toolbar.
Setup Screen Bug Fix - File Retrieval Tab: Fixed an issue where if a datalogger file was successfully retrieved but could not be stored in the specified location (i.e. network drive) and the file was marked for deletion after retrieval, the file would be deleted from the datalogger but not stored on unavailable drive.
Connect Screen Bug Fix - Fixed a problem where occasionally array elements were not displayed correctly and incorrect values would be shown.
Connect Screen Bug Fix - Fixed an issue where you could not send a NAN value to a datalogger.
Short Cut Enhancement - Added sensor file support for the optional FillNaN parameter in an SDI-12 measurement for dataloggers that support it.
Short Cut Bug Fix - Fixed a bug where a compile could fail if extended (non-ASCII) characters were in the file path.
Short Cut Bug Fix - Improved manual moving of wires for some sensors.
CRBasic Editor Bug Fix - Fixed a bug where a compile could fail if extended (non-ASCII) characters were in the file path.
RTMC Enhancement - Warning icons are now suspended for 10 seconds to allow normal data flow to occur without reporting an error.
RTMC Enhancement - Changed the library used for the TLS stack from axTLS to mbedTLS.
RTMC Bug Fix - Fixed renaming issue reported with some components.
View Pro Bug Fix - Fixed a bug where Histogram, FFT, and Rainflow data could fail when graphed.
LoggerNet Server Bug Fix - Fixed an issue where if a datalogger file was successfully retrieved but could not be stored in the specified location (i.e. network drive) and the file was marked for deletion after retrieval, the file would be deleted from the datalogger but not stored on unavailable drive.

v4.2 [Sep 5, 2013]
- Known Issues - Mapped network drives cannot be used when LoggerNet is running as a service. This is caused by a Windows update that disallows the use of mapped network drives when running as a service for security reasons. To use network drives when running LoggerNet as a service, you must use the full UNC path (e.g., computer_namedirectoryilename). Note that the ability to write to the network drives will be governed by Windows security. It will be necessary to configure the LoggerNet service to run under an account that has network privileges. This requires changes to the properties of the LoggerNet service in Windows. Contact your network administrator for assistance.
- Known Issues - When using LogTool to zip all log files and certain file errors occur, the operation may still be reported as successful. For example, If LoggerNet is running as a service and an attempt is made zip all log files and store them in the root directory of a mapped network drive, a failure will probably occur as the service cannot access mapped drives but the operation is reported as successful.
- Known Issues - The following LNDB issue affects View Pro and RTMC Pro when using an LNDB database: If LNDB has been running with a SQL Server 2005 database, the timestamps in the tables will be of type DateTime. If you then upgrade to SQL Server 2008 the DateTime data type for the timestamps is carried over to the 2008 database. However, LNDB expects the timestamps to be of type DateTime2 which has a higher precision than DateTime. This type mismatch causes queries to fail. In order to fix this issue, you will need to use the SQL Server management tools to change the data type for the timestamp columns to DateTime2.
- Toolbar Enhancement - Added an "Allow IPv6 Connections" check box to the Tools
- Options dialog box. By default, IPv6 connections are not allowed. (Enabling IPv6 may cause problems if IPv6 is not fully functional in a network. The main issue is that clients cannot connect to the server.)
- Setup Screen Standard View Bug Fix - Fixed a bug in scheduled backups where the default value for number of files was set to zero. A value of zero causes all of the backup files to be retained. The default value has been changed back to 5.
- Task Master Bug Fix - Fixed a bug where data collection triggered by a task did not trigger any subsequent collection related tasks on the station collected from.
- Task Master Bug Fix - Fixed multiple issues with renaming of tasks and illegal naming of tasks.
- Task Master Bug Fix - Fixed a bug where tasks triggered by "After Any Call", "After Successful Call" and other triggers were being triggered by data displays in the Connect screen.
- Task Master Bug Fix - Fixed a bug where "Pending Actions" was not showing queued execution of a program.
- RTMC Bug Fix - Fixed a bug where touch events on mobile devices weren't working properly.
- RTMC Bug Fix - Fixed a bug where an alarm did not function, if it was grouped with other components.
- RTMC Bug Fix - Fixed an issue where the pipe wasn't displayed properly after switching tabs if pointed at a boolean value because it is reported as -1 and the test was looking for > 0 instead of != 0
- RTMC Bug Fix - Fixed an issue with publishing a project when the screen name has a symbol in it.
- RTMC Bug Fix - Fixed an issue where fixed size screen dimensions weren't being honored.
- RTMC Bug Fix - Fixed a directory traversal security issue in CSI Web Server.
- Device Configuration Utility Bug Fix - Fixed a bug where DevConfig could not read a NL240 config file created with an older NL240 OS.
- Server Bug Fix - Fixed a bug where tasks that were triggered by any poll, and failed poll, and failed poll with data, and poll with data, and etc. failed to recognize when a poll attempt took place because it was triggered by another task.
- Server Bug Fix - Fixed a bug in the task poll station action where, if the polling process had to do specials (such as doing file retrieval), the task would never get reported as complete.
- Server Bug Fix - Fixed a bug where changing the PC clock backwards caused scheduled collection, scheduled tasks, and scheduled backups to trigger immediately. Now the schedules' next time is recalculated only if the difference between the system time and the last time checked is greater than five minutes. This will make the LoggerNet server less sensitive to possible minor changes when the computer clock is updated.