none
SharePoint 2010 Excel document freezing when uploading

    Question

  •   I am researching why intermittently people who have an Excel document open freezes when they try to save the document to our on Premise SharePoint 2010 farm.   From the End user perspective the experience looks like the similar problem as in the screenshot: https://answers.microsoft.com/en-us/msoffice/forum/all/excel-freezing-when-files-uploading-to-sharepoint/20a8d815-8143-4d45-bf4a-b933a86e0095

    For the particular end user I am working with PC Windows 7 (64-bit) Enterprise, Office 2013 plus (32-bit).  

    Any thoughts on what could be causing the intermittent issue?

    In my ULS logs I am seeing some event entries about a low query as shown below.  (Unfortunately, I've not seen consistent log entries that match every time users see the issue.)

    Slow Query StackTrace-Managed:    at Microsoft.SharePoint.Utilities.SqlSession.OnPostExecuteCommand(SqlCommand command, SqlQueryData monitoringData)     at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, CommandBehavior behavior, SqlQueryData monitoringData, Boolean retryForDeadLock)     at Microsoft.SharePoint.SPSqlClient.ExecuteQueryInternal(Boolean retryfordeadlock)     at Microsoft.SharePoint.SPSqlClient.ExecuteQuery(Boolean retryfordeadlock)     at Microsoft.SharePoint.Library.SPRequestInternalClass.PutFile(String bstrUrl, String bstrWebRelativeUrl, Object punkFile, Int32 cbFile, Object punkFFM, PutFileOpt PutFileOpt, String bstrCreatedBy, String bstrModifiedBy, Int32 iCreatedByID, Int32 iModifiedByID, Object varTimeCreated, Object varTimeLastModified, Object varProperties, String bstrCheckinComment, Byte partitionToCheck, Int64 fragmentIdToCheck, String bstrCsvPartitionsToDelete, String bstrLockIdMatch, String bstEtagToMatch, Int32 lockType, String lockId, Int32 minutes, Int32 fRefreshLock, Int32 bValidateReqFields, Guid gNewDocId, UInt32& pdwVirusCheckStatus, String& pVirusCheckMessage, String& pEtagReturn, Byte& piLevel, Int32& pbIgnoredReqProps)     at Microsoft.SharePoint.Library.SPRequest.PutFile(String bstrUrl, String bstrWebRelativeUrl, Object punkFile, Int32 cbFile, Object punkFFM, PutFileOpt PutFileOpt, String bstrCreatedBy, String bstrModifiedBy, Int32 iCreatedByID, Int32 iModifiedByID, Object varTimeCreated, Object varTimeLastModified, Object varProperties, String bstrCheckinComment, Byte partitionToCheck, Int64 fragmentIdToCheck, String bstrCsvPartitionsToDelete, String bstrLockIdMatch, String bstEtagToMatch, Int32 lockType, String lockId, Int32 minutes, Int32 fRefreshLock, Int32 bValidateReqFields, Guid gNewDocId, UInt32& pdwVirusCheckStatus, String& pVirusCheckMessage, String& pEtagReturn, Byte& piLevel, Int32& pbIgnoredReqProps)     at Microsoft.SharePoint.SPFile.SaveBinaryStreamInternal(Stream file, String checkInComment, Boolean checkRequiredFields, Boolean autoCheckoutOnInvalidData, Boolean bIsMigrate, Boolean bIsPublish, Boolean bForceCreateVersion, String lockIdMatch, SPUser modifiedBy, DateTime timeLastModified, Object varProperties, SPFileFragmentPartition partitionToCheck, SPFileFragmentId fragmentIdToCheck, SPFileFragmentPartition[] partitionsToDelete, Stream formatMetadata, String etagToMatch, Boolean bSyncUpdate, SPLockType lockType, String lockId, TimeSpan lockTimeout, Boolean refreshLock, Boolean requireWebFilePermissions, Boolean failIfRequiredCheckout, Boolean validateReqFields, Guid newDocId, SPVirusCheckStatus& virusCheckStatus, String& virusCheckMessage, String& etagReturn, Boolean& ignoredRequiredProps)     at Microsoft.SharePoint.SPFile.SaveBinary(Stream file, Boolean checkRequiredFields, Boolean createVersion, String etagMatch, String lockIdMatch, Stream fileFormatMetaInfo, Boolean requireWebFilePermissions, String& etagNew)     at Microsoft.SharePoint.SPFile.SaveBinary(Byte[] file)     at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterSharePointDav.<>c__DisplayClass1.<UploadToLocalSite>b__0(Boolean differentIdentity)     at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterUtil.Impersonate(DataAdapterInformation adapterInfo, String userName, String userDomain, String password, CodeToRunUnderImpersonation codeToRun)     at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterUtil.Impersonate(DataAdapterInformation adapterInfo, String userName, String password, CodeToRunUnderImpersonation codeToRun)     at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterSharePointDav.UploadToLocalSite(Uri targetUri, Byte[] buffer, Boolean allowOverwrite, DataAdapterCredentials credentials)     at Microsoft.Office.InfoPath.Server.SolutionLifetime.DataAdapterSharePointDav.Execute(XPathNavigator input, Uri folderUri, Boolean allowOverwrite, XPathTypedValue fileNameXpath, Boolean ensureXMLExtension, Document document, DataAdapterCredentials credentials, Boolean useDcl)     at Microsoft.Office.InfoPath.Server.DocumentLifetime.DataAdapterSharePointDav.Execute(XPathNavigator input)     at Microsoft.Office.InfoPath.Server.DocumentLifetime.Document.ExecuteDefaultSubmitAction()     at Microsoft.Office.InfoPath.Server.SolutionLifetime.ButtonSubmit.Click(Document document, XPathNavigator container)     at Microsoft.Office.InfoPath.Server.DocumentLifetime.EventClick.Play(Document document, BindingServices bindingServices, EventLogProcessor eventLogProcessor)     at Microsoft.Office.InfoPath.Server.DocumentLifetime.EventLogProcessor.ExecuteLog(Int32 expectedEventLogID)     at Microsoft.Office.InfoPath.Server.DocumentLifetime.Document.<>c__DisplayClass13.<PlayEventLog>b__11()     at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock)     at Microsoft.Office.InfoPath.Server.DocumentLifetime.Document.RunAndHandleExceptions(TryBlock tryblock)     at Microsoft.Office.InfoPath.Server.DocumentLifetime.Document.PlayEventLog(EventLog eventLog, Boolean partialPostback)     at Microsoft.Office.InfoPath.Server.Controls.PostbackPage.ProcessIndividual(HttpContext context, String eventLogText, Boolean firstEventLog)     at Microsoft.Office.InfoPath.Server.Controls.PostbackPage.OnPreInit(EventArgs e)     at System.Web.UI.Page.PerformPreInit()     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)     at System.Web.UI.Page.ProcessRequest()     at System.Web.UI.Page.ProcessRequest(HttpContext context)     at Microsoft.Office.InfoPath.Server.Controls.PostbackPage.<>c__DisplayClass1.<HandleRegularPostback>b__0()     at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock)     at Microsoft.Office.Server.Diagnostics.ULS.SendWatsonOnExceptionTag(UInt32 tagID, ULSCatBase categoryID, String output, Boolean fRethrowException, TryBlock tryBlock, CatchBlock catchBlock, FinallyBlock finallyBlock)     at Microsoft.Office.InfoPath.Server.Controls.PostbackPage.HandleRegularPostback(HttpContext context)     at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()     at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)     at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)     at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)     at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)     at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)     at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)     at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)     at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr managedHttpContext, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)  


    Joe--

    Tuesday, March 26, 2019 9:33 PM

