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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Server Error :Index was outside the bounds of the array-Site Crashed !!Server Error :Index was outside the bounds of the array-Site Crashed !!
Previous
 
Next
New Post
8/17/2007 9:08 AM
 

Hello Folks,

I have had this happen to me today. I looked high and low to figure out what I had done so that I could back-track.

HOW TO FIX:
It seems that there is a bug that is causing this, but the bug is yet to be indentified, nor the cause. However, there is a way to fix it! -- Simply RECYCLE you application pool (restart iis). 

WHAT IF I HAVE NO ACCESS TO IIS?
Modify your web.config (add a space or something) and upload it. This will force your app to recycle.

This solution has helped me (thank you ErikVB) and I hope it helps you too!

 


Maxiom TechnologyAntonio Chagoury | Microsoft MVP
Maxiom Technology
Professional .net & DotNetNuke Solutions
web: www.maxiomtech.com
blog: www.cto20.com
twitter: @antoniochagoury & @maxiomtech

 
New Post
8/25/2007 6:54 PM
 

Thanks Antonio and ErikVB,

this was the solution to my problem too, just stumbled in on this one and I must say it's a great solution (or workaround) and I must say that giving this extra line for people with no access to IIS (like me ) is even better.

thanks so much, this made my day.

 
New Post
8/28/2007 9:37 PM
 

I had this issue and was getting lots of these errors in my event log. I would get about 20 at almost exactly every 30 minutes. So is this some type of session issue? I am at DNN 4.5.3. I have a lot of users that need to use this application on Wed morning. So I am trying to decide if an upgrade to DNN 4.5.5 might work for me.

Any thoughts?

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: DNPSERVER01

 


Forerunner Communications, LLC
DotNetNuke Integration Specialists

 
New Post
8/29/2007 5:02 AM
 

Hello all,

 

I had these problems as well and I suspect that these are performance issues related to IIS Logging and SQL indexing.

 

 

1. IIS Logging

 

If you have IIS [log visits] set to on and your DNN Portal is up and running for sometime, i.e. several months,  check the following.

 

IIS and other applications are creating and storing their logfiles on your server in the directory [C:\WINDOWS\system32\LogFiles].

 

Check the size of the directory and the size and amount of files it contains.

When I encountered the problems, IIS and thus my DNN portal had generated about 4 Gigs of data and 100s of files within 7 months.

 

It meant that when the site was really busy, IIS couldn’t log as easily to the [C:\WINDOWS\system32\LogFiles] location and pump out DNN pages simultaneously. One could say that it was harder for IIS to write to a directory already storing 4 Gigs of data thus causing a performance hit.

 

If you hardly check the logfiles ever,  then you could just delete the generated logfiles within the directory and set the option in ISS  to no.

 

If you need logging information, within DNN there is the [Site Log] functionality which also logs all user visits to you DNN portal to your database.

 

 

2. SQL server 2000 indexing

 

If you are using SQL 2000 standard edition, make sure you index often and frequently. Set a job to run on the slowest hour of your portal. Check the SQL books online on how to do this.

 

If your running many multiple portals, and your database is bigger then approx. 200 to 250 Mb, and have about 80 concurrent users, then the disappearing menu items bug tend to occur more often.

 

Mind that I still have the occasional events within the event viewer like:

 

Event code: 3005

Event message: An unhandled exception has occurred.

 

But far less often then before, at one point it occurred around 5 times a day. Now just once in two days and the site overall is also responding much faster.

 

I am still looking into the problem, if it’s really a DNN bug problem are a DNN / SQL server / ISS performance issue. I am suspecting the latter.

 

Ok hope this helps, 

 

 

 

Regards,

 

 

Jerry Tjon

IT Consultant 

Amsterdam

 

 


Regards,

Jerry Tjon
IT Consultant
Amsterdam,
the Netherlands
 
New Post
10/18/2007 9:25 AM
 

Hi Jerry !

I'd like to know if you find something about this problem ? What is the exact source of error ? I have this problem every 2 weeks and restarting IIS is a good solution but... :)

If you find anything I appreciate some information.

Thank you!

Regards,
Kevin

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Server Error :Index was outside the bounds of the array-Site Crashed !!Server Error :Index was outside the bounds of the array-Site Crashed !!


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