Invalid subscription error with sbo 3.2

[esari]

Hello

We got slow response from new SBO 3.2 Enterprise Server. We have create SOAP REST Providers to https ports with base route. Before new SBO 3.2 create subscription will take 10s for 270 modbus points, but now with new SBO version it will get only error message "Invalid Subsription" after 7min waiting. This waiting also affect other smartconnector users so that they cannot login to smartconnector.

Yesterday I tested that will get subscription to work with 50 points and it took 2min to create subscription.

We have clients which would like to use REST API, but it is not possible at the moment. 

Before it was 500 points per subscription and now it is 50. Can someone test smartconnector with SBO 3.2 with 300 points? 

Here is error message after 7min waiting:

2020-09-25 06:53:04.9156,Debug,EwsConsume,SCLapinDAS,Subscribe,0f23a7c8-20a1-4f14-ba22-c41e06e00b02,CommunicationException Handler,
{"ClassName":"System.ServiceModel.FaultException","Message":"Invalid subscription","Data":null,"InnerException":null,"HelpURL":null,"StackTraceString":" at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)\r\n at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)\r\n at Ews.Client.IDataExchange.Subscribe(SubscribeRequest request)\r\n at Ews.Client.DataExchangeClient.Subscribe(Subscribe request)\r\n at Ews.Client.EwsClient.ExecuteAndLogCall[TRequest,TResponse](String methodName, TRequest request, Func`2 methodToLog)","RemoteStackTraceString":"\r\nServer stack trace: \r\n at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)\r\n at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)\r\n at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)\r\n at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)\r\n\r\nException rethrown at [0]: \r\n","RemoteStackIndex":1,"ExceptionMethod":"8\nHandleReturnMessage\nmscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089\nSystem.Runtime.Remoting.Proxies.RealProxy\nVoid HandleReturnMessage(System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Messaging.IMessage)","HResult":-2146233087,"Source":"mscorlib","WatsonBuckets":null,"code":[{},{}],"reason":[{}],"messageFault":{"Actor":"","Code":{"IsPredefinedFault":true,"IsSenderFault":false,"IsReceiverFault":false,"Namespace":"http://www.w3.org/2003/05/soap-envelope","Name":"Server","SubCode":{"IsPredefinedFault":true,"IsSend... subscription"}]},"IsMustUnderstandFault":false},"action":null},,,,

--

Esa

[JeffBowman]

Hi Esa,

This is curious. I have reached out to someone in EBO R&D to see if there is something to do with timeouts that have changed in the later version of EBO.

I will update when I hear back.

Best Regards,

-Jeff

[JeffBowman]

Hi @esari ,

I have heard back from EBO R&D about the error, they are asking if you would be able to turn on trace logging in EBO to trace on the module in EBO:

/Server 1/System/Modules/Trace/Loggers/nsp/nsp.csc/nsp.csc.CWSServer/nsp.csc.CWSServer.CWSCommand_Subscribe

This should hopefully help to determine why this Invalid Subscription error is occurring. Is this something you are able to do? 

Let me know if you have any questions.

Best Regards,

-Jeff

[esari]

Hello

I didn't get modbus or bacnet points to work with EBO 3.2 and SmartConnector, but I have done workaround to get SmartConnector work norrmally again. I have now created all modbus ja bacnet point to local points so those will be faster to read by smartconnector client. SmartConnector client now reading newly created local points. Some reason in EBO 3.x (EBO Hotfix 3.2.1.2000) 'Create Subscription' will take too long so SmartConnector will be timeout and return 'invalid subscription'.

Now we had to create policy for SmartConnector clients that it is not allowed to read modbus or bacnet points. Unfortunately there are no way to SmartConnector client know that is some smartconnector id modbus or bacnet point. EWS interface don't separe those points so SmartConnector interface cannot get this information. So we had to check all the point that are those local points or modbus/bacnet points.

Hope that EBO product support can find root cause of this issue and release hotfix for EBO.

--

Esa