web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics RMS (Archived)

Why are our RMS transactions posting so slowly?

(0) ShareShare
ReportReport
Posted on by 335

Hey friends,

I am having trouble figuring out why transactions are posting so slow after being tendered.

The Problem:

Whether a transaction is made with cash, student account, or credit card, the RMS POS will freeze for upwards of a minute after tendering the transaction. It doesn't happen all the time. Its random. It happens on both workstations.

The Setup:

2 workstations (registers), 1 Database workstation (Database Server). Workstations are running Windows 7 Pro x86 with latest version of RMS. DB workstation running Windows 7 pro x86 and SQL 2008 R2 x86. Printers are Obvios ORP-800 (Drivers by SEWOO?) and are connected  DB25/DB9 (cable 1) to DB9/USB (cable 2) to computer.  The drawer is a std cash drawer made by Obvios and receives its power from a DC 24V modular connection on the printer (Drivers by SEWOO).  Barcode Scanners are Obvios OBS 2200 and are connected directly to computers via USB.

I have checked:

Protocols used and their order (Shared Memory, Named Pipes, TCP/IP), all stations are statically addressed, Database option to “auto-close” is currently set to TRUE (I have also tried setting to FALSE and no change in the situation), antivirus software and malware is NOT the problem, and my Cisco Catalyst switch seems to be configured properly.  I have tried running both registers without the printers and drawers attached to no avail.  I had deleted the printers and drawers from the OPOS Setup, but I didn’t actually go to Device Manager and delete the drivers.  I made sure that all software was 32-bit.  Database Server has been restarted very recently.  The database is approximately 1.9GB out of a possible 2GB size.

What haven't I thought of?

Wayne

*This post is locked for comments

I have the same question (0)
  • TODD TARTALIA Profile Picture
    740 on at

    RMS only uses TCP and this is the only protocol that needs to be enabled on your SQL Server (unless you have another need for it).

    1. I would turn on a resource monitoring component on the database workstation to see if the processor, or the memory is being overtaxed for some reason. If so, you could have faulty memory or processor.

    2. I would also temporarily put in simple router and replace wire from database server to isolate this possibility. Routers and switches can cause all kinds of problems if faulty. (Are there more than these three computers on the network?)

    3. Your database size is worrisome.  Too close to the maximum, so could be causing problem.

  • Community Member Profile Picture
    on at

    Hi TechGuy,

    I got exactly the same problem since updated to SP4. I hope someone can come up with solution.

  • Suggested answer
    Community Member Profile Picture
    on at

    I'd look at your db size. What version of sql are you on?

  • Community Member Profile Picture
    on at

    if you are on SP4, please apply the hotfix for SP4. this fixes the slow sales issue at RMS POS.

  • Jeff @ Check Point Software Profile Picture
    13,382 on at

    Wayne,

    I suspect that when you created you database, you went by the defaults.  RMS by default adds to the database by percentage, 10% if you didn't change it.  So in your case, when the database needs to grow, it adds ~200MB.  When you get to 3GB, it will add 300GB at a time.

    So the SQL Server sees a transaction comming and needs to grow, it has to add 200MB before posting the sale.

    We always change the default to grow by 20MB becasuse its quickly done, even on slow machines.

     

    To the guy that installed SP4 and is slow, (sorry this stupid forum will not show all posts when replying) make sure that you are not running 2.0.0151 as it was as slow as hell.  It was also called SP4 before it was pulled from CustomerSource after about a week.

     

  • Clint Skog Profile Picture
    Microsoft Employee on at

    Hello,

    I would also recommend looking at the database size, it looks like it is getting close to its max.

  • jachterberg Profile Picture
    85 on at

    If that is the case ( when the database was created it was set to grow by 10%) then how do you fix it?

    Thanks

  • Community Member Profile Picture
    on at

    You can do it through SQL Server Management Studio Express or by SQL script.

    SQL Studio

    Right click on Database -> Properties->Files->Change the Autogrowth settings

  • jachterberg Profile Picture
    85 on at

    Thanks for the response. Do you know what the setting should be set at? They currently have it growing by 10% and it was 250 GB in size.

  • Community Member Profile Picture
    on at

    Are you referring to Store operation database or HQ database?

    For Store operation database

    You can set it up to increase by 20 mb as suggested by Jef. This is pretty much fine when

    there s a size limitation in database when you use the SQL Express editions. (SQL express 2005 - 4GB limit, SQL express 2008 - 10GB limit)

    For HQ,

    This is different, it need to be setup based on transaction volume and updates etc... 

    Typical environment, 10% is fine for HQ

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > 🔒一 Microsoft Dynamics RMS (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans