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 2024.37(8) to 2025 Fails to Upgrade
-
Currently running Proget 2024.37 using it's own internal web server and PostGreSql database.
Just attempted to upgrade to Proget 2025 and it fails with the below error, and the service will not start.
Reverted back to 2024.37 and upgraded to 2024.38 which worked with no problems
Tried to upgrade 2024.38 to 2025 and got the same error.
I cannot see any steps I am missing to upgrade to 2025, but currently seem stuck not being able to upgrade from 2024.
Note, that due to the server being off internet - I always use the offline installers from https://my.inedo.com/downloads/installers
The error I am getting is :
** (unnamed scope) **
** (unnamed scope) **
ERROR: Error processing template InstallProduct: Line 39: Error: Unknown operation "InedoInternal::Create-SymbolicLink".Any suggestions to be able to upgrade this instance to 2025 would be grateful, as I am ready to put this server live and replace our old 5.3 server with it.
Thanks
Darren
-
A bit more testing, and one other thing of note - not sure if related or not.
I migrated to Postgresql a few versions back (as soon as you enabled it), and Proget confirms I am running Postgresql.
However, the MS SQL service IS still running (the upgrade never stopped the service)
If I stop the MS SQL service, Proget continues to function as expected as it not using it.
However, if I try to run the upgrade application (any version 2024 or 2025) with MS SQL stopped, I do not get the option to upgrade as the upgrade application still seems to want to talk to MSSQL.
So it seems the offline InedoHub installer still tries to talk MSSQL even though Proget is using PostGresql?
Error trying to launch installer with MSSQL stopped:
Product: ProGet
Version: 24.0.38System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling, SqlAuthenticationProviderManager sqlAuthProviderManager)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource
1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions) at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource
1 retry)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at Inedo.Hub.Data.InstalledProduct.ScrapeFromInstallation(String targetPath)
ClientConnectionId:00000000-0000-0000-0000-000000000000
Error Number:-1,State:0,Class:20
-
Thanks for all of the information! Installer issues take a bit to debug through, but we are looking into this now. Please hang tight and should have an update later today or early tomorrow morning on this.
Thanks,
Rich
-
This looks like it was caused by us packaging an old version of Inedo Hub as part of the offline installer. We'll have it fixed for the 2025.1 release which will go out this week.
-
Thanks for the quick reply.
Good to know it is nothing I have done on my end. I'll keep an eye out for the next release and give it a go.
Thanks Again
Darren
-
Hi Darren,
We pushed a new installer last night and you should be able to use that to upgrade now.
Thanks,
Rich
-
@rhessinger Hi. Been looking at the new installer and testing all day ( I noticed it after I posted this morning)
Can confirm the offline installer upgraded from 2024.38 to 2025.1 with no issues.
Even better, the installer worked with MSSQL disabled, so the reliance on MSSQL running also seems to have gone.
Now happily running 2025.1 use internal web server and PostGreSQL - thanks for you quick response and fix.
-