Sage 100

 View Only
  • 1.  Hope I'm putting this in the right place. First po

    Posted 10-11-2010 06:35
    Hope I'm putting this in the right place. First post. You do not have the rights to SOA. Client is on MAS 90 3.71, 2 users on an XP workgroup just using GL and AP. System has worked for years. Two days after support run out this happens. When trying to log into the client computer, MAS tries to start but then a message comes up the says you don't have the rights to SOA folder. We have rerun the WKSetup as Admin, user can log in from server - no problem, we can create and save a file to the SOA folder from the workstation, the IT department worked on the network for 3 hours and could find nothing wrong relating to permissions and believe it or not, a Sage techie worked on this for over an hour (must have felt sorry for me) without luck. Any ideas what could have happened or where to look?


  • 2.  RE: Hope I'm putting this in the right place. First po

    Posted 10-11-2010 06:52
    Any chance a file is read only? If you copy to local drive does it still so this? Anti-virus issue?


  • 3.  RE: Hope I'm putting this in the right place. First po

    Posted 10-11-2010 07:11
    Changed the attributes just in case Read Only was the problem. Anti-virus was first disabled , then uninstalled. All users can log in and save files, open files from the XP server. All users can access the XP server, open and write files (including those in the MAS90 folder) from the workstation. MAS just will not open.


  • 4.  RE: Hope I'm putting this in the right place. First po

    Posted 10-11-2010 07:46
    I'd pull it quickly to a local workstation to rule out a corrupt system control file. If it can be run on a local setup (no network) then it's likely one of many things in the network settings (rights, ACL, anti virus, malware, etc).


  • 5.  RE: Hope I'm putting this in the right place. First po

    Posted 10-11-2010 07:47
    Also if this is MAS 200 (and I understand you stated 90) -- I believe on this level the server has to be able to ping the workstations attempting to connect or you get fluky errors.