From moving up to the most recent form or putting in new applications to refreshing Windows or servers, there are an assortment of reasons that Sage 100 may be running somewhat more slow than it used to. Some of the time the fix is basic, different times somewhat more testing. Here are a few hints to help.
An as of late introduced update can cause execution issues. Models incorporate Windows Updates, antivirus or firewall refreshes that change or reset past settings, changes to reinforcement programming processes, and numerous others. Specifically on the off chance that a new Windows Update happened, think about moving back the update to check whether the presentation issue is settled.
Sage 100 Advanced and Premium gander at the default printer on the server each time an undertaking is sent off. Sage 100 Standard release actually looks at the workstation’s default printer. For network printers, ensure they’re all on the web and on the off chance that an organization printer is disconnected and at this point not required, eliminate it from Control Panel > Devices and Printers.
For Sage 100 Standard, Workstation Setup ought to be introduced from a planned drive letter way, with the end goal that the easy route to send off Sage 100 likewise has the planned drive letter way. The drive letter should be planned to a catalog above “MAS90.” For Sage 100 Advanced or Premium, Workstation Setup ought to be introduced from an UNC way, with the end goal that the easy route to send off
Sage 100 additionally has the UNC way. The UNC share point should be an index above “MAS90.”
Check that your antivirus programming is designed to avoid each of the most recent Sage-related organizers, documents, filter settings, and so on as suggested by this Sage Knowledgebase Article.You can also chat – Sage 50 Live Chat
Send off Sage 100, right-click the Sage 100 alternate route, and select Run as Administrator. Then, at that point, contrast Sage 100 execution with when the alternate way isn’t set to Run as Administrator.
As indicated by current framework prerequisites, common ping timings with 1,800 bytes of information ought to be 20-30 milliseconds or quicker. An exemplary issue would be where execution is fine on the Sage 100 server yet sluggish at workstations (in view of the organization speed).
This is only a speedy reference guide. Look at this Sage Knowledgebase article for all relevant information and directions for all investigating tips.
Read Also-: How to Restore Sage 50 Backup