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

Community site session details

Session Id :
Microsoft Dynamics RMS (Archived)

Transaction posting slowly

(0) ShareShare
ReportReport
Posted on by 130

Hi all,

I've been dealing with this problem for quite sometime, but as of late it is getting absolutely ridiculous.

When a cashier goes to ring a sale up and gets to the tender screen. The screen either lags or hangs. Sometimes, it'll post the sale after a minute sometimes it can be a total of five minutes before the transaction posts and kicks out a receipt. I have two register setup, but if one register lags, it kills the other register too, which leads me to believe that the problem is with DB server.

I've tried replicating the problem, but to no avail. It happens at odd times throughout the day with no rhyme or reason.

I've reindexed and checked the DB. I've read Jeff@Checkpoint's guide to properly setup the DB (SQL Express 2008 R2). I've turned off all 3rd party apps. Nothing seems to work and I'm at a loss why.

I'm running RMS SO and HQ v 2.0.1006. . The POS registers are running WIN 7 Pro. DB Server is running SBS 2003 with SQL Express 2008 R2. The SO DB is approximately 2.4GB.

I've searched the forum and I see others had similar problems, but I have yet to find a post where it seems to be definitively answered. Any guidance would be appreciated.

Thanks!

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    on at
    RE: Transaction posting slowly

    Can you make sure that the database option "Auto Shrink" is not enabled?

    A Hassan

    RMS Leaders

  • Erin Holmes Profile Picture
    130 on at
    RE: Transaction posting slowly

    Yes, Autoshrink is set to False. Still no luck.

  • Spencer McCandless Profile Picture
    2,087 on at
    RE: Transaction posting slowly

    It's not really a solution, but I've got a similar issue that is cleared up (temporarily) by stopping and restarting the MSSQL service on the database machine.  In our case, it happens rarely enough that I've never gotten around to working out a better fix.

    I'd also wouldn't rule out it being network related. Does other traffic flow without issue when this occurs?

  • Erin Holmes Profile Picture
    130 on at
    RE: Transaction posting slowly

    I've actually tried that and it does help, but it's not something I want store staff to be doing with the DB server.

    Other traffic flows fine so I believe I've isolated the problem to the DB server.

    I've ordered an additional 4GB of RAM to see if it relieves the problem.

  • Jeff @ Check Point Software Profile Picture
    13,382 on at
    RE: Transaction posting slowly

    We recommend re-starting 32b machines daily and 64b weekly.

    One can easily set it up in Task Scheduler, add a command of Shutdown.exe -r -t -1 and set it to run early morning, say 5-6AM. That command reboots in less than 1 minute. Make sure all work is saved!!!

    How much RAM is in there now?  How many Services are you using of SBS? What are the machine's specs.

    To be honest, MS recommends that one use a separate Server for SQL, especially if using lots of SBS services. Also remember that SQL Express can only use up to 1g or RAM.

    Are you positive that when you created your database that you selected to grow by xx meg instead of the default 10%? In your case that would be ~240 meg which could take a while to create, especially on slower/very active machines.

    Here is a link to a very good article about SQL AutoGrowth and how to see, change, monitor its growth patterns; www.simple-talk.com/.../sql-server-database-growth-and-autogrowth-settings.

  • Jeff @ Check Point Software Profile Picture
    13,382 on at
    RE: Transaction posting slowly

    I forgot to add the key point of the article noted;

    When SQL Server performs an auto-grow event, the transaction that triggered the auto-grow event will have to wait until the auto-grow event completes before the transaction can finish. These auto-growth events cause your performance to degrade a little when an auto-grow event is taking place. For this reason it is best if you can size your database appropriately so auto-growth events rarely occur.

  • Nicole Hellerud Profile Picture
    1,712 on at
    RE: Transaction posting slowly

    Erin,

    Thank you for your post.

    I have the following suggestions to help improve the performance.

    1. Verify that port 1433 is enabled as inbound and outbound exceptions. 1433 is the default SQL port, if you have changed the SQL port then uses that port number instead of 1433.

    2. I have send issue with hardware drivers cause performance problems. Do you have the POS in use on the server computer? If so, you could try to disable the hardware and see whether the issue occurs.

    3. Enabled Named Pipes and TCP/IP on the Client Network Utility.

    4. Enabled Named Pipes, TCP/IP and Shared Memory protocols on the SQL Server.

    I hope these help point you in the right direction or solve the issue for you.

    Thanks,

    Nicole

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics RMS (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans