Forum Discussion

cam909's avatar
cam909
Copper Contributor
Jan 11, 2021
Solved

Excel Error (Microsoft Visual Basic)

Hi

I've got an issue where one of our users is using a Macros Enabled spreadsheet, every time they go to write something in one of the cells within the Excel workbook and then come out of it again, the below message appears. The user is running a Windows 10 64 version, we're on O365 Build 2002 64bit 

 

 

If you click ok the message disappears but as you can imagine this is a pain having to do this all the time.

 

When the user goes to save the worksheet to their desktop or network drive, the below message comes up.

 

The user has forwarded the same offending spreadsheet to a colleague of hers and he's been able to amend the cell and save it fine without the above messages coming up, he's on the same version and build of office as she is and also the same operating system. 

 

Below are the following steps I've done to try and resolve, any help or guidance on this would be greatly appreciated. 

 

  1. pushed out windows updates including .Net 4.8 
  2. done an sfc /scan now and a chkdsk
  3. done an online repair of Office 
  4. uninstalled Office completed and re installed it 
  5. re created the users windows profile 
  • mtarler it turns out that when moving the corrupted Excel file to another location within the network drive, it worked and the errors went away. I think it's possible due to the  fact that the location of where the user had this file windows couldn't detect it as the file path was longer than 250 characters  

2 Replies

  • mtarler's avatar
    mtarler
    Silver Contributor

    cam909 since it is a macro enabled sheet I would open the VBA editor (alt-F11) and then find out what line or subroutine the error is happening (assuming it is happening in a macro).  That should help find the problem.  

    • cam909's avatar
      cam909
      Copper Contributor

      mtarler it turns out that when moving the corrupted Excel file to another location within the network drive, it worked and the errors went away. I think it's possible due to the  fact that the location of where the user had this file windows couldn't detect it as the file path was longer than 250 characters  

Resources