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 Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Recent content by JimFromCanada

  1. JimFromCanada

    Any one Have sample code to send & reserved data from ISL

    The ISL manual comes with a sample SIM server. It's TCP communications with a very simple packet structure. One doesn't usually send to SIM without first receiving a request from one of the terminals--unless the terminal is sitting in the "RxMessage" state, it won't actually do anything. If you...
  2. JimFromCanada

    micros 3700 isl - tcp interface issue with multiple workstations

    It sounds like your SIM server is potentially single-threaded and will only do one thing at one time. The alternative is that you're hitting the built-in nature of SIM on a workstation which is very much blocking in nature. While a SIM is running / doing anything, nothing else will be running /...
  3. JimFromCanada

    RE: MICROS RES 3700: IFS error

    @pradeepckmeta: did you manage to resolve the issue? I'm curious what the source of your issues may have been and if it is different from the ones I encountered.
  4. JimFromCanada

    RE: MICROS RES 3700: IFS error

    It's typically just a "passthrough". It will only contain the workstation ID and interface name iirc, and you can just respond with the same properties on your response, or, depending on your implementation, just send the request right back as the response. Edit: It might actually just be the...
  5. JimFromCanada

    RE: MICROS RES 3700: IFS error

    I stand corrected: I thought it was mandatory to respond to the PING requests (ACK) but apparently the sample code in the documentation just ignores them outright--the sample code (written in C) in the documentation explicitly ignores the ACK/NACK requests. Huh. I log these and respond to them...
  6. JimFromCanada

    RE: MICROS RES 3700: IFS error

    When defining the interface there is an option for a timeout, but that timeout determines how long the POS should wait for a SIM server to respond to a message. If your timeout is set to 30 seconds in the POS Configurator then it points towards your server not communicating (outright). The...
  7. JimFromCanada

    RE: MICROS RES 3700: IFS error

    Regarding these two previous posts from June 2024 and July 2024 (I can't post a follow-up within those topics, likely due to age): The culprit was seemingly a 'ghost' node which did not exist but was somehow in the database acting as a backup server. The reason why the IFS errors were so...
  8. JimFromCanada

    MICROS RES 3700: IFS error status -21 / IFS_ADAPTER_ERROR

    As a follow-up, this specific pattern is observed: When the IFS service is restarted, the IFS server will immediately connect to the configured interfaces. The IFS service maintains a connection on its own and sends pings every 5 minutes. The workstations also connect to the SIM server when...
  9. JimFromCanada

    MICROS RES 3700: IFS error status -21 / IFS_ADAPTER_ERROR

    This issue mysteriously resolved itself. The resolution may have been a combination of checking the network gear / cables / firewalls / etc. The very odd thing was that _some_ connections were being sustained while others would die but there was no pattern to it--it could fail on any and all of...
  10. JimFromCanada

    MICROS RES 3700: IFS error status -21 / IFS_ADAPTER_ERROR

    For posterity, the error codes line up with the index of the string in MDSIFSProxy.cpp 01: IFS_INVALID_CONFIG 02: IFS_SERVER_NAME_SIZE_ERROR 03: IFS_INTERFACE_NAME_SIZE_ERROR 04: IFS_NO_TX_DATA 05: IFS_DATA_SIZE_ERROR 06: IFS_BIND_ERROR 07: IFS_ID_SIZE_ERROR 08: IFS_NOT_REGISTERED 09...
  11. JimFromCanada

    MICROS RES 3700: IFS error status -21 / IFS_ADAPTER_ERROR

    This is related (but not identical) to a previous post about IFS error -20 (timeout). The IFS timeout in the link above was resolved by turning off the "Log Transactions" option. The same system (5.7.8) now hits an IFS_ADAPTER_ERROR instead. This error will appear roughly 10 seconds after a...
  12. JimFromCanada

    MICROS RES 3700: IFS error status -20 / IFS_RECEIVE_TIMEOUT / IFS_PROXY_ERROR / 0xc70700d7

    I found a potential source of the problem. The server was quite sluggish and while attempting to inspect the 3700d.log file it became obvious that the logs for our interface were rather large (4GB). I did not get a chance to look at the log retention settings but we usually do not configure "Log...
  13. JimFromCanada

    MICROS RES 3700: IFS error status -20 / IFS_RECEIVE_TIMEOUT / IFS_PROXY_ERROR / 0xc70700d7

    Update: it appears as though this can also happen mid-flight. We originally thought it was only a "while the system is idle even if only for a few seconds" issue. This was an incorrect assumption. Our SIM message processor (in our system) received a message, processed it, and then as it was...
  14. JimFromCanada

    MICROS RES 3700: IFS error status -20 / IFS_RECEIVE_TIMEOUT / IFS_PROXY_ERROR / 0xc70700d7

    These errors will appear in OPS when a SIM event is fired. The BOH was replaced quite recently and the configurator seems to keep reverting some settings for the IP addresses. At one point, using hostnames for the interfaces seemed to work for a few days but it just stopped working again. The...
  15. JimFromCanada

    RES 3700 - Merchant receipt to print only tender details (not itemized receipt) for any tender

    Is there a way to have the customer receipts be printed as normal but have the merchant receipt be printed with only the tender information? I.e.: almost like a CC voucher style, but for any tender. The main requirement is to ensure every payment is printed out in a voucher-style receipt for...

Part and Inventory Search

Back
Top