I'm assuming you're storing media in Azure?

As of Umbraco 11, the Umbraco.StorageProviders.AzureBlob package was split in two.

You need to make sure both Umbraco.StorageProviders.AzureBlob and Umbraco.StorageProviders.AzureBlob.ImageSharp are installed and configured for things to continue working as they did under Umbraco 10.

https://docs.umbraco.com/umbraco-cms/extending/filesystemproviders/azure-blob-storage

The issue is caused by an incorrect database connection string. The call stack mention of ImageSharpMiddleware seems to be a bit of a red herring.

In this case the connection string needs to have ;TrustServerCertificate=True appended as the default used by the .NET SQL database library is now False.

Step 8: https://docs.umbraco.com/umbraco-cms/fundamentals/setup/upgrading#upgrade-your-project-using-visual-studio.

Credits: https://our.umbraco.com/forum/using-umbraco-and-getting-started/112407-umbraco-v12-exception-at-startup-when-run-in-docker

We already have "TrustServerCertificate=True" in our connection string, but still the same issue.

Step done for migration was.

1. Change the .net version from ".net 6" to ".net 8"
2. Update the umbraco version "10.0.0" to latest i.e. "13.0.3".
3. Added "TrustServerCertificate=True" in connection string.

4. updated the program.cs

   WebApplicationBuilder builder = WebApplication.CreateBuilder(args);
   

   builder.CreateUmbracoBuilder().AddBackOffice().AddWebsite().AddComposers().Build();

       WebApplication app = builder.Build();
   
   
   await app.BootUmbracoAsync();
   
   
   app.UseUmbraco()
       .WithMiddleware(u =>
       {
           u.UseBackOffice();
           u.UseWebsite();
       })
       .WithEndpoints(u =>
       {
           u.UseInstallerEndpoints();
           u.UseBackOfficeEndpoints();
           u.UseWebsiteEndpoints();
       });
   
   
   await app.RunAsync();
   
   
   

5. Clean and rebuild the solution.

FYI : The same connection string is working fine with newly created umbraco 13.0.3 project.

Is there anything that we are missing or is there any other way to get more details about the issue.

I'd suggest disabling all your custom or 3rd party middleware references and then see if the site starts up, as at this point you're presumably just interested in getting Umbraco to work?

If that does work then enabling them one by one should help you narrow this down, as it doesn't sound like a problem with Umbraco itself if your clean solution is running ok.

Hi,

Thanks for reply,

We are not using any 3rd party middleware.

I have a similar issue, but mine is upgrading from V 11.0.0 to 13.1.1.

It was from a blank solution Umbraco Solution this is the error I get

is working on a reply...