If that service account is a domain user, then the permissions should be fine (unless IT actually restricted it), but it sounds like DFS-R's getting you and that IT took the lazy way out and replicated the whole drive rather than folders (which means they are not using or misusing DFS-N). The simplest' solution would be to add a new drive (outside DFS-R) for just the Sage/MAS90 folders and let them know it's not aware or compatible with DFS.
Steve Iwanowski, NextStep Technology Advisors, aka DSD Lancaster PA ¯\_(ツ)_/¯
Original Message:
Sent: 06-06-2023 08:43
From: Wayne Schulz
Subject: Use of Distributed File System ( DFS ) on Server 2022
What this customer did is confusingly name their servers nearly identically:
\\dc1 (old Sage 100 v2021)
\\dc01 (new Sage 100 v2022)
Then DFS mirrors a D: drive to both servers.
I installed Sage 100 2022 to the new \\dc01 server ( I used the \\dc01 full name wherever I was prompted for a path and avoided using a local D: drive). And that drive is mirrored/synchronized so that it shows up in \\dc1 ( old server ) with the same path d:\acct.
I suspect, but have no way to know;
a. Somehow, the service account running Sage 100 doesn't have proper access to whatever DFS is doing. Yet I replaced that SERVICE acct with the Windows Account I'm using to access their network "Sage" and restarted the service and the same results. Yet I can MAS90 mode this and run MAS90 "As Sage," and everything works fine without error ( seems to possibly rule out a permissions issue on the Windows user account 'sage').
b. Some other magic that DFS is doing and jumping into a position between the Sage service and the actual network path
c. This seems to hamper the typical diagnostic things I would try -- for example, renaming the old folder on \\dc1 to \old.mas90 to be sure there wasn't some confusion in paths ( I think if I rename that folder on \\dc1 it's just going to replicate/sync to \\dc01)
------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT
------------------------------
Original Message:
Sent: 06-06-2023 08:24
From: Steve Iwanowski
Subject: Use of Distributed File System ( DFS ) on Server 2022
It sounds like you've moved on, but I'm a daily digest guy, so here are my thoughts for posterity:
One quick question: on the client, if you go to CMD and type ECHO %USERPROFILE%, do you see C:\users\blahblah or is it a redirected folder (\\server\folder\blahblah)?
DFS can be configured to do two things: replicate folders/files from server to server (DFS Replication) or create a logical network path in front of the true network path (DFS-N, which eases future server migrations or recovery efforts). We used to use both DFS for Paperless Office so that we wouldn't need to update the links after upgrades/movements but neither DFS was reliable for the Application Service for us. I'm guessing that the service is trying to use the actual path but the client is trying to use the logical path (or vice versa), but either way, IT should be able to remove Sage from their DFS namespace and replication.
------------------------------
Steve Iwanowski, NextStep Technology Advisors, aka DSD Lancaster PA ¯\_(ツ)_/¯
Original Message:
Sent: 06-06-2023 08:10
From: Wayne Schulz
Subject: Use of Distributed File System ( DFS ) on Server 2022
The new Sage 100 2022 Advanced is setup on a new server. The paths appear to be correct and I've been checking them very regularly in *INFO and it always seems to point to the \\dc01 ( correct new server ).
At this point, I don't have another four weeks to wait and see whether more people log in to 90 Minds, and the IT vendor seems a bit ahead of their skis in terms of knowing what DFS is doing for them ( they at first denied using it and then later said "oh year" without much information on why it's there. I opened a case with Sage and they didn't have much to offer except their thoughts and prayers.
I'm rolling back and suggesting the customer is going to be indefinitely on 2021
And I've made a reasonable effort - short of pulling out the polygraph - to ensure that the account running the service is a global super domain admin. When you have third-party IT running the show and they seem a little out of their element, then these things - at least for me - end with a big question mark as to whether I fully have a Domain Admin account.
On to my next gig - quoting people for extracting data to Intacct and Netsuite....
------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT
Original Message:
Sent: 06-06-2023 01:48
From: Todd Martin
Subject: Use of Distributed File System ( DFS ) on Server 2022
What is the path that is used in the application setup? Is the account the local user or a domain user or did you try both for the service? Does the file path in Sage 100 for the company reflect the path used for DFS or the local?
Original Message:
Sent: 6/5/2023 4:37:00 PM
From: Wayne Schulz
Subject: RE: Use of Distributed File System ( DFS ) on Server 2022
I did try running it as an application - it didn't seem to work any worse/better.
------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT
Original Message:
Sent: 06-05-2023 16:26
From: Kevin Moyes
Subject: Use of Distributed File System ( DFS ) on Server 2022
I remember one issue with a client using DFS related to My Documents not being a local path.
When installing Sage server, you used proper local paths? Anything that changes based on the active Windows login won't work for the Sage service.
You might want to try running the Sage service using application mode, to test if paths not being available to the Windows Service is the issue.
------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.