I have not been able to communicate with my OPC Servers since i reinstalled the manufacturing apps, i am getting the following error in the ApplicationLog.log file:
2018-08-01 13:19:45.445+0000 [L: ERROR] [O: c.t.c.s.c.j.Jsr356ServerConnection] [I: ] [U: ] [S: ] [T: http-nio-8080-exec-4] Error [authenticating connection], Server websocket will be closed. cause: Missing application key!
Since you have reinstalled the manufacturing apps, can you create a new app key and put the new app key into your OPC server configuration.
If my response has answered your question, please mark as Accepted Solution, for the benefit of others who may have the same question.
I already updated the OPC server with the new HOST and key that i got from the Controls Advisor console and that didn't solved the problem.
Can you share the complete application logs OPC server details and screenshot of configuration screen from your OPC server where you have added Host and app key.
Which version of Manufacturing apps and ThingWorx Composer installed on your machine.
Looking at the logs seems to be an issue with validation properties. Could you please take the backup of validation.properties file from the location C:\ThingworxStorage\esapi and remove the file from the location.
After removing, restart the tomcat.
If the issue still persists, share your newly generated validation.properties and catalina.log file from the tomcat logs
Hello, i don't see the application key error anymore but i still see errors on the catalina.out, and now i am a little concerned about an http error logged:
[http-nio-8080-exec-6] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens
I am attaching the new validation.properties file and the catalina.out where you can se the http errors.
Could you please try https:// to http:// in your client url and see if the issue still persists.
This exception can occur when you try to execute an https request on an endpoint which isn’t https enabled.