We are not able to upload any files > 20mb even though the maximum is set to 50mb. We get a File Not Found error in Sharepoint which returns immediately. There are no errors in the SP logs; however, after inspecting Fiddler I can see several 401.2 and 401.1 errors on the _layouts/Upload.aspx page. These are the only errors that I can find around this problem, but what is strange is that these errors also show up in Fiddler for a successful file upload (<20mb) followed by 200 result.The issue only occurs in our production environment, but we can't find anything that could be the culprit.I don't think it's timing out because it doesn't even seem to get that far.I would appreciate any advice before I'm forced to open a support ticket. We are using IIS 6.0, MOSS Std, Win Svr2003 Std. SP2Thanks!

check your site quota and make sure you still have space available.

The site collection is set to Individual Quota, but no limits are set. Also checked web.config <httpRuntime maxRequestLength="51200" /> .

I have found error in SP logs:UnexpectedUnexpected query execution failure, error code 266. Additional error information from SQL Server is included below. "Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = 0, current count = 1." Query text (if available): "DECLARE @@S uniqueidentifier; DECLARE @@DocId uniqueidentifier; DECLARE @@Level tinyint; DECLARE @@DocUIVersion int; DECLARE @@DoclibRowId int; DECLARE @@iRet int;DECLARE @DN nvarchar(256); DECLARE @LN nvarchar(128); DECLARE @FU nvarchar(260); SET @@Level=255 SET @@DocUIVersion =512 SET @@DocId='513AFA25-F3CF-4463-8A9D-AAB3D85C5660' SET @@S='FE6C59CE-6F2E-43D3-A4E7-6DB4B91EB72E'; EXEC @@DoclibRowId = proc_GenerateNextId '042F8887-BE5C-42EC-A275-F7F690FB0559','0454715E-EC35-4107-A753-CC0ED37F606E'; SET @DN=N'AreaTemplateSite/Documents'; SET @LN=N'Large Test.doc';BEGIN TRAN; EXEC @@iRet = proc_AddDocument 'FE6C59CE-6F2E-43D3-A4E7-6DB4B91EB72E','042F8887-BE5C-42EC-A275-F7F690FB0559',8,NULL,@DN, @LN OUTPUT, @@Level, @@DocUIVersion, @@DocId,'0454715E-EC35-4107-A753-CC0ED37F606E',@@DoclibRowId,?,?,21065728,456,0,0,332,NULL,NULL,0,2097154,0,0,0,-2,NULL,0,NULL,NULL,NULL,NULL,NULL,? OUTPUT,0,?,? OUTPUT; SET @FU = dbo.fn_GetFullUrl(@DN, @LN); IF @@iRet <> 0 GOTO done; EXEC proc_DirtyDependents @@S,1,@FU;IF @DN IS NULL SET @DN=N'AreaTemplateSite/Documents'; IF @LN IS NULL SET @LN=N'Large Test.doc'; EXEC @@iRet =proc_AddListItem @WebId='042F8887-BE5C-42EC-A275-F7F690FB0559',@SiteId='FE6C59CE-6F2E-43D3-A4E7-6DB4B91EB72E',@ListID='0454715E-EC35-4107-A753-CC0ED37F606E',@ItemId=@@DoclibRowId,@UIVersion=@@Do... Unexpected...cUIVersion,@RowOrdinal=0,@DocIdAdded='513AFA25-F3CF-4463-8A9D-AAB3D85C5660',@Size=0,@ItemName=N'Large Test.doc',@ItemDirName=@DN OUTPUT,@ItemLeafName=@LN OUTPUT,@ItemDocType=0,@UserId=8,@Level=@@Level, @TimeNow='20090723 17:53:30', @tp_ContentTypeId = ?,@nvarchar1=?,@nvarchar2=?,@nvarchar3=?,@nvarchar7=?,@tp_ContentType=?,@tp_ModerationStatus=?,@acl=0xF3FE000001000000000000002200000008000000FFFFFFFFFFFFFF7F0B000000FF13433CB001000014000000000001081000000015000000FF1B5F3CB001000016000000EF1BE77EF001004017000000FF13433CB0010000180000002100030810000000190000000000010810000000D1090000FFFFFFFFFFFFFF7FD2090000EF124338B0010000D309000061104308B0000000ED0900000000010810000000EE0900000000010810000000EF0900000000010810000000F00900000000010810000000F10900000000010810000000F20900000000010810000000F30900... Unexpected...000000010810000000F40900000000010810000000F50900000000010810000000F60900000000010810000000F70900000000010810000000F80900000000010810000000FD0900000000010810000000FE0900000000010810000000FF0900000000010810000000000A00000000010810000000050A000061104308B0000000E70A00000000010810000000910D00000000010810000000021000000000010810000000302200000000010810000000312200000000010810000000FFFFFF3F0000010810000000; IF @@iRet<> 0 GOTO done; SELECT @@iRet, @@DoclibRowId; done: IF @@iRet=0 BEGIN EXEC proc_GetLinkInfoSingleDoc @@S,@DN,@LN,@@Level; END ELSE ROLLBACK; SET ?=@@iRet;"

