Schulz Consulting

Consulting and Upgrades

Eight Tips for Speeding Up Sage 100

by

We’ve heard from some users that after upgrading Sage 100 to version 2020 that they’ve experienced slower performance.

Slow performance can be cause by many things ( see below for a list of the top 8 reasons your Sage 100 might be slow ).

In many instances the slowness of a new Sage 100 upgrade can be traced back to overly aggressive anti-virus or malware scanners causing interruptions in processing.

The suggestions below may ( or may not ) help speed up your Sage 100 system. Prior to calling support I recommend walking through each and seeing if they might apply to your particular installation.

  1. Change the default printer to another physical or network printer and then test/check the performance
    1. Sage 100 Advanced and Premium looks at the default printer on the server every time a task is launched.
    2. Sage 100 Standard edition checks the workstation’s default printer.
    3. Make sure all Network Printers are on-line
    4. If a Network Printer is off-line and no longer needed, remove it from Control Panel, Devices and Printers
  2. Check the path
    1. For Sage 100 Standard, Workstation Setup should be installed from a mapped drive letter path, such that the shortcut to launch Sage 100 also has the mapped drive letter path. The drive letter must be mapped to a directory above “MAS90”
    2. For Sage 100 Advanced or Premium, Workstation Setup should be installed from a UNC path, such that the shortcut to launch Sage 100 also has the UNC path. The UNC share point must be a directory above “MAS90”
  3. Check that the latest Sage Anti-Virus setting exclusions have been applied
  4. Consider temporarily disabling anti-virus and malware scans
    1. This is trickier than it should be – and may require uninstalling and rebooting the server
  5. Consider setting Sage 100 so that the shortcut always “runs as administrator”
  6. Check ping times for Advanced/Premium
    1. PING servername -l 1800 ( Note the -l is lowercase letter L ) 
    2. Anything over 40 ms is slow and may be cause for further investigation
  7. Turn off the Sage Product Enhancement Program
    1. Login to Sage as Administrator
    2. Select Sage Product Enhancement Program
    3. Deselect “Participate in the Program” by removing the checkmark
  8. Never run Sage over WiFi without use of RDP or Terminal Server/Citrix
    1. Customers may refer to this as “using a VPN” but the VPN does NOT act as a remote desktop
    2. Customers running solely over WIFI or the Internet with RDP will see most pronounced slowdowns in printing

All information was drawn from this Sage KB article – Slow performance when opening a new task or starting Sage 100, or when running Sage 100 across a network

How To Upgrade Older MAS 90 3.6x to Current Sage 100cloud

by

Occasionally we run into very old versions of Sage 100. These are typically defined as any version 3.x.

Thankfully, you can upgrade all of your existing data without no re-keying. Here’s how.

First, I recommend you start off at version 3.71 or higher. If you are on an earlier version you should upgrade to 3.71.  I found it was sometimes possible to install 3.71 on top of ( aka in place ) the older release. If you install over the prior Sage version be certain to take a full backup first.

From 3.71 you should be able to migrate directly to Sage 100 2017. If you try to go higher than this you may receive an error suggesting that you migrate to 4.5 PU8.

From Sage 100 2017 you can migrate to the latest version of Sage 100.

Be sure you make backups of your original MAS 90 data and program files before you begin.

Finding source files for each of these versions is a bit of a project so you may want to enlist the help of your Sage partner.

Sage 100cloud – Providex ( PVX ) vs SQL – Pros And Cons

by

As Sage 100 users migrate to  Sage 100cloud we are often advising them to consider whether a move to a SQL database may be of benefit to their operations.

One of the key benefits of the Sage 100cloud subscription is the ability to use any of the following flavors of Sage 100cloud with no additional charge for changing the underlying database driving Sage 100cloud:

  1. Sage 100cloud Standard  – Providex based
  2. Sage 100cloud Advanced – Providex based – runs in a client-server type environments
  3. Sage 100cloud Premium – SQL backend – runs on Microsoft SQL server

What’s The Best Option For Sage 100cloud: Providex or SQL?

Below is a condensed version of the pros and cons of changing your Sage 100cloud to a back-end SQL database. Typically we recommend considering this switch when you:

  1. Have significant database sizes (> 500 MB) and expecting to continue growing
  2. Noticeably slow reporting – especially with externally connected reports/queries
  3. 10+ users on the system concurrently (now or expected in the future)

Your end users don’t need to know anything about SQL. About the only thing they’ll notice is if they use the SOTAMAS90 for external reporting they will have to change drivers in favor of a connection to the SQL tables.

