Group Policy blocks EXE’s

[datafastlr]

I, and many others, have no access to the group policy on GoDaddy servers, so it is impossible to upgrade to version 10, due to the exe files in /bin/roslyn/
Very disappointing.

[bdukes]

In the upgrade package, rename Install/Library/Microsoft.CodeDom.Providers.DotNetCompilerPlatform_04.01.00_Install.zip to Install/Library/Microsoft.CodeDom.Providers.DotNetCompilerPlatform_04.01.00_Install.zip.resources to avoid installing that package. We'd love to have GoDaddy support reach out and discuss concerns, since this is a common package from Microsoft that is needed to move the Platform forward in terms of language support.

[datafastlr]

I did as instructed. The upgrade procedure worked as it should, but when I opened the website, I got a 500 error (/Default.aspx?tabid=21&error=An+unexpected+error+has+occurred&content=0)

[mitchelsellers]

Can you look at the file in the folder /portals/_default/logs to see if there are any reported errors.

[datafastlr]

There are multiple errors (attached log).
2025.08.26.log.zip

[mitchelsellers]

Based on those logs, it seems that you might have a few problems going on. It looks like for some reason your SQL Server is not allowing you to connect which is very unusual for an upgrade.

Additionally it looks like the version of the file System.Web.Http doesn't match, it is possible a third-party module may have updated it in the past you may try to grab a copy of that file from the /bin directory from your backup and replace it and see if that gets you back online.

But othewise you may want to get with GoDaddy to see about why the DB is failing.

[datafastlr]

Thanks for the info!
I installed a new version of DNN 10.1.0. Installation went well, but back to the same problem. I guess I'm going to have to move off GoDaddy and find a web and DB server provider. I've been using DNN since 6.1.2, and refuse to switch to Joomla or Wordpress.

[datafastlr]

Finally got DNN 10.1.0 to work with your suggestion to change the Install/Library/Microsoft.CodeDom.Providers.DotNetCompilerPlatform_04.01.00_Install.zip to a resources file, on a fresh install. Not sure why it didn't work on an upgrade.

[datafastlr]

Oh well. Everything was working fine until I installed Mandeeps libraries, modules and Porto skin. Then I got a 500 Error. 9Log attached).
2025.08.27.log.zip

[valadas]

There are a lot of different issues in those logs, Database access issues, can't find some libraries that should have been part of the upgrade, then usage of deprecated APIs from 3rd party modules.

I would revert and check if any/all 3rd party modules are still used (or can be removed), then update the ones you decide to keep to the latest version available (potentially checking with each vendor if their extensions were testing for DNN v10. Then only start the upgrade process.

Also, did you upgrade to the latest v9 before upgrading to v10 ?

[valadas]

Wait, you mentioned an upgrade before, I am confused. If that is a clean new install than those modules would not yet be on it. Is this an upgrade or not?

[datafastlr]

Yes. Sorry about the confusion. (1) At first, I tried to upgrade from a 9.13.8, and the group policy would not allow the EXE's to be executed. So, I added the ".resources" to the Microsoft.CodeDom.Providers.DotNetCompilerPlatform_04.01.00_Install.zip file. The upgrade still did not work. So, (2) I installed a fresh version of 10.1.0, again with the ".resources" attached to the Microsoft.CodeDom.Providers.DotNetCompilerPlatform_04.01.00_Install.zip, and the installation succeeded. (3) Then when I installed Mandeeps skin, libraries and modules and refreshed to activate them, the site crashed to a 500 error.

I have a fresh install of 10.1.0 installed and running now. I am going to install the 3rd party modules one at a time and monitor the DB to see if the tables are writing correctly. I beginning to think it's a connection issue with GoDaddy's DB servers and not the software.

[mitchelsellers]

Given my history with GoDaddy, they do not provide enough resources for a lot of the third party stuff, especially when installing/upgrading when there are a lot of operations going on.

[valadas]

That...

[datafastlr]

I figured out that the Mandeeps Porto skin is causing the issue. I installed and licensed all the modules one at a time with no problems. Then I installed the skin and changed the Theme to the new skin and container. That broke the site.

I'll get with Mandeeps and let them know.

[valadas]

And, not pointing fingers at GoDaddy here, but I would probably pull a copy locally to test and document the process before doing it on production. I have seen all kinds of weird issues with them specially for windows hosting.