Hello, Based on my experience, the issue is very possibly caused by the lack of virtual memory. Please check the application pool in the IIS manager, modify the value to a higher one, for example 1500MB or unlimited; then, modify the timeout value in web.config from 20 by default to 40. Last, reset the IIS, check if the issue persists. Let us know the result if possible. Thanks. Best Regards, Lionel Chen

web.config has <httpRuntime executionTimeout="999999" maxRequestLength="51200" />On the Recycling tab, the Maximum virtual memory and Maximum used memory are both unchecked. IIS website properties has connection timeout = 300 seconds.I have taken one of the web front end servers out of our load balancer to make these changes. Since this is our production environment I have to minimize any disruption in service. Issue still persists if I try to upload locally from this server (server.domain.com). Do I need to make the changes to both web applications/servers? I appreciate the help!

After rebooting the server, now there is no error in the web page; however, the file is not uploaded. Still shows db error in SP logs:"Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = 0, current count = 1." Query text (if available): "DECLARE @@S uniqueidentifier; DECLARE @@DocId uniqueidentifier; DECLARE @@Level tinyint; DECLARE @@DocUIVersion int; DECLARE @@DoclibRowId int; DECLARE @@iRet int;DECLARE @DN nvarchar(256); DECLARE @LN nvarchar(128); DECLARE @FU nvarchar(260); SET @@Level=255 SET @@DocUIVersion =1 SET @@DocId='525EE09F-6AC6-4FE7-8AF7-66066B8E10EB' SET @@S='FE6C59CE-6F2E-43D3-A4E7-6DB4B91EB72E'; EXEC @@DoclibRowId = proc_GenerateNextId '9086D965-E03F-453D-9479-41FF91B23713','A554FD68-7BC6-44FC-B69A-855968D932D0'; SET @DN=N'Documents'; SET @LN=N'Large Test.doc';BEGIN TRAN; EXEC @@iRet = proc_AddDocument 'FE6C59CE-6F2E-43D3-A4E7-6DB4B91EB72E','9086D965-E03F-453D-9479-41FF91B23713',8,NULL,@DN, @LN OUTPUT, @@Level, @@DocUIVersion, @@DocId,'A554FD68-7BC6-44FC-B69A-855968D932D0',@@DoclibRowId,?,?,21065216,456,1,0,332,NULL,NULL,0,2097154,0,0,0,-2,NULL,0,NULL,NULL,NULL,NULL,NULL,? OUTPUT,0,?,? OUTPUT; SET @FU = dbo.fn_GetFullUrl(@DN, @LN); IF @@iRet <> 0 GOTO done; EXEC proc_DirtyDependents @@S,1,@FU;IF @DN IS NULL SET @DN=N'Documents'; IF @LN IS NULL SET @LN=N'Large Test.doc'; EXEC @@iRet =proc_AddListItem @WebId='9086D965-E03F-453D-9479-41FF91B23713',@SiteId='FE6C59CE-6F2E-43D3-A4E7-6DB4B91EB72E',@ListID='A554FD68-7BC6-44FC-B69A-855968D932D0',@ItemId=@@DoclibRowId,@UIVersion=@@DocUIVersion,@RowOrdinal=0,@DocIdAdded='525EE09F-6AC6-4FE7-8AF7-66066B8E10EB',@Size=0,@ItemName=N'Large Test.doc',@ItemDirName=@DN OUTPUT,@ItemLeafName=@LN OUTPUT,@ItemDocType=0,@UserId=8,@Level=@@Level, @TimeNow='20090802 16:42:06', @tp_ContentTypeId = ?,@tp_ModerationStatus=?,@nvarchar1=?,@nvarchar2=?,@nvarchar3=?,@nvarchar7=?,@tp_ContentType=?,@acl=0xF3FE000001000000000000002200000008000000FFFFFFFFFFFFFF7F0B000000FF13433CB001000014000000000001081000000015000000FF1B5F3CB001000016000000EF1BE77EF001004017000000FF13433CB0010000180000002100030810000000190000000000010810000000D1090000FFFFFFFFFFFFFF7FD2090000EF124338B0010000D309000061104308B0000000ED0900000000010810000000EE0900000000010810000000EF0900000000010810000000F00900000000010810000000F10900000000010810000000F20900000000010810000000F30900000000010810000000F40900000000010810000000F50900000000010810000000F60900000000010810000000F70900000000010810000000F80900000000010810000000FD0900000000010810000000FE0900000000010810000000FF0900000000010810000000000A00000000010810000000050A000061104308B0000000E70A00000000010810000000910D00000000010810000000021000000000010810000000302200000000010810000000312200000000010810000000FFFFFF3F0000010810000000; IF @@iRet<> 0 GOTO done; SELECT @@iRet, @@DoclibRowId; done: IF @@iRet=0 BEGIN EXEC proc_GetLinkInfoSingleDoc @@S,@DN,@LN,@@Level; END ELSE ROLLBACK; SET ?=@@iRet;" I have also noticed this error at the same time (don't know if it's related):SQLException while Executing the cache invalidation simple timer job. We will not abort the job, and will retry in 60 seconds: System.Data.SqlClient.SqlException: Invalid object name 'AR_CacheCounters'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.Office.Server.Data.SqlSession.ExecuteReader(SqlCommand command, CommandBehavior behavior) at Microsoft.Office.Server.Data.SqlSession.ExecuteReader(SqlCommand command) at Microsoft.Office.Server.ApplicationRegistry.Infrastructure.CacheInvalidationStateTracker.CheckStatus(Object stateInfo)

