error 2147467259

Gill

Is this happen> I received error 2147467259 The system could not post the transation and I

It happening on 2nd station and once in while. I am running RMS 2.0 with SQL

error 2147467259 The system could not post the trasation on debit card on second register. I receive this arrie once in while. When I look on EDC I can see charged amount But I can not print receipt for customer and I can see under item data The item was sold. I am running RMS 2.0 with SQL 2000 standard addtion because my data is over 5gb. and Oprating system is XP SP3 I need step by step help to fix this problem I already put NAME PIPE on top on Client network utility and no help.

Hi Gill,

Do you have your SO comps running on a domain? If so, you need to add your Domain Admin account to the Admin group on each comp running SO POS. After this, you can only log on to the comps under the domain, not the local comp.

Hi Gill, This has been a headache for a long time and I'm not sure that anyone has definitively come up with a solution. If you search the forum for "2147467259" you will find a lot of discussion on the subject but no real answer.

Good luck and PLEASE post if you find a solution to this one :)

Thanks,

"Gill" wrote:

I think it fixed on version (2.0.0123). try to apply this hotfix

This hotfix is applied to RMS sp2, if you are not planned to update your database to this step DO NOT APPLY THE HOTFIX.

Here is another example of this proble. During regular store operations we get the following message: Store Operations Business Rule Error#2147467259 (DBNetLib)(Conenction Open) SQL Server does not exist or access denied. (Source Microsoft) OLE DB Provider for SQL Server Seelct GetDate() as current date time We then push cancel

Invalid Procedure Call or Argument Push Cancel Screen goes to black. Restarted POS.

The custoemr is charged. The receipt is not stored. Our product sales totals are correct on the X-report. However the Total Sales amount on the X-report are off by this transaction amount.

I've seen a lot of discussion on this topic, but no final resolution. Has anyone identified the hot fix or IP settingsZ? We've adjusted the Surface config to Named Pipes followed by TCP/IP.

Thanks.

"Gill" wrote:

It is in your network. I had this prblem before I and I do not have anymore. I have made few changes and I upgraded to RMS 2.0 SP1 I asked that question to MS on January 2009 chat and answers are still there. It may help you here is link

Has anyone documented that any of the fixes suggested in the whitepaper have helped with this issue? Specifically I'm curious about the configuration of the TCP/IP and Named Pipes and Alias in the client network utility.

BK

"Gill" wrote:

Hi Gill, I can tell you what worked for us after almost 2 years of headaches. First, I'll tell you that we were running Dell Optiplex systems that we had shipped with serial add-in cards to run our PINpads. Recently, after running for 2 years, one of our stores started having this issue. After a month of troubleshooting were were able to isolate the problem. When we removed the serial add-in cards the issue completely disappeared. I did convert the devices to a serial/usb adapter that we plugged our pole displays into without any negative side effects. No guarantee that this will resolve your issue as I have no idea what your hardware setup is, but that's what worked for us.

Thanks,

"Gill" wrote: