• Sage Mas 90 Record " is missing from [path]\mas90\mas_system\SY_WORKSTATION.M4T"

    Hello, I get the Error Record " is missing from [path]\mas90\mas_system\SY_WORKSTATION.M4T" when trying to log on to Mas 90 from all our workstations. I have Mas 90 version 4.50. I've tried restarting our server and computers with no luck. I've also…
  • The wizard cannot copy the backup files needed to continue. Use SQL server Management Studio to backup the MAS_System.bak and company databases that you want to migrate.

    KB 64515 FYI, (posting in case it might help someone else). I just had this error, and it turns out the firewall on the destination SQL server was blocking access to the c$ share. I'm not sure which one was the magical fix, but enabling the selected…
  • Recover Admin Password for MAS 90 4.05 for Migration

    Is there any way to recover the Admin password for MAS 90 4.05. Someone (who is not longer with the company) changed it and we are attempting to do a Parallel Migration to Sage 100 ERP. The PM requires the Admin password for the old version. We have users…
  • In Sage 100 is there a way to see who is in a particular record, such as, a single work ticket?

    I know is Master Console you can see what activity in a module a user is in but can you ascertain exactly what record the user is in, such as, Work Order 10?
  • CRM User taking up license seat

    We have the designated CRM user in Sage 100 showing as logged into Sage 100 and occupying a seat, however no user is actually signed in. It shows the user is signed in from the user, even when there are NO windows users logged into the server. Does…
  • Blank screen when double clicking sage 100 2013 shortcut with no login screen

    Hi, I have this workstation when starting sage 100 shortcut or program files it launches with a blank screen with a "+" on the corner with no text or menu. tried reinstalling the program, rebooting and no solution. other workstations works fine. Affected…
  • Database Login Error Sage 100 2014

    Recently we have been running into an issue with our 64-bit Windows users where they receive the below error when running any report in Sage 100 2014. Does any one have an idea of why this happens?