Please refer to this topic for help uninstalling the product.

I would try to reboot the server; sometimes the windows service manager caches information that makes it hard to detect. Next, it could be that you don't have permission to view the service. You can use a tool like sc.exe to unregister the service. Then, it should work

Yes. the latest version will work.

Hi Alana, Thanks for the information. I've reinstalled ProGet and IIS several times and at attempt four it suddenly worked fine. So I'm not touching the setup anymore and will keep it as-is now! Thanks, Eelko

I would try reinstalling it. I didn't have to create the site in IIS.

Great to hear it got fixed. Thanks !

This is on the all versions page, just click "Traditional Installer".

The connection string used by ProGet is stored in its configuration file (see this documentation page for the format and location). The Windows user account used is whatever user the INEDOPROGETSVC service is running under - generally, ProGet configures this to be NetworkService, but could be configured to be any user account.

These are available on the All Versions page: https://inedo.com/proget/versions

Yes, it just involves changing the license key. Please refer to License Key Management

You can request a free key at https://my.inedo.com/

Ok, I use this KB 2 days ago and i added netbios name, fqdn but same problem. I try to change the user context but same pb. Error 503 - service unvailabable I will change my stack of web and i will go to install IIS...but is strange for an editor to indicate don't use "web integrade proget server" Thanks.

After more investigation I discovered the problem was due to lack of permissions on the Storage folder assigned (DOH!). Would be a good idea to improve the ProGet error message as you indicated so it gives a more helpful clue. Thanks for your help. Dwight

Thank you Alana. That worked.

hi Keith, We definitely plan on having an offline process, and welcome your feedback on it. You can read a bit about how the hub works (it's in beta, so please forgive the rough docs). Specifically, check out "Configuration and Offline Installs": https://inedo.com/support/documentation/proget/installation/hub/inedo-hub The Inedo Hub wraps Romp (more coming soon on that), so you could also use that to install ProGet as well, as a command line process. Does that help?

Thanks for letting us know. We are totally redoing our installer soon, so we will probably take care of it then! I think, generally, you might want to install SQL separately when going automated. When SQL fails to install, it's not so graceful, and it will be harder to tell what went wrong when diagnosing a failed ProGet installation

I'm not sure why, but looking at .11 and .12, they would only impact Windows installations, so you can just use .10 or upgrade to v5.

That's the default root directory. Each feed can be customized to have its own path (or use a different storage provider, like Amazon S3).

When this build finishes, docker pull inedo/proget will fix the issue with special characters in the database password: https://hub.docker.com/r/inedo/proget/builds/bi8ds7thvriyfldkbh2daj6/

Hello I installed it using your integrated database installation.