locked
NetCache\Conent.MSO warnings after rebuild and office upgrade RRS feed

  • Question

  • User had Win10 Office 2010

    Ever since we upgraded to Office 2016 Pro User gets the warning when opening excel files:

    "...Couldn't find C:\Users\jsmith\AppData\Local\Microsoft\Windows\lNetCache\Conecnt.MSO\46GF4343.xlsx. Is it possible it was moved, renamed or deleted...."

    Files were originally Outlook attachments, currently saved on Network Drives. 

    There is no ...Windows\lNetcache.. folder. Assume that is why there is the warning. 

    How do I make it go away. Since there is no lNetCache (on any of our Win10\Office2016 machines for that matter)

    Thanks,

    • Moved by Steve Fan Thursday, March 1, 2018 7:06 AM move to dedicated Outlook forum
    Monday, February 26, 2018 8:27 PM

Answers

  • Pulled the original from Outlook -> same issue. So problem is with the file. 
    • Marked as answer by SJMP Tuesday, February 27, 2018 3:45 PM
    Tuesday, February 27, 2018 3:45 PM

All replies

  • Hi,

    Does it happen with all Excel files saved on the network drive or just certain ones?

    What if we try to copy the Excel file from the network drive to your local drive and then try to open it again? 

    Besides, you may try to reconfigure the mapped network drive on your PC and then test it again.

    Regards,
    Steve Fan


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, February 27, 2018 5:43 AM
  • What would reconfig the map drive do? Access is not an issue and drives are mapped from GPO. Just certain files. trying to find what they have in common. 1) encrypted 2) originated as Outlook attachments. Assume this is why they had some reference in that netcache folder. but it looks like office2016 doesnt use it at all. 
    Tuesday, February 27, 2018 3:25 PM
  • Pulled the original from Outlook -> same issue. So problem is with the file. 
    • Marked as answer by SJMP Tuesday, February 27, 2018 3:45 PM
    Tuesday, February 27, 2018 3:45 PM