Sign in
 
Home20132010Other VersionsLibraryForumsGallery
TechCenter >
> 
> 
Unable to save excel 2010 files to san

Answered Unable to save excel 2010 files to san

  • Thursday, May 03, 2012 9:16 AM
     
     
    Sign In to Vote
    0

    Hi all,

    We recently acquired a new IBM StorWiz 7000 SAN.
    Data migration ( using robocopy) went fine, but after copying the first folder and giving users access to the new data location, a problem popped up on all PCs.

    All these PCs run:
    Windows 7 SP1 x64 Professional
    Office 2010 SP1 x64
    McAfee Virusscan Enterprise 8.8
    The SAN is approached using CIFS
    I myself am owner of and have full permissions on root/ all subfolders.
    there is no offline functionality in play.
    Saving to local disk or the old SAN works fine
    Windows w2k3 domain.

    problem description:
    When a user ( any user) tries to save an excel file to the server, he gets a window stating "Document not saved"
    This happens on new or already existant files. When looking in the network folder, a file IS saved however, with the correct name, but it is 0Kb size and when opened presents an empty spreadsheet.

    I have searched hi and lo but this time my case seems to be different from all the others experiencing roughly the same issue.

    I implemented and tried all the below steps in trying to resolve this, I may forget a couple, none helped in any way;
    - Hotfix KB983458-x64 ( not applicable for my system)
    - Run Excel in safe mode.
    - Save document as .xls instead of default .xlsx.
    - Add the network resource to trusted locations in Excel options.
    - Saving from any other application to the share presents no problem. ( robocopy had no problem replicating the folder from the old to the new san)
    - A couple of registry hacks, more than I care to recall, had no effect.
    - it is NOT a ntfs security problem, I am admin ( Full control, owner) on all systems/folders in the domain.
    - Disable Antivirus

    Until this is resolved, our new SAN is unusable to a solution is needed urgently.

    I am fairly convinced that the problem lies with Office as other applications do not experience the same symptoms.

    thanks for any input


    • Edited by ICT Dept Thursday, May 03, 2012 9:19 AM
    •  
     

All Replies

  • Friday, May 04, 2012 7:58 AM
    Moderator
     
     
    Sign In to Vote
    0

    Saving to local disk or the old SAN works fine


    Hi,

    According to your description, the issue is related to the host end. Except the Anti-Virus software, I would suggest checking files backup settings on the new SAN which can lock the shared folder from being written.

    Or

    Can you determine if it is caused by network issue?

    Sincerely
    Rex Zhang

    Rex Zhang

    TechNet Community Support





     
  • Thursday, May 10, 2012 6:46 AM
     
     
    Sign In to Vote
    0

    Hello Rex,

    it is none of the above.

    As I stated, the problem only appears when saving Office 2010 SP1 x64 edition files to the SAN.
    Anything else, be it simple text files to huge photoshop files, works flawlessly, so there's something about the way office saves files that's causing this problem.

     
  • Monday, June 11, 2012 6:40 PM
    Answerer
     
     
    Sign In to Vote
    0

    Hi - I've been looking over this issue, we've seen some issues around Excel files saving at 0KB, most of them have to do with Anti-Virus not "letting go" of the file when saving.  A few of them deal with the network connection dropping in the middle of the save.

    However most of them are more difficult than a Forum post can deal with, so if you're still having the problem you might need to open a support case with Microsoft to help troubleshoot in more depth.

    Please remember to mark this as "answer" if it resolves/answers your issue.

     
  • Tuesday, June 12, 2012 7:19 AM
     
     Answered
    Sign In to Vote
    0
    I just got word back from the SAN producer, there was appearantly a firmware problem which caused a failure in writing Office files with custom attributes. The firmware update solved the issue. Thank you for any help given though! Feel free to close the thread.