How to Fix: Sage 100 Desktop Launcher Closes Immediately After Login (No Error)

If you log into Sage 100, watch the Desktop Launcher start to load, and then instantly see it close without any error message, you aren’t alone. This silent crash is a common issue that usually stems from an incomplete system shutdown broadcast or missing/corrupted system data files following a migration.

Below is a quick breakdown of why this happens and how to get your users back into Sage 100.

Why Is This Happening?

1. Broadcast Shutdown Flag Set to ‘Y’: If an administrator or workstation broadcasted a system shutdown from the Master Console and the process was canceled or left incomplete, the system flag (BroadcastShutdown) in your data directory stays active. This actively blocks any new user logins, causing the launcher to exit immediately.
2. Post-Migration Data File Issues: Missing files within the MAS90\MAS_SYSTEM directory after a recent server migration or upgrade can trigger the same behavior.
3. Workstation-Specific Preferences: In rare single-user cases, automatic logoff preferences saved locally can cause immediate launcher crashes.

Step-by-Step Resolutions

1. Clear the Broadcast Shutdown Prompt

If the shutdown was triggered from a specific workstation, check that machine for an active Master Console or OK prompt. Completing or dismissing the dialogue box often resets the status automatically.

2. Update SY_System.m4t via Data File Display and Maintenance

If the system is stuck in shutdown mode across all workstations, you will need to manually reset the flag:

• Open a working Sage 100 installation (or access the utility on the server) and navigate to Data File Display and Maintenance.
• Open the ..\MAS90\MASSYSTEM\SY_System.m4t file (or SYSystem table if you are on Sage 100 Premium/SQL).
• Locate the BroadcastShutdown field/column and change its value from Y back to N.

(Note: If you do not have access to this utility, you can restore SY_System.m4t from a recent backup taken prior to the shutdown attempt, or contact Sage Customer Support to edit the file for you.)

3. Clear Local User Profiles

If the issue persists or only impacts a single user on a specific computer:

• Navigate to the Documents folder on the affected user’s computer and rename the Sage 100 folder (e.g., to Sage 100_OLD).
• Alternatively, log in via another admin account, navigate to User Maintenance > Preferences tab, and try toggling off the Automatic logoff option for that user.

Official Support Reference

For the original knowledge base article, additional details, and technical updates, view the full guide on the Sage Knowledgebase Solution Page.