Please refer to this topic for help uninstalling the product.

Apologies - I broke that endpoint earlier ironically by accidentally disabling logging :( It should work now; I also note that you can request a key at https://my.inedo.com and manually enter it.

Great to hear it got fixed. Thanks !

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

Hi Benedikt, We haven't been able to reproduce this, and I don't see any instances in the installer code where SQL connections are not released immediately after being used. What do you mean that it was not possible to install SQL Express with our installer? Did it fail with an error, or was the option disabled?

Thanks for the additional troubleshooting. I suspect this is due to the way we are migrating dates from the old table to the new. I've created an issue to track this here. (It may not be publicly accessible yet, it's a new project and the permissions may not have propagated)

Thank you so much, build master now works.

Hi Alana, Thanks its working fine now.

It's hard to say, but if you're not seeing anything come up when you visit the web interface.. it sounds like the web server or IIS isn't running or otherwise configured. The error you shared from the Windows Service would verify this (the service cannot talk to the web application either). Take a look at the Manual Installation Instructions to see if you can identify how things are mis-configured.

There appears to be a problem with the windows service manager. I recommend you to reboot the server, and try again. If that fails, you can use the manual installation instructions.

This must be it, redownload solved it. I downloaded 5.6.11 sometime on Apr 4.

Aside from following the general back-up/restore instructions (database / package store / config files), there's nothing else to configure on ProGet. If you're getting errors, then something wasn't migrated properly. If a different file path is reported in an error, then a different file path is configured in the new instance; check out the error message under ADmin > Errors to see what the 500 was getting.

When you un/re-install ProGet, it will not delete the database unless you explicitly say to. If you run the service interactively (just run the ProGet.Service.exe), there is an option to reset the admin account permissions.

Hi Christian, the information you posted had mentioned internal packages (Aeon Framework, etc), so I removed it That said, it wasn't an error message, but a JSON document that contained metadata information about packages. This is an expected response if you visit an API URL directly in your browser, and when the npm client relies on the JSON data. If you are receiving an error from the npm client, please make sure to share: the precise error message that npm client is using the precise URL that the npm client is requesting; you can get this by running Fiddler, and seeing the requests that the client makes Note that you will need to disable Windows Integrated Authentication at the IIS level, not just within ProGet.

Please refer to the High-level Architecture Diagram to see the components of a ProGet installation. The Database is a SQL Server database. The Web and Indexing Nodes are both .NET application that interact with the database using the standard SqlClient API. The connection string you specify in the configuration file is assigned to the ConnectionString property of that API. All of this is very standard, but it's very likely that your DBA/Network Admins configured the SQL Server you wanted to use in such a way that a simple/intuitive connection string was not sufficient. Maybe they used a special port, security, etc.; they would be much better suited to answer your question about why it's so complicated :) Also, please note that the ProGet Installer will create/update the tables and object in the database. ProGet itself does not modify (nor have the privileges to modify by default) the database structure. If you wish to install the database component outside of the installer, then you will need to follow the Manual Installation Instructions.

Hello; you can request a key from my.inedo.com, and then enter that in the installer. Once installed, there will be activation instructions (because the software can't auto-activate). No internet access is required to install or use BuildMaster.

Good point; we can add a note to the guide to consider those when you migrate/backup a server. But, it's very easy to do; just copy whatever you have in the extensions folder (i.e. one with .bmx files), and copy them to the new server's folder. Then, restart web app and service, and it will function the same as if you had just downloaded them from Inedo.com

Make sure that the service has started; if it's not, then investigate the windows error log to see if anything in there occur when you attempt to start it. Make sure there are no firewalls, or other tools are preventing access from that port being accessed.

ProGet on IIS is only supported as a root level web site of IIS - it cannot be a virtual directory of another application. If this is not an option, you'll have to go with the built-in web server option.