Option 1: Switch between Classic and Standard Desktop Views

• Note: Available only for Sage 100 2016 through Sage 100 2019 (Classic Desktop is not available in Sage 100 2020 and above)
• Switch to the Classic Desktop view (or if already using Classic, switch to the Standard Desktop view), then back again
  • See Article ID 70470 DocLink: How to change the Desktop view between Classic or Standard in Sage 100 for instructions

Option 2: Delete Damaged Registry Subkey

• Delete Registry Subkey (HKEY_CURRENT_USER\Software\Sage Software\BIE Explorer\Explorer)
  • See Article ID 93618 DocLink: Business Insights Explorer Views appear blank for users that use Standard View for instructions
• Check the Views location in Business Insights registry keys:
  • Check the ViewsPath value under the registry key: HKEY_CURRENT_USER\Software\Sage Software\BIE Explorer\Products\MAS90

Option 3: Recreate the "Sage 100" Folder

1. Via File Explorer (Windows Explorer), browse to the Workstation user's "Documents" folder (or "My Documents" on older workstatations such as the retired Windows 7 operating system)
   • Note: For example, "C:\Users\ \Documents"
2. Rename the "Sage 100" folder
   • Example: Rename to "xSage 100"
3. Log in to Sage 100
4. Select Standard Mode when prompted to select a view.
   • Note: A new "Sage 100" folder will be created in the Workstation user's "My Documents" folder
5. Open Business Insights, Explorer menu, Views and make sure they are now working
6. Log out of Sage 100
7. If favorites were created (existed prior):
   1. Via File Explorer (Windows Explorer), access the renamed ("xSage 100") folder
   2. Copy the favorites.json file to the newly created "Sage 100" folder

Option 4: Copy working Views over

• Note:
  • This may only work if the issue appears to be with a specific view or views
  • These steps require access to an additional working installation
• The issue may be the Views do not exist or the incorrect (or non-existent) path is specified in the Windows Registry

1. Check the Views location in Business Insights registry key:
   • Check the ViewsPath value under the registry key: HKEY_CURRENT_USER\Software\Sage Software\BIE Explorer\Products\MAS90
   • If the path does not exist, either the path needs to be corrected in the ViewsPath to the correct location or the Views folders may need to be copied over from a "working" machine to the local machine in the path specified (see below). You may need to compare ViewsPath value on a "working" machine.
2. Navigate to "...\MAS90\BIExplorer\Views" on the server where Sage 100 is installed and verify that views exist in this directory (this could affect multiple users on server)
3. Copy a view file from a known "working" installation and replace your local workstation file (in newer versions this may be moved to "C:\ProgramData\Sage\BIE Views")

Option 5: If after trying all the options above and issue occurs on only one workstation (or works fine on the server and at least one other workstation)

1. Uninstall the Sage 100 Workstation Setup client (via Windows, Control Panel, Programs and Features) (Article KB 18240)
2. Rename any leftover folders like "Sage 100" on the workstation's "C:\Users\ \Documents" location, or the "MAS90" folder where the removed Workstation Setup had been installed (if still exist).
3. Run the Sage 100 Workstation Setup client install as Administrator (Article KB 18248)

Option 6: (Premium only) Verify the MAS_Reports user has db_datareader access to all MAS_* SQL databases.

1. Log into SQL Server Management Studio with account with sysAdmin role
2. Expand Security, Logins
3. Right-click 'MAS_Reports' then select Properties
4. Select 'User Mapping' under 'Select a page' on the left panel
5. Verify the user has 'db_datareader' and 'public' access to all MAS_* databases.
6. If user does not have 'db_datareader' access to database perform the follow steps for each database.
   1. Select 'New Query' from the toolbar
   2. Copy/Paste the following SQL query into New Query window
      

      --begin
      
      --Reset MAS_Reports permissions to Database
      
      EXEC sp_dropuser 'MAS_Reports'
      GO
      EXEC sp_grantdbaccess 'MAS_Reports'
      GO
      -- Assign db_datareader permissions to the user
      EXEC sp_addrolemember 'db_datareader', 'MAS_Reports'
      GO
      -- Set the default schema to dbo for the user
      ALTER USER MAS_Reports WITH DEFAULT_SCHEMA = dbo;
      
      --end

   3. Select Database that user does not have 'db_datareader' permissions from dropdown list on the Toolbar
   4. Click Execute to run query
   5. Repeat Steps c and d for each database the user does not have 'db_datareader' permissions
7. Log back into Sage 100 and verify data appears on BI Explorer view.

Option 7: (Advanced/Premium) Verify Sage 100 client is not configured to run in Windows XP Compatibility mode

1. 
   

   Right-click Sage 100 shortcut and select Properties.

2. 
   

   Click on Compatibility tab.
3. If ‘Run this program in compatibility mode for:’ is checked go to
   step 4 to disable.

4. 
   

   Select ‘Change settings for all users.’

5. 
   

   Uncheck ‘Run this program in compatibility mode for:’

6. 
   

   Click OK twice to save settings.

7. 
   

   Log back into Sage 100 and verify BIE views display data.

Option 8: Unblock the App in Windows Defender