Below are common issues customers run across with haystack connection. We recommend you take a look at the following issues and see if any of them resolve your issue. If you happen to see a different error/issue, go to our Haystack Debug doc and see what error you get when debugging it.

Issue 1: Get 500: Internal Server Error (N3.8)

...

If you are trying to connect to a N4.3 station via FIN Stack. Go here and look at the Custom Haystack Pod part: Haystack Compatibility#Custom-Haystack-Pod---N4.3+-with-FIN-v2.1.15 

Issue 6: Get "sys::ParseErr: Unexpected token: eof [line 1]"

If connecting to a haystack connector and get the above error, its likely that there may be some unescaped spaces in the point paths. Its recommended to execute the Initialize, Remove Broken Refs, and Rebuild Cache actions on the haystack service.

Issue 7: Get "sys::IOErr: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed"

If you get the above error, it means you have HTTPS enabled on your station. Follow the doc below when connecting with HTTPS.

...

This error means that the user likely doesn't have the JACE commissioned to use runtime+UI (not runtimeOnly). This will display a 500 Internal Service error when hitting ip/haystack/about.

Issue 20: Get "haystack::AuthErr: 404 Not Found"

If all looks good and no error returned when debug this, then make sure to check that "/haystack/" is appended to the host in the URI scheme on the connector. The URI scheme should look something like this: http://10.10.10.100/haystack/ not http://10.10.10.100/

Issue 21: Get "haystack::AuthErr: 403 Authentication failed." with N4 and FIN v2.1.15

This error means that the user didn't enter the correct credentials and/or that specific user doesn't exist in Niagara anymore. Enter correct credentials or create new user if doesn't exist.

Issue 22: Get "auth::AuthErr: 403 Authentication failed." sporadically with N4 and FIN

This error means that the authentication to Niagara failed. Tridium has implemented a new auto-logoff property on the users in N4. What this would do is auto-logoff the user after a certain time has elapsed. The connectors in FIN would fault briefly for a few seconds and then be back to normal when it reconnects to the station. To resolve this, the user has to disable the auto-logoff property on the user and it would then be fine since it won't have to try and reconnect to the station.

Issue 23: CPU usage is high, which sometimes can cause points to go into fault for couple seconds

This can be few different things. It could mean you have a lot of points and a lot of them being in a watch either by being trended or used in a program. Or another thing is the polling is to frequent for the JACE. To help tune this, the user can add a number tag called "haystackPollFreq" set to maybe 10-15 seconds (default is 1sec, which can be to frequent if JACE can't handle it). Make sure to include unit "s" for seconds when setting value. Then disable and re-enable the connector.

Issue 24: Get “sys::IOErr: HTTP error code: 404”

This error could mean that the modules don’t exist and/or incorrect port being used.