We have an application, which consists of a set of controls written in C#, used to manage documents in SharePoint Portal Server 2003.  Our users are reporting that they encounter problems uploading documents using our interface.  This is the error they get while trying to upload documents.  Note: The document is uploaded into SharePoint using the SharePoint API.

System.OutOfMemoryException: Exception of type System.OutOfMemoryException was thrown.

In addition, they are sporadically get the following error:

InnerException: System.Threading.ThreadAbortException: Thread was being aborted.
at Microsoft.SharePoint.SPWeb.a(String A_0, Object[,]& A_1, Object[,]& A_2, UInt32& A_3, UInt32& A_4)
at Microsoft.SharePoint.SPFolder.b()
at Microsoft.SharePoint.SPFolder.get_Files()
at SCDOT.Web.SharePoint.Utilities.UploadFile(String webSpace, String libraryPath, String fileName, Byte[ fileData)
at SCDOT.Web.SharePoint.Utilities.UploadFile(String webSpace, String libraryPath, String fileName, String filePath)
at SCDOT.EDMS.SharePoint.Controls.Interface.Base.Upload.Submit_Upload_Click(Object sender, EventArgs e)

Does anyone have any ideas or suggestions as to what could be causing the problem here?

Thanks in advance.

Could you please post a code snippet of your API usage?! It seems you are consuming memory in something or the files that is being uploaded are too large. 

Below is a snippet of the code used to upload the file to SharePoint:

Microsoft.SharePoint.SPSite site = SPControl.GetContextSite(System.Web.HttpContext.Current);
SPWeb web = site.AllWebs[webSpaceName];
SPFolder folder = web.GetFolder(libraryName);

folder.Files.Add(path, data, true);

Thanks.

Do your users encounter this issue everytime they try to upload document event after restarting the SPS application? or after sometimes of uploading operations they encounter this?!

Are you closing and disposing the SPSite and SPWeb instances after finishing working with them?

What I think is that these things are the reasons of your OutOfMemoryException.

The problem seems to be sporadic.  I have been told by the users that the error seems to occur after they have uploaded 4-5 documents but that number is not consistent.  The size of the files tend to range from 100-300KB in size.  They are all PDF documents.  When this error was reported I had to do a code review of my review and found out the SPSite and SPWeb instances weren't being disposed of so I added this code after the folder.Files.Add(path, data, true) statement.

   if (web != null)
   {
    web.Close();
    web.Dispose();
   }
   if (site != null)
   {
    site.Close();
    site.Dispose();
   }

However, adding this code did not correct the problem.  The method responsible for uploading the files is contained inside a helper class.

 Well, did you restrarted you application after adding this code? did you redeploy it?

I cannot see anything wrong but the disposing issue 

I executed an iisreset on the server once the assembly was redeployed after making this change.  The users still receive the error.

Ok, are you able to test your code on some test environment that is similar to the production one?

You need to do so, and if you encounter the issue on your test environment I recomment that you omit/comment the part of your code that is uploading your document to SharePoint, that would make the method do nothing actually. but you'll start to focus on why exactly this issue is happening. you need to troubleshoot on some test environment

We do have a test environment I could try this on.  It's not a carbon of the production environment but it's pretty close.  I'll run a few tests in the test environment to see if I can reproduce the error.  I'll let you know how this goes.  Thanks again.

I've been unable to reproduce this error in our test environment so far this morning.  I've uploaded several documents into the system without any such error.  I'll keep trying and let you know what happens.

maybe because in production there are many users who are trying to do that at the same time?! 

At maximum, there are only two users uploading documents at the very same time on this system.

Do you think it would be in my best interest to have this class implement the IDisposable interface?  Doing so would allow me to dispose of the resources used by the class.  What do you think?  How would this affect the static methods within this class?  Even the UploadFile method is declared as static.

Hi

 I have a similar problem see my thread on http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3253419&SiteID=1

 We have been struggling with this issue on Development and Testing environments, and tried everything. We even took out the document add to the library did that manually and just update the listitem of the document and still get the exceptions...

 Any ideas? because we are stuck!

In our situation, it appeared to be an operating system issue.  The systems administrators discovered the server had Windows Server 2003 SP1 installed and not SP2 so he proceeded to upgrade the service pack.  Once the service pack was upgraded, we haven't received the OutOfMemoryException error since.  I wanted to wait long enough until I was satisfied the service pack actually corrected the issue at hand.  At this point, I guess it is safe to say the service pack corrected our problem.  Are you running Windows Server 2003?  If so, what service pack are you running?

John Richardson, MCP, A+
Applications Analyst
S. C. Department of Transportation