Error#-2147467259 dropped transactions

(0) Share

Report

Posted on by Chris Rayment

We have 14 stores and about 22 Microsoft RMS POS lanes.

A few of the POS computers are receiving this error on a very random basis. The error will occur at the end of a transaction and will "drop" the transaction from the journal viewer and the X-Report will show a discrepancy between the Total Sales and the Dept Sales. The Dept Sales will be higher by the amount of the transaction that "dropped". This then causes the Over/short to be wrong as well as our perpetual inventory which is extremely annoying and time consuming to fix.

Error#-2147467259 (DBNETLIB)(ConnectionOpenConnect()) General Network Errro. Check your network documentation. Select GetDate()AS Current DateTime.

This was occuring at two of our stores with one back office computer acting as the server and one RMS POS lane. We moved the database from the back office computer to the POS and it fixed the problem. This made us think its a server or network problem until I had this problem happen in a two lane environment and only affect one lane.

I now have another store with two RMS lanes and it is now getting this error on only one lane and not the other. The back computer is a HP RP5700 with RAID1 and Windows XP Pro SP3. The registers are different. One is a HP R5700 with RAID1 and Windows XP Pro SP3, and the second register is an HP RP5700 with Windows 7 Pro 32.

The register that is getting the above error is the HP RP5700 Windows XP Pro SP3 station. The register running Windows 7 Pro 32 is NOT getting this error.

When we had this occur on the one lane environment at two other stores, I sent everything to Microsoft and they concluded that it must be a hardward related problem. I have since quit trying to solve the problem because putting the database locally on the one lane environment fixed the problem.

I can't do the same thing in a two lane environment so I need to fix this problem.

I have followed every KB article on troubleshooting general network errors as well as setting up SQL Aliases and all required SQL settings for RMS.

It is interesting to note that on this current problem register, if I set an SQL alias using the IP address of the server, then the POS will not connect to the database and it will open in Offline mode. If I set the SQL alias using the server computer name, then the POS opens just fine. Not sure if this has any correlation to the problem or not.

I would appreciate anyone's insight or help on this.

Thanks

*This post is locked for comments

All responses (12)

Answers (0)

raelhefn on at

Like (0)

Report

RE: Error#-2147467259 dropped transactions

This issue causes

1- Network connectivity issue. try to check response between devices measure it in rush hours also synchronization timing between lanes.

2- Check another applications in your POS accessing RAM ( or increase your PC's RAM Size)

3- Printers issue if you are using incompatible drivers with your windows version

4- database log size (shrink it in case of huge size)
LanceM on at

Like (0)

Report

RE: Error#-2147467259 dropped transactions

Thank you Chris.

I was ultimately able to reduce the frequency of crashing by about 95%. My 2 registers still occasionally crash (about twice per month) but it's manageable and almost never happens during a transaction. What fixed it was replacing one of the pc's, which had been running XP, with a new machine running Windows 7. Apparently the old machine was causing interruptions to the SQL Server that was even affecting the other machine. What is strange is that there were no other symptoms or crashing with other piece of RMS besides the POS.
Chris Rayment on at

Like (0)

Report

RE: Error#-2147467259 dropped transactions

Our dropped transactions have cleared up. We have changed our environment and honestly since it was a random problem I don't know what fixed the problem. I'll explain our current hardware and software setup.

We previously had HPrp5700 computers with WinXP Pro and RAID1 hard drives and now we have HP computers with Win7Pro and NO RAID1 hard drives. Microsoft tech support suggested the RAID1 setup could be causing the problem but we had RAID1 on all computers and some were fine whIle others were not.

We are now running SQL Express 2008 R2.

We are upgraded to RMS Cumulative update 5 (CU5).

We have USB scanners, no pole displays, using Net display, Magtek IPad SC.

Let me know if you have addition questions.

Thanks
LanceM on at

Like (0)

Report

RE: Error#-2147467259 dropped transactions

Hi Chris,

Were you ever able to resolve the problem? I've experienced the same thing at 1 of my 3 locations for a long time and have tried every suggested solution to no avail. If you discovered a solution I'd great appreciate hearing it. Thanks!
tahir on at

Like (0)

Report

RE: Error#-2147467259 dropped transactions

Check your hold transactions if there are nay hold transactions cancel them and check your scanner settings.
Community Member Microsoft Employee on at

Like (0)

Report

Re: Error#-2147467259 dropped transactions

I seen same error when Ii chnaged my main server xp to 7 . You should log in to mssqltips.com. You can find lots of sql tips.

Pls see below sql tips

www.mssqltips.com/.../configuring-sql-server-to-use-multiple-ports
Community Member Microsoft Employee on at

Like (0)

Report

Re: Error#-2147467259 dropped transactions

Well Chris, I know this problem and i had faced it for years and I see that you described it very well, I have some recommendations that I tried myself in a 40 store environment with heavy transactions load and with a considerable number of 'incomplete' transactions every month, my recommendations below decreased the monthly average of incomplete transactions by 90% and it became very rare, so give it a try on one database and see

install the latest SQL SP

on the sql server engine level, go to properties|advanced|query timeout, make it '1' instead of' '-1'

on the database level, make sure that "auto shrink" is false

on the database level, make sure that the recovery model is simple

create a clustered index on Item.ID field

create a clustered index on Transaction.TransactionNumber

create a clustered index on TransactionEntry.TransactionNumber

create a non-clustered index on TransactionEntry.ItemID
Chris Rayment on at

Like (0)

Report

Re: Error#-2147467259 dropped transactions

No, not at all. The error just shuts down POS and we have to reopen it without any problem.
Community Member Microsoft Employee on at

Like (0)

Report

Re: Error#-2147467259 dropped transactions

Oh, and any chance you've had any corresponding BSOD's?
Community Member Microsoft Employee on at

Like (0)

Report

Re: Error#-2147467259 dropped transactions

Here's another thought that someone suggested a couple of years ago. Dells running serial add-in cards have also displayed some significantly quirky behavior along the same lines.