Error: No access rights in system or No Wiegand formats in system.

The user receives this error when trying to add a visitor while no access rights or Wiegand formats are set up in the system.

Solution: First add access rights to the system, then refresh the service. If this issue persists even after you add an access right and Wiegand format, , invoke the Load Values action.

Error: Visitor Type already exists.

The user receives this error when trying to create a new visitor type while there is already a row in the table with the same visitor type.

Solution: To configure the visitor type, edit the previously existing row as visitor type must be unique in this mapping.

Facility code out of range.

The user receives this error when they enter the facility code, which is not in the range with the Wiegand formats for the badges.

Solution: Provide a facility code that is in range with respect to the Wiegand format you are planning to use.

Access right and Wiegand format are not available in the drop-down list.

Even though the user has added at least one access right and one Wiegand format to the system, those options are not available in the drop-down list.

Solution: Right-click VisitorIntegrationService, navigate to Actions and Invoke action Load Values and then refresh the service once.

Visitor Subscribe Proxy Ext Failure:

The Visitor Subscribe Proxy Ext (under Points > SubscriptionPoint > Proxy Ext) is at Fault due to Publish Point should have a Non-Null Ord:

Solution: In the Publish Point property of the visitor proxy ext, set the value as the ord for the publish point in the Visitor Integration Service > Points.

The Visitor Subscribe Proxy Ext Points > Subscribe Point > Proxy Ext is at Fault due to Publish Point type should be a StringPoint:

Solution: In the Publish Point property of the visitor proxy ext, the ord should be pointing to a String Point. Change the ord to the publish point provided in the palette for visitorintegration.

The Visitor Subscribe Proxy Ext (under Points->SubscriptionPoint->Proxy Ext) is at Fault due to "Input to proxy extension is not JSON"

The Visitor Subscribe Proxy Ext under (Points > Subscribe Point > Proxy Ext) is at Fault due to Input to proxy extension is not JSON.

Solution: If you get this fault just after the initial setup of visitor integration or when you restart the station, don't worry about your setup. It is working fine. This is an extra validation. The fault goes away after one successful check in happens. If this is not your initial setup of visitor integration, check all the input slots for the Subscribe point. There should be one link mark from the MQTT subscribe point. Apart from that, if there are any link marks, then this error may occur.