Windows 7 Pro very slow to open office files?

Unanswered Windows 7 Pro very slow to open office files?

  • Sunday, September 02, 2012 12:21 AM
     
     

    Here's the problem: two computers in the same office, one Windows XP on a Core2Duo notebook; the other a Lenovo i7 workstation running Windows 7 Pro x64; the XP computer is attached to a 10/100 5-port work group switch which in turn goes to a 48 port managed gigabit switch; the Lenovo i7 workstation is wired directly to the gigabit switch and shows as being connected at gigabit speed. Both computers are running Office 2003; both computers are running the same version of Kaspersky anti-virus; the Server runs Windows Server 2003 on an a small HP/Compaq rack mount Proliant; both computers are members of the active directory domain.

    When the XP computer opens an Excel file it opens within a few seconds; when the Lenovo Windows 7 computer tries the same file it can take 30 seconds to several minutes for the file to open.

    I've been trying to figure this for weeks and not making any headway; as far as I can tell active directory and DNS is properly configured.

    Does anyone have any idea's or trouble shooting steps?

    Thanks,

    - Norm

All Replies

  • Sunday, September 02, 2012 12:12 PM
     
     
    If You Make A Local Copy of the same file that is on the network, does the local file opens quickly ?
  • Sunday, September 02, 2012 5:43 PM
     
     

    yes that was mi question too , did you try that file copied down to your computer and clicked it ? whats that response ? it did get opened promptly ?


    or 

     

    What I did notice was when you opened the file , the network usage would spike to 7mb/s for the entire time while only retrieving a 600kb file. Opening .pdf / .doc files around double or triple the size would open instantly A bit of research online only proved the fault/fix with a Windows 7 setup accessing office 2003 documents 

    http://support.microsoft.com/kb/982860

     Just go  “Under the registry entry, disable these two registry keys: Right-click Enablesecuritysignature, and then click Modify. Type 0 in the Value data box and then click OK.

    Right-click Requiresecuritysignature, and then click Modify. Type 0 in the Value data box and then click OK.”


    and  disable OFV



    You can use the EnableOnLoad registry entry to configure how you want Excel to handle opening workbooks for the OFV. By default, the EnableOnLoad entry is not present in the Windows registry. To add the EnableOnLoadentry to the Windows registry, follow these steps:

    Exit Excel.
    Click Start, click Run, type regedit, and then click OK.
    Locate and then click to select the following registry key:  , the proper key is
    HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\11.0″ Old key “HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0\”
    After you select the key that is specified in step 3, point to New on the Edit menu, and then click Key.
    Type Excel, and then press ENTER.
    Select Excel, point to New on the Edit menu, and then click Key.

    Type Security, and then press ENTER.
    Select Security, point to New on the Edit menu, and then click Key.
    Type FileValidation, and then press ENTER.
    Select FileValidation, point to New on the Edit menu, and then click DWORD Value.
    Type EnableOnLoad, and then press ENTER.

    Note: The default value is 0 which disables the validation.
    On the File menu, click Exit to quit Registry Editor.


    Alternative Solution

    And if it doesnt work
    , i need more information ? wat server you are running  ? i guess its 2003 ? file accessing using SMB Protocol Between 2003server and XP dont  have any problem, since both uses SMB 1.0 versions..! but if windows /vista clients connect to server means it use SMB2.0 Server(Win8 has pretty impressive 3.1 SMB) ...so may be due to that in win7 excel file accessing is slow


    Chech this out :


    Here's how SMB is used when related to SMB versions:

    • When a Windows Server 2008/Vista "client" connects to a Windows Server 2008/Vista "server", SMB 2.0 is used.
    • When a Windows Server 2008/Vista "client" connects to a Windows 2000/XP/2003 "server", SMB 1.0 is used.
    • When a Windows 2000/XP/2003 "client" connects to a Windows Server 2008/Vista "server", SMB 1.0 is used.
    • When a Windows 2000/XP/2003 "client" connects to a Windows 2000/XP/2003 "server", SMB 1.0 is used.


      So you need to disable the SMB 2.0 in order to make it work normal just like ur XP machine

      To disable the SMB 2.0 In Win7 Follow this Link

      Disabling SMB2.0 In Win 7

      I
       Hope it answers your questions and your issue will be resolved !!

      Thanks,
    • Suren

    Face the fact tat we all have plenty to learn about this field. Deal wit the failures, use tem as motivation, learn something new everyday. Claiming false credentials & phantom skillsets will not get you far, especially when 63248651487512645876531864 people in the universe know how 2 use the internet Please remember to click “Mark as Answer” on the post that helps you, Please VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.

  • Sunday, September 02, 2012 5:45 PM
     
     

    Bro But am very sure if nothing work Disabling the SMB 2.0 in Win7 Will defeinately Fix this , i have faced such issues !!

    Thanks,
    Suren


    Face the fact tat we all have plenty to learn about this field. Deal wit the failures, use tem as motivation, learn something new everyday. Claiming false credentials & phantom skillsets will not get you far, especially when 63248651487512645876531864 people in the universe know how 2 use the internet Please remember to click “Mark as Answer” on the post that helps you, Please VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.

  • Monday, September 03, 2012 1:11 PM
     
     

    Several IT people have been looking at this and so far no headway; I haven't tried this (but that doesn't mean someone else hasn't) and the office isn't open today but I'll try making a local copy tomorrow and let you know.

    Thanks to everyone who responded, I appreciate the help!

    - Norm

  • Wednesday, September 05, 2012 6:37 AM
    Moderator
     
     

    Hi,

    I am currently standing by for an update from you and would like to know how things are going. If you have any feedback, please let us know.

    Niki
    TechNet Subscriber Support
    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Niki Han

    TechNet Community Support

  • Tuesday, September 11, 2012 2:50 AM
     
     

    Hi Norm,

    I resolved similar issue by disabling Windows Auto Tuning on Windows 7.

    http://deinfotech.blogspot.com/2011/07/accessing-file-share-is-very-slow-with.html

  • Tuesday, September 11, 2012 8:47 AM
    Moderator
     
     

    Hi,

    As this thread has been quiet for a while, I assume the issue has been resolved. At this time, we will mark it as "Answered" as the previous information should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.

    BTW,  we'd love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts.

    Niki
    TechNet Subscriber Support
    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Niki Han

    TechNet Community Support

  • Monday, September 17, 2012 2:16 PM
     
     

    Hi Niki:

    Sorry but I've actually been gathering more information; sometimes the problem is not as straight forward as it first appears and as I've found out just because someone's not complaining doesn't mean they're not having a problem. Also while annoying this problem has had to take a backseat to other more pressing problems around the office so I'm sorry for the delayed response.

    The person who was complaining the most had Windows 7 and the person who sat next to him who had Windows XP actually had different versions of Office. As I've come to find out through talking to the rest of the staff; I've found that the operating system is really irrelevant and that in actuality everyone who's using Office XP (Office 2002) is not having the issue and that everyone who's using office 2003 or above is having the problem.

    I haven't really tried any of the suggestions made by people here since they were based on the premise that what was happening was specific to Windows 7 such as an SMB version problem i.e. XP and Server 2003 used SMB 1.0 while Window's 7 used SMB 2; this is not the case as I have found people using Windows XP and Office 2003/2007 who try and open small and medium sized Excel files and it takes 3 to 5 minutes while other people who are running Office XP can open the same file instantly. Also as several people asked, when the file is copied to the local machine the file opens instantly and does not have the lag that it does when being opened from the network.

    Does this suggest anything?

    Thanks,

    - Norm

  • Thursday, September 20, 2012 3:29 AM
     
     

    Hi Norm,

    If the delay only occurs through network. I strongly suggest that you can try to disable the SNP feature on the file server to see the result. Please refer to the following article:

    http://support.microsoft.com/kb/948496

    Best Regards

    Scott Xie

  • Tuesday, September 25, 2012 1:00 AM
     
     
    Hi Scott:

    I'll give this a try the first chance I get, however I'm not sure when I'll be able to make these changes. This is a production environment and work / getting things done comes before all else and no one (under any circumstances) is allowed to make any changes or do anything to the network during the course of the business day. IT is only allowed one Saturday a month as a Maintenance day to do this sort of thing and I'm not sure when the next scheduled day is so I'd ask the moderators to be patient and not mark this as answered until I can get in there and test this out.

    Some other facts, I'm sort of the new guy on the team and I'm still catching up on the exact makeup and topology of the network. The network consists of two HP/Compaq Proliant Servers running Windows Server 2003 both setup for Active Directory; there are three NAS's; two are Iomega running Server 2003 embedded and one is a Buffalo running Storage Server 2008; the Buffalo is being setup to replace one of the Iomega's which is getting pretty old. The files that seem to be very slow to open are stored on the newer Iomega NAS that's not being replaced; the Buffalo has only been on the network for several weeks and this problem has been happening a lot longer than it's been installed. All the NAS's are members of the Active Directory domain.

    Also I have to clarify one of my previous statements: I'd previously said that people with Office 2003 and above are having this problem, that is not a certainty; There are only a few Office 2007/2010 users and I'm going to have to verify with them if they are actually having this problem or not.

    Thanks,

    - Norm

    • Edited by NormAtHome Tuesday, September 25, 2012 1:02 AM
    •  
  • Friday, September 28, 2012 2:12 AM
     
     

    Hi,

    I would like to follow up with you on the issue. Is there any update about it?

    Best Regards

    Scott Xie

  • Tuesday, December 18, 2012 4:25 AM
     
     

    Hi Scott:

    I'm sorry that this has taken so long for me to post on this again. As I may have mentioned in the previous post, I'm the most junior guy on the team and I'm very limited in what I'm allowed to do i.e. I've been admonished by my supervisor for speaking to the employees about this problem and taking them away from their work etc. I've tried to make the argument that this is never going to get fixed if I can't determine what files are affected and if it's specific versions of Office and I basically got told not to argue, shut up and do what I was told.

    As far as I've been able to determine, the people using Office XP don't have this issue while the people using Office 2003 do (which I'd mentioned) and as far as I can tell no one is using Office 2007 but about a dozen people have been upgraded to Office 2010 and they aren't having the problem.

    So I believe that this may be an issue with Office 2003 since that seems to be the only version where the users are having this problem. For budgetary reasons, the company is slowly migrating to Office 2010 in two's every couple months and I expect that as people are upgraded this will slowly become a non-issue.

    Thanks for your patience.

    - Norm