Dana D
asked on
Excel 2016 standard (not office 365) taking a minute and a half to open spreadsheet on a network share which opens with error.
Excel 2016 (standard) is slow (takes about 1 minute and a half) to open spreadsheet and when it finally opens it has this as an error:
"" cannot be accessed. The file may be corrupted, located on a server that is not responding.
When the file is copied from the network share to the desktop it opens quickly (as expected) without any delay and also has no error and is ready top be edited (as expected).
Here is what i have tried so far:
removed any protection mode settings
turned off validate links on open
repaired office
replaced hard drive
reinstalled windows 10 pro 64 bit and office 2016 standard 32 bit
When i reached this point i decided to tried opening the same file at the same network shared location from another windows 10 pro 64 machine and got the same exact behavior.
This makes me believe it may be something related to the VPN tunnel setup between the location and the destination (HQ) where the San in question is located.
What in the VPN tunnel should i look for that could cause this type of behavior. Also i tried to look for microsoft support phone number for office 2016 standard and i am unable to find onw - it wants me to log in to get the number but i dont have the creds for this license. Does anyone have the specific office support number for this version of office 2106 standard 32 bit? It is not office 365 as far as i can tell and it has a serial key.
Thanks in advance for any help you could supply!
"" cannot be accessed. The file may be corrupted, located on a server that is not responding.
When the file is copied from the network share to the desktop it opens quickly (as expected) without any delay and also has no error and is ready top be edited (as expected).
Here is what i have tried so far:
removed any protection mode settings
turned off validate links on open
repaired office
replaced hard drive
reinstalled windows 10 pro 64 bit and office 2016 standard 32 bit
When i reached this point i decided to tried opening the same file at the same network shared location from another windows 10 pro 64 machine and got the same exact behavior.
This makes me believe it may be something related to the VPN tunnel setup between the location and the destination (HQ) where the San in question is located.
What in the VPN tunnel should i look for that could cause this type of behavior. Also i tried to look for microsoft support phone number for office 2016 standard and i am unable to find onw - it wants me to log in to get the number but i dont have the creds for this license. Does anyone have the specific office support number for this version of office 2106 standard 32 bit? It is not office 365 as far as i can tell and it has a serial key.
Thanks in advance for any help you could supply!
Since it also happens from other PCs, it could be a problem with the file on the server. Try copying the original to a new name on the server. Then see if the new name doc works from the same server. Its possible the original is sitting on a disk sector with a recoverable error, that may extend the read response time for that portion of the original file. The time it takes to reply with the recovered data may be causing some issue over the network.
ASKER
Actually i found something interesting which points to DNS - The issue is happening when opening the file via double clicking the file in windows explorer (the file is in a shared folder on the a file server and is mapped as the S drive.
So what i did was instead of using the existing mapped S drive i was able to navigate to the ip address of the file server using the UNC path to the same file and when opening the file via double clicking the file in windows explorer - this time it opened in Excel at a normal speed (as you would expect) and with no error. Thus the issue is resolved when opening the file this way!
So this points to a dns issue but what could be wrong with DNS to cause this issue and what are my next troubleshooting steps to find the exact issue and resolve it?
The other thing i want to mention is that the DNS server is over a vpn tunnel at the HQ location and this same DNS server is also the file server, DC, DNS, DHCP server.
So what i did was instead of using the existing mapped S drive i was able to navigate to the ip address of the file server using the UNC path to the same file and when opening the file via double clicking the file in windows explorer - this time it opened in Excel at a normal speed (as you would expect) and with no error. Thus the issue is resolved when opening the file this way!
So this points to a dns issue but what could be wrong with DNS to cause this issue and what are my next troubleshooting steps to find the exact issue and resolve it?
The other thing i want to mention is that the DNS server is over a vpn tunnel at the HQ location and this same DNS server is also the file server, DC, DNS, DHCP server.
you may check how the S drive letter was mapped. if it uses the 'name' of the server exchange it by the IP4 address of the server.
for example \\192.168.1.1\myshare
alternatively look for the hosts file at windows\system32\drivers\e
you can add the ip address of your server here and the hosts file works like a mini DNS.
all that makes only sense if the ip4 is fixed and still supported.
Sara
for example \\192.168.1.1\myshare
alternatively look for the hosts file at windows\system32\drivers\e
you can add the ip address of your server here and the hosts file works like a mini DNS.
all that makes only sense if the ip4 is fixed and still supported.
Sara
ASKER
I was able to change the mapped drive script to the ip of the server and it still has the same result.
Have you tried copying the file to a new file on the server? One of its allocated sectors could be a marginally bad sector. That would cause excessive read time as the disk read is retried, which could be causing a network read timeout. I have seen read retrys take seconds, that sort of issue would surely cause the network transfer protocols heartache.
The clue you provide is that other PCs are having the same issue with this particular file. That points to the server, which seems to be fine accessing other files. Its a simple test, just copy your-file to your-file2, chances are the new sectors occupied will be good. Its not unusual for a disk to develop marginally bad sectors over time, especially if the sectors are not rewritten for long periods.
The clue you provide is that other PCs are having the same issue with this particular file. That points to the server, which seems to be fine accessing other files. Its a simple test, just copy your-file to your-file2, chances are the new sectors occupied will be good. Its not unusual for a disk to develop marginally bad sectors over time, especially if the sectors are not rewritten for long periods.
Is there any link in the spreadsheet (for example to an image or to a database) which might cause the troubles? you could test whether the contents of the file is responsible or the file access by copying a new much simpler spreadsheet to the same server location and open this file the same way.
how did you open the spreadsheet file?
- by using an entry in the recent file list?
- by using the file open dialog of excel?
- by double-clicking at the file in windows explorer (via network and/or S drive) ?
- by typing the full path (using S drive or UNC) as command after WIN+R?
you may try any of these variants and check whether the result is always the same.
Sara
how did you open the spreadsheet file?
- by using an entry in the recent file list?
- by using the file open dialog of excel?
- by double-clicking at the file in windows explorer (via network and/or S drive) ?
- by typing the full path (using S drive or UNC) as command after WIN+R?
you may try any of these variants and check whether the result is always the same.
Sara
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
how do you invoke the file? do you click on it in the Windows Explorer? or do you try to open a recent file?
did you try to open the file from a command window?
you would type the full UNC path to the excel file (within double quotes if it contains spaces) finished by <ENTER>.
or, if there is a drive letter mapped to the share, you would navigate by 'cd' to the folder where the file resides and invoke it by filename.
Sara