Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

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 ...Cannot edit ANYTHINGCannot edit ANYTHING
Previous
 
Next
New Post
1/3/2008 5:45 PM
 

pfunk wrote

In my Event Viewer there seem to be two alternating General Exceptions over and over.  They are:

1)

AssemblyVersion: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: Could not load type ''.
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message: System.Web.HttpException: Could not load type ''. ---> System.ArgumentException: String cannot have zero length. at System.Reflection.Assembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase) at System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) --- End of inner exception stack trace --- at System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) at DotNetNuke.Framework.Reflection.CreateType(String TypeName, String CacheKey, Boolean UseCache, Boolean IgnoreErrors)
Source:
Server Name:
MYSERVER

2)

AssemblyVersion: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: Value cannot be null. Parameter name: type
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message: System.ArgumentNullException: Value cannot be null. Parameter name: type at System.Activator.CreateInstance(Type type, Boolean nonPublic) at DotNetNuke.Framework.Reflection.CreateObject(String TypeName, String CacheKey) at DotNetNuke.Services.Search.ModuleIndexer.GetModuleList(Int32 PortalID)
Source:
Server Name: MYSERVER

I don't know about your other problem, but that pair of errors is one that really should have been dealt with in the core by now. You can fix it with a small script:

http://www.mitchelsellers.com/Blogs/tabid/54/articleType/ArticleView/articleId/111/Default.aspx

Rob

 
New Post
1/10/2008 6:44 PM
 

Thanks, that fixed the pair of errors that were showing up in my Event Log every half hour.

My problem still exists, and I have some more detail about it...

First, there are no errors in my Event Log when this issue comes up.

Secondly, other forms on the site also fail when this issue arises.  When I'm logged in as Host admin trying to update pages and the issue arises, my simple forms for collecting user data also fail.  They simply return the same page as if I had never submitted the form.  This seems to hold true for all Postback links as well.

Clearing my browser's cache and cookies does not seem to help.  I can login to the site from an entirely new computer and the problem will persist.  Today when it came up, I rebooted IIS and closed all of my browser windows and it went away.  In the past rebooting IIS has not solved the issue, rather it will simply go away on its own after a few hours or overnight.

Is there some other way I can investigate this while it's occuring?  I was wondering if an incomplete page load could be causing HTML forms to be incomplete and thus run into each other.  But due to the complexity of the postback mechanism across a large page, this sounds like a huge hassle for such a blind guess.

Has anyone else experienced this problem?

 
New Post
1/10/2008 9:34 PM
 

As you have confirmed, events are definitely not wiring up.  How about this...  Restart IIS and then delete your Temporary Internet Files from the .Net Framework folder.  Do this before the site is hit again.  This will clear out any precompiled code.  The directory will be something like:

C:\WINDOWS\Microsoft.NET\Framework\<version>\Temporary ASP.NET Files\

While it probably wouldn't hurt anything to delete all of the application folders in that directory, it is probably a good idea to only delete the one(s) that is having this problem.  The next time your site is requested, the folder will be recreated, and the site will be recompiled from scratch.  On a side note, I sometimes have to restart the SQL Server service as well to avoid deletion errors.


Will Strohl

Upendo Ventures Upendo Ventures
DNN experts since 2003
Official provider of the Hotcakes Commerce Cloud and SLA support
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Cannot edit ANYTHINGCannot edit ANYTHING


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.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out