Issue with inconsistent Excel file corruption when not connected to a VPN?
Issue with inconsistent Excel file corruption when not connected to a VPN?
Hi all, I’m dealing with a few end users experiencing problems with certain shared Excel files on our network drive. These are .xlsx files, and everyone should be using version 2308 of Excel. One file contains macros, while another does not. Only one user is permitted at a time. There’s a 50/50 chance the files open correctly for them, but sometimes it shows a corruption error and requests a repair. After fixing it, the issue may resolve, only to reappear later. Even after repairs or reverting back to an earlier version, the files still cause problems.
I was thinking about letting them create a new worksheet and paste the data in, but it turns out these two users don’t have issues with corruption warnings appearing when they’re connected via Cisco Any Connect VPN from home or office. This seems contradictory since they’re at the office during the time of the error.
I really don’t know what’s causing the problem or where to begin troubleshooting beyond the obvious workaround of copying and pasting data.
I only have my mind on the fact that the file was altered by someone (or something) and that this alteration is perceived by another entity as corruption.
Suggestions from afar:
1) Examine the routes—both VPN and non-VPN—to the Excel files in question.
2) Ensure everyone uses Excel version 2308.
3) Clarify what “it” refers to when it says the file is corrupted.
4) Check how two users can work on the same file simultaneously; are shared links or spreadsheets involved?
5) Could macros be the cause? Are the files linked or shared so a change in one spreadsheet appears in another? This might look like a hidden adjustment leading to corruption?
Get the spreadsheets functioning and fixed via VPN. After resolving, perform controlled testing in-office to spot any unexpected changes.
Plan carefully and coordinate with the end-user community. Work methodically, making only one adjustment at a time.
Test on copies if possible.
Full backups are advised beforehand.