Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Sebastian Dammark 581 posts 1385 karma points
    Feb 10, 2016 @ 10:49
    Sebastian Dammark
    0

    Problems upgrading from 7.2.6 to 7.3.7

    When I try to upgrade from 7.2.6 to 7.3.7 I get the attached error: enter image description here

    Here is a link to the error from the event viewer: https://www.dropbox.com/s/mixc7218f2bmgr7/event-error.txt?dl=0

    I've followed the General Upgrade guide and the version specific for 7.3.0

    I hope that anyone can see what I'm doing wrong.

  • Comment author was deleted

    Feb 10, 2016 @ 11:00

    Your DefaultAppPool is that set to the correct .net version (and managed pipeline mode) ?

  • Sebastiaan Janssen 5045 posts 15476 karma points MVP admin hq
    Feb 10, 2016 @ 11:06
    Sebastiaan Janssen
    2

    From your log:

    File name: 'System.Net.Http.Formatting, Version=5.2.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' ---> System.IO.FileNotFoundException: Could not load file or assembly 'System.Net.Http.Formatting, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

    I think the assembly bindings are missing or wrong in your web.config, they should look like:

    <runtime>
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
    
            <!-- Old asp.net ajax assembly bindings -->
            <dependentAssembly>
                <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" />
                <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="4.0.0.0" />
            </dependentAssembly>
            <dependentAssembly>
                <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" />
                <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="4.0.0.0" />
            </dependentAssembly>
    
            <!-- Ensure correct version of MVC -->
            <dependentAssembly>
                <assemblyIdentity name="System.Web.Helpers" publicKeyToken="31bf3856ad364e35" />
                <bindingRedirect oldVersion="0.0.0.0-3.0.0.0" newVersion="3.0.0.0" />
            </dependentAssembly>
            <dependentAssembly>
                <assemblyIdentity name="System.Web.WebPages" publicKeyToken="31bf3856ad364e35" />
                <bindingRedirect oldVersion="0.0.0.0-3.0.0.0" newVersion="3.0.0.0" />
            </dependentAssembly>
            <dependentAssembly>
                <assemblyIdentity name="System.Web.WebPages.Razor" publicKeyToken="31bf3856ad364e35" />
                <bindingRedirect oldVersion="0.0.0.0-3.0.0.0" newVersion="3.0.0.0" />
            </dependentAssembly>
    
            <!-- Ensure correct version of HtmlAgilityPack -->
            <dependentAssembly>
                <assemblyIdentity name="HtmlAgilityPack" publicKeyToken="bd319b19eaf3b43a" culture="neutral" />
                <bindingRedirect oldVersion="0.0.0.0-1.4.9.0" newVersion="1.4.9.0" />
            </dependentAssembly>
    
            <dependentAssembly>
                <assemblyIdentity name="System.Net.Http" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
                <bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0"/>
            </dependentAssembly>
    
            <dependentAssembly>
                <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
                <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
            </dependentAssembly>
    
            <dependentAssembly>
                <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" culture="neutral" />
                <bindingRedirect oldVersion="0.0.0.0-5.2.3.0" newVersion="5.2.3.0" />
            </dependentAssembly>
            <dependentAssembly>
                <assemblyIdentity name="System.Web.Http" publicKeyToken="31bf3856ad364e35" culture="neutral" />
                <bindingRedirect oldVersion="0.0.0.0-5.2.3.0" newVersion="5.2.3.0" />
            </dependentAssembly>
            <dependentAssembly>
                <assemblyIdentity name="Microsoft.Owin" publicKeyToken="31bf3856ad364e35" culture="neutral" />
                <bindingRedirect oldVersion="0.0.0.0-3.0.1.0" newVersion="3.0.1.0" />
            </dependentAssembly>
            <dependentAssembly>
                <assemblyIdentity name="Microsoft.Owin.Security.OAuth" publicKeyToken="31bf3856ad364e35" culture="neutral" />
                <bindingRedirect oldVersion="0.0.0.0-3.0.1.0" newVersion="3.0.1.0" />
            </dependentAssembly>
            <dependentAssembly>
                <assemblyIdentity name="Microsoft.Owin.Security" publicKeyToken="31bf3856ad364e35" culture="neutral" />
                <bindingRedirect oldVersion="0.0.0.0-3.0.1.0" newVersion="3.0.1.0" />
            </dependentAssembly>
            <dependentAssembly>
                <assemblyIdentity name="Microsoft.Owin.Security.Cookies" publicKeyToken="31bf3856ad364e35" culture="neutral" />
                <bindingRedirect oldVersion="0.0.0.0-3.0.1.0" newVersion="3.0.1.0" />
            </dependentAssembly>
            <dependentAssembly>
                <assemblyIdentity name="System.Net.Http.Formatting" publicKeyToken="31bf3856ad364e35" culture="neutral" />
                <bindingRedirect oldVersion="0.0.0.0-5.2.3.0" newVersion="5.2.3.0" />
            </dependentAssembly>
    
        </assemblyBinding>
    </runtime>
    
  • Sebastian Dammark 581 posts 1385 karma points
    Feb 10, 2016 @ 11:43
    Sebastian Dammark
    0

    My appPool looks like this: enter image description here

    And my bindings are looking exactly like yours.

    I'm running on IIS 8.5

  • Comment author was deleted

    Feb 10, 2016 @ 11:47

    And those assemblies it is complaining about are in the bin dir?

  • Sebastian Dammark 581 posts 1385 karma points
    Feb 10, 2016 @ 11:52
    Sebastian Dammark
    0

    I've merged everything between the 2 bin folders.

    Just like the upgrade guide says.

  • Comment author was deleted

    Feb 10, 2016 @ 11:54

    Hmm mind checking the permissions on the bin folder then

  • Sebastian Dammark 581 posts 1385 karma points
    Feb 10, 2016 @ 12:02
    Sebastian Dammark
    0

    IUSR, IIS_IUSRS have Modify access

    NETWORK SERVICE has Full Control

  • Comment author was deleted

    Feb 10, 2016 @ 12:03

    Same on web.config?

  • Sebastian Dammark 581 posts 1385 karma points
    Feb 10, 2016 @ 12:09
    Sebastian Dammark
    0

    Yes, they're inherited from the root folder.

  • Comment author was deleted

    Feb 10, 2016 @ 12:12

    Ok and your app pool runs as one of the identities that have access?

  • Sebastian Dammark 581 posts 1385 karma points
    Feb 10, 2016 @ 12:46
    Sebastian Dammark
    0

    Yes, but I think I've found something.

    The version specific guide for 7.3.0 says:

    Delete bin/System.Net.Http.*.dll (all dll files starting with System.Net.Http)

    So since 7.3.0 is between my version and the latest release I followed the guide and deleted 'System.Net.Http.Formatting'.

    Apparently I shouldn't do that, so I moved them back :)

    So now I get this error enter image description here

    And here are the details: https://www.dropbox.com/s/vrkc4fjvtnkc22q/event-error2.txt?dl=0

  • Comment author was deleted

    Feb 10, 2016 @ 12:57

    Great a step forward :) is there a valid connectionstring in the web.config ?

    Seems the error you are getting now is

    A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.

  • Sebastian Dammark 581 posts 1385 karma points
    Feb 10, 2016 @ 13:07
    Sebastian Dammark
    1

    Yes, it's valid. I can use the same credentials to connect via SMSS.

    This solved it for me: http://stackoverflow.com/questions/17615260/the-certificate-chain-was-issued-by-an-authority-that-is-not-trusted-when-conn

    The site is an Azure site that I've downloaded for the upgrade.

  • Comment author was deleted

    Feb 10, 2016 @ 13:12

    Glad it's solved :)

  • Comment author was deleted

    Feb 10, 2016 @ 12:59
  • Sebastian Dammark 581 posts 1385 karma points
    Feb 10, 2016 @ 13:14
    Sebastian Dammark
    0

    Thanks a lot for your help guys.

  • Sebastian Dammark 581 posts 1385 karma points
    Feb 10, 2016 @ 15:34
    Sebastian Dammark
    0

    Apparently, I'm not quite out of the woods yet.

    All problems where gone, in the back end. But my fronted still fails, like this. enter image description here

    And here is the log file from the Event Viewer: https://www.dropbox.com/s/3i53e91k1d31d1a/event-error3.txt?dl=0

    If I remove 'Microsoft.Web.Helpers.dll' from the 'bin', the backend works flawlessly, but the frontend still fails.

  • Markus The 10 posts 31 karma points
    Feb 11, 2016 @ 13:09
    Markus The
    1

    I had the exact same problem, but solved it by updating ~/Views/web.config, which for some reason still contained a reference to Microsoft.Web.Helpers:

      <system.web.webPages.razor>
        <host factoryType="System.Web.Mvc.MvcWebRazorHostFactory, System.Web.Mvc, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
        <pages pageBaseType="System.Web.Mvc.WebViewPage">
          <namespaces>
            <add namespace="System.Web.Mvc" />
            <add namespace="System.Web.Mvc.Ajax" />
            <add namespace="System.Web.Mvc.Html" />
            <add namespace="System.Web.Routing" />
            <add namespace="Umbraco.Web" />
            <add namespace="Umbraco.Core" />
            <add namespace="Umbraco.Core.Models" />
            <add namespace="Umbraco.Web.Mvc" />
            <add namespace="Microsoft.Web.Helpers" /><!-- PROBLEM HERE -->
            <add namespace="umbraco" />
            <add namespace="Examine" />
          </namespaces>
        </pages>
      </system.web.webPages.razor>
    

    Replacing this file with the one from the 7.3.7 zip-download solved the problem.

    (It explains why the backend works - it does not render any of your views, which the frontend does!)

    I hope that solves your problem, too! It took me three hours to track down...

  • Sebastian Dammark 581 posts 1385 karma points
    Feb 18, 2016 @ 17:09
    Sebastian Dammark
    0

    Yep, that and the ClientDependency issue fixed it for me.

Please Sign in or register to post replies

Write your reply to:

Draft