ProGet web page fails to load -- fresh install

Hi,

We've installed the free version of ProGet on our Windows 2012 server for evaluation. All default values were used during installation. We choose to use existing SQL Server instance (SQL Server 2014). We also chose to use the integrated web server. Installation was completed without error.

However, the page at localhost:81 fails to load (ERR_CONNECTION_REFUSED). There doesn't appear to have been any errors in creation of the database ProGet within our SQL Server instance. The ProGet service appears to be running without error although it takes a very long time to start. While the service is starting, a series of login failures occur on our SQL Server with the following text:

Login failed for user 'OUR_DOMAIN\SERVER-NAME$'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]

Product: ProGet
Version: 4.0.8

In this case, the account you configured ProGet to run under does not have permission to access the database. You will need to either grant access to ''OUR_DOMAIN\SERVER-NAME$' on SQL Server, or change the ProGet service credentials to an account with privileges. Generally speaking, the service account should have minimal privileges (ProGetUSer_Role only).

The account you installed ProGet with did have dbo privileges (which is required to make database changes), which is why it installed fine.

Hi Alana,

Thanks for your reply. Still having trouble.

I checked the ProGet service configuration. It's set to log on as the "NETWORK SERVICE" account. This was the default choice during the installation process. I also verified that the "NETWORK SERVICE" account is present in the ProGet database users list and is a member of the database role ProGetUser_Role. This is proper configuration, no?

I can't follow your first suggestion of granting access to "OUR_DOMAIN\SERVER-NAME$" to my knowledge because that is actually a machine name, not a user account.

This is a Windows Integrated Authentication issue.

Keep in mind that "NETWORK SERVICE" is always a local machine account. Your SQL Server is on a different machine, so the "NETWORK SERVICE" on that machine is not the same as the "NETWORK SERVICE" on the ProGet machine.

When a local/machine account tries to use Windows Integrated Authentication, it will always come through as OUR_DOMAIN\SERVER-NAME$. This is why you need to grant the machine access, or use a domain account.

The other option is to not use Integrated Authentication, and instead use SQL Authentication (name/password) in your connection strings.

Thank again Alana. I opted to use SQL authentication instead of integrated security and all is well now. Still not sure why "NETWORK SERVICE" wasn't working before since the installation is entirely local (SQL Server database was not on a separate machine).

I bumped into this issue as well. It turns out if you wanna use existing local SQL server, you need to add an account "NT AUTHORITY\NETWORK SERVICE" to your SQL database. To be clear, this account is added to ProGet database during installation but it didn't mark as "Public" in server role.