@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.

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

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.38

System.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, TaskCompletionSource1 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(TaskCompletionSource1 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

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

Hi @dean-houston

Thank you for the ultra-quick response. Disabling that feature did indeed provide a workaround solution and currently testing is back on track.

Thanks again
Darren

The following is from the proget log if it helps:

An error occurred processing a GET request to https://<server url>/nuget/Chocolatey/package/nxlog/2.11.2190: 22001: value too long for type character varying(15)

Npgsql.PostgresException (0x80004005): 22001: value too long for type character varying(15)
   at Npgsql.Internal.NpgsqlConnector.ReadMessageLong(Boolean async, DataRowLoadingMode dataRowLoadingMode, Boolean readingNotifications, Boolean isReadingPrependedMessage)
   at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token)
   at Npgsql.NpgsqlDataReader.NextResult(Boolean async, Boolean isConsuming, CancellationToken cancellationToken)
   at Npgsql.NpgsqlDataReader.NextResult(Boolean async, Boolean isConsuming, CancellationToken cancellationToken)
   at Npgsql.NpgsqlCommand.ExecuteReader(Boolean async, CommandBehavior behavior, CancellationToken cancellationToken)
   at Npgsql.NpgsqlCommand.ExecuteReader(Boolean async, CommandBehavior behavior, CancellationToken cancellationToken)
   at Inedo.ProGet.Data.PostgresDatabaseContext.PostgresCommand.ExecuteReaderAsync(CancellationToken cancellationToken)
   at Inedo.Data.DatabaseContext.DbResult.CreateAsync(IGenericDbCommand command, DatabaseContext context, DateTimeOffset startTime, Stopwatch stopwatch)
   at Inedo.Data.DatabaseContext.ExecuteInternalAsync(String storedProcName, GenericDbParameter[] parameters, DatabaseCommandReturnType returnType)
   at Inedo.Data.DatabaseContext.ExecuteNonQueryAsync(String storedProcName, GenericDbParameter[] parameters)
   at Inedo.ProGet.Feeds.StandardCanonicalPackageFeed`5.<>c__DisplayClass15_0.<<DownloadPackageAsync>g__recordAsync|0>d.MoveNext()
--- End of stack trace from previous location ---
   at Inedo.ProGet.Feeds.StandardCanonicalPackageFeed`5.DownloadPackageAsync(TPackage package, IPackageDownloadContext context, OpenPackageOptions options, PackageInstallContext installContext, CancellationToken cancellationToken)
   at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi.GetHandler.TransmitPackageAsync(AhHttpContext context, WebApiContext apiContext, ICanonicalNuGetPackage package, String packageFileName, Boolean includeSymbols, Boolean includeSource, Boolean includeSignature, NuGetFeed feed)
   at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi.GetHandler.ProcessGetRequestAsync(AhHttpContext context, WebApiContext apiContext, RequestData urlData, NuGetFeed feed)
   at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetApi.ProcessRequestAsync(AhHttpContext context, WebApiContext apiContext, NuGetFeed feed, String relativeUrl)
   at Inedo.ProGet.WebApplication.FeedEndpoints.NuGet.NuGetFeedHandler.ProcessRequestAsync(AhHttpContext context, WebApiContext apiContext, NuGetFeed feed, String relativeUrl)
   at Inedo.ProGet.WebApplication.FeedEndpoints.FeedEndpointHandler.FeedRequestHandler.ProcessRequestAsync(AhHttpContext context)
  Exception data:
    Severity: ERROR
    SqlState: 22001
    MessageText: value too long for type character varying(15)
    Where: SQL function "PackageDownloads_AddDownload" statement 1
    File: varchar.c
    Line: 640
    Routine: varchar

::Web Error on 04/06/2025 15:29:51::

Hi

Have been running a the last couple of releases uses the new PostgreSQL backend and have come across an issue.

I have downgraded back to a few previous versions just to confirm the issue has occured since the first database upgrade.

We are in the process of migrating from an old proget 5 server to a new proget 2024 server, and we use it mainly as a choco rep for our puppet system.

Testing an choco install today I noticed that all choco installs that use the proget server fail with 'The remote server returned an error: (500) Internal Server error'

Testing the exact same command against our Proget 5 system the command still works and the choco package installs.

Working command from proget 5:
choco install nxlog --version 2.11.2190 --source https://<server url>/nuget/Chocolatey/

Failing command from proget 2024:
choco install nxlog --version 2.11.2190 --source https://<server url>/nuget/Chocolatey/

Obviously I have omitted the server URL.

This all worked in 2024 prior to upgrading from MSSQL to PostgreSql

So, the error choco gives when using proget 2024 as the source is:

nxlog not installed. An error occurred during installation:
Error downloading 'nxlog.2.11.2190' from 'https://<server url>/nuget/Chocolatey/package/nxlog/2.11.2190'.
sysmon package files install failed with exit code 1. Performing other installation steps.

is 22001: value too long for type character varying(15)

Whereas is if you use the same URL for the old proget server (obviously changing the server url) the package downloads

So, it appears that since the upgrade to PostGreSQL some column in a table somewhere is now maxing out at a 15 character limit causing the system to fail.

Is this a known issue, or does anyone have any suggestions on how to resolve rather than revert back to MS SQL?

Thanks
Darren