Sage 100

 View Only

  • 1.  MAS_SYSTEM Issue on Test Servers

    Posted 05-28-2021 09:50
    Version 2019 Premium.  Working well in live environment and in one test environment.  Client provided two additional virtual servers, one DEV and one for testing Unified Logon (which we tried to talk them out of to no avail!).  Installed Sage 100, third parties, all good.  Copied the MAS_SYSTEM folder from live; launched Sage 100; "Unable to create a session object. The workstation may have been corrupted."  Uninstall and reinstall wksetup, same issue.  Wipe the slate clean (SQL as well), reinstall Sage 100 and third parties, all good.  Restored MAS_SYSTEM SQL database from live; same issue.  This occurred on both servers.  Any ideas?  (Going to their IT provider for help is not an option in this case unless we can tell them exactly what we need them to do and why.)

    ------------------------------
    Susan Pawlowic
    Sage 100 Solutions Architect
    RKL eSolutions, LLC
    ------------------------------


  • 2.  RE: MAS_SYSTEM Issue on Test Servers

    Posted 05-28-2021 10:03
    Did you try migrating instead of just copying?

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 3.  RE: MAS_SYSTEM Issue on Test Servers

    Posted 05-28-2021 10:49
    Yes, and I get a message stating we need about 20% more disk space, despite there being plenty.

    ------------------------------
    Susan Pawlowic
    Sage 100 Solutions Architect
    RKL eSolutions, LLC
    ------------------------------

    Original Message


  • 4.  RE: MAS_SYSTEM Issue on Test Servers

    Posted 05-28-2021 10:57
    There was a bug with the migration database copy phase, where the data path used in the SQL install is used instead of the active data path in SQL.  If you (for example) used default paths (C-drive) during the SQL install, then changed the paths to a larger drive (D,E...) the migration would still copy the .BAK files and restore the MDF / LDF to the C-drive path, which may not have enough space.

    Sage said they would fix this, but for 2019 it could still be a problem.  If you can, reinstall SQL with data paths set properly during the install.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 5.  RE: MAS_SYSTEM Issue on Test Servers

    Posted 05-28-2021 11:15
    @Kevin Moyes thank you for the timely response, as I have a meeting with IT in about 17 minutes.  Happy holiday weekend, everyone.​

    ------------------------------
    Susan Pawlowic
    Sage 100 Solutions Architect
    RKL eSolutions, LLC
    ------------------------------

    Original Message


  • 6.  RE: MAS_SYSTEM Issue on Test Servers

    Posted 05-28-2021 10:17
    Ownership on that MAS_SYSTEM folder in SQL? See

    ------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ------------------------------



  • 7.  RE: MAS_SYSTEM Issue on Test Servers

    Posted 05-28-2021 10:54

    @Wayne Schulz that was it - MAS_USER was not owner.  I did not even go there, as I "assumed" it was not an issue since I was able to restore the DB.  ​Feeling a little foolish but a little wiser.



    ------------------------------
    Susan Pawlowic
    Sage 100 Solutions Architect
    RKL eSolutions, LLC
    ------------------------------

    Original Message


  • 8.  RE: MAS_SYSTEM Issue on Test Servers

    Posted 05-28-2021 11:08
    Addendum:  I re-restored the MAS_SYSTEM database and found that doing so resets the MAS_USER permissions.  Resetting after the restore is required.  Not sure why that would be, since the permissions are correct on the DB where the backup was made.

    ------------------------------
    Susan Pawlowic
    Sage 100 Solutions Architect
    RKL eSolutions, LLC
    ------------------------------

    Original Message


  • 9.  RE: MAS_SYSTEM Issue on Test Servers

    Posted 05-28-2021 12:20
    MAS_User / MAS_Reports are SQL logins and technically different for each SQL install.  Database owner is determined by who restores the backup in the new system (but is easy to change after that).

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 10.  RE: MAS_SYSTEM Issue on Test Servers

    Posted 05-28-2021 12:30
    We don't have permission to make the backups, so that was it!

    ------------------------------
    Susan Pawlowic
    Sage 100 Solutions Architect
    RKL eSolutions, LLC
    ------------------------------

    Original Message


Related Content