Benefits of SQL for Sage 100 and Sage 100cloud

  • No premium for premium (a true benefit of Sage 100cloud subscription)
  • External reports based on SOTAMAS90 pretty easy to convert to Premium
  • Customers notice a speed increase in external reporting (true value added)
  • Virtually all 3rd party ISV solutions work with Premium
  • Reporting via external tools/connections can be significantly faster
  • Straightforward to set up Sage 100cloud on Premium
  • The prior penalty for SQL speeds in native Sage screens seems mostly gone
  • Data File Display & Maintenance (DFDM) goes away but you can download a free DSD SQL DFDM
  • Skilled users can use SQL tools for query/changes (recommend locking users out of write capabilities)

Disadvantages of SQL for Sage 100 and Sage 100cloud

  • Need to be comfortable setting up a SQL server
  • Some customers reluctant to invest in a new server to maintain (especially if they don’t have on-staff IT person)
  • Sage has limited info about how to configure the SQL server
  • Easy to use SQL tools to change data without Sage 100cloud which could result in lost data if not performed by a qualified person
  • WO, MRP users can’t use Premium as of December 2018 (due Q1 2019)
  • Tricks you may do with Providex such as swapping in or out single data files are difficult/impossible with Premium
  • Cannot simply insert a new license key – a system upgrade will be required which involves migrating existing data to a new installation of Sage 100cloud Premium

 

If you are considering a move to Sage 100cloud Premium ( aka SQL ) then consult our summarized guide to selecting and configuring Microsoft SQL for Sage 100 Premium.

The use of SQL is a popular selection for growing Sage 100cloud customers with significant reporting requirements now or in the future.

For more information contacts us or give your Sage 100cloud partner a call.

Sage 100cloud Upgrade Master Checklist and Guide

by

 

Revised April 23, 2018 – While we strive to keep the information on our site current, you should verify that the content below is applicable to your version of Sage 100cloud.

You may wish to use this link which is an Evernote document containing the most current version of the information below but formatted in a slightly more readable manner.

 

Please read these instructions through prior to beginning your upgrade testing. If you have any questions please let us know. These instructions are meant to cover the most frequently asked questions and there may be additional information we provide or we may advise that your upgrade is performed in a modified way.

 

Before starting your upgrade please consult with your IT Advisor or Sage Business Partner. In most cases you should have them assist you with the upgrade process.
Generally, you will want to break your upgrade down into stages and take time at each stage to review and test before deciding to perform a final upgrade.
OUR STANDARD SAGE 100CLOUD UPGRADE APPROACH IS FOUR STAGES
These four stages can occur over a period of time and are designed so you have adequate time to test each step of the upgrade.
  1. Configure and load new version
  2. Test convert and review
  3. Go-Live
  4. Post Go-Live
Legend:
  1. (Critical) – Very important – management, accounting, IT review
  2. (FYI) – management, accounting review
  3. (IT Dept) – IT department review
BEFORE EVERYONE LEAVES FOR THE NIGHT
  • Unless instructed otherwise, have all data entry updated
  • Do not have anyone logged into the system overnight (check Master Console before leaving for the day)
  • Disable any integrated solutions ( Sage Integration Server, Third-Party Integrations)
  • Make a full backup
