Troubleshooting

You receive an error: You have not set up any access rights or Wiegand formats in the system and you are trying to add a visitor type. No access rights in system or No Wiegand formats in 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.

You receive an error: If you try to create a new visitor type and there is already a row in the table with the same visitor type, then he gets the error message: "Visitor Type Already exists!".

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

You receive an error: If you enter the facility code that is not in the range with the Wiegand format for the badges then he gets the error message “Facility code out of range”.

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

Although you added at least one access right and one Wiegand format, they are not visible in the drop-down lists.

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

Check-in fails.

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.

In Visitor Integration Service > Points > Subscribe Point > Visitor Proxy Ext Publish Point type should be a String Point.

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.

In Visitor Integration Service > Points > Subscribe Point > Visitor Proxy Ext Input to proxy extension is not a 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.