x Want to participate? Join the group to interact
Options
  • State Not Answered
  • Replies 4 replies
  • Subscribers 106 subscribers
  • Views 2623 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
45
topics
92
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
963
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
Jason Cole

DFDM used on Terminal Server, UNC vs Mapped Drive to open file.

Posted By

Here is the issue:

Terminal server (RDP) used to login to, launch Sage 100 ERP 2013 ADV, Library Master module, Utilities, DFDM.

Click to select the file to edit (any at this point), can navigate to directory & file, once selected, MAS stated in dialog box "File M:/pathtofile/xxx.M4T file not found" Which the file appears in explorer just fine. Selecting the file through a mapped drive is most ideal and easier for accounting staff!!!

Navigate using full UNC path \\SERVER\pathtofile\xxx.M4T file opens just fine and can edit at will.

These two users are administrators and have full access to the server, this setup is a workgroup setup and no domain controller.

Any thoughts? I'm going a little crazy...

Thank You,
Jason

  • 0

    Is the mapped drive through a different share (with read only access perhaps...)?  That might explain being able to see the file but being unable to open in DFDM.

    If you are in the correct company code, simply typing filename.M4T should open the file without entering the full path... and you can see the pathtofile that MAS wants to use.

    Edit:

    And another thought.  If you are spawning tasks from the server, the path would need to be relative of the service, not the user... which is why a UNC would work.

  • 0 in reply to Kevin M

    This problem is from using the "Local System" account for the "Sage 100 ERP service" Log On account.  Change it to a local admin type account and it will work.  Local System accounts cannot find the UNC path.

  • 0 in reply to dskantor

    Local System accounts can't access network resources, but that's not what was described in Jason's original post.

    I really do think it is that the mapped drive is not available to the service (with "spawn tasks from the server" enabled in User Maintenance).

  • 0 in reply to dskantor

    I checked the service on the server, and YES it's set to local system account. I could change it to the Administrator service same a Sage Exchange is set to. FYI, the UNC path does in fact work all the time, not the mapped drive path on the terminal server AND later as I discovered on my personal desktop on the same LAN!!! Even after uninstalling the workstation client and reinstalling the client then launching the automatic updates then logging on and trying again...

*Community Hub is the new name for Sage City