Answers

  • We created a ticket with Microsoft on this issue, and it turned out to be a slow DB query.  We were directed to have SQL server do the indexes & statistics then ran  DBCC FREEPROCCACHE . 

    We ended up creating a weekly SQL server maintenance job for the indexes & stats. 

    As documented: https://docs.microsoft.com/en-us/sharepoint/support/server-performance/outdated-database-statistics

    So far we've noticed performance improvement with SharePoint as a whole and no more reports on this issue.

    But, given you're disabling a couple SharePoint health jobs, and creating SQL jobs.  May be a good idea to open a case with Microsoft and get their blessing. 


    Joe--

    • Marked as answer by rainmakers Monday, May 20, 2019 4:29 PM
    Monday, May 20, 2019 4:29 PM

All replies

  • Hi, Joe,

    I am trying to reproduce your issue and want to confirm something with you

    1. Do the users experience the same issue when saving word or PowerPoint files to SharePoint?
    2. Do the issue occur when uploading to a certain document library or anywhere in the SharePoint site?
    3. What’s the size of the file?
    4. Will the problem occur again with Excel safe mode?

    Best Regards

    Jerry Xu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Wednesday, March 27, 2019 9:15 AM
  • Jerry,

    For your questions.   Currently I only have 1 officially reported issue, but a second individual had mentioned the issue as well. 

    1. The report I have is just for Excel.   

    2. For the reported issue. It is just with one Excel file.   (This file does get edits multiple times a week. )  Also, per the user primarily he just views documents on SharePoint, so this one is the oddity that he edits.

    3. 116Kb

    4. He hasn't tried using Excel in Safe mode. 

    When talking with the person having the problem, he mentioned that he would try to copy the data to a new excel file as well.



    Joe--

    Friday, March 29, 2019 1:06 PM
  • Hi, rainmakers,

    According to your description, for now there is only one excel file having such issue. The file may be corrupted. Try to copy the data to a new excel file and upload it to see if it occurs again.

    For the second individual, we shall get more information about the issue to see if they have the same symptoms

    Best Regards

    Jerry Xu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Tuesday, April 2, 2019 1:37 AM
  • For the first person, the new file test is in progress.   

    For the 2nd individual there are two Excel files.   I suggested trying the same test.   

    Given this is an intermittent issue I think it will take some time to see if corrupt office files are the culprit.

    Thanks.



    Joe--

    Tuesday, April 2, 2019 4:28 PM
  • Hi, rainmakers,

    Feel free to reply with any update, we are looking forward to help with your issue.

    Best Regards

    Jerry Xu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Thursday, April 4, 2019 8:51 AM
  • The new file did not resolve the problem.  I just got a report that the new file & new name is experienced the same issue.


    Joe--

    Tuesday, April 9, 2019 2:32 PM
  • I did try clearing the SharePoint cache in guid subdirectory of: C:\ProgramData\Microsoft\SharePoint\Config\.   But, still looking for other suggestions.

    Joe--

    Tuesday, April 9, 2019 9:28 PM
  • I do have an update.   When viewing the issue with my user. I found that the document does eventually save, but it takes 3-5 minutes for the first save.  Subsequent saves are significantly faster.

    Joe--

    Monday, April 22, 2019 7:08 PM
  • We created a ticket with Microsoft on this issue, and it turned out to be a slow DB query.  We were directed to have SQL server do the indexes & statistics then ran  DBCC FREEPROCCACHE . 

    We ended up creating a weekly SQL server maintenance job for the indexes & stats. 

    As documented: https://docs.microsoft.com/en-us/sharepoint/support/server-performance/outdated-database-statistics

    So far we've noticed performance improvement with SharePoint as a whole and no more reports on this issue.

    But, given you're disabling a couple SharePoint health jobs, and creating SQL jobs.  May be a good idea to open a case with Microsoft and get their blessing. 


    Joe--

    • Marked as answer by rainmakers Monday, May 20, 2019 4:29 PM
    Monday, May 20, 2019 4:29 PM