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!
Update failed due to unhandled SqlException
-
We tried to update ProGet from 5.1.8 to 5.1.9 and the Updater (Offline Installer) ran into the following exception:
Debug: Executing OBJECTS\4.PROCEDURES\1.NuGetPackagesV2_SetListed.sql...
Error: Unhandled Exception: System.Data.SqlClient.SqlException: Incorrect syntax near '('.
Error: Must declare the scalar variable "@NuGetPackageV2_Id".I we try to start the updater again it doesn't offer to update ProGet any more but wants to install a new version instead.
I attached the complete logfile to Ticket [EDO-5296]
Product: ProGet
Version: 5.1.9
-
It looks like we inadvertently used T-SQL syntax that requires SQL Server 2008 or newer for that script, and I assume you are running SQL 2005. Though we don't officially support SQL Server 2005 anymore, it wasn't that long ago that we were bundling it with our installers so we try not to break compatibility with it. That said, sometimes this type of thing can slip through our reviews.
We'll see about getting this fixed for the next release, or at least making sure we add a warning/error to the installer if an older SQL is detected.
If your ProGet installation still working (even though the installer won't let you upgrade it)?
-
We use the SQL Server that came bundled with the ProGet Installation in the assumption that this will cause least incompatibilities. If you advice us to do so we can easily move the database to our SQL Server cluster that is currently running Microsoft SQL Server 2016.
Will that fix the installer issue we ran into?
Our ProGet installation is still working on the old version because we run ProGet on a virtual machine and take snapshots before upgrading. Due to the error we rolled back the snapshot and are on 5.1.8 again.
-
Yes, that would fix the installer issue and we do recommend moving to SQL Server 2016. The bundled SQL 2005 instance in the old installer was intended more for quick setup for evaluation purposes rather than production use, but we did a very poor job of making that clear. We are fixing that now; we're working on updating all of our installers to detect the SQL Server version and suggest/require an upgrade.
Here is the current article about SQL Server requirements - basically it's any version currently supported by Microsoft.
Sorry for the confusion, and hope this helps!