Hello again, im having trouble with uploading files, my webconfig settings are below

<!-- allow large file uploads -->
    <httpRuntime executionTimeout="4000" appRequestQueueLimit="2000" useFullyQualifiedRedirectUrl="true" maxRequestLength="39192" requestLengthDiskThreshold="39192"/>

I don't understand whats going on to my head :( Cant upload files, does reinstall of Repository module make a solution?

The error is listed below



AssemblyVersion: 04.03.05
PortalID: 0
PortalName: Mikroproje
UserID: 1
UserName: host
ActiveTabID: 156
ActiveTabName: 3B Animasyonlar
RawURL: /mp/Dosyalar/3BAnimasyonlar/tabid/156/ctl/UserUpload/mid/608/Default.aspx
AbsoluteURL: /mp/Default.aspx
AbsoluteURLReferrer: http://mikroproje.net/mp/Dosyalar/3BAnimasyonlar/tabid/156/ctl/UserUpload/mid/608/Default.aspx
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; Avant Browser; Avant Browser; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 0fce5852-b730-4fd5-92d9-cb1ccaed28d6
InnerException: Arithmetic operation resulted in an overflow.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Modules.Repository.RepositoryBL.UploadFiles
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: Arithmetic operation resulted in an overflow. ---> System.OverflowException: Arithmetic operation resulted in an overflow. at DotNetNuke.Modules.Repository.RepositoryBL.UploadFiles(Int32 PortalID, Int32 ModuleID, String fileURL, String imageURL, Object objFile, Object objImageFile, RepositoryInfo pRepository, String strCategories, String strAttributes) at DotNetNuke.Modules.Repository.RepositoryBL.UploadFiles(Int32 PortalID, Int32 ModuleID, HttpPostedFile objFile, HttpPostedFile objImageFile, RepositoryInfo pRepository, String strCategories, String strAttributes) at DotNetNuke.Modules.Repository.Form.btnUpload_Click(Object sender, EventArgs e) at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---
Source:
Server Name: WHxxx

---

Or-Rouge Team Or-Rouge
Personally recommend Hostgator for hosting single or multiple DotNetNuke Websites.
DotNetNuke Tips and Tutorials
Install DotNetNuke to Godaddy root
DotNetNuke Türkçe Hakkinda Hersey

I sure wish someone would finally fix this problem.  I've been reading about it (and experiencing it first hand) for over a year now.  After reading your post I updated to 4.4.1 and am still experiencing this problem with the Repository.  I've seen source code fixes for the original problem posted on the web, but now it seems to have moved into a module.  I can't imagine that this would be a hard bug to track down since it throws a very well defined exception.  I almost get the impression that this bug is being ignored for a reason, especially since it has been give so many people grief.

I even checked the Repository project itself, and it seems the last update was back in June.  If I'm missing something would you please share it.  I've upgraded from a Version 3 site, is there a requirement that you install from scratch?

Everyone keeps saying in the forum that it is going to be fixed.  In the thread you mentioned it was stated that it would be fixed in the next release.  That statement was made prior to the 4.4.1 release.  But that really isn't what frustrates me.  I'm willing to be patient, as I know this is a public domain package.  But I've experienced this problem in one form or another for over a year, and the response seems to always be the same, wait for the next release.  Well my needs have reached a crusial  point, and I'm going to have to do major rework on our site if I cannot resolve this issue within a day or two.