I had tried to configure SmartConnector to connect to OPC and ran into the following problem:
in the EBO I have the error “System alarm SOAP-ENV-Reciever. Timeout Gsoap_Communication_Error: 28 connect failed in tcp_connect () ”(see screenshots in the attachment).
In the SmartConnector logs, the processor responsible for connecting to the OPC starts normally and manages to connect to the Insat OPC server (see screenshot).
Settings of the OPC processor and EWS in EBO are in the third screenshot.
Does any have any idea what could be the reason for such an error?
Hello @IvanSpokojnyj , thank you for your question
I moved your question to the SmartConnector forum when the community of experts will be able to provide you the right support and answer your question!
PS: don't hesitate to check the Knowledge base and use the search bar with keywords. there is a lot of content discussed every day and your issue may have already been solved 😉
Posted: 2019-10-07 08:00 AM . Last Modified: 2019-10-07 08:01 AM
I can't tell what you problem is from the screenshots and log, but can you confirm:
- The EWS Username and Password is correct?
- Instead of 127.0.0.1 try 'localhost' in EBO (it shouldn't matter, but I've seen stranger things happen).
- Is the EWS Server in Smart Connector running? (in the EWS Servers tab)
If none of those are the problem, can you turn on EWS Server Logging in Smart Connector as well as changing the logging level to trace, and then restart Smart Connector, and try and connect to the EWS Server again?