Problem with SQL connection for Basic version

serveradmin_0226

We would like to purchase a license key for the ProGet Basic version. Currently, we are using the trial version, but we have noticed an issue with the ProGet instance.

At the moment, we are using Docker Compose along with a connection to SQL Server. In the logs, we are seeing the following errors:
An error occurred in the web application:

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: TCP Provider, error: 26 - Error Locating Server/Instance Specified)

Eventually, the application stops working and returns a 500 error.

Interestingly, even though this error appears in the logs, all log data seems to be successfully added to the database.

Have maybe someone similar problem? This is a big blocker for us, because we are not sure if Basic License works correctly, or if ProGet will be a good choice as an artifactory hub.

rhessinger

Hi @serveradmin_0226,

Does this error happen after ProGet has been running for a bit or is this the error you get as soon as you start ProGet preventing it from running at all? Can you please confirm which version of ProGet you are running and your SQL Server version? Also, is SQL Server running as part of your Docker Compose setup as well?

Thanks,
Rich

monika.sadlok_5031

Hi,

ProGet was working until the key was replaced.(for Basic License)
Proget version 2024.21 and SQL Version 2022
Yes, in docker compose we have a connection link to SQL Server, which is on the same VLAN and we haven't any firewall rules as well.

atripp

Hi @monika-sadlok_5031,

That error means that the ProGet application container cannot make a network connection to the the SQL Server container.

I would try to restart the containers, start with SQL Server. Make sure it's running. If it's running, you can try connecting to it with another tool like SSMS if you'd like to verify.'

Otherwise, on the ProGet side, you can only configure the connection string; upgrading or changing the license key has zero impact on this. If it worked in the past, then it means that the SSQL Server container is not running or your network/container configuration changed.

This can be hard to discover exacgtly what changed, so I would recommend "starting from scratch" on a new server/environment, then compare/contrasting what changed. Sometimes it's as simple as a typo or an errant - (dash character) in the wrong place/script.

Cheers,
Alana