Deploying problems version 12

[smrtonos11333]

Hello,

i need deploy our scripts whitch was working in version 11. But after upgrade to version 12 have this » 

Preliminary checks failed! Task Service Error. BinaryFormatter serialization and deserialization are disabled within this application.

Any solution?

[Riley]

Hi all!

As @TechGuy2223 mentioned, We have released Lansweeper On-premises version 12.2.0.4, addressing the BinaryFormatter errors and other issues:

• Fixed BinaryFormatter deployment errors (LAN-16968)
• Resolved vCenter scanning timeouts (LAN-16727)
• Fixed Windows Server OS version detection (LAN-16936)
• Improved SNMP data scanning (LAN-16852)

Before updating: Back up your installation

Still experiencing problems? Contact our support team at Support Portal - Lansweeper Community or through support@lansweeper.com.

[smrtonos11333]

thanks, this version works

[wikilike7]

Same issue.

Latest version also have the Preliminary checks failed.

When it will be fix?

[TechGuy2223]

Updating ASP.NET Core Runtime to 8.11 using the hosting bundle installer appears to resolve the issue.
Download .NET 8.0 (Linux, macOS, and Windows)

[TechGuy2223 · Accepted solution]

• 12.2.0.4, LsPush 8.4.100.1, LsAgent Windows 11.4.1.2, SQL 1060

  If you use SQL LocalDB 2014, this release will update your database. Before updating to the newest version, make sure to back up your installation.

  • Fixed: LAN-16727 Scanning large vCenters could result in an HTTP timeout.
  • Fixed: LAN-16852 New scans without SNMP data would be ignored if the existing asset already contained SNMP data.
  • Fixed: LAN-16936 Windows 2025 would show up as Windows 2022.
  • Fixed: LAN-16967 A number of issues related to the chart widget were resolved.
  • Fixed: LAN-16968 Deployments would fail due to BinaryFormatter errors.

[Raphel1421]

I updated to 8.11 and the deployments are still failing. 

[djskipnz]

Upgraded from 11.1.9.1 to 12.0
Deployments no longer work.
Error message: Preliminary checks failed! Task Service Error. Binary Formatter serialization and deserialization are disabled within this application. 

The deployments is a key capability so I hope it's repaired soon

[FrankSc]

Dear all, 

We are looking into this internally. The binaryformatter is part of the TaskScheduler. We are looking into this as well with Microsoft, as it seems to be caused indeed with the move to .NET 8.
We'll keep you all updated when we have more news.

[smrtonos11333]

Hi FrankSc,

any progress?