TRY_CONVERT Error When Running Patch Tuesday Reports

[#1]

Patch Tuesday reports help you track urgent security fixes. When they fail, visibility fades and risk grows. A common error stops these reports cold and leaves admins puzzled. Today’s tip explains why this happens and how you can restore clear, reliable reporting in minutes.

What is going on

Many admins see an error when running Patch Tuesday reports:

'Try_Convert' is not a recognized built-in function name.
Incorrect syntax near the keyword 'As'

The report refuses to run. The dashboard stays incomplete. Patch compliance becomes harder to track.

This error appears because the report uses TRY_CONVERT, a SQL Server function introduced in SQL Server 2012. The function only works when the Lansweeper database uses a compatibility level of 110 or higher. If the database sits at an older level, SQL treats TRY_CONVERT as an unknown command.
This mismatch often occurs after a migration, restore, or upgrade. The SQL Server instance may be modern, but the database remains locked to an outdated compatibility mode. The report then breaks when it hits TRY_CONVERT in its reboot and date‑handling logic.

How can I fix this

You can fix the issue by raising the database compatibility level. This change is safe, quick, and does not alter your data.

Check your current compatibility level

1. Open SQL Server Management Studio.
2. Connect to your SQL Server instance.
3. Right‑click your Lansweeper database.
4. Select Properties.
5. Open the Options page.
6. Review the Compatibility level setting.

Update the compatibility level

Set the compatibility level to match your SQL Server version. Make sure it is at least 110.

1. Right‑click the Lansweeper database.
2. Select Properties, then Options.
3. Choose the correct Compatibility level.
4. Click OK.
5. Restart the Lansweeper service if needed.

You can also update it with T‑SQL:

SELECT name, compatibility_level
FROM sys.databases
WHERE name = 'lansweeperdb';

ALTER DATABASE lansweeperdb
SET COMPATIBILITY_LEVEL = 150;

Verify the fix

1. Open Lansweeper.
2. Go to Reports.
3. Create a new report.
4. Paste the Patch Tuesday report code.
5. Validate it with the green checkmark.
   The error should vanish.

This small adjustment restores full report functionality. Your Patch Tuesday dashboards fill with fresh, accurate data again, giving you a sharp and reliable view of your environment.