New Reply

Hi, I am trying to upgrade our ProGet from 5.1.23 to 5.2 but the upgrade failed during DB schema changes. After the failed upgrade the DB was corrupted and all registries were wiped and just the main web page was working. I done fresh 5.1.23 install on a test server to get copy of the registries keys and restore the DB from the backup. At the moment our server works fine but we could not upgrade.

We use ProGet as PowerShell and Chocolatey packages repository with intention to have some Python moved there. The server is visualised Windows Server 2012R2. The initial installation was 4.x (4.6 probably)
then we upgraded to 5.

How we can test is the problem with the DB or is it something in the schema upgrade script? Any other ideas for troubleshooting/fix are welcome.

Here it is the part of the log file with the error.

   Debug: Executing OBJECTS\4.PROCEDURES\1.Dashboards_GetFeedVulnerabilityAssessments.sql...
   Debug: Executing OBJECTS\4.PROCEDURES\1.Dashboards_GetLargestPackages.sql...
   Debug: Executing OBJECTS\4.PROCEDURES\1.DebianPackages_CreateOrUpdatePackage.sql...
   Error: Unhandled Exception: System.Data.SqlClient.SqlException: Cannot assign a default value to a local variable.
   Error: Must declare the scalar variable "@Package_Id".
   Error: Must declare the scalar variable "@Package_Id".
   Error:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   Error:    at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   Error:    at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   Error:    at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
   Error:    at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   Error:    at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   Error:    at Inedo.DbUpdater.SqlServer.SqlServerDatabaseConnection.ExecuteQuery(String query, SqlTransaction transaction)
   Error:    at Inedo.DbUpdater.SqlServer.SqlServerDatabaseConnection.ExecuteScripts(IEnumerable`1 scriptFiles)
   Error:    at Inedo.DbUpdater.Program.Update(String scriptPath, String connectionString)
   Error:    at Inedo.DbUpdater.Program.Main(String[] args)
   Debug: C:\Program Files\ProGet\WebApp restored.
   Debug: C:\Program Files\ProGet\Service restored.
   Debug: Starting service INEDOPROGETSVC...
   Debug: INEDOPROGETSVC service started.
   Error: System.InvalidOperationException: C:\Users\******\AppData\Local\Temp\ProGetSetup\SqlScripts\dbupdater.exe returned exit code -532462766


Product: ProGet
Version: 5.2.0

Here another upgrade error while upgrade from 5.1.23 to 5.2.2:

9.5.2019 06:44:15ProGet version is
9.5.2019 06:44:15Attempting to use shared configuration for ProGet.
9.5.2019 06:44:16Shared configuration file loaded from /usr/share/Inedo/SharedConfig/ProGet.config.
9.5.2019 06:44:16No encryption key is configured. Credentials will be stored in plain text.
9.5.2019 06:44:16Current DB schema version is unknown.
9.5.2019 06:44:17Determining which change scripts need to be run...
9.5.2019 06:44:1714 change scripts need to be run.
9.5.2019 06:44:1801. Connector name constraint.sql executed successfully.
9.5.2019 06:44:1810. Alter Connector Filter Column failed: 0A000: cannot alter type of a column used by a view or rule

I'm using it with postgres 9.5

The same error with 5.2.2 installer.

Hi Svet,

It looks like your first issue is due to SQL Server 2005 which we no longer support. Your 2nd issue about installing on a Postgres server is going to be something we have created support ticket for will be targeting for the next maintenance release.


Thanks Jason,

Do you suggest to install highest version of SQL Express and then try the upgrade?


P.S. The postgres issue is from Michael Kriese.

Yes. the latest version will work.

Answer Details


Post Reply