Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Digital Assets Manager - 500 error on ActionButtonDigital Assets Manager - 500 error on ActionButton
Previous
 
Next
New Post
6/14/2018 8:05 AM
 

Hi chaps

One of my DNN 804 instances all of a sudden has a problem. When I attempt to access the module settings of the file manager (digital assets manager) via the ActionButton menu item (my containers use the ActionButtons), it throws a 500 error, the details of which are pasted below. When there are other modules on the same, page, they also do the same thing. However I've boiled it down to the file manager as it is the only module that does it in isolation.

I can get into the settings no problem via the ActonMenu settings link, which is a standard anchor URL rather than a __doPostBack as the ActionButton is.

Regardless of the details, All my DNN instances are identical, same skin, same modules, same everything, except for different websites and content. This is only occurring in one instance. All other modules work fine in the same system.

I've reapplied permissions, reinstalled the module, and tried different skins. Always the same. It's just the file manager that is causing ActionButtons to break and I can't see why.

I'm hoping the exception messages below provide a clue?

Regards
Rob


[NullReferenceException: Object reference not set to an instance of an object.]
   DotNetNuke.Admin.Containers.ModuleActions. (EventArgs e) +108

[ModuleLoadException: An error has occurred.]
   DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(String FriendlyMessage, Control ctrl, Exception exc, Boolean DisplayErrorMessage) +627

[PageLoadException: An error has occurred.]
   DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +449
   DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc) +101
   DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(String FriendlyMessage, Control ctrl, Exception exc, Boolean DisplayErrorMessage) +806
   DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(Control ctrl, Exception exc, Boolean DisplayErrorMessage) +178
   DotNetNuke.Admin.Containers.ModuleActions. (EventArgs e) +1722
   System.Web.UI.Control.LoadRecursive() +59
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +678

[PageLoadException: An error has occurred.]
   DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +449
   DotNetNuke.Framework.PageBase. (EventArgs e) +724
   System.Web.UI.Page.HandleError(Exception e) +84
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +6560
   System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +245
   System.Web.UI.Page.ProcessRequest() +72
   System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +22
   System.Web.UI.Page.ProcessRequest(HttpContext context) +58
   ASP.default_aspx.ProcessRequest(HttpContext context) +4
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +188
   System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) +48
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +71
 
New Post
6/14/2018 1:35 PM
 
I didn't even think action buttons worked/were supported anymore?

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
6/14/2018 3:41 PM
 
Chris Hammond wrote:
I didn't even think action buttons worked/were supported anymore?

Bingo! :)

One of the steps that should be performed when upgrading to DNN 8.xx and above is to remove SolPart and any actions menu/button references from ALL of your skins and containers.  DNN adds the actions menu for you.  Action buttons can be supported in many instances, but it's really been deprecated to ensure a consistent user experience across all DNN instances.


Will Strohl

Upendo Ventures Upendo Ventures
DNN experts since 2003
Official provider of the Hotcakes Commerce Cloud and SLA support
 
New Post
6/15/2018 12:09 AM
 

Thanks for the replies guys

The solpart is long gone and custom 3rd party action buttons and action menus are fully supported, thankfully! As mentioned, the same buttons and menus work perfectly throughout this and all my identical DNN instances and have done so since the 804 upgrade back in 2016 and also many years prior. 

This problem is specific to one instance and only the DAM module. It is triggered when the action button is clicked, but the action button is not the flaw. Again, it works everywhere else. I'm looking for some other problem that might have arisen; probably a data issue, as that is the only thing that is different across these DNN instances. I think the browser error message is probably misleading. 

The event log has the following exception that might be  more relevant:


 

InnerMessage:Error: File Manager is currently unavailable.

InnerStackTrace:

   at DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL)
   at DotNetNuke.Framework.PageBase. (EventArgs e)
   at System.Web.UI.Page.HandleError(Exception e)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
   at System.Web.UI.Page.ProcessRequest()
   at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)
   at System.Web.UI.Page.ProcessRequest(HttpContext context)
   at ASP.default_aspx.ProcessRequest(HttpContext context)
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

										
 
New Post
6/15/2018 12:31 AM
 
Hey Rob:

I get what you're saying, but the action buttons literally have had code removed. While you can sometimes see them working, they are no longer a supported feature. In fact, I don't think they work at all in a clean instance - only upgraded DNN instances.

Will Strohl

Upendo Ventures Upendo Ventures
DNN experts since 2003
Official provider of the Hotcakes Commerce Cloud and SLA support
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Digital Assets Manager - 500 error on ActionButtonDigital Assets Manager - 500 error on ActionButton


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

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

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. 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.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  

What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out