Lasernet Issues and Workarounds

Connection to the Lasernet database and to temporary files that are locked by third-party services can be blocked, causing crashes and/or instability. This article describes how to resolve this issue.

When the instance name in the portal and the instance name in Lasernet Developer do not match, then this can cause instability, missing log files etc. This article describes how to resolve these issues.

On occasion, Lasernet Developer needs to be started as Administrator to have the rights to save changes. To do this, follow the steps in this article.

Microsoft has recently made a change to its TLS handling protocol. This has resulted in a connection failure with the Lasernet Mail Output port. This article describes a solution.

Lasernet 9.15.5 (and earlier) and Lasernet 10.5.2 (and earlier) install a version of the driver (18.3.0) that has a vulnerability.

A recent automatic update to Microsoft Edge WebView2 has caused an issue with the Lasernet Sign In window and Outlook Mail login window. Summary If WebView2 version 134.0.3124.51 is installed, you cannot enter an entire username into the windows...