Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Micros 3700 CC Auth says * SYSTEM ERROR

Status
Not open for further replies.

Airstram2

Vendor
Aug 21, 2018
1
US
Hello, today when coming into work all of our pos systems say * SYSTEM ERROR on tab close out/ aka when we attempt to run the credit card to auth it.

We have called WorldPay everything is said to be good on their end. We have done nothing different, changed nothing, no apparent updates we have seen, etc.

I cannot find anything on this * SYSTEM ERROR in any guides/support sites. We also do not have support thank you. Would save us potentially thousands if you could help, thanks.
 
for the vast majority of customers who have had this error, it's been due to lack of PCI compliance. are you running credit cards directly through the workstations? if so, what is the version number of your credit card drivers? you can check this in credit card batch -> diagnostic.
 
If there is a missmatch with PCI Compliance Error, in the 3700d.log you will find the settings which are incorrect.
MICROS\RES\POS\ETC\3700d.log
 
Yes sorry, old username would not work. It was a brownout by our credit card company, yet first 3 calls they said everything was fine. We had to escalate it the 4th time. They sent no emails, letters, nothing just blacked out our card from being used. Super Shady by World Pay. Thanks for the responses.
 
Hey new to this forum however I’ve encountered the same issue. Luckily we have a stand-alone credit card machine as a backup but the “* system error” has been occurring on and off. More often than not lately.

I’ve been told it’s possibly because of still running Windows XP however I have colleagues tell me they have much older systems that are still working fine. Sometimes it stops on weekends and holidays which could be a coincidence or maybe not.

We have no service plan with Mircos/Oracle and are a small family business on a budget.

Any tips, solutions, and help is welcome.

Thanks!

Jason
jason@striketenlanes.com
 
If you are with merchant link, they are doing rolling blackouts. Windows XP is no longer PCI Compliant (this is NOT a micros 3700 thing) and windows XP does NOT support TLS 1.2. If you aren't on TLS 1.2 the rolling blackout will affect you. It is possible other processors / gateways have not started blocking non-compliant stores yet.
 
Thanks so much for the response!

So my next steps I need to figure out are:

-Recover my password because we are not sure what are Micros Log In Password is. I know I once ran dbisql to remove enhanced security to get some reports, but wasn't sure how to reset my password from there.

-Upgrade our server from Windows XP to... What would be the best one to upgrade for us to become compliant but still be compatible with our hardware.

I wish I was more tech savvy, but if anyones able to help, you can also reach me at jason@striketenlanes.com or by phone 630-307-8100. Thanks in advance!



 
Well, honestly, you are going to want to go all the way to Windows 10. Windows 7 is reaching end of life January of 2020 - it would be really painful to upgrade to windows 7 only to need to upgrade by the next year.

Windows 10 has very low spec requirements so will probably run fine on your machine; what you're really going to need to think about is your RES system. What version of RES are you running? If you're running RES 4.11+ it probably won't be that hard to upgrade, but if you are running RES 3, or something like RES 4.1, the upgrade process can be quite rough.

You could also consider implementing an EMV solution of some kind, whether through Merchant Link (their OPI/OGDH system is very clunky.. wouldn't recommend) or a third party that integrates with micros 3700. That would take your point of sale out of scope and remove the need to upgrade (it can still be a good idea, but you at least wouldn't be required to do it for credit cards). Your issue likely boils down to the fact that they are doing rolling brown outs for TLS 1.2 (your intermittent issues point to this) and Windows XP doesn't support TLS 1.2 natively.

There are multiple ways to skin this cat.
 
Implementing an integrated EMV chip card solution that removes the old Micros RES 3700 POS system from the scope of PCI DSS compliance is the best bet for anyone that doesn't want to start over with a new POS system. You can checkout for such a solution. Hope this helps.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top