[BUG]

[AleksanderKruecken]

Component

Full Dashboard

Performance Monitor Version

2.5

SQL Server Version

MSSQL server 2022 standard CU23 + GDR

Windows Version

Windows server 2025 standard

Describe the Bug

I have installed version 2.4 a week ago onto 35 sql servers (from my managed server) and everything went without a problem.
Today I wanted to upgrade installed version on this servers to 2.5 (also from my managed server as I did a week ago with GUI installer). Last week I entered a server name, ticked the box to trust the certificate and that was it.
I see that GUI installer isn't available anymore so I run command line installer.
I entered the following and I get the following error (see the picture). I tried on 2 servers and they both return the same error. It's strange, because both of them have 2.4 version intalled and I'm making installation from the same managment PC as I did last week. What am I doing wrong?

Steps to Reproduce

Run PerformanceMonitorInstaller.exe and enter server name and option to not check certificate, choose windows authentication

Expected Behavior

performance monitor would be successfully upgraded to 2.5 on sql server

Actual Behavior

Error regarding connection failed appears.

Error Messages / Log Output

? Connection failed: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
The network path was not found.

Screenshots

No response

Additional Context

No response

[AleksanderKruecken]

I managed to upgrade the version by copying the installer on the sql server itself and run it from there. I tried on two servers and they both had problems by installing from managed server.

On the first server everything went fine:

On the second server the installation froze in the middle:

[AleksanderKruecken]

Funny thing - If I double click PerformanceMonitorInstaller.exe and then enter sql server name the error in the first post gets displayed. If I open cmd and then go to the folder where installer lies and then run the installer everything installs without the problem.

[AleksanderKruecken]

Ok, I also found out that the problem with freezing installation occurs on server where version name of performance monitor is not displayed via T-SQL (I reported the bug last week).
Reinstall parameter helped in this case a bit because then installation completed successfully. Lost the data in the database from the last week, but I will survive :)

[erikdarlingdata]

Fixed in #785. The CLI installer's interactive mode defaulted to Mandatory encryption with no certificate trust, which fails on servers with self-signed certificates. The retired GUI installer used Optional encryption + trust cert by default, which is why v2.4 worked.

Interactive mode now prompts for both settings:

• Trust server certificate? (default: Y)
• Encryption level: Optional/Mandatory/Strict (default: Optional)

This matches the old GUI installer behavior. If you prefer command-line mode, you can also use:

PerformanceMonitorInstaller.exe SERVERNAME --trust-cert --encrypt=optional

[erikdarlingdata]

@AleksanderKruecken Thanks for the additional detail — a few follow-ups:

1. Double-click vs cmd: This should be fixed now in #785. The interactive mode (double-click) was defaulting to Mandatory encryption with no certificate trust. Running from cmd likely worked because you passed --trust-cert or the connection resolved differently.

2. Installation freezing: You mentioned this happened on a server where the version name wasn't displaying via T-SQL. Could you share more detail on that?

• What did the version detection show (or not show) in the installer output?
• Was there an existing PerformanceMonitor database on that server? If so, did it have a config.installation_history table, and did it have any rows?

We fixed a bug in #774 where the Dashboard's upgrade path silently failed to detect upgrade scripts, which could cause installs to hang. If you're running the CLI installer, that uses a different code path (filesystem) which should work — but I want to make sure your freezing issue isn't a separate problem.

3. Data loss with --reinstall: That flag drops and recreates the database by design, so data loss is expected. For future upgrades, just run the installer without --reinstall — it will detect the existing version and apply only the upgrade scripts, preserving all collected data.

If you can reproduce the freeze, the installer writes a report file to the working directory (PerformanceMonitor_Install_*.txt) — that would help us pinpoint where it got stuck.