Technically, working on a mapped drive is not supported, but it does usually work. Do you have problems if you work off the local drive? Is this restricted to a single file? Does it work if you log on to the computer using a new user account?
Thanks for the response.
Yes the drives are mapped from the data server and tested the network. Popped the switches a boot too but no change. The other workstations are working fine it's just this particular workstation.
I did copy the file over to the local drive and tried working on it from there same problem.... This is not restricted to a single file as it happens with every file. HOWEVER I was able to pinpoint that it does happen more frequently with larger size files.
These same files work on other workstations? Sounds like a software conflict. Is there a utility or plugin on this one that is different from the others?
Yip these files work on other workstations 100% only this workstation that gives me this error. The user stated that she was able to work on it until a windows update happened and after the update she experienced this. I did try the system restore option but no luck. To go and pinpoint what update might be causing this would be like finding a needle in a haystack.
As for plugins or utilities I am not entirely sure nothing seems out of the ordinary when comparing to other workstations.
I'd run MSconfig and turn off startups and non-essential services to see if it works in a relatively "clean" boot state, then add them back in groups to find the problem if it does.
I haven't thought about the MSconfig. Ill give that a try and check. This will require a lot of reboots, but might pinpoint the problem. I will get back to the thread with a response.