POS Error after configured Customer pole display Invalid URI: The hostname could not be parsed

POS Error after configured Customer pole display Invalid URI: The hostname could not be parsed

Problem Statement

After configured the customer pole display in POS system an below error displayed “Invalid URI: The hostname could not be parsed”

Environment

 iVend 6.6 integrated with SAPB1

Symptoms

 NA

Resolution/Work Around

This issue generally occurs due to wrong class name in hardware registration pole display configuration so suggest to delete the hardware registration for Pole Display and select "OPOS pole display" from class name drop down. Please find attached screenshot for reference

Recommendations /Suggestion

​NA


    • Related Articles

    • iVend POS Customer Facing Display

      Introduction With the option of the Customer Facing Display in iVend, retailers can now exercise the option to be more transparent with processing of a POS transaction to the customer. With dual displays, the customer will be able to see the items ...

    • Remove Customer Master which has transaction and also remove those customer which has no transaction

      Environment:   Ivend 6.6 Problem statement: Need to Remove Customer Master which has transaction and also need to remove those customers which has no transaction details. Resolution/Work Around: 1. Remove customer master which has no transaction ...

    • Scan Sequence Resolution

      iVend POS – Barcode Scan Sequence Resolution Order The user at the POS scans either the barcode of the product when it is being transacted or swipes the loyalty card for the customer or the security user card. The system follows a sequence of methods ...

    • To customize the "Customer Display" screen

      Version 6.5 Update 6 and not the version-specific Query The customer wants to customize the "Customer Display" screen. Below is the screenshot for the same: Response The customer may check the "Customer Display" feature, which is a licenses ...

    • Integration Error "invalid BP Code"

      Problem Statement Integration Records are stuck in Integration Failure Monitor with the error message "invalid BP Code" and "This entry already exists in the following tables" Resolution/Work Around If this error is reported in the older versions of ...