9999 bar codes occur when there is a loss of communication the POS terminal and Punchh Proxy Service. A connection is established each time a bar code is printed. If the connection is not successful, 9999 bar codes are printed.
The most common 9999's are a result of the following conditions:
1. the proxy service is NOT running.
2. the port that proxy service (e.g. usually set to 8008) is running on is being blocked by firewall on the boh.
3. the proxy port is not set correctly in punchhinter.config file. E.g. it may be blank or is different than what punchh.exe (proxy service) is set to run on.
External firewall settings, will NOT cause 9999's.
Please check the following items:
1. Please make sure the Punchh Proxy service is actively running on the file server in the BOH. Restart if it is not running.
2. Verify the TCP Port Punchh proxy service is running on the BOH
a. Check the most recent proxy logs found in C:\program files\punchh\bin\logs. There will be an entry showing the Port number (e.g. 8008) that is being used
b. If the Punchh Proxy can NOT start on the port, it will log an error indicating that it has an issue
c. Check the port used by Punchh Proxy that is stored in the file: c:\program files\punchh\bin\config\Aloha.cfg
3. Verify the TCP Port used by the FOH applications. It should match what is used by the proxy found in item 2 above (e.g. 8008 is the most common setting)
a. The file names PunchhInter.config, which is located in the Aloha bin folder has a line that identifies the proxy port: i) <proxyport value="8008" />
4. Confirm that the following FQDN (Fully Qualified Domain Names) endpoints are properly whitelisted in the site's firewall/router:
TCP using port 443 to:
pos.punchh.com
isl.punchh.com
TCP using port 80 & 443
punchh.freshservers.net
5. Make sure the following directories and sub-directories are excluded from AntiVirus and real time scanning on the AlohaBOH Server:
c:\Program Files\Punchh\*
c:\Program Files (x86)\Punchh\*