SharePoint Developer Center > SharePoint Products and Technologies Forums > SharePoint - Excel Services > 'Document Not Saved' when publishing an over 30MB workbook to Excel services
Ask a questionAsk a question
 

Answer'Document Not Saved' when publishing an over 30MB workbook to Excel services

  • Friday, October 23, 2009 8:18 AMStu Pittwood Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi All,

    When I try to publish a workbook which is over 30Mb to Excel services I'm getting 'Document Not Saved' everytime.  The max size of documents on the farm is 100Mb & I am able to Save the document into a normal library.  I can't see anything in the moss logs that relates to this.

    MOSS 2007, SP2 x64 running on Windows 2008 (x64).  The client is Windows 7 x64 & Office 2007 SP2.

    Has anyone seen this before?

    Thanks in advance.

    Stu

Answers

  • Tuesday, October 27, 2009 7:50 AMLambert QinMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Hi Stu,

     

    Thanks for your cooperation.

     

    I successful reproduce your issue in my Windows Server 2008 64 bit environments, and this is a known issue that Windows Server 2008 have restrict the upload size to 28M.

    See KB article for more information, You cannot upload files that are larger than 28 MB on a Windows Server 2008-based computer that is running Windows SharePoint Services 3.0 (http://support.microsoft.com/kb/944981)

     

    I set the value of the maxAllowedContentLength property to 52428800 (50M), and I could publish the excel files to the SharePoint.

    Please change it in your environment to resolve your issue.

     

    However, the Excel file you gave me seems not capability with Excel Services, it keeps throwing File Not Found: Excel Services cannot load the workbook that you requested error.

    Could you please clarify that the excel file works normally in your environment?

     

    Lambert Qin

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  


    Sincerely,
    Lambert Qin
    Posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked As Answer byStu Pittwood Wednesday, October 28, 2009 8:37 AM
    •  

All Replies

  • Monday, October 26, 2009 4:03 AMLambert QinMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi Stu,

     

    As there is no obvious logs related with your issue and the workbook could be saved to a normal library, I suppose the issue is related with Publish to Excel services feature in Office Client.

     

    Could you please collect a network monitor trace and a SPSReport and send to the workspace for further investigation? (If you are not sure how to do that, please refer to steps at the end of the reply.)

    Workspace URL: (https://sftasia.one.microsoft.com/ChooseTransfer.aspx?key=af2dab6d-833e-4ed5-8682-0b967dcd2207)

    Workspace Password: -86{!@L2*5V3N

     

    If the workbook does not contain sensitive data, please also send the workbook to the workspace so that I could try to make a local reproduce.

    If you could send me the workbook, please try some different workbooks and let me know if the issue happened on other workbooks.

     

    Here is the steps to capture a network trace log for your reference:

    1.       Download Microsoft Network Monitor 3.3 if you don’t have Network Monitor tool installed.

    http://www.microsoft.com/downloads/details.aspx?familyid=983B941D-06CB-4658-B7F6-3088333D062F&displaylang=en

    2.       Install the Microsoft Network Monitor 3.3 on one of your desktop.

    3.       Launch the Network Monitor.

    4.       Create a New Capture in the toolbar.

    5.       Click Start to capture the network traffic.

    6.       Reproduce the issue.

    7.       Click Stop to stop capturing the network traffic.

    8.       Click Save as button to Save the network trace log as a cap file.

    9.       Send the cap file to the workspace

     

    To capture SPSReports, please follow the steps:

    1)      Download the SPSReport tool from http://spsreport.codeplex.com/

    2)      Reproduce the issue.

    3)      Run the SPSReport.exe on the WFE and Application Server runs Excel Services.

    4)      Choose option 3 (Full).

    5)      On your system a CAB file will be generated in the %systemroot%\SPSReports\Portal\rpt\Cab directory called %COMPUTERNAME%_SPSReports.CAB.

    6)      The CAB file will contain the reports generated by the SPS Reporting Tool.

    7)      Send the cab file to the workspace below.

     

     

    Lambert Qin

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact mtngfb@microsoft.com  

     


    Sincerely,
    Lambert Qin
    Posting is provided "AS IS" with no warranties, and confers no rights.
  • Monday, October 26, 2009 1:57 PMStu Pittwood Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Lambert,

    I'm uploading the files to the workspace.  I've tried many files, everything over ~30Mb fails.  if I split the sheets into two, upload them & create a dashboard that ties the two together it all works (allbeit very slowly ... as per my other post).

    Regards

    Stu

  • Tuesday, October 27, 2009 7:50 AMLambert QinMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    Hi Stu,

     

    Thanks for your cooperation.

     

    I successful reproduce your issue in my Windows Server 2008 64 bit environments, and this is a known issue that Windows Server 2008 have restrict the upload size to 28M.

    See KB article for more information, You cannot upload files that are larger than 28 MB on a Windows Server 2008-based computer that is running Windows SharePoint Services 3.0 (http://support.microsoft.com/kb/944981)

     

    I set the value of the maxAllowedContentLength property to 52428800 (50M), and I could publish the excel files to the SharePoint.

    Please change it in your environment to resolve your issue.

     

    However, the Excel file you gave me seems not capability with Excel Services, it keeps throwing File Not Found: Excel Services cannot load the workbook that you requested error.

    Could you please clarify that the excel file works normally in your environment?

     

    Lambert Qin

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  


    Sincerely,
    Lambert Qin
    Posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked As Answer byStu Pittwood Wednesday, October 28, 2009 8:37 AM
    •  
  • Tuesday, October 27, 2009 8:49 AMStu Pittwood Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Lambert,

    Yes, the sheet works normally in our environment.

    Do I need to make the change to the web.config file on each front end server?

    Stu
  • Tuesday, October 27, 2009 9:04 AMLambert QinMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi Stu,

     

    Yes, the changes should be applied to all the WFEs.

     

    As the sheet works normally in your environment, the issue should be resolved after applying the settings.

     

    Let me know the result if possible.

     

    Lambert Qin

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com  


    Sincerely,
    Lambert Qin
    Posting is provided "AS IS" with no warranties, and confers no rights.
  • Wednesday, October 28, 2009 8:37 AMStu Pittwood Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Lambert,

    Working perfectly.

    Thanks very much.

    Stu