BEFORE THE UPGRADE BEGINS
CHECK THESE THINGS BEFORE YOU START THE UPGRADE TESTING
  • (Critical) Ensure any 3rd party integrations are compatible with the version of Sage 100 being upgraded to
  • (Critical) Verify all servers and workstations meet or exceed minimum hardware and operating requirements established by Sage – https://goo.gl/Zh7AzP
  • (Critical) If you are using Sage 100 Payroll ensure that you are enrolled in a Payroll Subscription. Read more here – Sage Payroll FAQ Existing Customers.pdf
  • (Critical) Schedule any 3rd party assistance required (ie. Starship, Scanco, Scanforce, Sage CRM, Sage Intelligence)
    • We generally recommend having the 3rd parties perform their upgrades alongside our Sage 100 upgrade (additional fee to 3rd party may apply)
    • FRX is no longer supported by Microsoft. In most cases, it will work but we cannot guarantee it and before you create any time consuming or costly new reports we think you should consider migrating to a supported report writer such as Sage Intelligence, BizNet or FYISoft (fka RenovoFYI).
  • (FYI) About the timing of your go-live
    • Ensure your key people – including IT – will be in the office on go-live date as we need them to login to the network and test
    • IT resources should be available in case of questions. Generally, they do not have to be in the building so long as they are reachable within a reasonable time
    • Do NOT schedule a go-live for a date with other mission critical reporting or meetings due
  • (FYI) You may only upgrade to a version of Sage 100 to which you have a valid license. Ensure you are enrolled in a valid license with Sage.
  • (FYI) Read and agree to the Sage EULA – https://goo.gl/lBiSWK .
    • During the upgrade we will need to accept it on your behalf while installing the program.
    • If there is anything you disagree with please bring it to our attention immediately.
    • You agree that we are instructed to enter through and agree to the EULA on your behalf during the upgrade.
  • (FYI) If you are on Sage 100 perpetual licensing you may want to consider whether Sage 100c and a platform change to Advanced or Premium (SQL) is advisable
  • ( IT DEPT) Check the network location for the new version of Sage 100 and ensure you have adequate disk space.
    • A good rule of thumb is have at least 100 GB remaining after the installation of the new version. The goal is to have enough remaining after the upgrade that you are relatively assured of not running out of space mid-year.
  • (IT DEPT) If using Sage 100 Advanced or Premium ensure that you are using a DOMAIN Administrator equivalent account to run the service – https://goo.gl/hPNlkM
  • (IT DEPT) If the upgrade is to a new server, be sure you modify your backup procedure to include the new server folder (typically \Sage 100 (formerly Mas90) and all subfolders) as well as any additional Sage data (ie. Paperless Office).
  • (IT DEPT) Sage Users must have full rights to the \MAS90 and all sub-folders. If they do not they will receive a licensing related message and be prohibited from starting Sage.
    • You (or your IT department) are responsible for creating required Sage 100 shares and establishing permissions. If you encounter difficulties or have questions on how to create the noted permissions please contact your IT support as we do not advise on security or IT configurations as part of our upgrade.
  • (IT DEPT) Exclude the following folders and file extensions from anti-virus scanning on your server – DCL, DD, DDE, DDF, LIB, M4D, M4L, M4P, M4T, PRM, PVC, PVX, RPT, SOA, XEQ.
    • In our experience, Anti-Virus and Malware scanners are the most common culprits responsible for slow performance.
    • See the following Sage knowledge article for a complete list of file exclusions – https://goo.gl/7kB7X8
TESTING (BEFORE GOING LIVE)
  1. In most cases we have no issues with data conversion. It’s always good to double check your data as soon as possible. Don’t wait several weeks to do this because if you find a discrepancy it’s likely too late to restore from a backup.
  2. Ensure all users can
  3. Login to Sage 100
  4. Navigate freely through Sage 100
  5. Print from Sage 100
  6. Access customary
    1. Forms
    2. Reports
    3. Data imports
    4. Third-party integrations
THE NIGHT BEFORE GO-LIVE
  1. Ensure you have a full system backup – if your backup kicks off overnight you may need to start it earlier in the day so you have a good backup prior to final data conversions that happen in the evening.
    1. Instructions on what files to backup – https://goo.gl/L7QiBl
  2. Ensure that your key people will be in the office
    1. We need them to login with their network credentials to test
  3. Before leaving for the day, have everyone log completely out of Sage 100 – do not leave any open sessions in remote desktop/Citrix/Terminal Server (if applicable). Verify this by looking at the Sage 100 master console which should display no logins except your own.
  4. Have all transactions posted in all modules
  5. Print key reports from each company as applicable. You should agree these totals to the new version on the day you go live.
    1. General ledger trial balances
    2. Accounts payable aging (last page)
    3. Accounts receivable aging (last page)
    4. Inventory valuation report (last page)
    5. Open Sales Order report (last page)
    6. Open Purchase Order report (last page)
  6. Additional reports for other modules – PR, JC, WO, – as needed to agree to post-conversion data
GO LIVE
  1. Compare reports printed from prior step for accuracy. Generally you only need to compare totals unless there is a reason to suspect other inaccuracy.
  2. Test all functions again – imports, forms, reports, third-party integrations
  3. If there is an issue with data your goal is to catch is ASAP
