NetXMS Support Forum

English Support => General Support => Topic started by: Watchman on April 07, 2025, 02:21:47 PM

Title: Client 5.2 closing after logging in
Post by: Watchman on April 07, 2025, 02:21:47 PM
Attempting to update NetXMS from version 5.1.3 to version 5.2.
The legacy client seemed to work, but the (modern) client closes without errors immediately after logging in.
The client was tested on different computers.
System environment: Server on Windows Server 2016, client on Windows Server 2016 or Windows 10.
How do i determine what the problem is?

Regards
Peter

Title: Re: Client 5.2 closing after logging in
Post by: Filipp Sudanov on April 07, 2025, 02:31:22 PM
Client writes log in \.nxmc4\nxmc.log in user's home folder. Are there any errors in this file?
Title: Re: Client 5.2 closing after logging in
Post by: Watchman on April 07, 2025, 03:09:49 PM
Because I rolled back to 5.1.3, I hope this is the correct section of the log file:
nxmc.log
Title: Re: Client 5.2 closing after logging in
Post by: Filipp Sudanov on April 07, 2025, 03:37:52 PM
Is this log from Windows Server 2016 system? Can you also show one from Windows 10?
Title: Re: Client 5.2 closing after logging in
Post by: Watchman on April 07, 2025, 04:29:57 PM
The log is from Windows 10.

Due to the rollback (Hyper-V checkpoint), the Server 2016 log file with the v5.2.0 entries is no longer available.
If it's important, I could enable the checkpoint with v5.2.0 installed. But since our system is in production, that wouldn't be desirable.
Title: Re: Client 5.2 closing after logging in
Post by: Filipp Sudanov on April 07, 2025, 04:42:32 PM
It's ok, logs are good. The thing that it needs is WebView2 - https://developer.microsoft.com/en-us/microsoft-edge/webview2

What's changed from previous version is that in 5.2. we have what's new screen that opens on the start. And current code does not check properly if WebView2 is available - this will be fixed.
Title: Re: Client 5.2 closing after logging in
Post by: Watchman on April 07, 2025, 05:07:37 PM
Then we'll wait for a new patch release.  ;)

Thanks for the quick support.

Regards
Peter