Huge credit card error.

I have seen that problem along with other points during the transaction where the process doesn't complete: doesn't write tender entry or jornal entry to the database or print the receipt. At any point previous to this when the program locks, you just close pos and try again, but freezing at the end of the transaction makes a mess.

Jeff from Check Po> Has anyone ever experianced this problem? Right after i swiped the credit

I experienced the same, Freezing after credit card transaction, what I found very useful to do is to rebuild the index file at leaset once a week as part of weekly maintenace and the problem stops.

__________ Information from ESET Smart Security, version of virus signature database 4717 (20091226) __________

The message was checked by ESET Smart Security.

Subject: Re: Receipt Not posting to the Journal 9/11/2009 12:46 PM PST By: Jeff @ Check Point Software In: microsoft.public.pos Follow these instructions on all RMS Server and Register machines (machines you install SQL on)

Start | Programs | SQL Server 2005 | Configuration Tools | double click on SQL Native Client Configuration on the left | double click Client Protocols | make sure that Named Pipes is enabled | right click on Named Pipes and select Order | change so the order is 2 if Shared Memory is #1, TCP/IP should be #3 | close

Start | Programs | SQL Server 2005 | Configuration Tools | SQL Surface Area Configuration | Surface Area Configuration for Services and Connections | select Remote Connections on the left | make sure that Local & Remote connections and Using both TCP/IP and Named Pipes is selected | close this screen Select Surface Area Configuration for Features | select Enable OPENROWSET and ... | close entirely

Turn off Auto_Close for SQL 2005/2008 Express

For all machines with RMS installed;

"paulo" wrote:

database 4717 (20091226) __________

here is the rest:

If 1.3R or 2.0 and using SQL 2005,

Start | Programs | SQL Server 2005 | Configuration Tools | double click on SQL Native Client Configuration on the left | double click Client Protocols | make sure that Named Pipes is enabled | right click on Named Pipes and select Order | change so the order is 2 if Shared Memory is #1, TCP/IP should be #3 | close

Start | Programs | SQL Server 2005 | Configuration Tools | SQL Surface Area Configuration | Surface Area Configuration for Services and Connections | select Remote Connections on the left | make sure that Local & Remote connections and Using both TCP/IP and Named Pipes is selected | close this screen Select Surface Area Configuration for Features | select Enable OPENROWSET and ... | close entirely

For all machines with RMS installed;

Start | Programs | Microsoft Dynamics RMS or Retail Management System | Client Network Utility | move TCP/IP and Named Pipes to the right hand box, making sure that Named Pipes is on top | select the Alias tab | Add button | put either the computer name of the database server machine or the IP address of the server machine | close (The database server machine should always have a static IP address, that's another post)

Restart Windows

"Matt Hurst" wrote:

database 4717 (20091226) __________