Supported Transport Profiles

[tisch]

Hey,

i am currently checking out which of the several transport profiles are usable with the .NET SDK. I tried to connect to a server with opc.tcp-, https- and http-BaseAdresses from different client apps (UaExpert, BasicClient example, FullClient example).

with UaExpert:

opc.tcp - works fine
https - from UaExpert console: Source: ServerNode, Message: Could not connect to server: BadCommunicationError
http - from UaExpert console: Source: ServerNode, Message: Could not connect to server: BadRequestHeaderInvalid

-> Q1) Are there any experiences with similar problems with UaExpert?

with FullClient:

opc.tcp - works fine
https - works fine
http - messages from the trace log look like this for all security modes:

09:00.15|0001|01|4|SECURE CHANNEL CREATED [UnifiedAutomation.UaBase.ChannelBase WCF Client 2.0.0.0] [] Connected To: http://169.254.160.154:48032/wssecurity/None [None/None/]
09:00.15|0011|02|1|[BadEncodingLimitsExceeded] Error during OnCreateSessionComplete.|StatusException|MaxCallDepth at ServiceDiagnostics. 0 < 1
09:00.15|0001|02|1|[BadEncodingLimitsExceeded] Error during EndConnect.|StatusException|MaxCallDepth at ServiceDiagnostics. 0 < 1
09:00.15|0001|02|4|CONNECTION STATUS CHANGED: Disconnected http://169.254.160.154:48032/wssecurity/None

-> I changed values for properties like MaxCallDepth, MaxMessageSize, MaxArrayLength and so on either from Code or the config file. Nothing works.
-> Q2) Are there any experiences with similar problems?

Best regards

[Support Team]

Communication via http and https is not released. These features are just experimental and (compared to connection via opc.tcp) rarely tested. Interoperability problems might occur.
There is a known issue for connections via https: UaExpert requires tls version 1.2 which is not available for .NET framework versions 3.5 and 4.0.