DNN Forums

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

Upgrading from 9.0.2 to 9.4.4

 5 Replies
 1 Subscribed to this topic
 23 Subscribed to this forum
Sort:
Author
Messages
Gil
New Around Here
Posts: 3
New Around Here

    After upgrading our DNN site from  9.0.2 to 9.4.4, the log file posted the error below.

    DotNetNuke.Services.Exceptions.Exceptions - DotNetNuke.Services.Exceptions.PageLoadException: Unhandled error loading page. ---> System.InvalidOperationException: No service for type 'DotNetNuke.UI.Modules.IModuleControlPipeline' has been registered.

    The site comes up properly on initialization; however, on the refresh it shows a 500 internal error.

    I have been trying to find and implement ideas on how to resolve this error for many days now, any help would be appreciated!

    Veteran Member
    Posts: 1236
    Veteran Member
      Which version of ASP.NET is being used?
      Gil
      New Around Here
      Posts: 3
      New Around Here

        ASP.NET 4.0.30319

        .NET Framework 4.7.2

        Veteran Member
        Posts: 1236
        Veteran Member
          So much for Guess #1 ...

          Do you use any DNNSharp modules? Any other 3rd party modules?
          Gil
          New Around Here
          Posts: 3
          New Around Here

            We do have custom module that we have created. These modules are precompiled when publishing to our servers.

            Perhaps this might be the issue. In version 9.0.2 or less, we usually deployed our site with the setting "Precompile during publishing" using Visual Studio.

            With this new version 9.4.4, this precompile setting seems to be generating the error mentioned above. When the precompile setting is unchecked the error message is no longer an issue and the site seems to function properly but with the .cs file present.

            Veteran Member
            Posts: 1236
            Veteran Member
              So, if you don't use the precompile option, then all is well with your site?

              If that's the case, I'd be looking at the module rather than at DNN as the culprit. Or perhaps the precompile option. I'd guess that there's something in your precompile environment (sorry ... but I have no idea how all of that works). Maybe the precompile is targeting the wrong ASP.NET? Or something else. When you don't select that option, then the compile is done in the context of your site, and all is well.

              At least that's another guess ... so I'd look there.

              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