I’ve not seen this error before, but assuming that you’re not getting other MSSQL error messages from the BES console, then I’d recommend clearing the cache and then reloading to see if the issue persists. If it does persist, then I’d recommend opening a support case with L2.
To clear the cache in the BES console, click “File” then “Preferences”. Then click the “Clear Cache” button on the “Preferences” modal window and then “OK” button to close.
Then close the BES console and wait for all threads to close. Then simply reload the BES console as normal and retest for the condition.