error while upgrading from v12 v131 - Using Umbraco and getting started

Meni 271 posts 528 karma points

Feb 01, 2024 @ 06:58

Error while upgrading from V12 -> V13.1

Hi, I'm trying to upgrade my website from V12 to V13.1

I was able to do it locally.

Then I did dotnet publish and copied \bin\Release\net8.0\publish\ folder to the ftp, and now I'm getting: HTTP Error 500.30 - ASP.NET Core app failed to start

(this time I made sure to create a lower dev region before I deploy to prod ... - so thankfully my website is up... , only dev is down ...)

Before copy to ftp , I went in Azure to Settings - configuration - General settings and changed from .NET 7 to .NET 8

I looked at the kudu eventlog.xml and this thing repeat itself along the file:

<Data>Application: w3wp.exe
CoreCLR Version: 7.0.222.60605
.NET Version: 7.0.2
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.DirectoryNotFoundException: C:\home\site\wwwroot\wwwroot\media\
   at Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(String root, ExclusionFilters filters)
   at Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(String root)
   at Umbraco.Cms.Core.IO.PhysicalFileSystem.Create()
   at Umbraco.Extensions.FileSystemExtensions.TryCreateFileProvider(IFileSystem fileSystem, IFileProvider&amp; fileProvider)
   at Umbraco.Cms.Core.IO.ShadowWrapper.Create()

and also

<Data>Application '/LM/W3SVC/1532634123/ROOT' with physical root 'C:\home\site\wwwroot\' hit unexpected managed exception, exception code = '0xe0434352'. First 30KB characters of captured stdout and stderr logs:
Unhandled exception. System.IO.DirectoryNotFoundException: C:\home\site\wwwroot\wwwroot\media\
   at Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(String root, ExclusionFilters filters)
   at Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(String root)
   at Umbraco.Cms.Core.IO.PhysicalFileSystem.Create()
   at Umbraco.Extensions.FileSystemExtensions.TryCreateFileProvider(IFileSystem fileSystem, IFileProvider&amp; fileProvider)
   at Umbraco.Cms.Core.IO.ShadowWrapper.Create()

And also

<Data>Application '/LM/W3SVC/1532634123/ROOT' with physical root 'C:\home\site\wwwroot\' failed to load coreclr. Exception message:
CLR worker thread exited prematurely</Data>
            <Data>Process Id: 3820.</Data>
            <Data>File Version: 18.0.23305.0. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: </Data>
        </EventData>
    </Event>
    <Event>
        <System>
            <Provider Name=".NET Runtime"/>
            <EventID>1026</EventID>
            <Level>1</Level>
            <Task>0</Task>
            <Keywords>Keywords</Keywords>
            <TimeCreated SystemTime="2024-02-01T06:47:18Z"/>
            <EventRecordID>-117778234</EventRecordID>
            <Channel>Application</Channel>
            <Computer>dw1sdwk0000ZX</Computer>
            <Security/>
        </System>
        <EventData>
            <Data>Application: w3wp.exe
CoreCLR Version: 8.0.23.53103
.NET Version: 8.0.0
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException: Could not load file or assembly 'BouncyCastle.Crypto, Version=1.9.0.0, Culture=neutral, PublicKeyToken=0e99375e54769942'. The system cannot find the file specified.
File name: 'BouncyCastle.Crypto, Version=1.9.0.0, Culture=neutral, PublicKeyToken=0e99375e54769942'
   at System.Reflection.RuntimeAssembly.InternalLoad(AssemblyName assemblyName, StackCrawlMark&amp; stackMark, AssemblyLoadContext assemblyLoadContext, RuntimeAssembly requestingAssembly, Boolean throwOnFileNotFound)
   at System.Reflection.Assembly.Load(AssemblyName assemblyRef)
   at Umbraco.Cms.Core.Composing.ReferenceResolver.ResolveAssemblies()
   at Umbraco.Cms.Core.Composing.FindAssembliesWithReferencesTo.Find()
   at Umbraco.Cms.Core.Composing.DefaultUmbracoAssemblyProvider.get_Assemblies()
   at Umbraco.Cms.Core.Composing.TypeFinder.GetAllAssemblies()

Any idea?

Thanks

Copy Link

Danny Paul van Iersel 14 posts 122 karma points

Feb 01, 2024 @ 07:33

Hello Meni,

I read some reports that there were issues in certain regions on Azure. Have you tried to install your solution on a clean app service?

You can try to run a console on your App Service and run "dotnet --info", to see if the correct version is running.

