All geek questions in one place

MICROS 3700 ResPosApiWeb API Client Configuration Record

We are working on integration with the Micros POS 3700 (version 4.8).

When we send any request to its web interface, we received the following error: The server could not process the request. → The type initializer for "ResPosApiWeb.ResPosApiWebService" threw an exception. → Failed to find API client configuration entry.

We did everything according to the official documentation - created a class of employees and employees, registered a new node device, device and workstation. The control panel displays our node and is indicated in green.

We spent a lot of time trying to figure out what was wrong, and we tried many ways to fix it, but nothing worked. There is no information about this error in the documentation, and we could not find anything on the Internet. Any help would be greatly appreciated.

+4
source share
4 answers

Just decided ...........

After following the setup instructions, follow these steps.

Add a new device as DiskFile with the same Node network.

Set this as a printer in UserWorkstations in the following printers

  • Customer receipt printer

  • Customer Validation Printer

  • CA Voucher Printer

  • Printer Log

+2
source

Another point to consider is to ensure that the 3700 system is in DEMO mode (or properly licensed) - this feature requires proper licensing, and the web service will not be able to respond if it is not properly licensed. The 3700d magazine shows the following ...

* ERROR * 3700 POS system is not properly licensed. | Fri Oct 12, 3:13:25 PM 2012 | SERVER | POSAPI | 0 | Failed to create or initialize ResDbs interface, HRESULT = c701045f |

Fri Oct 12 15:13:25 2012 | SERVER | POSAPI | 0 | [0xC701045F] Could not find API client configuration entry. |

Assuming you are NOT working on a production system and you want to put the system in DEMO mode, follow these steps:

Start → Programs → Firmware Applications → Utilities → License Manager

Make sure the [] Demo checkbox is selected. (also each section can be included separately in the demo mode if you are developing a system in real time (not recommended))

Hope this helps

0
source

I just solved this problem differently ... I tried all of the above solutions without success, but eventually fixed it by replacing ResPosApiWeb.asmx with a copy from the working environment. I have no idea how this went wrong, but the one who was 8 years old.

0
source

For me it was a stuck check. A stuck check 5 days before RESDBS did not know how to handle it, and when POSAPI requested a check update, it generated an SQL error. Spent 3 hours double checking IIS, configurator and random files for a crazy stuck check.

0
source

Source: https://habr.com/ru/post/1398960/

More articles:


All Articles