Errors opening Visio drawings

I have a user who is experiencing a series of errors intermittently when attempting to open drawings using Visio 2003 SP3. Sometimes, the user will be successful in opening, editing and saving the drawings without any issues. Other times, when the user attempts to open the file, the first error he receives states "An error (1564) has occurred during the action Open File. DOS Network name was deleted." After acknowledging the error and attempting to open the file again, the next error message he receives states "<filename>.vsd is already open for editing. Would you like to open a copy?" He clicks "OK" to open the file but it will not open.

Other users are able to open these same files without any issues at all. Sometimes, the user will be able to open the files without the errors. The files are stored on a network drive, and the user has full control of the folder in which they are stored. I have verified on the server that the file was not opened by another user at the same time. He also has no issues opening other files on the same network share. I have tried reinstalling Visio 2003 + SP3, but the issue continues. Any suggestions would be appreciated.
IASysTechAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Brian BEE Topic Advisor, Independant Technology ProfessionalCommented:
If he copies the problem file locally, does it work then? At least that could rule out the network as the source of the problem.
IASysTechAuthor Commented:
When the issue occurs, he is unable to copy the file locally. It just hangs on the file copy process, and eventually errors out, although accessing other network resources works just fine.
Brian BEE Topic Advisor, Independant Technology ProfessionalCommented:
I would suggest trying to copy the file locally before the issue occurs. Then see if the prbolem comes back with the local copy.

Perhaps Visio is not releasing the files from the previous time he used it. On the server, in system management, look up the share he is using to retrieve the file and check for open connections. Make sure the file is being released once he closes the file.

Perhaps a remove and reinstall of Visio will help clear out some potential file problem. If that doesn't help I'd even completely rebuild his system, but that obviously takes time.
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

IASysTechAuthor Commented:
When the issue occurred, I did check the server to see if the file was in use and it was not. I also reinstalled Visio, but the issue occurred again. At this time, the issue is not occurring, but I worry that it may come back. I'd like to avoid rebuilding his system if at all possible, since we do not use any type of imaging/ghosting to build up the systems, so each system must be built from scratch.

Do you have any suggestions on troubleshooting steps I can take when the issue occurs, to see if I can narrow down what is causing the problem?
Brian BEE Topic Advisor, Independant Technology ProfessionalCommented:
I think we can rule out network, since other users can access the same files with no problems. Since you uninstalled and reinstalled Visio, its not the Visio program itself.

You didn't confrim if the user is able to copy the file locally before the error starts and then work with it from there with no problems. That will tell us if the problem is the network drivers or something related to that.

If we can rule out the network as the source of the problem, that leaves the system. You could take a lot of time poking around looking for the source, but you will probably take longer doing that than wiping the entire sysetm and rebuilding it. At least with a rebuild you will either fix the problem, or know for sure that its not a corrupted program file or something.

Assuming there is nothing else unique about this system versus others on your network, a rebuild might be the next choice.
IASysTechAuthor Commented:
Today, the issue cropped up again, but this time it was with an Excel file. Strangely, it was with a single file in a network location, and he was able to open other Excel files saved in the exact same network folder. He was unable to copy the file to his local machine, it gave him an error message that "the specified network name is no longer available." I copied the file for him, and he was able to open the local copy without an issue.

What baffles me is that it was with that single Excel file; he created that file serveral days ago, I was able to open it across the network and he was able to open other files save in that same location. I'm beginning to lean towards an issue with his network card and/or NIC drivers, because he noted that his SQL queries errored out with a message that he says indicates a possible loss of network connectivity. However, he was able to ping the server where the file in question was stored.
Brian BEE Topic Advisor, Independant Technology ProfessionalCommented:
You are right that there may be something going on with network conenctivity. I was wondering about that when I first replied to your question.

So checking the drivers would be a good idea. Also have a look at the event viewer on the workstation to see if it is showing any errors.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
IASysTechAuthor Commented:
After finding nothing in the event log, updating the NIC drivers, resetting the winsock catalog, resetting the TCP/IP stack, trying another Cat5e cable and rewiring the wall jack, I'm left with the conclusion that it has to be the port on the network switch in our server room that he connects to. Unfortunately, our network tester is unavailable at this time, so tracing the line is going to be out of question for a little while. For the time being, I've installed a 5-port mini-switch to share out a known good wall jack in the same office, and that seems to be working until I can implement something more permanent.
Brian BEE Topic Advisor, Independant Technology ProfessionalCommented:
Interesting conclusion. Please post back once you have confirmed the error is gone or not.

If you don't have a patch panel or labelled cables, you might also look for a line toner to help trace the wire in the future.
IASysTechAuthor Commented:
I was able to identify which network switch and port he was using, so I have switched him to a an empty port on the same switch, since no one else seems to be experiencing the same issue. I will post back after a while when I see if this makes any difference. I can confirm that switching him from the wall jack in his office to the mini-switch did resolve the issue as a temporary solution.
Brian BEE Topic Advisor, Independant Technology ProfessionalCommented:
Interesting... Goes to show that flaky hardware can cause any number of weird problems.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Visio

From novice to tech pro — start learning today.