Kind regards, Danny Paul

Copy Link

Meni 271 posts 528 karma points

Feb 04, 2024 @ 07:14

Hi, thanks for the answer - should I contact Azure? If they have issues, they need to fix them asap

I just copied the publish folder through ftp (like I always do..)

I did dotnet --info and it said .NET 8

Copy Link

Mehmet Yildiz 3 posts 75 karma points c-trib

Feb 04, 2024 @ 09:29

The first two errors are about the media folder: Exception Info: System.IO.DirectoryNotFoundException: C:\home\site\wwwroot\wwwroot\media\

Did you check on the app service if the media folder exists? I have had an issue where the folder dissapeared after an update. If the folder is not there you can try manually creating it.

Copy Link

Meni 271 posts 528 karma points

Feb 04, 2024 @ 18:00

it's there

enter image description here

Copy Link

Meni 271 posts 528 karma points

Feb 09, 2024 @ 06:45

Hi, I tried to delete all the current files of the previous version (V12) and copied again the content of bin\Release\net8.0\publish\ through FTP.

This is what I'm getting now

enter image description here

And this what I get in the kudu log:

<Event>
    <System>
        <Provider Name="IIS AspNetCore Module V2"/>
        <EventID>xxxx</EventID>
        <Level>4</Level>
        <Task>0</Task>
        <Keywords>Keywords</Keywords>
        <TimeCreated SystemTime="2024-02-09T06:26:42Z"/>
        <EventRecordID>xxxx</EventRecordID>
        <Channel>Application</Channel>
        <Computer>xxxx</Computer>
        <Security/>
    </System>
    <EventData>
        <Data>Application 'C:\home\site\wwwroot\' started successfully.</Data>
        <Data>Process Id: 4692.</Data>
        <Data>File Version: 18.0.23334.1. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: </Data>
    </EventData>
</Event>
<Event>
    <System>
        <Provider Name="IIS AspNetCore Module V2"/>
        <EventID>xxxx</EventID>
        <Level>4</Level>
        <Task>0</Task>
        <Keywords>Keywords</Keywords>
        <TimeCreated SystemTime="2024-02-09T06:27:26Z"/>
        <EventRecordID>xxxx</EventRecordID>
        <Channel>Application</Channel>
        <Computer>xxxxx</Computer>
        <Security/>
    </System>
    <EventData>
        <Data>Application 'MACHINE/WEBROOT/APPHOST/XXXXX' has shutdown.</Data>
        <Data>Process Id: xxxx.</Data>
        <Data>File Version: 18.0.23334.1. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: </Data>
    </EventData>
</Event>
<Event>
    <System>
        <Provider Name="IIS AspNetCore Module V2"/>
        <EventID>1032</EventID>
        <Level>4</Level>
        <Task>0</Task>
        <Keywords>Keywords</Keywords>
        <TimeCreated SystemTime="2024-02-09T06:35:56Z"/>
        <EventRecordID>391233141</EventRecordID>
        <Channel>Application</Channel>
        <Computer>xxxxx</Computer>
        <Security/>
    </System>
    <EventData>
        <Data>Application 'C:\home\site\wwwroot\' started successfully.</Data>
        <Data>Process Id: xxxx.</Data>
        <Data>File Version: 18.0.23334.1. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: </Data>
    </EventData>
</Event>

Any idea?

Also, any other places I can check log besides the kudu console?

Thanks :)

Copy Link

Danny Paul van Iersel 14 posts 122 karma points

Feb 09, 2024 @ 08:02

Hello Meni,

Since the message comes from Umbraco about the Boot Failed. Is there any umbraco log file in "umbraco\Logs". maybe this gives some information why the boot failed.

Kudu log is for the environment it self (hosting of the website). Since the app does appear to start it only gives it started. If the app does not start at all (like in the beginning) you can find some information here.

Kind regards, Danny Paul van Iersel

Copy Link

Meni 271 posts 528 karma points

Feb 12, 2024 @ 02:26

Thank you so much!

I looked at umbraco\Logs and finally found the issue - had issue with the connection string.

To summarize: When upgrading to a new major version - first delete the current version, then copy the publish folder as a fresh install (Obviously make sure not to delete wwwroot and the media folder inside !!!! )

Copy Link

Danny Paul van Iersel 14 posts 122 karma points

Feb 12, 2024 @ 06:51

Hello Meni, Glad you got it figured out.

Copy Link

is working on a reply...

Flag this post as spam?

Error while upgrading from V12 -> V13.1