InterviewSolution
Saved Bookmarks
InterviewSolution
| 1. |
Solve : MSOffice not responding when saving on mapped drive? |
|
Answer» Someone please help I’ve been having a issue lately with a mapped drive on our sever, what happens is that people have been reporting that ms WORD and ms excel have been not responding while accessing it through a mapped network drive connected to a 2008 server. Once they OPEN it over the mapped drive the file continuously hangs and when they create a file locally and try and save it to the mapped drive it freezes with no response the second they try to save as. I’ve looked everywhere over the internet and have tried so much with no luck whatsoever, but I have DISCOVERED that the only way of fixing this issue temporarily is to create a shortcut on the desktop to the server’s files.. Besides that all I can do is reformat the PC and not even that permanently fixes it since the PC did the issue all over again. -It only happened to 5 – 10 people on a network of 50 or so Are these systems by chance located in a certain area that all share a network switch where others do not communicate through the same switch etc? Is there anyone being a bandwidth hog on corporate network causing latency and time outs? With specific workstations is the problem happening all the time or at random? Are there other users using Windows 7 Pro with no issues like this? Hey Dave its been happening random, and there is no one being a network bandwidth hog there all fairly the same. The workstations that are experiencing the problem are scattered throughout the area. We have a total of 5 network closets and I've seen it happen at our main headquarters as well as two different areas that have network closets.And yes there are many people using windows 7 pro that aren't experiencing the issue One suggestion I have is that if all the work stations are all using the same image and systems are alike, swap the system that is FREQUENTLY having this problem with one that isnt and monitor to see if the problem MOVES or remains. If the problem moves then you know its something wrong with that specific workstation, if the problem remains then its something on the network side that is causing an issue for that specific location. A more costly way to deal with this would be to set up network and workstation monitoring software and look for hiccups. But this is not very affordable for most, and in the past I have pretty much done pretty well diagnosing network problems by pinging from strategic locations and sending the information from the pings to a log file with date/time stamps to look at further. One affordable tool I did buy was Alert Ping Pro http://www.bestshareware.net/alert-ping.htm which allowed for me to be notified right when problems are detected by having it trigger a program I wrote and compiled as exe which would call me on my cell phone and play an audio track looped for pointing out where problem area is. One last thing to check would be the event logs of the systems that have had this issue to see if there is anything there that points out any issues. as well as I had an accounting system once that had random issues that I thought was a bug with an accounting program, but it ended up being a 1GB RAM stick that was failing in the 628MB range according to memtest86, and all other programs were not memory hogs and so the system ran fine, but when the memory hog accounting program ran a bug like problem would pop up in regards to a function call. Swapping out the RAM stick after finding it was problematic fixed the issue with that HP SFF Business class workstation. Thanks for the pointers I will check that out for sure. |
|