Receipt Not posting to the Journal

I have had this problem in the past and for me it was caused by a timeout error. It happened very infrequently. There is no receipt and you will probably find that the items from that transaction have not been removed from inventory. The database transactions never complete.

The fix was to put the SQL protocols in the proper order. I do not remember the proper order off the top of my head, but if you search this group you will find at least one thread on the topic with instructions on ordering the protocols.

Marc

I've tried all the post and I have never completely eliminated it. The order was TCP/IP first and Named pipes second and add the alias of the server. If someone ever finds the solution post it as I would like to eliminate this accounting night mare. It may subtract from inventory and not post to the journal or not post ot the tender total. I have my operators using the Task manger to close the Store POS and then restart the program. You may want to try to reindex the DB frequently

Paul

"Marc" wrote:

Good point. I always rebooted the server to clear the problem, but fortunately the protocol fix did work for us.

Marc

Thanks for the Info, where can I find the SQL protocols?

There should be a server configuration manager utility that you can probably find on the start menu under your server software, MSDE or SQL Server 2005. You need to be a the PC that is running the server software.

Marc

Thanks for all your help, I will keep everyone updated

Just recently one of my stores has encountered an error after tendering a sale. The POS station froze at printing receipts, when they get back in, there is no receipt in the journal (Therefore the customer cannot get a receipt). If it is a charge the transaction shows in the EDC batch or if I run certain management reports it shows with a transaction number but I cannot access the receipt.

Does anyone know what may be causing this problem, it is completely random and has no rhyme or reason.

Thanks in Advance.

Scott

I have had two clients experiencing this issue in the past month. One of them I was able to fix by using static IP addresses. The other one still happens, but only around 9:30 AM every day.

I have pored over their servers for any processes that run around this time but haven't found anything. Does anybody have any idea why this may be happening? I have also tried the protocol trick at every register.

Thanks,

Alex Nielsen Retail Evolved