Customer Support: (510) 898-2269
Tech Support: (877) 836-8988
International Support: +(39) 3467320800
- Verify that correct URL has been entered.
- Check that SNAPS IP address and DNS name are valid.
- Ping the SNAPS server.
- Check that browser is online (supported browser).
- If SNAPS splash screen displays, but you are unable to log onto SNAPS, have the SNAPS administrator validate your SNAPS login ID and password.
- Check for missing information (required fields not completed).
- Check for duplicate labels.
- Check that only allowable characters are used.
- Check that AP/APCC naming conventions are followed. (SNAPS 2.6.1 validates names automatically)
- Confirm that user account has sufficient rights.
If you can successfully ping the AP from the SNAPS console, check the AP entries in SNAPS.
Check the AP configuration entries in SNAPS
- IP address or DNS name
- HTTP port
- TCP port
- VPN name and password
- If the AP configuration entries in SNAPS are correct, verify that all of the necessary ports are open on the firewall.
If you cannot successfully ping the AP from SNAPS, try to ping the router from SNAPS console.
If you cannot successfully ping the router from SNAPS console, contact your IT department for further assistance.
If you can successfully ping the router from SNAPS console, get someone to go onsite and have them ping their local router from APCC.
- If you cannot ping local router from APCC, contact IT department.
- If a cellular modem is used, confirm that equipment and service has been activated.
Verify VPN configuration on SNAPS and TrafficDOT.
- If the VPN user name and password match those on the AP, check the AP modem page.
Verify that the NTPD service is running.
Check the IP address(es) or host name(s) of the NTP servers designated on the systems configuration network tab in TrafficDOT.
- If the information is not correct, make correct entries and then restart the AP.
- If the information is correct, ping the NTP server from the AP.
- If you are unable to successfully ping the NTP server, contact your IT department for assistance.
Check if NTP ports are blocked (firewall).
- If the NTP ports are blocked, have your IT department unblock them.
- If the NTP ports are not blocked, contact Sensys Networks for assistance.
The NTPD service is not running.
- Start NTPD service or ask your IT department to do so.
- After NTPD service is started, check the date on the AP.
- If the date on the AP is still not set, contact Sensys Networks.
- Verify that none of the AP/APCC logging Statuses are red. Check connection and configuration.
- Verify that there is data for date which the report is being run.
Confirm that none of the AP/APCC processes are red.
- Receiving Data?
- DotTable in sync?
- Verify that AP/APCC's current sensor positions are synchronized in DotTable.
- Verify that AP/APCC's IP configuration is correct.
- Verify that multiple AP/APCC's are not assigned to the same IP address.
- Verify that report is running for intended AP/APCC's.
- Verify that the Dot tables contain accurate and relevant sensor information.
- If any configuration changes are made, reboot the AP/APCC (to immediately resynchronize AP with SNAPS server).
- Verify that you are using a supported browser.
- Verify that you have selected Plots as the display format.
- Verify that recipient is a valid user..
- Verify that the SNAPS user configuration is using valid email address.
- Verify that report was run and not just saved.
- If report was sent as a scheduled report, verify that delivery date and time have passed and that SNAPS server reflects the proper date and time.
- Verify that email account/server for the SNAPS have been set up. (Check with Sensys Networks.)
- Verify that your email server is up and running. (Check with IT department.)