Hi
Il use the lesson 1 code
and the status code return by UaServer_StartUp is 803d0000 which is OpcUa_BadNotSupported
/*============================================================================
* The requested operation is not supported.
*===========================================================================*/
#define OpcUa_BadNotSupported 0x803D0000
The version is Unified Automation UA SDK ANSI C Bundle 1.8.2 (Evaluation Edition)
This SDK was compiled with Microsoft(TM) Visual Studio vs2015 and thusdepends on the runtime components (CRT) of MS Visual Studio vs2015.
I modify the endpointURL by opc.tcp://{HOSTNAME]:4820
in my case : opc.tcp://FIXE-MEUNIER:4820
or opc.tcp://127.0.0.1:4820
I Have this error 803d0000 returned by function UaServer_StartUp
What is false ?
Best Regards
UaStatusCode 803d000 OpcUa_Endpoint_Open failed
Moderator: uasdkc
-
- Jr. Member
- Posts: 3
- Joined: 18 Jun 2018, 10:17
-
- Jr. Member
- Posts: 3
- Joined: 18 Jun 2018, 10:17
Re: UaStatusCode 803d000 OpcUa_Endpoint_Open failed
More information
All trace show
UA Server : Initiliaze Security...
UA Server : Initiliazing PKI of endpoint 0...
UA Server : Creating Endpoint 0...
UA Server : Opening Endpoint....
UA Server_OpenEndpoint.... : OpcUA_Endpoint_Open failed (0x803d0000)
I use wih the same start than lesson 02
why OpcUA_Endpoint_Open failed with this error : 0x803d0000 : The requested operation is not supported. ?
All trace show
UA Server : Initiliaze Security...
UA Server : Initiliazing PKI of endpoint 0...
UA Server : Creating Endpoint 0...
UA Server : Opening Endpoint....
UA Server_OpenEndpoint.... : OpcUA_Endpoint_Open failed (0x803d0000)
I use wih the same start than lesson 02
why OpcUA_Endpoint_Open failed with this error : 0x803d0000 : The requested operation is not supported. ?
-
- Jr. Member
- Posts: 3
- Joined: 18 Jun 2018, 10:17
Re: UaStatusCode 803d000 OpcUa_Endpoint_Open failed
The solution is found
I upgrade the uastack.lib version 1.8.2 may 2018 in link
But the uastack.dll in executable directory was not updated . it is february 2018
update de uastack.dll resolve the problem
I upgrade the uastack.lib version 1.8.2 may 2018 in link
But the uastack.dll in executable directory was not updated . it is february 2018
update de uastack.dll resolve the problem