After working with MS support on this issue, I am happy to report that it has been resolved. It turned out to be some kind of corruption in the content database. We were able to create a new content database, backup the old one and restore it into the new content db and then attach the new content db to our web application. It now works as expected, even though we really don't know exactly what it was or how it happened.Hope it helps someone else.

I have found a solution to this problem, and it is not caused by a corrupt database. It is simply a .NET limitation, and you need to add some lines to the web.config to resolve it. We have experienced this issue withMOSS servers running on Windows Server 2008. For some reason, Central Admin fails to update the web application's web.config when changes are made in the properties. At least, this is what I was told by some of my tech guys.The solution that works for us is to add the following block of entries to the <configuration> section. I usually just add it right at the bottom just above the closing </configuration> tag:<system.webServer><security><requestFiltering><requestLimits maxAllowedContentLength="52428800"/></requestFiltering></security></system.webServer>Works fine every time! Enjoy!-Bryan PriceSharePoint Solutions ArchitectCPI Solutions - 805.445.6653 SharePoint Practice Manager, MCTS CPI Solutions - (805) 445-6653

I just wanted to mention that we tried all of the settings in web.config including this one and they never fixed the issue. Our MS support engineer tried all other options around http content & request limitsand we continued to receivethe SQL db error (proc_AddDocument) upon file upload.For our particular problem, the only fix was to create a new content db.I really appreciate all of the help on these forums. Sometimes this is my only source for advice of this kind and it's great that people actually respond here.Keep up the great work guys!Thanks!

I just wanted to mention that we tried all of the settings in web.config including this one and they never fixed the issue. Unfortunately, recreating the db is not the acceptable solution when we're talking about production systems.

I have found a solution to this problem, and it is not caused by a corrupt database. It is simply a .NET limitation This solution worked very well!.. Thanks a lot