Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
ProGet upgrade migrates wrong DB
-
We currently have 2 instances of ProGet talking to the same SQL server instance. The first uses the db name "proget" the second uses "proget2018".
On the second server this value is specified via the "Initial Catalog" argument in the connection string. The connection string is presented correctly with "Initial Catalog = proget2018" when prompted before upgrade from the InedoHub. After upgrade the connection string gets reset with "Initial Catalog = proget" resulting in the data being shown from the first server. It looks like schema upgrades are being applied to "proget" rather than "proget2018" during the upgrade.
Is there any way to fix this?
Product: ProGet
Version: 5.1.6
-
Hi Martin,
Thanks for reporting this problem. We do make the standard (old) installer available as well so it can be used in case of bugs like this with the new one. We will issue an update for InedoHub to fix this, but for now you can still use the old installer (available here under the "Traditional Installer" links).