Run Sage 100 Advanced in Sage 100 Standard mode (bypassing the Sage 100 Advanced or Premium edition's service or application) to troubleshoot issues such as the following:

• Deferred is the only printer option available
• Errors on the screen that are otherwise disguised
• Network connection issues
• Other tasks that may require using a mapped drive instead of a UNC to retrieve the data
• Other problems that may be tied to the running of the Sage 100 Advanced edition's service or application, such as program or data corruption

• It does not use the primary Sage 100 Advanced features (for example: processing data at the server rather than the workstation, performance, network security)
• Users cannot "see" each other. Users in "Sage MAS 90" mode do not display in the Sage 100 Advanced Master Console. Sage 100 Advanced users do not display in the "Sage 100 Standard" Master Console.
• The correct toolbar bitmaps and HTML pages do not display on the Business Desktop (Launcher).

1. Map a drive to the parent drive or folder above the "..\MAS90" folder where Sage 100 Advanced is installed (for example: "F:\Apps\MAS90").
   • A UNC path cannot be used. The "Sage 100 Standard" user must have Full Control permissions to the "..\MAS90" folder and all subfolders.
2. Then, either run Sage 100 from the Providex prompt, or create a Sage 100 Standard shortcut icon.

To run Sage 100 Advanced from the ProvideX prompt:

To create a "Sage 100 ERP Standard" shortcut icon:

1. Make a copy of the Sage 100 ERP Advanced shortcut icon
2. Modify the following fields in the new icon (where X is the mapped drive letter, or C at the server):

• Target:
  "X:\MAS90\Home\ Pvxwin32.exe" ..\Launcher\Sota.ini ..\SOA\Startup.m4p
• Start In (quotes are required only if the path contains a space):

"X:\MAS90\Home"

Note: In case of an upgrade, for Sage 100 versions 3.7x (MAS200), on Step 2 above, target will be "x:\MAS90\Home\Pvxwin32.exe" ..\Launcher\Sota.ini ..\SOA\MAS90

Sage 100 ERP Premium Server Edition:

Assign SQL database permissions to the user:

Note: This step is not necessary if you log on as Administrator. The trusted Windows Administrator will be mapped into the SQL Builtin\Administrators group, unless specific SQL Server security has been set up.

1. Note the user's Windows domain account.
2. Open a command prompt (Start / Run / CMD) and type SET
3. Note the values for USERNAME and USERDOMAIN
4. Have the SQL Database Administrator (DBA) assign the following database roles to domain account for the MAS_XXX and MAS_SYSTEM databases (XXX = company code):
   • DB_DataReader
   • DB_DataWriter
5. Create the MASSQL DSN driver to access the data.
   • Note: If you are at the server, this step is not necessary. The MASSQL DSN already exists.
6. At the Windows Start menu, click Control Panel.
7. Double-click Administrative Tools and Data Sources (ODBC) to open ODBC Data Source Administrator (or run Start / Run / ODBCAD32). (Note: For a 64-bit operating system, you must run ODBCAD32.EXE from the "C:\Windows\SysWOW64" folder to access the 32-bit ODBC Data Source Administrator).
8. Click System DSN tab.
9. Click Add
10. Select SQL Server and click Finish to start the wizard.
11. Enter the following and click Next:
    • Name = MASSQL
    • Description = MASSQL
    • Server = The name or IP address of the SQL Server
12. Click With Windows NT Authentication Using Network Login ID option button.
13. Click Client Configuration
14. Click TCP/IP option button, and OK to return to the authentication window.
15. Click Next.
16. Note: If "Logon Failure" or similar occurs, the user account does not have sufficient rights to the SQL Server. Close the window, give the user sufficient rights, and start over.
17. Select both of the ANSI check boxes, and clear all other check boxes. Click Next.
18. Accept the default selections and click Finish.
19. Click Test Data Source to verify the connection.
20. Make a copy of the Sage 100 ERP Premium shortcut icon
21. Modify the following fields in the new icon (where X is the mapped drive letter, or C at the server):
22. • Target:
      "X:\MAS90\Home\Pvxwin32.exe" ..\Launcher\Sota.ini ..\SOA\Startup.m4p
    • Start In (quotes are required only if the path contains a space):
      "X:\MAS90\Home"

Note: In case of an upgrade, for Sage 100 versions 3.7x (MAS200), on Step #21 above, target will be "X:\MAS90\Home\Pvxwin32.exe" ..\Launcher\Sota.ini ..\SOA\MAS90