Unfortunately there's nothing for us to go on here; with the limited information we have here, everything appears to be fine (the 401 is to be expected when you have an authenticated feed). Because you're using the unsupported VS2013 NuGet Plugin (which we cannot test with), and you upgraded from an a two-year old version of ProGet with a ton of changes between, we have no idea what is going on. We would need to know precisely which requests worked before (request/response), and precisely what it's doing now. Otherwise, you should just consider rolling back to 3.8.6 until you can upgrade to a supported version of Visual Studio.

You'll need to run bmdbupdate.exe. It doesn't need to be run on the database server itself; the user that runs it must have dbo permissions to the proget database.

Assuming ProGet.Service.exe is in C:\Program Files\ProGet\Service, there should be a folder named C:\Program Files\ProGet\WebApp. Does the WebApp folder exist?

Please make sure that the Amazon extension is downloaded. You can see which extensions are installed on the ADmin > Extensions page. When the service is loaded, the extensions are unzipped and put in the foloder you referenced.

We had switched to IIS hosting of the web site, and so the solution was to first stop the web site in IIS Manager before running the installer.

This means that your computer cannot connect to My.Inedo for alicense key. Please request one by logging into my.inedo.com.

This can be found in the lower-right of any page in the software.

I solved this by configuring the URL including port number in the Advanced Settings at "Web.BaseUrl"

ProGet for Linux is already out; it's shiped as a docker container. We have a lot of users who install ProGet on server core, but please note it's an advanced OS and requires a lot of commandline use. So, it's a bit more difficult to install ProGet on this. A ProGet Node is either the Web or Indexing Service. The "Load Balanced Only" comes with just three nodes, so for this yo you would have two web nodes and then Service node. An enterprise installation will have 5+ nodes, which typically is multiple services nodes (at least two) and then the rest web nodes. With automatic failover, basically if one of the indexing services becomes inactive, then the other takes over indexing duties. Sure, as long as the web and indexing service can access the files using the regular File IO (i.e. it shows up as a drive in windows), then you can use the regular disk package store for this.

Figured it out. It's not the user running the installation that needs db_owner membership. It's the SQL user (i.e. progetuser) created in the original setup that needs temporary db_owner membership for the upgrade process. Thanks.

Please note that this (or any multi-node) installation requires a ProGet Enterprise or ProGet Load Balanced License to be purchased. ProGet Basic and ProGet Free only permit a single server to be used in a single installation. That said, we recommend IIS because it's the easiest to support (by your own network admin team) and has many configuration options. In theory, you could probably use the integrated server. A HA configuration ought to use a SQL Cluster, otherwise you have a single point of failure.

Glad that worked! I created an issue for this; we should get this behavior a little more intuitive in an upcoming maintenance release.

Hi Alana, the EventView helped. Thanks for the hint. An SQL Error was noting that the "EXECUTE" permission was missing for the Database-User of ProGet. Once I fixed that, everything runs smoothly now.

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.

That was it. The user had access, but not permission to change schema. I really think this should be catch and a nicer message displayed instead of the installer just crashing though.

Ok, so I have now got something working. It seems it was failing because I had the smaller installer (without sql server). That does absolutely nothing when running the silent command. If that's meant to be the case, then maybe that should be documented somewhere. Thanks

I have renamed the roles just incase, but as soon as I upgrade to 4 it appears I get knocked out of the necessary task groups. Your user account does not have the Admin_ConfigureProGet task. I also get the same message if I don't change the role names.

You can install a separate website in IIS that points to the same home directory, which supports forms authentication, then use that separate URL for npm & bower. With a separate IIS site, upgrading won't touch it so it will upgrade as per normal with the installer.

Nevermind, apparently, the installation was messed up because of the failed previous upgrades (due to the antivirus). The program was not registered anymore so the installer didn't detect it for upgrade. I simply installed over the previous installation and it worked! Now running on 4.0.9! Thanks a lot for the info and help!

It's a false positive; see KB#1113 - Anti-malware False Positives, Code Signing, and Safety of Inedo Products for more information. Please let your malware protection provider know about the false positive; the more people who do, the greater the chance they won't flag these in the future.