Common Dataset Errors


This document describes and provides solutions for common dataset issues and errors.


This is by far our most common dataset error. In our default datasets, we try to prevent this by limiting the amount of data pulled in, but in some instances, even that is not enough. This is caused by large influxes of data ( often due to mass updating old tickets or an RMM creating lots of tickets).  Our support team will be glad to work with you on limiting the data pulled when this occurs on default datasets.  For custom datasets, they can take a look and give you pointers as well.


This is an error due to the need to use a function SQL Server to help expose some data. Currently, this error only exists in a few ConnectWise Manage On Premises datasets. To resolve, please refer to Connecting to ConnectWise Manage On Premises for help on adding the permissions or contact Support.


Older iterations of SQL Server (2008 and older) lack the concat() function used by some default datasets. Contact our support team for help on removing that function from your datasets.  

Datefromparts error

This error shows itself as:

  • 'datefromparts' is not a recognized built-in function name

This error indicates that a function of SQL Server we're using to create a date is not available in your version of SQL Server. It started with SQL Server 2012, but we can make an adaption on the back end. Please contact Support and let them know if you're having a datefromparts error.

Invalid object error

This error indicates that a table used in a default dataset is not there. In most instances, this means that you are on an earlier version and need to upgrade. In rare instances, the table is not a part of your setup. For custom datasets, this usually means that the table you were using no longer exists. To see if a fix is available, contact Support for more information.


Deadlocks occur when the database kills our query because another process has locked the table(s) our query is trying to read. Deadlocks are rare because they normally affect processes writing to a table instead of just reading (SQL queries do lock tables, but release them quickly), but there have been situations where we encounter these. If you experience deadlocks, look into what is using the database first. These other processes are what are causing BrightGauge's queries to be locked out. For help, you should contact the vendor that set up your SQL database or consult a database administrator (DBA). As a last-ditch effort, BrightGauge can help work around these errors, but again it's a last-ditch effort since the workaround can cause incorrect data to be read.  For more information, you can read Microsoft SQL Server documentation or contact Support.

Was this article helpful?
1 out of 9 found this helpful