DNN Forums

Ask questions about your website to get help learning DNN and help resolve issues.

Continuous 302 after upgrading to 9.7.1

Sort:
You are not authorized to post a reply.





Growing Member





    After updating my localhost to 9.7.1 many, but not all, of my portals are exhibiting this error when you try to load them:

    09/12/2020 13:37:10
    Page Load Exception

    AbsoluteURL:/dotnetnuke/Default.aspx

    DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke

    ExceptionGUID:1d275430-4210-4d82-9da3-6b79eb26c4b1

    AssemblyVersion:9.7.1

    PortalId:27

    UserId:-1

    TabId:1400

    RawUrl:/dotnetnuke/

    Referrer:

    UserAgent:Mozilla/5.0 (Windows NT 10.0; rv:80.0) Gecko/20100101 Firefox/80.0

    ExceptionHash:8qYLdWOa6Jr9thoH1Lrm5TNLA8I=

    Message:Object reference not set to an instance of an object.

    StackTrace:

    InnerMessage:Object reference not set to an instance of an object.

    InnerStackTrace:

       at DotNetNuke.Services.Tokens.BaseCustomTokenReplace.ReplaceTokens(String sourceText)
       at DotNetNuke.Services.Tokens.TokenReplace.ReplaceTokens(String sourceText)
       at DotNetNuke.UI.Skins.Controls.Language.parseTemplate(String template, String locale)

    Source:

    FileName:

    FileLineNumber:0

    FileColumnNumber:0

    Method:

    A Network Trace in the browser shows that 302 redirects back to the same url repeat til the end. 

    The Logfile at Portals\_Default\Logs shows this:

    2020-09-12 13:35:14,116 [SPORT][Thread:5][ERROR] DotNetNuke.Framework.Reflection - iSearchable
    System.Web.HttpException (0x80004005): Could not load type 'iSearchable'.
       at System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase)
       at DotNetNuke.Framework.Reflection.CreateType(String TypeName, String CacheKey, Boolean UseCache, Boolean IgnoreErrors)
    2020-09-12 13:37:10,726 [SPORT][Thread:15][ERROR] DotNetNuke.Services.Exceptions.Exceptions - /dotnetnuke/
    System.NullReferenceException: Object reference not set to an instance of an object.
       at DotNetNuke.Services.Tokens.BaseCustomTokenReplace.ReplaceTokens(String sourceText)
       at DotNetNuke.Services.Tokens.TokenReplace.ReplaceTokens(String sourceText)
       at DotNetNuke.UI.Skins.Controls.Language.parseTemplate(String template, String locale)
    2020-09-12 13:37:10,757 [SPORT][Thread:15][ERROR] DotNetNuke.Services.Exceptions.Exceptions - /dotnetnuke/
    System.Threading.ThreadAbortException: Thread was being aborted.
       at System.Threading.Thread.AbortInternal()
       at System.Threading.Thread.Abort(Object stateInfo)
       at System.Web.HttpResponse.AbortCurrentThread()
       at System.Web.HttpResponse.End()
       at System.Web.HttpResponse.Redirect(String url, Boolean endResponse, Boolean permanent)
       at DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL)
       at DotNetNuke.UI.Skins.Controls.Language.parseTemplate(String template, String locale)
       at DotNetNuke.UI.Skins.Controls.Language.handleCommonTemplates()
       at DotNetNuke.UI.Skins.Controls.Language.OnLoad(EventArgs e)

    Which then repeats. The theme used is Xcillion. I've tried restoring 9.6.2 from backup and updating all modules to their latest versions, then updating to DNN 9.7.1, but this problem remains.  Some portals do work, but they do not use the Xcillion theme. No portals that use Xcillion work; they just give this error. I am not using the token replace feature on these home pages.

    I read somewhere that if an error occurs in certain ways, it causes a redirect to the root/home page. That would explain the continuous redirects, but how do I find the initial cause?






    Veteran Member





      I believe that this is an issue. There is a workaround, so please to back to https://github.com/dnnsof...nn.Platform/releases and read the updated release notes for 9.7.1 which describes the issue and the workaround.

      There is also a release candidate for 9.7.2 which, when released, should fix the issue.
      Joe Craig
      DNN MVP
      Patapsco Research Group





      Growing Member





        Thanks Joe!!  Don't know how I missed that.

        Love how the Community helps each other out.

         






        Veteran Member





          You probably didn't miss it. The release notes were updated after the issue was discovered and the workaround figured out.

          Yes, we are all here to help one another out ... and it works!
          Joe Craig
          DNN MVP
          Patapsco Research Group
          You are not authorized to post a reply.

          These Forums are dedicated to the discussion of DNN Platform.

          For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

          1. If you have (suspected) security issues, please DO NOT post them in the forums but instead follow the official DNN security policy
          2. No Advertising. This includes the promotion of commercial and non-commercial products or services which are not directly related to DNN.
          3. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
          4. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
          5. No Flaming or Trolling.
          6. No Profanity, Racism, or Prejudice.
          7. Site Moderators have the final word on approving / removing a thread or post or comment.
          8. English language posting only, please.

          Would you like to help us?

          Awesome! Simply post in the forums using the link below and we'll get you started.

          Get Involved