fallenlight
asked on
Sharepoint 2010, Can not delete file.
I`m having a trouble with deleting files. I can add new files or update files and database size is getting larger.
DB is not FULL and log size OK.
Checked the logs for the correlation. Here is the result from ulsviewer.
System.Data.SqlClient.SqlE xception: A severe error occurred on the current command. The results, if any, should be discarded. A severe error occurred on the current command. The results, if any, should be discarded.
at System.Data.SqlClient.SqlC onnection. OnError(Sq lException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsP arser.Thro wException AndWarning (TdsParser StateObjec t stateObj)
at System.Data.SqlClient.TdsP arser.Run( RunBehavio r runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlD ataReader. ConsumeMet aData()
at System.Data.SqlClient.SqlD ataReader. get_MetaDa ta()
at System.Data.SqlClient.SqlC ommand.Fin ishExecute Reader(Sql DataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlC ommand.Run ExecuteRea derTds(Com mandBehavi or cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlC ommand.Run ExecuteRea der(Comman dBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlC ommand.Run ExecuteRea der(Comman dBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlC ommand.Exe cuteReader (CommandBe havior behavior, String method)
at System.Data.SqlClient.SqlC ommand.Exe cuteReader (CommandBe havior behavior)
at Microsoft.SharePoint.Utili ties.SqlSe ssion.Exec uteReader( SqlCommand command, CommandBehavior behavior, SqlQueryData monitoringData, Boolean retryForDeadLock)
Unknown SQL Exception 0 occurred. Additional error information from SQL Server is included below. A severe error occurred on the current command. The results, if any, should be discarded. A severe error occurred on the current command. The results, if any, should be discarded.
SqlCommand: 'DECLARE @@iRet int;SET @@iRet = 0;BEGIN TRAN EXEC @@iRet = proc_DeleteUrl @wssp0, @wssp1, @wssp2, @wssp3, @wssp4, @wssp5, @wssp6, @wssp7, @wssp8, @wssp9, @wssp10, @wssp11, @wssp12, @wssp13, @wssp14 OUTPUT, @wssp15 OUTPUT;;IF @@iRet = 0 BEGIN EXEC @@iRet = proc_EnsureTranLockNotRequ ired @wssp16, @wssp17, @wssp18; END;IF @@iRet = 0 COMMIT ELSE ROLLBACK;SET @wssp19= @@iRet;' CommandType: Text CommandTimeout: 0 Parameter: '@wssp0' Type: UniqueIdentifier Size: 0 Direction: Input Value: 'b4ad4689-5d9a-49c0-9862-9 77824df2ca 6' Parameter: '@wssp1' Type: UniqueIdentifier Size: 0 Direction: Input Value: '4f93e81a-4942-4547-ba0b-a 1b64db3ff0 9' Parameter: '@wssp2' Type: NVarChar Size: 4000 Direction: Input Value: 'sharedservices/it/MIS Documents/Copy of Crash timeline.xlsx' Parameter: '@wssp3' Type: Int Size: 0 Direction: Input Value: '397' Parameter: '@wssp4' Type: Bit Size: 0 Direction: Input Value: 'True' Parameter: '@wssp5' Type: Bit Size: 0 Direction: Input Value: 'False' Parameter: '@wssp6' Type: Bit Size: 0 Direction: Input Value: 'True' Parameter: '@wssp7' Type: TinyInt Size: 1 Direction: Input Value: '0' Parameter: '@wssp8' Type: Int Size: 0 Direction: Input Value: '3' Parameter: '@wssp9' Type: Bit Size: 0 Direction: Input Value: 'False' Parameter: '@wssp10' Type: Bit Size: 0 Direction: Input Value: 'False' Parameter: '@wssp11' Type: Int Size: 0 Direction: Input Value: '4' Parameter: '@wssp12' Type: Int Size: 0 Direction: Input Value: '0' Parameter: '@wssp13' Type: Bit Size: 0 Direction: Input Value: 'True' Parameter: '@wssp14' Type: NVarChar Size: 520 Direction: Output Value: '' Parameter: '@wssp15' Type: UniqueIdentifier Size: 0 Direction: Output Value: '' Parameter: '@wssp16' Type: UniqueIdentifier Size: 0 Direction: Input Value: 'b4ad4689-5d9a-49c0-9862-9 77824df2ca 6' Parameter: '@wssp17' Type: UniqueIdentifier Size: 0 Direction: Input Value: 'd3b09288-1cc5-4acf-b52d-6 3a13adebdc 5' Parameter: '@wssp18' Type: Bit Size: 0 Direction: Input Value: 'False' Parameter: '@wssp19' Type: Int Size: 0 Direction: Output Value: ''
Unknown SPRequest error occurred. More information: 0x80131904
System.Runtime.InteropServ ices.COMEx ception: Exception from HRESULT: 0x80131904
at Microsoft.SharePoint.Libra ry.SPReque stInternal Class.Dele teItem(Str ing bstrUrl, String bstrListName, Int32 lID, UInt32 dwDeleteOp, Guid& pgDeleteTransactionId)
at Microsoft.SharePoint.Libra ry.SPReque st.DeleteI tem(String bstrUrl, String bstrListName, Int32 lID, UInt32 dwDeleteOp, Guid& pgDeleteTransactionId)
I`m out of ideas at the moment. (We will apply update patches and restart the server. and see what will happen :)
DB is not FULL and log size OK.
Checked the logs for the correlation. Here is the result from ulsviewer.
System.Data.SqlClient.SqlE
at System.Data.SqlClient.SqlC
at System.Data.SqlClient.TdsP
at System.Data.SqlClient.TdsP
at System.Data.SqlClient.SqlD
at System.Data.SqlClient.SqlD
at System.Data.SqlClient.SqlC
at System.Data.SqlClient.SqlC
at System.Data.SqlClient.SqlC
at System.Data.SqlClient.SqlC
at System.Data.SqlClient.SqlC
at System.Data.SqlClient.SqlC
at Microsoft.SharePoint.Utili
Unknown SQL Exception 0 occurred. Additional error information from SQL Server is included below. A severe error occurred on the current command. The results, if any, should be discarded. A severe error occurred on the current command. The results, if any, should be discarded.
SqlCommand: 'DECLARE @@iRet int;SET @@iRet = 0;BEGIN TRAN EXEC @@iRet = proc_DeleteUrl @wssp0, @wssp1, @wssp2, @wssp3, @wssp4, @wssp5, @wssp6, @wssp7, @wssp8, @wssp9, @wssp10, @wssp11, @wssp12, @wssp13, @wssp14 OUTPUT, @wssp15 OUTPUT;;IF @@iRet = 0 BEGIN EXEC @@iRet = proc_EnsureTranLockNotRequ
Unknown SPRequest error occurred. More information: 0x80131904
System.Runtime.InteropServ
at Microsoft.SharePoint.Libra
at Microsoft.SharePoint.Libra
I`m out of ideas at the moment. (We will apply update patches and restart the server. and see what will happen :)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.