Skip to main content
A
Aruna1-Visitor
1-Visitor
October 16, 2018
Question

Remote Thing is not binding after successful authentication. It gives "Bind request failed" error

  • October 16, 2018
  • 1 reply
  • 2388 views

We are using .Net SDK for edge implementation. Sometimes it gives "Bind request failed" error and connection doesn't happen but sometime client gets connected to server still the same error is thrown. Not able to find the exact root cause for the issue.

Here is the SDK logs. 

2018-10-15 13:55:49.791Z [L: Information] [T: 4] [U: SYSTEM] [O: IotSubscriber.IotSubscriberService] Service started!
2018-10-15 13:55:50.601Z [L: Information] [T: 14] [U: SYSTEM] [O: com.thingworx.communications.client.ConnectedThingClient] Websocket connected and authenticated
2018-10-15 13:55:50.606Z [L: Information] [T: 16] [U: SYSTEM] [O: com.thingworx.communications.client.ConnectedThingClient] Websocket connected and authenticated
2018-10-15 13:55:50.967Z [L: Error] [T: 5] [U: SYSTEM] [O: com.thingworx.communications.client.TwApiWrapper] [Error] twMessaging::handleMessage: Response ID 2 has code 160: Binding failed, see server log for more information
2018-10-15 13:56:05.969Z [L: Warning] [T: 5] [U: SYSTEM] [O: com.thingworx.communications.client.TwApiWrapper] [Warning] twWs_Connect: Already connected

1 reply

P
posipova20-Turquoise
20-Turquoise
October 18, 2018

What versions are you using, for both SDK and the platform?

Is there anything in the application log on the ThingWorx platform side?

 

A
Aruna1-VisitorAuthor
1-Visitor
October 18, 2018

 

.net SDK version - 5.7.6.3407

server version - ThingWorx 8.2.1-b140

Application log screen shotApplication log screen shot

 

 

 

P
posipova20-Turquoise
20-Turquoise
November 2, 2018

I apologize for the late response, for some reason I did not get notifications about this. Do you have a firewall enabled, perhaps? Could you please share your configuration too?

Terms & ConditionsCookie settingsAccessibility statement