Autoupdate stuck on installing

[nieboerb]

Autoupdate stuck on installing

In the end I installed the update manually.

[DonMario73]

Same issue here.  Follows the answer from Lansweeper support:

"After further review, we've identified a potential SQL compatibility issue that appears to be occurring when the auto-feature queries information in the database. The following error from the logs supports this finding:

2025-04-03 10:15:36.966 -05:00 [ERR] Failed executing DbCommand (2ms) [Parameters=[@__dje_zN92JDUUCV2HE4FA_ejd_0='?' (Size = 4000), @__dje_z4XQMSTH8_ejd_1='?' (Size = 20)], CommandType='"Text"', CommandTimeout='30']SELECT [t].[AutoUpdateHistoryId], [t].[Description], [t].[InstallationDate], [t].[ScanServer], [t].[Status], [t].[Version], [t].[WebsiteInstallId], [t0].[WebsiteInstallId], [t0].[LastPolledUtc], [t0].[MachineName], [t0].[StartedUtc], [t0].[Version]FROM [dbo].[tsysAutoUpdateHistory] AS [t]LEFT JOIN [dbo].[tsysWebsiteInstall] AS [t0] ON [t].[WebsiteInstallId] = [t0].[WebsiteInstallId]WHERE EXISTS ( SELECT 1 FROM OPENJSON(@__dje_zN92JDUUCV2HE4FA_ejd_0) WITH ([value] nvarchar(60) '$') AS [d] WHERE [d].[value] = [t].[ScanServer] OR ([d].[value] IS NULL AND [t].[ScanServer] IS NULL) OR ([t0].[WebsiteInstallId] IS NOT NULL AND ([t0].[MachineName] = [d].[value] OR ([t0].[MachineName] IS NULL AND [d].[value] IS NULL)))) AND [t].[Version] = @__dje_z4XQMSTH8_ejd_12025-04-03 10:15:36.967 -05:00 [ERR] An exception occurred while iterating over the results of a query for context type 'Lansweeper.OnPremise.AutoUpdate.Persistence.AutoUpdateContext'.Microsoft.Data.SqlClient.SqlException (0x80131904): Incorrect syntax near the keyword 'WITH'.Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon.

We have escalated this case to our Development Team for further investigation under BUG case LAN-17395. They will be reviewing this behavior, specifically the potential SQL compatibility issue, and will provide an update once their review is complete."

We are using SQL Express 2014 and are planning to upgrade.  This is the what support suggests:

"You're correct that upgrading your SQL Server instance to a newer version could potentially resolve the behavior you're experiencing, as our review suggests it's specifically occurring with SQL Server 2014.

However, we also want to assure you that our Development Team is actively working on this behavior, as it has been escalated. They are investigating the root cause and potential fixes within the current environment as well.

Therefore, while upgrading might offer a solution, it's not the only path forward. "