locked
Office 2007 and Windows 7 Slow saving file to the network RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    1
    Sign in to vote
    I have installed a small network in our office.  I have 2008 server and all the workstation are runnin windows 7 and office 2007.  Saving files to the file server from Office is slow.  Any other application works fine.  File copy works fine as well, very fast.  I have one windows XP and that is fast as well.  This only happens with windows 7 and office 7 saving file to the network.  Local save is fast as well.  Please please help.

    Thanks
    Wednesday, January 27, 2010 6:05 PM

Answers

  • Question
    Sign in to vote
    7
    Sign in to vote

    I have spent a month researching this problem.  You will need to disable SMB2 on the server that holds the share.  To do so:

    Add a REG_DWORD entry named Smb2 with a value of 0 to
    HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters


    Then reboot the server.

     

    -Vitaly

    • Proposed as answer by almazalmazov Friday, March 26, 2010 7:59 PM
    • Marked as answer by dtabib Tuesday, April 6, 2010 12:03 PM
    Friday, March 26, 2010 7:56 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    Please boot the system to clean boot and see how it works:

     

    How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

     

    Hope this helps. Thanks.

    Nicholas Li - MSFT
    • Marked as answer by Nicholas Li Monday, February 1, 2010 6:40 AM
    Thursday, January 28, 2010 10:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you Vitaly very much, this worked 100%. 
    • Marked as answer by dtabib Tuesday, April 6, 2010 12:04 PM
    Tuesday, April 6, 2010 12:04 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    Please boot the system to clean boot and see how it works:

     

    How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

     

    Hope this helps. Thanks.

    Nicholas Li - MSFT
    • Marked as answer by Nicholas Li Monday, February 1, 2010 6:40 AM
    Thursday, January 28, 2010 10:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    No difference.
    Monday, February 1, 2010 5:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Are you still having this issue?  i am having the same issue on my win 7 pcs saving with office 2007 to my domain.  its fine on xp with office 2007
    Tuesday, March 9, 2010 8:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have a similar problem, with a Windows 7 Pro 64 bits in Excel 2007 fully patched a specific file make an AppCrash when saving to the SBS 2008 server. The AppCrash doesn't happen each time but often (50 % to 75 %).
    With an XP SP3 in Excel 2007 fully patch saving the same file never fails.

    Wednesday, March 10, 2010 9:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes, I still have the same issue.   I do not know what to do.
    Thursday, March 11, 2010 4:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It seams to be linked with the use of compatibility mode in a 64 bits OS, when saving the same file to xlsx I have no more AppCrash but I have to use compatibility mode. I still have no solution
    Friday, March 12, 2010 9:42 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm having the same problem saving a file with Excel 2007 to a mapped network drive.  

    My computer is a new Dell Precision Workstation running Win7 64 bit, the server is a brand new Dell running SBS 2008 (both fully patched)

    If I try to 'SaveAs' to a mapped network drive Excel just hangs.  Sometimes loading files with Word or Excel from the mapped drives will not work either. 
    Oddly my mapped drives always show the red 'X' suggesting they aren't available but when I click on the icon the contents are fully accessible.

    Any suggestions?
    Sunday, March 14, 2010 8:35 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    If you have installed some security software (firewall, anti-virus, anti-spyware, etc.), please temporarily disable or uninstall it to see if it works.

    Nicholas Li - MSFT
    Monday, March 15, 2010 2:25 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    If you have installed some security software (firewall, anti-virus, anti-spyware, etc.), please temporarily disable or uninstall it to see if it works.

    Nicholas Li - MSFT
    I'm not sure if this is directed at me but I do have MS Security Essentials and Symantec 'Endpoint' Protection 11.0.5002.333 running.
    To be honest it would be too big of a pain to uninstall Symantec (and I'm not aware of any way to disable it when it's being managed by the network service) and I'm going to assume MS Security Essentials is not the culprit.

    I'll see if it works any better next time we get a fresh Win7 computer to test on before installing Symantec.


    Monday, March 15, 2010 10:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm seeing the same issue in our environment.  One user takes up to 40 seconds to save a 100k file.  The delay will last for a few minutes then clear up.  In the latest case my user saved the file about 6 times with it taking about 40 seconds to save.  After another try, the save time is normal again. 
    Tuesday, March 16, 2010 7:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I have to say I am having the same problem, but it is taking so long I need to reboot.

    Windows 7 64bit Office 2007, Server 2008. Document is ion compatability mode... Any ideas, Anti Virus and Firewall not affecting it.
    Wednesday, March 17, 2010 9:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Any updates from MS on this? 
    Wednesday, March 24, 2010 6:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I have not heard anything back.  Still this is an issue.
    Thursday, March 25, 2010 12:45 PM
  • Question
    Sign in to vote
    7
    Sign in to vote

    I have spent a month researching this problem.  You will need to disable SMB2 on the server that holds the share.  To do so:

    Add a REG_DWORD entry named Smb2 with a value of 0 to
    HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters


    Then reboot the server.

     

    -Vitaly

    • Proposed as answer by almazalmazov Friday, March 26, 2010 7:59 PM
    • Marked as answer by dtabib Tuesday, April 6, 2010 12:03 PM
    Friday, March 26, 2010 7:56 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    On your 2008 file share server:

    Add a REG_DWORD entry named Smb2 with a value of 0 to
    HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters

    Reboot the server.

    Friday, March 26, 2010 7:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Has anybody else had an opportunity to try almazalmazov's fix? 
    Monday, March 29, 2010 3:31 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Has anybody else had an opportunity to try almazalmazov's fix? 
    Monday, March 29, 2010 3:31 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I will try this and let you knwo. 

    Thanks

    Tuesday, March 30, 2010 1:49 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    We are having this exact same issue with saving files over the network on Windows 7 / Office 2007. Takes about 40 seconds at times. This is intermittant.
    Tuesday, March 30, 2010 7:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have the same issue. I fixed it under 1 user ID but now I can't remember what I did.

     

    Tuesday, March 30, 2010 8:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    windows 7/office 2007/windows 2008 domain and IFS file share on AS400. Administrator account on local works just fine. All domain accounts are slow. I change something (can't remember what) and made it faster (opens in 6 seconds vs. 45 seconds). 
    Tuesday, March 30, 2010 9:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Curious why SMB2 would need to be disabled for traffic between Win7 and SBS 2008.  I am hesitant to try this fix in my environment without conformation and explanation...

    Here is my environment

    Dell T710 Dual Xeon 2.6ghz  12GB, raid 1 (os)  raid 5 (data)

    SBS 2008

    10 Windows 7 Clients with Office 2007

    Desktop and Documents directories mapped to the server raid 5 array

    S drive mapped to shared folder on the raid 5 array  (\\server.domain.local\SHARED)

    First file loading (or saving) of the day (doesnt matter if from Documents/Desktops or Shared) takes FOREVER, all that is displayed is a "Downloading (or Saving) FILENAME" with a blank progress bar on the bottom part of excel or word (where the zoom bar is).

    Sometimes after 20 seconds it loads or saves, sometimes its minutes.  But after that first one, everything seems to be fine, and works quite fast.

     

    I have hunted around for fixes, most of them do not make any sense, but one I did try was to use \\server.domain.local\shared instead of \\server\shared.  This didn't seem to make a difference.

    Any help would be appreciated!

    Thursday, April 1, 2010 5:09 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    SMB2 is and updated version of SMB1 protocol.  SMB2 is native to Server 2008 and Windows 7 and Vista.  If any of your clients would be XP, OR your server would be W2K3, then SMB1 would be used instead and you would not have the problem you are experiencing right now.  Disabling SMB2 on the W2K8 server forces Windows 7 to become backward compatible and switch to using SMB1.  However, the problem you are experiencing is caused by MS Office 2007 is not working properly with SMB2 protocol.  Since I am not a developer and I do not work for Microsoft I can not tell you why Office 2007 works this way with SMB2.  For testing purposes, you can try to search for how to disable SMB2 on your Windows 7 client rather then disabling it on the server.  This should provide same result.  I know that disabling something may not be the prettiest solution but this is the only one that worked for this problem so far.

    Thursday, April 1, 2010 3:57 PM
  • Question
    Sign in to vote
    2
    Sign in to vote

    SMB2 is and updated version of SMB1 protocol.  SMB2 is native to Server 2008 and Windows 7 and Vista.  If any of your clients would be XP, OR your server would be W2K3, then SMB1 would be used instead and you would not have the problem you are experiencing right now.  Disabling SMB2 on the W2K8 server forces Windows 7 to become backward compatible and switch to using SMB1.  However, the problem you are experiencing is caused by MS Office 2007 is not working properly with SMB2 protocol.  Since I am not a developer and I do not work for Microsoft I can not tell you why Office 2007 works this way with SMB2.  For testing purposes, you can try to search for how to disable SMB2 on your Windows 7 client rather then disabling it on the server.  This should provide same result.  I know that disabling something may not be the prettiest solution but this is the only one that worked for this problem so far.

    Thanks for the post, I did stumble upon a site that mentioned how to do on both client and server, its vista, but I checked the reg is the same in 7
    http://www.petri.co.il/how-to-disable-smb-2-on-windows-vista-or-server-2008.htm

    I will do this tonight and report back my findings.

    Thanks

    Thursday, April 1, 2010 11:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you Vitaly very much, this worked 100%. 
    • Marked as answer by dtabib Tuesday, April 6, 2010 12:04 PM
    Tuesday, April 6, 2010 12:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    For all of you,

     

    I want to thank you for your posts.  Just follow Vitaly's recommendation and it will fix the problem.  It worked for me.

     

    On your 2008 file share server:

    Add a REG_DWORD entry named Smb2 with a value of 0 to
    HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters

    Tuesday, April 6, 2010 12:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Glad to hear it worked for you. My issue is a little different though. My File Share is on my AS400 System not on a 2008 server.  I wonder if this would help with my issue too? anyone have any thoughts?  Also could someone explain SMB2 protocol?
    Tuesday, April 6, 2010 12:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have same problem. I diabled SMB2 from server 2008 R2x64. It's help temperary, but next day and after boot server its slowly again. Now I running my server only for DNS and DC and i move my file server is old XP. Now everything work fine, but only limited users can connect xp same time.

    I hope some some service pack etc. patch came soon.

     

    Saturday, April 10, 2010 12:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I figured out what I did. I have done this fix on 4 Windows 7 machines and they are all working just fine. it is a little tricky and I can't explain why this happens, maybe one of you can.

    logged on as the user having the issue:

    #1 in Excel 2007 turn on the allow trusted locations on my network (Trust Center, Trusted locations it is at the bottom of the page)

    #2 change the IP address of the computer to something else. 

    #3 Try the mapped drive now. It should open in 6 seconds verses the 45 seconds it was taking before.

    #4 you can put the IP address back to the old number and turn off the Trust Locations

    #5 test again and it should still work.

    Bad part is you have to do that for each user that will be on that computer. I don't know why or what I am fixing when I do this. But it worked for me.

    Thanks and good luck.

     

     

    Friday, April 16, 2010 2:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I figured out what I did. I have done this fix on 4 Windows 7 machines and they are all working just fine. it is a little tricky and I can't explain why this happens, maybe one of you can.

    logged on as the user having the issue:

    #1 in Excel 2007 turn on the allow trusted locations on my network (Trust Center, Trusted locations it is at the bottom of the page)

    #2 change the IP address of the computer to something else. 

    #3 Try the mapped drive now. It should open in 6 seconds verses the 45 seconds it was taking before.

    #4 you can put the IP address back to the old number and turn off the Trust Locations

    #5 test again and it should still work.

    Bad part is you have to do that for each user that will be on that computer. I don't know why or what I am fixing when I do this. But it worked for me.

    Thanks and good luck.

     

     

    Friday, April 16, 2010 2:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi -- this is occurring for me with Windows 7 x64, Office 2007 and Windows Server 2003 R2.  Disabling SMBv2 on the server isn't an option for me since 2003 doesn't use SMBv2.

    This only happens when saving to Desktop and My Documents, which are redirected to a share.  We *can't* reproduce the problem with a mapped drive letter, only when saving to the Desktop or My Documents.

    Also, there is a discussion on Server Fault regarding this problem.
    Tuesday, April 27, 2010 7:51 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Unfortunately none of this has worked for me.  I guess I'll be forced into opening a support case with Microsoft.
    Tuesday, May 11, 2010 1:47 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi -- this is occurring for me with Windows 7 x64, Office 2007 and Windows Server 2003 R2.  Disabling SMBv2 on the server isn't an option for me since 2003 doesn't use SMBv2.

    This only happens when saving to Desktop and My Documents, which are redirected to a share.  We *can't* reproduce the problem with a mapped drive letter, only when saving to the Desktop or My Documents.

    Also, there is a discussion on Server Fault regarding this problem.


    We may have found a fix for this.

    Users who had this issue were also getting one or more undeletable .tmp files on their Desktop.  (These files would disappear upon reboot.)  While not totally relevant, this article (http://support.microsoft.com/kb/328607) points to an indexing of these files as the cause.

    Since our Desktop and My Documents folders are redirected to the network, these locations are available offline.  Disabling indexing of the offline files cache seems to have worked -- we haven't experienced any slow saves since doing this.

    To summarize: try disabling indexing on the file locations where you are experiencing slow save times.  Try disabling indexing of Offline Files if appropriate for your situation.

    • Proposed as answer by jnelsoncpath Wednesday, June 23, 2010 9:50 PM
    Wednesday, May 12, 2010 9:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Sorry I am jumping in on this older thread.  So glad I saw this post from Clay.  I am also plagued with this slow save problem, but like Clay, it is with Server 2003 rather than 2008 so no SMB2 in effect.  My domain has 34 Windows 7 Enterprise clients connected to SBS 2003 R2 and Win 2003 R2 file servers.  When users open a file from the redirected documents location on the network and click the save icon after making changes in Office 2007 apps (any of them), the file fades out, says not responding in the title bar, the circle shaped mouse cursor appears and spins, and a small box pops up over Office that says, " Saving As \\servername\sharename\filename" for about 60-80 seconds and then all is back to normal again.  I can copy files to the servers at 50-80MB per second on my network so it isnt the infrastructure.

    The indexing idea makes good sense.  I will test this and post my results.

    James

    James Nelson
    Friday, June 18, 2010 3:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi, we too are having the issue of Office applications (in this case Office 2007) running on Windows 7, being slow to save files to the User's Documents folders where this folder is configured as an Offline folder (i.e. Offline files). In our situation the folder is redirected to a Windows SBS 2003 server share.

    I tired the SMB2 set to 0 and SMB1 set to 1, and this reduced the slow saves which had been from 5-35 minutes down to about 35 to 60 seconds. I then tried Clay's suggestion of turning off Indexing on the Offline files, and this has stopped the slow saves completely.  This is the workaround that we are currently using.

    Interestingly, our Windows XP, and our Windows Vista users have never had this issue.  Also removing antivirus programs from the User's Windows 7 PCs (and Win SBS 2003 server) did not remove or alter the issue either. For us the "slow save" does not occur every time but about every third "modify document and save". I found that just resaving a non-modified file did not cause the issue to happen, but even a slight modification and then saving, would cause the problem on around the third "modification and save".  It was easy to create a small test file of a few lines only.  And as soon as I re-enabled Indexing the issue could be caused once again.

    I am hoping that Microsoft's Windows 7 teams will be able to come up with a fix so we can turn Indexing back on.  Clay, thanks for your suggestion, it sure helped me out.

    Wednesday, June 23, 2010 1:43 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I believe I have repaireed my issue thanks to Clay Kimber (above). 

    This thread appears to have two problems discussed; slow Office save times to Server 2008 AND slow Office save times to Server 2003.  The SMB2 option was suggested for the 2008 users experiencing the problem, however SMB2 doesnt exist in a 2003 environment so cannot be the fix for it.

    Clay suggested the cause may be an offline files cache that was being indexed by Windows 7 which made good sense.  I tested this solution in the lab and found that all issues went away and I could not make them happen again after disableing indexing on the offline files cache.  I have since instructed my affected users to disable indexing on their offline files, and presto!  No more slow save times between Windows 7 and 2003.

    James

    James Nelson
    Wednesday, June 23, 2010 9:54 PM
  • Question
    Sign in to vote
    6
    Sign in to vote

    we think we have fixed the issue here in our office. Turns out Xp machines have a service on by default but Windows 7 machines do not. After spending 6 weeks working with MicroSoft and also opening a ticket with IBM (As400).  We have been running just fine and NO SLOW REPSONSE issues. We went from 45 seconds to open or Save As a file to 3 seconds.

    Go into your services (this must be done with an Administrator account).  Locate the service WEB CLIENT. I would bet it is set to manual.  If you look at your XP machines the service is set to automatic. Turn this service on and set it to automatic.  Now try opening your files and saving them from the shared drive. It should be MUCH faster.

    Please let me know if this doesn't work for you.

    • Proposed as answer by Avery Scott Monday, August 9, 2010 4:27 PM
    Thursday, June 24, 2010 11:59 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I would also like to report the same issue.

    Brand new equipment and network with SBS 2008 and Win 7 Desktops all very good spec and gigabit lan.

    Its is slow to open Office docs from the shared drive and slow to attach office docs in Outlook.

    Im going to try the SMBv2 fix but surely there has to be a proper MS solution soon.

    • Proposed as answer by riethriley Thursday, July 1, 2010 4:31 PM
    Thursday, July 1, 2010 4:14 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    QWAZ01 - I don't think the SMBv2 will do the trick for you. Check your services. see if the WEB CLIENT service is on. If it is not on, turn it on. That has fixed the issue for ALL 30 of my computers here that are running Windows 7. This service is turned on by default in Windows XP but not in WIN7.
    • Proposed as answer by riethriley Thursday, July 1, 2010 4:32 PM
    Thursday, July 1, 2010 4:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Folks,

    I am reading this with great interest. We have the same problem. Saving a file takes 40 seconds. Here is the setup:

    Windows 7
    Office 2007
    Windows 2003 File Server
    My Documents Redirected via GPO

    There are several different solutions suggested here. How should one approach this?

    Thanks!

    Thursday, July 1, 2010 4:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    QWAZ01 - I don't think the SMBv2 will do the trick for you. Check your services. see if the WEB CLIENT service is on. If it is not on, turn it on. That has fixed the issue for ALL 30 of my computers here that are running Windows 7. This service is turned on by default in Windows XP but not in WIN7.


    Were you having similar issues then?

    My network is SBS2008, Win7 Pro, Office 2007 all with full patching. The problem is that its slow to open Office docs from the shared drive and slow to attach office docs in Outlook. This isnt a constant issue, it comes and goes randomly throughout the day on different shares, files and computers.

    Other people on other forums have had some success with disabling SMBv2 thats why i was going to try it. Did yours fix itself instantly after enabling the Web CLient service? Was your issue random or constant?

    Thanks

    • Proposed as answer by riethriley Thursday, July 1, 2010 5:19 PM
    Thursday, July 1, 2010 4:50 PM
  • Question
    Sign in to vote
    2
    Sign in to vote

    RudyDude,

    If you are seeing this with Windows 7 and Win 2003 file server with redirection in place, I have to suggest that the offline files cache on Windows 7 may be the issue.  Have a look in your users' folders on the server and look for temp files.  If you see a bunch of odd looking temp files with alpha-numeric characters in their names, run a test by disabling indexing on the user's offline files cache in Indexing Options in the Control Panel. 
    In our environment, which is very simialr to yours, we found that as soon as we disabled the indexing of offline files, all slow save speeds were repaired and Office started deleting its temp files again. Just make sure to have the users delete any remaining temp files from their folders.
    I hope this helps.

    James

    James Nelson
    Thursday, July 1, 2010 5:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    it was taking us 30-45 seconds to open or do a save as with Office 2007 files. We have a Windows Server 2008 domain, Windows 7 computers and my share is on an AS400 (IFS drive). I spetn 4 weeks working with Microsoft on the issue but they couldn't figure it out. I could open TXT and PDF files just fine. it was only OFFICE. Logged on as Administrator, turn WEBCLIENT service from MANUAL to AUTOMATIC and start the service. Once you do that the user can log in and MAGIC...3 seconds my files opened. I could also do a save as in 3 seconds.

     

    Thursday, July 1, 2010 5:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    RudyDude,

    If you are seeing this with Windows 7 and Win 2003 file server with redirection in place, I have to suggest that the offline files cache on Windows 7 may be the issue.  Have a look in your users' folders on the server and look for temp files.  If you see a bunch of odd looking temp files with alpha-numeric characters in their names, run a test by disabling indexing on the user's offline files cache in Indexing Options in the Control Panel. 
    In our environment, which is very simialr to yours, we found that as soon as we disabled the indexing of offline files, all slow save speeds were repaired and Office started deleting its temp files again. Just make sure to have the users delete any remaining temp files from their folders.
    I hope this helps.

    James

    James Nelson


    Thanks for the suggestion James. I will have a look at that now.

    Rudy

    Thursday, July 1, 2010 6:31 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    RudyDude,

    If you are seeing this with Windows 7 and Win 2003 file server with redirection in place, I have to suggest that the offline files cache on Windows 7 may be the issue.  Have a look in your users' folders on the server and look for temp files.  If you see a bunch of odd looking temp files with alpha-numeric characters in their names, run a test by disabling indexing on the user's offline files cache in Indexing Options in the Control Panel. 
    In our environment, which is very simialr to yours, we found that as soon as we disabled the indexing of offline files, all slow save speeds were repaired and Office started deleting its temp files again. Just make sure to have the users delete any remaining temp files from their folders.
    I hope this helps.

    James

    James Nelson


    Thanks for the suggestion James. I will have a look at that now.

    Rudy


    James,

    This appears to have worked. One thing I noticed is that a status message is now displayed when you hit the "Documents" Library. It says "Some library features are unavailable due to unsupported library locations. Click here to learn more..."

    When I click to learn more I can ignore future messages or click help. Help says:

    What types of locations are supported in libraries?

    You can include folders in a library from many different locations , such as your computer's C drive, an external hard drive, or a network.

    On a network

    Yes, as long as the network location is indexed or has been made available offline. (See the question below.)

     

    It is made available offline in my case so I think I am OK on this. Just need to suppress the message for users.

     

    Thanks again.

    Rudy

    Thursday, July 1, 2010 7:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes that message is normal.  It just means that instant searches will not be available on that folder.  Searches should still be plenty fast though. 

    Best, James

    James Nelson
    Thursday, July 1, 2010 7:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Disabling SMBv2 doesnt seem to have worked for me. Is there a way of checking to see if it is enabled or not other than the reg key?

     

    Users have reported that when adding attachments to emails, if they add the attachment before writing the message the freeze problem doesnt seem to happen.

     

    Saving office docs to the network has improved but still takes a few seconds per save.

     

    Any other ideas or updates?

    Friday, July 9, 2010 12:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    James Nelson's post regarding disabling indexing options seems to have worked for a lot of my clients. We have been getting reports of slow saving and slowness browsing network shares only on our networks running SBS 2008, with Windows 7 client workstations. The reports seem to only be related to Office files, PDFs have not been affected.

     

    Here's the troubleshooting procedure I've gone through when a client reports this slow saving:

     

    1. From the Start Menu , type in 'Indexing Options' in the Search Bar 
    2. Click 'Modify'
    3. Uncheck 'Offline Files'
    4. Restart the workstation (not sure if this is necessary).

    If they still are experiencing slow saving, or opening of files on the network, that's when I'll apply the SMBv2 Fix on the server and client listed here:


    So far, I have not had anyone report the issue with both fixes applied. I am currently testing disabling the Offline Files indexing only with one client, to see if we can leave SMBv2 running and avoid a server restart.

    Sam

     

    • Edited by SamHopwood Tuesday, July 20, 2010 3:55 PM additional info
    Tuesday, July 20, 2010 3:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi HeadShok,

    Did this work for you? We are experiencing the same issues except problem is not with file saving (that I know of) but with file opening... Usually hangs in the morning first thing, then is OK opening any file for quite a while, then hangs again after a random time (could be ten minutes, could be hours, could be the next day!) then is ok for a while...

    For anyone else who is interested under normal circumstances a packet sniffer shows SMB2 being used with no errors of any great issue. Then when the random 'hang' happens there are two errors I don't normally see repeated a few times "getinfo response, error STATUS_OBJECT_NAME_NOT_FOUND" and "STATUS_OBJECT_NAME_COLLISION".

    This affects about 5 clients in a 50 user site accessing an SBS 2008 server (which was migrated from SBS 2003)... I have only seen it hang with Excel (although this is the most used application), Excel just sits saying 'Downloading <filename>' and then eventually if left if will sometimes come up with an error saying  - " Cannot be accessed. The file may be corrupted, located on a server that is not responding, or read-only. - ... I find the " quotation mark at the beginning unusual, I think this error normally has file name there?

    I have disabled SMB Version 2 on the client only, rebooted, and from the packet sniffer can confirm it is now running SMB and not SMB2. I will log back in in the morning as the problem is reproducable if left after a while, if it works I'll post back.

    Thank you

    Wednesday, October 13, 2010 4:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This worked for us also, WOOHOO! :o)

    Friday, October 15, 2010 3:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi, we met the same problem: Windows 7 with mapped drive to IFS on AS400. Thanks to your post we fixed it in 1 day searching the web for anrswers.

    Thanks again!

    Monday, October 25, 2010 7:59 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for this, I have struggled with this as well. I always thought it's a network latency issue but this fixed the problem. Thank you.
    Anise
    Monday, November 15, 2010 3:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi rithriley

    Absolutely fantastic, we battled the same issue for a few days now.

    Setting the web client service to auto on 64bit windows server 2008 R2 fixed our issue opening xlss and docx on the iseries netserver

     

    thanks

    Kind Regards

    Tuesday, November 16, 2010 11:25 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Guys

    What exactly was the fix ( as there seem to be a few different approaches mentioned)

    Our users are intermittenly experiencing a saving issue in Excel to the shared drives. It just hangs and doesnt save, also creates a huge .tmp file.

    users are generally windows 7 machines access windows server 2008 file share in a hyper V environment.

     

    thanks in advance

    Wednesday, December 1, 2010 12:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I've had this issue with Office 2007 and 2010, and Windows Vista and Windows 7 (both 64-bit and 32-bit).

    Our issue was that saving Excel spreadsheets to a network share took 25+ seconds.  The problem was that Offline Files (from the network share) were being indexed.

    To fix this, I simply opened the Indexing Options in Windows 7, clicked Modify, and unchecked Offline Files.  Now my Excel spreadsheets save to the network share instantly with zero delay.

    Hope this helps,

    Gary

    Gary Evans
    Thursday, May 12, 2011 3:53 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Thanks, I had Nod32 on my machine, once I removed it, it was like life came back into my server.
    Thursday, August 4, 2011 9:32 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

     into your services (this must be done with an Administrator account).  Locate the service WEB CLIENT. I would bet it is set to manual.  If you look at your XP machines the service is set to automatic. Turn this service on and set it to automatic.  Now try opening your files and saving them from the shared drive. It should be MUCH faster

     

    In my case starting web client servuce worked..

    thanks for solution.

    Thursday, August 25, 2011 11:31 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    we think we have fixed the issue here in our office. Turns out Xp machines have a service on by default but Windows 7 machines do not. After spending 6 weeks working with MicroSoft and also opening a ticket with IBM (As400).  We have been running just fine and NO SLOW REPSONSE issues. We went from 45 seconds to open or Save As a file to 3 seconds.

    Go into your services (this must be done with an Administrator account).  Locate the service WEB CLIENT. I would bet it is set to manual.  If you look at your XP machines the service is set to automatic. Turn this service on and set it to automatic.  Now try opening your files and saving them from the shared drive. It should be MUCH faster.

    Please let me know if this doesn't work for you.

    I already tried the registry fix and that had no effect.  Starting the Web Client service was my fix, MS Office documents located on the IBM Power7 server would take up to 5 minutes to load on my Windows 7 machine.  Now it doesn't take more 20 seconds load even with .csv files and sql statements imbedded in the document.  Everyone should try this first before attempting to open the registry.


    • Edited by slimjim2234 Tuesday, September 27, 2011 6:57 PM
    • Proposed as answer by slimjim2234 Tuesday, September 27, 2011 6:57 PM
    • Unproposed as answer by slimjim2234 Tuesday, September 27, 2011 6:57 PM
    Tuesday, September 27, 2011 6:56 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Go into your services (this must be done with an Administrator account).  Locate the service WEB CLIENT. I would bet it is set to manual.  If you look at your XP machines the service is set to automatic. Turn this service on and set it to automatic.  Now try opening your files and saving them from the shared drive. It should be MUCH faster.

    Please let me know if this doesn't work for you.

    We switched from NetWare to a DSF setup with two Windows 2003 R2 servers.

    Clients are a mix of WinXP and Win 7 and Office 2003/2007/2010 in all possible combinations (except 2010 on WinXP) and experienced serious delays in opening and often also closing of Word and Excel files not matching the expected speed of the setup with GBit ethernet all over.

    For the Win 7 clients with Office 2007/2010 solution was this (turning on the Web Client) in combination with switching off indexing of off-line files as suggested by James Nelson.

    For the Win 7 clients with Office 2003 and WinXP clients, this didn't change much (for WinXP the Web Client was already set to Automatic). However, turning off OFV (Office File Validation) made the trick. This is explained here next to the bottom:

    http://technet.microsoft.com/en-us/library/gg985445%28office.12%29.aspx

    <quote>

    To prevent Office File Validation from validating files you must create the following registry key and assign it a value of “0” for the specified application in Office 2003 or Office 2007:

    HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\<11.0 or 12.0>\<application>\Security\FileValidation, where <11.0 or 12.0> represents the version of Office and where <application> represents the specific Office application for which Office File Validation is installed, such as Word, Excel, and PowerPoint.

    All necessary parameters for configuring the registry key are listed as follows:

    • Value: EnableOnLoad

    • Type: REG_DWORD

    • Default: 2

    • Description: Disable Office File Validation

    • 0 = Don’t validate

    • 1 = Validate

    • 2 = Validate unless called via object model

    </quote>

    For Office 2010 replace the key above (11.0 or 12.0) with 14.0

    Thanks for all the contributions to this thread! I can't imagine how I otherwise should have come across the Web Client and indexing of off-line files. 

    /gustav

    Gustav Brock
    Friday, October 28, 2011 10:43 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This worked for me.  Thanks!
    Thursday, November 3, 2011 6:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Awesome - thanks!!!!!  Suffered this strangeness for a couple of weeks.  Now having Web Client set to Automatic, the slowness is finally GONE!!!!!

    (Running Win7-Pro 64bit with Office 2007)

    Saturday, November 5, 2011 7:48 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    I had the same problems. Disabling ESET Antivirus 4 solved  this problem after enabling it, the problem came back.

    I've uninstaled it and installed ESET Antivirus 5, now the opening/saving files works as it should.

    • Proposed as answer by Haris Alatovic Thursday, January 12, 2012 1:16 AM
    Wednesday, January 4, 2012 1:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Same problems we cannot solved for long time. We searched all Internet with no success until now, tnkx to Kevid and Matjaz.

    My situation is little bit different. I have mixed environment XP and Win 7 machines with Office 2003, Office 2007 and Office 2010 as clients and Windows 2000, 2003 and 2008 file servers all connected by 1Gbbs switches. All clients and servers are running eset 3.2 (XP machines) and 4. Lot of our users have combination of Win7 and Office 2003 and they suffer of slow .doc save (more than 20 sec for 600KB file)  on network shares on 2008 servers. Interesting thing is that XP machines with any Office version and win7 machines with Office 2007 or Office 2010 save files almost instantly (with enabled eset 4).

    We tried a lot of actions like disabling SMB2, various netsh commands etc with no success. It seems that there is some problem with that specific combination Win7 with Office 2003 and Eset 4 working with network shared files on Windows 2008.

    Solution with disabling eset 4 on specific clients works for me. I hope so eset 5 will work fine.

    Thanks guys.

    Thursday, January 12, 2012 1:41 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi HeadShok,

    Did this work for you? We are experiencing the same issues except problem is not with file saving (that I know of) but with file opening... Usually hangs in the morning first thing, then is OK opening any file for quite a while, then hangs again after a random time (could be ten minutes, could be hours, could be the next day!) then is ok for a while...

    For anyone else who is interested under normal circumstances a packet sniffer shows SMB2 being used with no errors of any great issue. Then when the random 'hang' happens there are two errors I don't normally see repeated a few times "getinfo response, error STATUS_OBJECT_NAME_NOT_FOUND" and "STATUS_OBJECT_NAME_COLLISION".

    This affects about 5 clients in a 50 user site accessing an SBS 2008 server (which was migrated from SBS 2003)... I have only seen it hang with Excel (although this is the most used application), Excel just sits saying 'Downloading <filename>' and then eventually if left if will sometimes come up with an error saying  - " Cannot be accessed. The file may be corrupted, located on a server that is not responding, or read-only. - ... I find the " quotation mark at the beginning unusual, I think this error normally has file name there?

    I have disabled SMB Version 2 on the client only, rebooted, and from the packet sniffer can confirm it is now running SMB and not SMB2. I will log back in in the morning as the problem is reproducable if left after a while, if it works I'll post back.

    Thank you

    I wonder if http://support.microsoft.com/kb/2628582 would be able to fix this issue. In that case it may not be necessary to disable SMBv2 at all.

    Monday, June 4, 2012 7:58 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I also had similar problem. i.e. Windows 2008 R2 64 bit OS and domain users facing problem for saving office 2007 files from win 7 client machines. I followed what is mentioned by almazalmazov . But there were two options in registry one for 32 bit and another for 64 bit. First I tried 64 bit, it doent work.  32 bit entry does the job.

    Thx for solution. Keep it up.

    Tuesday, October 27, 2015 10:05 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You will need to disable SMB2 on the server that
    holds the share. To do so:
    Add a REG_DWORD entry named Smb2 with a value of 0 to
    HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters

    A: To disable the use of Server Message Block (SMB) 2.0 protocol on a
    Windows client, perform the following:
    1. Start the registry editor (regedit.exe).
    2. Move to
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters.
    3. From the Edit menu, select New, DWORD value.
    4. Enter a name of Smb2 and press Enter.

    Really it's work....................................

    • Edited by SPJ333123 Wednesday, April 11, 2018 9:54 AM
    Wednesday, April 11, 2018 9:53 AM