Installer crashing with no output

[Jim Tupper]

Upgrading from 3.10 (build 8)

On windows 2008r2, fully patched (now) running proget.setup.exe exits silently after unzipping

Application: ProGet.Setup.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Data.SqlClient.SqlException
Stack:
   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(System.Data.Common.DbConnection, System.Data.ProviderBase.DbConnectionFactory, System.Threading.Tasks.TaskCompletionSource`1<System.Data.ProviderBase.DbConnectionInternal>, System.Data.Common.DbConnectionOptions)
   at System.Data.SqlClient.SqlConnection.TryOpenInner(System.Threading.Tasks.TaskCompletionSource`1<System.Data.ProviderBase.DbConnectionInternal>)
   at System.Data.SqlClient.SqlConnection.TryOpen(System.Threading.Tasks.TaskCompletionSource`1<System.Data.ProviderBase.DbConnectionInternal>)
   at System.Data.SqlClient.SqlConnection.Open()
   at Inedo.ProGet.Setup.ProGetInstallerOptions.ReadDbInfo(System.Version)
   at Inedo.Installer.InstallerApplication.Run[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.String[])
   at Inedo.ProGet.Setup.App.Main(System.String[])

Product: ProGet
Version: 3.6.1

[Dean]

By default, the installer uses the same connection string configured for the ProGet service to connect to the database and run change scripts, etc. If you're using integrated SQL authentication, then the account you ran the installer from probably just doesn't have permission to access the ProGet database.

To troubleshoot this, make sure you can connect to the ProGet database from a tool like SQL Server Management Studio, or osql.exe.

We'll file a bug about improving the error message for this.

[Jim T]

You got me on the right track.

I think the problem was that I was upgrading with the default download, which includes sql-express. We installed using an existing version of sql-server.

I searched around a bit and found the upgrade without sql-express and it worked fine.

Cheers.

[Alana]

Thanks; we've identified a possible race condition during initialization, specifically involving discovering the connection string of the currently installed instance.

We've made a small code change which should resolve this issue - assuming it is the cause. We haven't been able to reproduce it on our systems. The installer for the next version (which should be 3.6.2) will have the fix, so you may want to try using the larger installer again just to see if the issue goes away. You never need the full installer to perform an upgrade, however.