Order Manager
Version 8
Order Manager
Version 8
Contents of this Topic: Show
This topic provides suggestions and possible causes for the Monsoon OMS to experience degraded performance. Some of the suggestions are software release dependent or specific and may not apply to your environment.
As the business grows, it may become necessary to move the Monsoon OMS data file to a dedicated server rather than using a host PC that is busy performing other tasks. If possible, use a server with a solid state drive (SSD) to house Monsoon Order Manager 's data file. Also refer to System Requirements to make sure that the processor speed and RAM requirements of all servers and workstations are being met.
Microsoft Access 2010 users should minimize the ribbon. Refer to the Knowledge Base topic MS Access 2010.
Do NOT use ZoneAlarm Personal Firewall software.
Check the settings of the anti-virus software installed on each workstation to see if it is possible to exclude MS Access from the list of programs and/or files it scans as they are opened and closed. Monsoon Commerce suggests using the Microsoft Security Essentials software.
Use a gigabit ethernet network ( LAN or WAN). All components of the network must be capable of processing at that speed or the user will not reap the benefits of increased performance. A network connection is only as fast as its slowest component. Make sure that the ethernet cables, routers, hubs and NICs (network interface cards) being used support gigabit speeds. Cat5E ethernet cable is preferred.
Compact an Access data file weekly after creating a backup copy.
Run OM Compiler on a regular basis on each workstation.
Change the DefaultOrderView parameter (in the Program group) to All.
Archive old data to reduce the size of an Access data file.
Add indexes to frequently searched fields (refer to Microsoft's documentation for adding indexes to an Access or SQL Server database), or use Monsoon Order Manager 's Ctrl+Shift+i key combination to rebuild the standard indexes as the program is distributed. Always make a backup copy of the database before adding or re-building indexes.
If using a Shared or Local Stack, check the stack viewer (Ctrl_Shift+S key combination at the Main Menu) to make sure that records are not "stuck" there. Sometimes, a record can fail to be sent and the program will exceed the limit of retries, but the program will never remove the failed record from the queue. All other records behind it in the stack remain in the stack queue which continues to grow as new orders are processed, causing the program to slow-down. Manually delete the "stuck" record from the stack queue.
A common reason for this happening is the user has the system parameter, UseGenericStatusUpdates set to TRUE in the main system parameters rather than in the cart-based parameters. When set in the main parameters, UseGenericStatusUpdates=TRUE causes the program to create status update records for every shopping cart in the current data file, whether or not the shopping cart requires that setting to send status updates. Any status records going to shopping carts that do not require UseGenericStatusUpdates=TRUE will fail, clogging the stack. Review the Updating Order Status documentation for each shopping cart to determine if it requires UseGenericStatusUpdates=TRUE and if so, set it in the Program group of the cart-based parameters. Leave the UseGenericStatusUpdates parameter in the main parameters set to FALSE, unless there is only one shopping cart defined in the data file and it is one of the types that requires it to be set to TRUE.
Similarly, if the user has selected the Send Updates To the Order Status System box and they do not subscribe to that service, the stack will become clogged with records that cannot be delivered. This setting can be found on Page 1 of the Order Status System section of the Setup Wizard.
Likewise, if only one shopping cart is defined in the current data file, and it does not support receiving status events at all, make sure there are no Status Events that have the Notify Cart box selected. Verify the status events settings by going to Main Menu>Settings>System Functions>Status Events.
Stay current with Microsoft Service Packs and recommended hot-fixes for Access and the operating system, as well. Make sure that they are being applied as well as downloaded to your PCs.
Microsoft Windows 7 users should refer to the Knowledge Base article, Windows 7.
As a last resort, try un-installing the current version of Monsoon Order Manager and reinstalling it, if the user has retained the installer (Setup.exe) for the currently installed version of Monsoon Order Manager. Monsoon Commerce only provides the installer for the latest version of the program at the download gateway.
Note: Backup the Monsoon Order Manager data files, including email templates and custom reports, before un-installing and reinstalling the program. Make sure all custom reports, forms or queries are stored in the Custom Reports database. Use the key combination of Ctrl+Shift+C at the main menu to determine the location of files that are used by the program.
Created: 12/14/10
Revised: 8/11/15
Published: 08/19/15