DNN Forums

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

Cant log in. ASP.NET error CS0433

Forums > Administration and Configuration
Sort:
You are not authorized to post a reply.





Shawn

New Around Here



Posts:5
New Around Here




7/19/2019 10:38 AM

    We have a site that recently began to experience issues. Users could not edit, or delete modules on the homepage, but could on other pages of the site. After looking at several things we decided to do a minor version upgrade from 7.03 to 7.04 backed up files and the database before performing the upgrade. The upgrade failed early on at updating the database. All permissions are correct in SQL, and the web.config file was set up correctly. I restored the files, and the DB. Now all aspects of the site are functioning as they should be, but users cannot login to the site. When clicking the login link it goes to a page diplaying "500-Internal Server Error". If browsing to the login while on the host it presents a blank page with a return to site button, and it states "DNN Error - An unhandled error has occured" When forcing the site to go to the login page by appending /Admin/SiteSettings.aspx?ctl=login to the url it just goes to a blank screen.

    Looking in logs it appears to be an ASP.NET error. After clicking the login link the following error is instantly generated.

    2019-07-19 10:05:38,905 [WEBSERVER-16][Thread:42][ERROR] DotNetNuke.Services.Exceptions.Exceptions - DotNetNuke.Services.Exceptions.PageLoadException: c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\5da6535d\a64f1f9e\App_Web_modulemessage.ascx.69b0ef64.tqhr7jnl.0.cs(432): error CS0433: The type 'DotNetNuke.Web.UI.WebControls.DnnScriptBlock' exists in both 'c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\5da6535d\a64f1f9e\assembly\dl3\6f101b7b\001338b7_8ff9d101\DotNetNuke.Web.Deprecated.DLL' and 'c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\5da6535d\a64f1f9e\assembly\dl3\a36825cb\0054fd68_a9f7cf01\DotNetNuke.Web.DLL' ---> System.Web.HttpCompileException: c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\5da6535d\a64f1f9e\App_Web_modulemessage.ascx.69b0ef64.tqhr7jnl.0.cs(432): error CS0433: The type 'DotNetNuke.Web.UI.WebControls.DnnScriptBlock' exists in both 'c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\5da6535d\a64f1f9e\assembly\dl3\6f101b7b\001338b7_8ff9d101\DotNetNuke.Web.Deprecated.DLL' and 'c:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\5da6535d\a64f1f9e\assembly\dl3\a36825cb\0054fd68_a9f7cf01\DotNetNuke.Web.DLL'
       at System.Web.Compilation.AssemblyBuilder.Compile()
       at System.Web.Compilation.BuildProvidersCompiler.PerformBuild()
       at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath)
       at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
       at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
       at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath)
       at DotNetNuke.UI.Skins.Skin.GetModuleMessageControl(String heading, String message, ModuleMessageType moduleMessageType, String iconImage)
       at DotNetNuke.UI.Skins.Skin.AddPageMessage(Control control, String heading, String message, ModuleMessageType moduleMessageType, String iconSrc)
       at DotNetNuke.UI.Skins.Skin.OnInit(EventArgs e)
       at System.Web.UI.Control.InitRecursive(Control namingContainer)
       at System.Web.UI.Control.AddedControl(Control control, Int32 index)
       at System.Web.UI.ControlCollection.Add(Control child)
       at DotNetNuke.Framework.DefaultPage.OnInit(EventArgs e)
       at System.Web.UI.Control.InitRecursive(Control namingContainer)
       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    Some research has revealed that you should be able to delete the contents of the Temporary ASP.NET folder, and things will recompile, and function as they should. Other research has stated that the obj, and bin folders can be deleted, and this will fix the issue. I commented out both of those folders, and the site instantly crashed. I have commented out the dll files that are referenced and received an error that they were missing, and the site did not function properly. I am hesitant to delete the temp files as there are hundreds of sites hosted on this server, and I would hate to have that many sites malfunctioning. Please advise. Thanks!
     






    Will Strohl

    Veteran Member



    Posts:1253
    Veteran Member




    7/19/2019 11:52 AM

      Wow... This is a painful one...  Sorry to hear about this.

      Do you happen to have a backup laying around that you know is good for you to login with, and are you able to restore to it?

      This is an older version of DNN, so...  To your knowledge, have the website been hacked and/or have you had someone look into that?  Are you able to compare the current and older web.config and Bin files to find any notable differences?

      Will Strohl

      Upendo Ventures Was my answer helpful to you? Please... Sponsor Us On GitHub ;)
      DNN experts since 2003 | We Build LOTS of DNN stuff...
      DNN-based E-Commerce w/ Hotcakes Commerce





      Shawn

      New Around Here



      Posts:5
      New Around Here




      7/19/2019 12:15 PM
        Thanks for the reply! We do have pretty solid backups of both the DB, and the file structure that go back for some time. I don't believe that hacking is an issue. Our sites sit behind a web application firewall that works pretty well. I guess I will start digging into previous files and comparing them to current files. Worst case scenario we go back a couple weeks with both the files and the db, and hope for the best. This was an odd one as we were able to log in to the site before the attempted upgrade even though there were other issues with the site. Hoped that someone else had maybe seen a similar error and could lend some advice. Thanks!





        Mitchel Sellers

        Growing Member



        Posts:97
        Growing Member




        7/19/2019 12:41 PM
          Looking at this, it appears that your site somehow ended up getting the DotNetNuke.Web.dll file replaced, but the newer DotNetNuke.Web.Deprecated.dll that was introduced later might also still be there in the directory.

          The best met will be to restore the site from backups, being sure to DELETE the directory first and then restore the backup.

          You MIGHT need to clear the Temporary files, but they should fix themselves.

          It looks like its just a DLL Verison issue.
          Mitchel Sellers
          Technology Advisory Group Leader
          CEO @ IowaComputerGurus, Inc. a DNN & .NET Solutions Provider
          Technical Blog: MitchelSellers.com





          Shawn

          New Around Here



          Posts:5
          New Around Here




          7/19/2019 3:13 PM
            Thanks allot for the insight guys. Ended up digging into previous versions of the Bin folder. When comparing the various versions extra files were found in the current folder version versus the older version. Commented out the newer files, and everything is now working well. Thanks again for the assistance! You guys rock!
            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