DNN Forums

Ask questions about your website to get help learning DNN and help resolve issues.
  • Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Using DNN Platform Upgrading DNN Platform

Default.aspx?tabid=21&error=An unexpected error has occurred&content=0

 12 Replies
 0 Subscribed to this topic
 29 Subscribed to this forum
Sort:
Page 1 of 212 > >>
Author
Messages
BiilC
New Around Here Send Private Message
Posts: 6
New Around Here
4/9/2025 8:35 PM

Upgraded to ver 10 and when I clicked view website I see this message in the browser address bar. Anyone know how to fix this? SQL server v 2017. .NET 4.8.0

Timo Breumelhof.
Veteran Member Send Private Message
Posts: 1196
Veteran Member
4/10/2025 5:01 AM

What errors do you see in Portals/_default/Logs/2025.04.[today].log.resources ?

BiilC
New Around Here Send Private Message
Posts: 6
New Around Here
4/10/2025 11:53 AM
I have a bunch of
DotNetNuke.Services.Exceptions.PageLoadException: Unhandled error loading page. ---> System.Runtime.InteropServices.ExternalException: Cannot execute a program. The command being executed was "W:\vhosts\\httpdocs\bin\roslyn\vbc.exe" /shared /keepalive:"10" /noconfig @"W:\vhosts\\tmp\root\ea856d5a\df8b8f0e\fwf1gr4m.cmdline". ---> System.ComponentModel.Win32Exception: This program is blocked by group policy. For more information, contact your system administrator

also

2025-04-10 00:00:07.198+08:00 [Wincloud01-AU][D:2][T:21][ERROR] DotNetNuke.Services.Exceptions.Exceptions - ~/Default.aspx?tabid=21&error=terminate
System.NullReferenceException: Object reference not set to an instance of an object.
at DotNetNuke.UI.Skins.Skin.GetSkin(PageBase page)
at DotNetNuke.Framework.DefaultPage.GetSkin()
at DotNetNuke.Framework.DefaultPage.OnInit(EventArgs e)
at System.Web.UI.Control.d__225.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Util.WithinCancellableCallbackTaskAwaitable.WithinCancellableCallbackTaskAwaiter.GetResult()
at System.Web.UI.Page.d__523.MoveNext()
Timo Breumelhof.
Veteran Member Send Private Message
Posts: 1196
Veteran Member
4/10/2025 2:37 PM

The most likely issue is that the Theme contains a deprecated Theme object.

Can you try this link? https://yourwebsite.com/?...ins/aperture/default

So add ?SkinSrc=[G]skins/aperture/default after the domainname?

BiilC
New Around Here Send Private Message
Posts: 6
New Around Here
4/10/2025 8:42 PM
Thank you, the site opened. I am logging in to set the aperture skin the skin of choice and will just have to do a little rebuilding. Hmmm, trying to log in crashed the site back to a 503 error. Can I edit the PortalAlias table to add a skin identifier?
BiilC
New Around Here Send Private Message
Posts: 6
New Around Here
4/11/2025 1:32 AM
In response to the first error, the host responded

During the recent security audit and process, we have placed restrictions that prevent certain file types from being uploaded or used on the server. This includes files with extensions such as .exe, .ps1, .yaml, and others commonly associated with scripts or application installers.

FSRM policy enforces file-screening rules, and prevents unauthorized or risky file types, contributing to security and operational stability.


To ensure the continued functionality and security of your website, you will need to recompile and redeploy the website using an alternative approach that complies with these restrictions. This may involve modifying script formats, using compressed archives, or replacing certain executable files with secure server-side equivalents.
Timo Breumelhof.
Veteran Member Send Private Message
Posts: 1196
Veteran Member
4/11/2025 4:42 AM

Yes, you can edit the PortalsSettings Table for that.
In general the issue in your existing skin should be easy to fix, but you might have to replace some skin objects with more modern options.

David Lee
Advanced Member Send Private Message
Posts: 133
Advanced Member
4/12/2025 5:03 AM
You can restrict file upload extensions from DNN using the security settings. "Settings>Security>More>More Security Settings>Allowable File Extensions". Those extensions you have mentioned are NOT in the list by default, so you should be OK. Of course this will only apply to uploaded through DNN and Module installation is excluded from these settings.

We also have a monitoring script that works sperate from DNN that checks the DNN folders for any invalid/strange extension types and alerts us of any possible attack. This is a nice approach for extra security.

Of course other options exist, it all depends on how tight you want the security, compared to the flexibility for users.
BiilC
New Around Here Send Private Message
Posts: 6
New Around Here
4/15/2025 9:15 AM
Bottom line here.

Although the host supports CodeDom they also block all exe file activity on their servers so DNN cannot invoke vdc to write their page scripts. I have accessed the site using the query string Timo offered above on every page, and copied basic functionality across to a local 9.13.08 install. I will have to wipe all files from the host and upload the local version as a new site. V10 is not going to work for me till I change host.
BiilC
New Around Here Send Private Message
Posts: 6
New Around Here
4/22/2025 10:09 PM

David, while this is true it does not get around the fact that v10 needs to run exe files on the server and host policy now prevents it from doing that. I have relaunched a reduced v9.13.8 site and will work with that for as long as I stay with this host.

Page 1 of 212 > >>

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