Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
Solved
Go to Solution
Link copied. Please paste this link to share this article on your social media post.
I just finished setting up an EcoStruxure Web Service with the Custom EWS from SmartConnector Tutorial, and I chose to 'Host EWS Objects'.
They were initially showing correct values and EWS State 'Good', but after 10 seconds (the polling interval I specified),
they all changed to EWS State 'Error', and lost their values.
The values are still appear correct when I look under Hardware, but they are in Error when I look under the EcoStruxure Web Service Interface.
Alarm Contents:
"State":",;|;,"
"Count":"1"
"Priority":"100"
"Triggered time":"2/16/2017 3:31:54 PM"
"Source name":"EcoStruxure Web Service"
"Source":"/JoshSBO/EcoStruxure Web Service"
"Alarm text":"System alarm: SOAP-ENV:Sender EWSv122:SCWS Gsoap_Communication__Error: 12 Invalid NotificationId parameter"
"System alarm ID":"CWS Value Poll failed"
"Timestamp":"2/16/2017 3:31:54 PM"
"Acknowledged by":""
"Category":"System alarm"
Accepted Solutions
Link copied. Please paste this link to share this article on your social media post.
The problem here is due an interoperability issue which exists between SBO 1.7 and SmartConnector 2.1 (and higher) when SmartConnector is the EWS Server and SBO is the EWS client. The issue is in how SBO handled consuming Subscriptions served by another EWS Server.
You have two options to work around this:
- Upgrade SBO to 1.81 or higher. The inteop issue has since been fixed and confirmed by Buildings Labs.
- Downgrade SBO's EWS client to communicate using EWS 1.1. This can be done from SBO by editing the properties of the EWS interface setting the "Server EWS Version" (really a misnomer as what you are doing is forcing the client to use this version) as shown here:
Link copied. Please paste this link to share this article on your social media post.
The problem here is due an interoperability issue which exists between SBO 1.7 and SmartConnector 2.1 (and higher) when SmartConnector is the EWS Server and SBO is the EWS client. The issue is in how SBO handled consuming Subscriptions served by another EWS Server.
You have two options to work around this:
- Upgrade SBO to 1.81 or higher. The inteop issue has since been fixed and confirmed by Buildings Labs.
- Downgrade SBO's EWS client to communicate using EWS 1.1. This can be done from SBO by editing the properties of the EWS interface setting the "Server EWS Version" (really a misnomer as what you are doing is forcing the client to use this version) as shown here:
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.