Windows 10 Update threw off mapped drive for two specific documents

SUGGESTED

Ok this is strange (to me) and unlike other mapped drive posts I've seen on here.

Windows 10 updates have been putting us in IT through hell in regards to sporadic Sage issues. In this instance, we cannot access 1 of 9 memo attachments for 2 particular accounts (same attachment sets as these are both subaccounts of the same customer). The other 8 can be accessed just fine, and are on the same general filepath as the problem-child.

When we go to open the attachment for this memo, the customer maintenance screen freezes briefly then closes entirely along with all child panels. 

We went to locate the file through the memo screen, and it opened up by default to the MAS90 folder on our SageData server. This led my boss and I to believe this is a mapped drive issue.

Things we've done so far:

- relocated the file to a root location for a shorter file path length

- confirmed the file is not corrupted

- performed all troubleshooting on our admin-level workstations to eliminate permissions-issues

What are some solutions that can solve this particular instance, and moreover how can we as a department be more proactive in being able to prepare and fix these issues that are commonly caused by Windows 10 updates?

  • 0

    A few  initial questions would be:

    Is this Sage 100 Standard or Advanced/Premium?

    Do the workstation shortcuts show as UNC path or mapped drive? (for Standard should be mapped drive... UAC often sets it to UNC path).

    Is the workstation Sage 100 shortcut set to "Run as Administrator"?

    If Advanced/Premium, is the Sage 100 application sever service running as "local system" or a domain account?

    Does that issue with the memo attachment happen on workstations and Sage 100 server too?  is the path for the files located on the Sage 100 server or another machine?

  • 0 in reply to DGR
    SUGGESTED

    Before I saw your reply, I had tried a "just for fun" idea that actually worked!

    I went through the file search under that document, selected the file, which reinitialized the file path and now it's working fine. I had come across what you're talking about via some documentation from my reseller.

    But to answer your questions, Sage 100 Standard, Run as Admin is unchecked, and we were having the issues on the Sage 100 server as well as a few of our IT workstations with local admin privileges. The file was on a shared drive not a local machine or Sage server.

  • 0 in reply to Yung_Grasshopper

    If someone is doing a copy / paste of the file path from Excel (instead of navigating through the interface properly), that could include extra invisible characters.

  • 0 in reply to Kevin M

    ok that's also good to know. We had actually done that as a first means of troubleshooting as we moved the file back towards the root to reduce the character length of the file path.