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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Exception has been thrown by the target of an invocation.Exception has been thrown by the target of an invocation.
Previous
 
Next
New Post
2/18/2016 12:24 PM
 

Hello,

My site is DNN 7.4.2 . I was logged in as host and I was changing some resources. I clicked save, I got the normal green message that my resources were saved and then I hit the x (close) button on the pop up window. The site refreshed and I got an internal server error (!).

I accessed the site again (not logged in) and I accessed it just fine. Then I tried to login as host and the nightmare began.

Every time I login as host or admin I get an internal error. going through the log files I found the said exception:

Exception has been thrown by the target of an invocation.
   at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
   at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
   at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
   at System.Activator.CreateInstance[T]()
   at DotNetNuke.Framework.ServiceLocator`2.InitInstance()
   at System.Lazy`1.CreateValue()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Lazy`1.get_Value()
   at DotNetNuke.Framework.ServiceLocator`2.get_Instance()
   at DotNetNuke.UI.ControlPanels.ControlBar.LoadCustomMenuItems()
   at DotNetNuke.UI.ControlPanels.ControlBar.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.AddAt(Int32 index, Control child)
   at DotNetNuke.UI.Skins.Skin.InjectControlPanel()
   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)

 

I only changed a resource of a module (for localization) which I have done a thousand times and everything exploded in my face. Now every time I try to login as host or admin I get this error, which means I have absolutely no access to edit my site's content. From the error I understand something is wrong when the page reloads and tries to "construct" the control bar? I'm not even sure at this point.

The website has heavy traffic but I checked the server memory and it is fine so it isn't due to memory issues. The resource files I changed are normal, nothing fishy there. And I have no idea where to look or what to do.

 
New Post
2/18/2016 2:27 PM
 

A quick follow up about this issue (in case anyone ever encounters it a loses a significant portion of his lifespan due to pure terror like I did!): Don't panic.

I downloaded locally a backup of the site files and database while the problem still occurred. I set up the site locally and ran it. Guess what? I logged in as host normally. I concluded a simple recycle of the IIS application pool would do the trick.

To be honest it was a suspected solution but I was terrified: what if I recycled the application pool and my website simply didn't restart again? As I previously said, the particular website has heavy traffic. How could I know what would happen and what if I wasn't able to download a backup that quickly?

Nevertheless, I pumped up some courage and did the recycle on the live site. And it worked.

Still, I'm quite curious in an explanation. Why did this happen and why did the recycle solve the problem? What went so awfully wrong that caused the administration panels to explode like that?

I would be grateful for an idea as it would help me understand better possible future issues.

Thank you!!

 
New Post
2/19/2016 6:04 AM
 
Most likely, there was an inconsistency of the cache, which caused the issue, in these cases, a restart of the application solves the issue.
Restarting the issue results in a short interruption, i.e. users will have to wait several additional seconds to get their page displayed. Restarting the site should happen at least once a day to prevent leaks becoming a problem - usually we do configure our app pools to recycle once per night.

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/22/2016 6:11 AM
 

Hello,

Thank you very much for the useful insight. I realize a restart of the application should be a part of everyday maintenance, so I will look into it and check how it goes.

Thank you again for the advice!

 
New Post
2/22/2016 8:25 PM
 
you are welcome, have fun using DNN :))

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Exception has been thrown by the target of an invocation.Exception has been thrown by the target of an invocation.


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.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out