COMMON ERROR MESSAGES
In most cases you will not experience any error messages. However, here is a list of common errors (and their causes) so that you can be familiar with them and if needed make the required correction.
  • Cannot open ACTIVATION key file / NO VALID ACTIVATION FOUND!!
    Typically caused by one of the following:
    • You don’t have rights to \MAS90\HOME\LIB\KEYS on the where the Sage registration is stored
    • You are running on terminal server / citrix and need to copy the key into the local folder using these instructions – https://goo.gl/RNBl6S
  • UNLOCK REGION FAILURE (less common)
  • Speed seems slow or slower than prior Sage 100
    • Review and apply file exclusions for anti-virus and/or malware (this is almost always the cause) – https://goo.gl/7kB7X8
    • Ensure that remote users are only coming in via a remote solution such as RDP (Remote Desktop), Citrix, Terminal Server. Technically you can setup Sage 100 Advanced to run over a thin client but some tasks like printing will be unacceptably slow for remote users.
  • Message “Cannot connect to Sage Exchange Desktop” when attempting to either process credit card or add/retrieve credit card information from a customer account in Accounts Receivable. Beginning with Sage 100 v2017+ you must now install Sage Exchange Desktop 2.0 separately from workstation setup. This can be done from your \mas90\wksetup\autorun.exe (be sure to right-click and “run as administrator” to ensure you have proper user rights to install).
WHAT’S NEW IN SAGE 100?
Everyone uses Sage 100 differently. We have found there is no “one size fits all” answer to “what’s new”. Use the guides below to determine what new features of the latest release of are interest to your company.
OTHER FREQUENTLY ASKED QUESTIONS
The links below lead to the Sage knowledgeable where you may view answers to the specific question.
(c) 2017 Schulz Consulting LLC – https://s-consult.com – Please send corrections, additions, changes to wayne@s-consult.com. This information was compiled from information deemed accurate at the time of creation. Please consult your consultant prior to implementing. Always make a backup of your data prior to beginning the update process.

Crystal Compatibility and Sage 100

by

Have you recently started an upgrade from an earlier version of Sage 100 to Sage 100cloud or Sage 100 version 2018 and run into this Crystal Reporting error?

 

Crystal Report Windows Forms Viewer

“Unable to cast COM object of type”
‘CrystalDecisions.ReportAppServer.Controllers.ReportSourceClass’ to interface type
‘CrystalDecisions.ReportAppServer.Controllers.ISCRReportSource’. This operation failed because the QueryInterface call on the COM component for the interface with IID ‘{98CDE168-C1BF-4179-BE4C-F2CFA7CB8398}’ Failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

Here’s the reason that you are encountering the error and the way to fix it.

Example: Sage 100 or Sage 100cloud STANDARD upgrade from 2016 to 2018

  1. Install 2018 to SERVER
  2. Run 2018 workstation setup on a WORKSTATION which also has 2016 installed
  3. This breaks Crystal Printing on that 2018 workstation (at this point 2016 workstations can still print)
  4. To fix the 2018 printing, copy the Pvxwin32.exe.Config file from the 2018 SERVER “..\MAS90\Home” directory where Sage 100 2018 is installed, into the 2016 SERVER “..\MAS90\Home” directory of the previous version(s) where the error is experienced.
  5. The issue resolves for 2018 TEST WORKSTATION – BUT …
  6. However, because you copied the config files to the 2016 folder you break printing for 2016 LIVE WORKSTATIONS NOT YET UPGRADED WITH 2018 WKSETUP
  7. Unless those 2016 LIVE WORKSTATIONS (a) also install 2018 WKSETUP (or presumably you remove the Pvxwin32.exe.Config from above which breaks your 2018 workstation but lets 2016 without 2018 installed print ) AND you’ve moved the config described in (4) above.

Business Issue:

  • Generally not a big issue if you are doing an upgrade in one day because you can uninstall 2016 and install 2018 wksetup and everyone can print
  • The problem appears when a customer wants to test over the course of several days/weeks and wants to run 2016 and 2018 on the same workstation(s) in a production environment.
  • You can’t just give one person 2018 wksetup (and move the config to the 2016 folder) without doing the whole company or the fix above breaks the 2016 people who don’t have 2018 wksetup
  • While this may not seem like a huge issue it is problematic in large installs with 20+ user counts, shipping, receiving because of the time it takes to travel from workstation to workstation and debug minor issues,

Possible workaround on this would be:

  • Install 2018 for testing to a standalone workstation that is not used for any prior version
  • Test on this workstation that has no other Sage version(s)
  • When ready run wksetup on remaining workstations and remove prior Sage version
  • The issue with this workaround is other users can’t test various workstation issue such as printing, credit cards, etc

The Sage KB entry which more fully describes the resolution can be read online at – Error: “Unable to cast COM object of type” when printing in prior Sage 100 versions after installing Sage 100 2018

Contact Us

Schulz Consulting
Connecticut Office
Click Here To Contact Schulz Consulting
Email Us
Available remotely nationwide.
We are a local branch of DSD Business Systems Connecticut.