We are receiving a Store Operations Business Rules - Timeout Expirederror whenever we do a transaction at the top of the hour (10:00, 11:00, etc.), credit card or cash. The error message shows SQL that Inserts INTO #Temp from TransactionEntry as well Insert Into #Temp2. Does anyone know what could be causing this error specifically at this time? Also if it is a app or database error?
Thank you for your help
Below is two screenshots of the error messages
*This post is locked for comments
Jeff,
RMS does not do anything like this out of the box. It is possible you may have some type of 3rd party plug-in that is causing this, though it is unlikely. If it is effecting multiple computers it is probably something significant happing on whichever computer is serving as the database computer. That is where i would begin. Something like an overly aggressive anti-virus (or similar) could potentially cause this.
I ran the fix mentioned where I prioritized the Named Pipes and TCPIP in the Client Network Utility. I had the clerks run a transaction at the top of the hour (after restarting the machine) and it did not time out.
However, later on there was a timeout that occurred and one machine even timed out when one clerk was trying to close out for the night. This caused significant issues with the report and numbers for the day.
I am going to try to get our vendor to check out and see if there is anything running on the machines at the top of the hour. Since it happens on all of our machines, it sounds to me like it is something scheduled per the domain or something pushed out by a server. Does RMS do anything like this?
Thank you for your help
Jeff,
Reindexing the database is almost always a good thing. It is very similar to defragmenting a hard drive for a computer. Not something that needs to be done every day, but something that can help if you are having problems.
Doing this from RMS Administrator is actually easier than doing it from a standard SQL Management client, so I'd say go for it, though you may want to run int by the DBA's to get their sign off.
If this does fix your problem, I have a feeling it will be a band-aid fix only and the problem will resurface. Something is causing the error every hour, which is too much of a coincidence.
The connection timeout is 60. We have 3 registers in two locations, they are dedicated machines with cash drawers. I'll check with the DB team for processes running. I did see in RMS that you can reindex the database from RMS Administrator. Would this improve performance or would it be better for the DB team to do the reindexing?
I'm not saying this is not a problem with how RMS is written, but it also looks like its being caused by a slow database. First off what is your connection timeout set to in RMS Administrator? Ensure its at least 60 and try again. How many registers do you have? Is your server a register or a dedicated machine? Is there any process that is happening every hour on your server? (Virus Scan, Database backup, automated reporting, etc)
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (