I recently upgraded all of our hardware and software for our bookstore retail database and registers and now a strange issue has surfaced. Most of the time, but not ALL the time, when a cash transaction is tendered, the POS register freezes. Sometimes it freezes for a couple of minutes and sometimes for much longer. I cant find any answers in the forum. Here is some further info:
All machines (database machine and registers) are running Win7 pro sp1.
All machines have static IP addresses
We are using Dynamics RMS 2.0 and SQL Server 2008 R2
On database machine, the protocols are set to the following order: 1. shared memory, 2. named pipes, 3. TCP/IP
On registers, Client Network Utility is configured such that named pipes and TCP/IP are both enabled and in that specific order.
On registers, Client Network Utility is configured such that an alias is created with an alias name, TCP/IP as the network library, and the ip address of the database machine using port 1433. Port 1433 is the port that the database machine is listening on.
There are no Antivirus or firewall obstacles causing this issue.
If anyone could offer some help, I would GREATLY appreciate it :)
I am having same issues. Did you happen to figure it out?
Do you have any 3rd party add-ins that may not be compatible with your recently upgraded system?
What type of peripherals do you have connected to this system?
Have you tried disconnecting them all and processing a test transaction?
If running OPOS for your reciepts printer, Manager | File | Configure | Options | POS Options | Check/uncheck Share OPOS printer... | exit POS and try again.
update your OPOS driver from the printer supplier
get rid of the OPOS driver situation entirely and use Windows drivers
Jeff HobbsCheck Point Software
Not sure if this was ever resolved or not, but have you tried re-indexing the database?
Ryan Sakry Program Manager firstname.lastname@example.org http://www.rite.us 320-230-2282 (Office) 320-230-1796 (Fax)
Check out our FREE iPhone / Android app for Microsoft RMS / POS 2009 - www.cloudretailer.com
Had the same issue,
I popped in more memory in the SQL Server box, and problem disappeared instantly, I recommend atleast 2GB
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13