I have News Articles installed on one of my web sites running DNN 3.1.

I keep getting the error message "A critical error has occurred. StartIndex cannot be less than zero. Parameter name: startIndex".

Every time this occurs I can reinstall the PA and everthing is fine for a few days, then it breaks again in the same manner. Is there something I can do to fix this for good?

Kent

Hi Kent,

Are you using the latest version? Is there anything peculiar you are doing (so that I can replicate?). Are you restricting by category, etc? Expiry dates?

When this happened about 2 weeks ago I upgraded to the latest. it has happened twice since then. When it occured 3 days ago I was away from the office and had to download directly from this site, so I know it was the latest then. Today it reoccured.

As for what I am doing, well visit any page with articles and I am getting that error. No restrictions, etc. I just set it up pretty simply on one tab and have about 5 articles posted. I fixed it about 6 hours ago and just checking it now it is again broken. I have tried permissions, etc to now avail.

Kent

I am seeing the same thing...

http://www.smcculloch.net/Forums/tabid/118/view/topic/forumid/4/postid/7411/Default.aspx

I am running DNN 3.1.1 as well... nothing has changed in over a month on the site. This just started happening.

This first occured with an older version, which I do not remember (00.04.?? maybe). Since there was a newer version on the web site I went ahead and upgraded. to the current version. This fixed the issue for about a week, then it died. I made no changes, did not add any articles, etc. A restart of ASP.NET, IIS, or even reboot does not fix it. The only thing that will fix it is to reinstall the module, however that is only a temporary fix.

Kent

I may have solved my problem. I say may have since it has only been 5 days and at times this has seemed to function fine for more than a week. I started poking around in the Admin Options for the module and found I had a catagory that had zero entries. I decided to delete the catagory and all has been well since then.

Kent

Take a look at my cross post... what does the site log look like when you see the error?  I dont have any categories created at all... I am using this as a simple blog on a site.

Thanks

An appeal for help.. I am running the latest version of News Articles on 3.2.2.   All of a sudden, I am seeing this error:    If I choose a file location (folder), I am redirected out of the page with a "Critical Error: Folder".

Any clues?   Thanks, Sal

Featured: If the page is featured it appears first in the article listing until it expires.

Image: You can choose an image to associate with this article. File Location: Root 2005 2005/images images Press SEC SEC/10-KSB SEC/10-QSB SEC/8-K SEC/Form-4 SEC/governance SEC/proxy File Name: Upload New FileUpload Selected File Select An Existing File An error has occurred. DotNetNuke.Services.Exceptions.ModuleLoadException: Folder ---> System.IndexOutOfRangeException: Folder at System.Data.Common.FieldNameLookup.GetOrdinal(String fieldName) at System.Data.SqlClient.SqlDataReader.GetOrdinal(String name) at System.Data.SqlClient.SqlDataReader.get_Item(String name) at DotNetNuke.Common.Globals.GetFileList(Int32 PortalId, String strExtensions, Boolean NoneSpecified, String Folder, Boolean includeHidden) at DotNetNuke.UI.UserControls.UrlControl.GetFileList(String strExtensions, Boolean NoneSpecified, String Folder) at DotNetNuke.UI.UserControls.UrlControl.ShowControls() at DotNetNuke.UI.UserControls.UrlControl.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---

Much like Semma, I am getting the same error messages. I have recently upgraded to 3.2.2 and continue to get the error below on any page with a file selection form:

DotNetNuke.Services.Exceptions.ModuleLoadException: Folder ---> System.IndexOutOfRangeException: Folder at System.Data.Common.FieldNameLookup.GetOrdinal(String fieldName) at System.Data.SqlClient.SqlDataReader.GetOrdinal(String name) at System.Data.SqlClient.SqlDataReader.get_Item(String name) at DotNetNuke.Common.Globals.GetFileList(Int32 PortalId, String strExtensions, Boolean NoneSpecified, String Folder, Boolean includeHidden) at DotNetNuke.UI.UserControls.UrlControl.GetFileList(String strExtensions, Boolean NoneSpecified, String Folder) at DotNetNuke.UI.UserControls.UrlControl.ShowControls() at DotNetNuke.UI.UserControls.UrlControl.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---

I made sure the database file table is in line with the actual files in the directories but I'm still stumped...any ideas? 

thanks...

Did you do a synchronize in the file manager? Does the documents module work? (it uses this control also).

Hmm, maybe its trying to select a file that no longer exists.

No...the documents module gives the same error (as do any of the file selections). I've used the TRTPortalFileMonitor module at Dave Buckner's site to check for orphans and that returns no orphans exist. I've got my toothcomb out now and will go through and make sure that the folders and the files tables match with the actual folder structure...

...also does anyone using Websecurestores know if their DNN installer tools completely wipe any existing folders and files...or does it upgrade the version only...?

thanks... 

Hi,

Yes, I have syncronized in file manager and the error does occur in documents as well as in the site settings file dialogue controls.   Since this was a production server , I had to restore from a backup.   I think that the root cause may have been someone (me) fiddling with files from the file system.  I am pretty sure that the database doesn't handle it well if files are moved or deleted from the file system.   

-For now... my problem has been solved but I'll let you know if I see it again.. 

Sal