Sorry for a late answer. Can you try the Method call with https://prosysopc.com/products.....a-browser/ (r-click the method node in the address space tree)? I could not reproduce the problem (using Browser). Can you verify via https://prosysopc.com/blog/opc.....wireshark/ (or the Req/Res Log tab in Simulation Server) that the Method Call request actually arrived in the server? Sometimes the statuscodes are also used to indicate client-side issues.

I created a method inside the Simulation folder. This method is designed not to have any input arguments, since I don’t want the function to accept any. As an output argument, I’ve defined a scalar String, similar to an example I found on the OPC UA website. For the SET action, I configured it to assign a constant value from the simulation folder to a specific variable (just for simple testing).

On the client side, my code for calling the method looks like this:

UA_Variant *output;
size_t outputSize;

UA_StatusCode retval = UA_Client_call(client,
UA_NODEID_STRING(3, "85/0:Simulation"), // Parent object
UA_NODEID_NUMERIC(3, 1011), // Method NodeId
0, NULL, // No input arguments
&outputSize,
&output);

if(retval == UA_STATUSCODE_GOOD) {
printf("Method call succeeded. Output count: %lu
", (unsigned long)outputSize);
// Handle output
UA_Array_delete(output, outputSize, &UA_TYPES[UA_TYPES_VARIANT]);
} else {
printf("Method call failed. StatusCode: 0x%08x
", retval);
}

However, this call fails with status code: 0x80020000 (BadInternalError).

Interestingly, when I define another method that does have one input argument (e.g., a Double), it works perfectly fine using the same approach.
The only difference between the two methods is that this one doesn’t take any input arguments.

Could someone help me understand what I might be missing in the configuration of the method with no inputs?
Do I still need to define an empty InputArguments property explicitly for methods without inputs?

Thanks in advance!

https://reference.opcfoundatio.....docs/6.2.2

If the client does not accept the certificate, it will prompt the user.

If cvcValidity is missing, it indicates that the certificate has probably been expired.
So, if you can find it from the rejected certificates in the disk, you can check the validity period of it. And if that turns out to be the case, you need to find out how to renew the server certificate.

I tracked the program and found that the PassedChecks returned by UaClient.OnValidateCertificate lacked the status of cvcTrusted and cvcValidity.
How do I make the client trust the certificate?

The OPC UA Specification (available online at https://reference.opcfoundation.org/) defines how StatusCodes are supposed to be used in Client-Server communication consisting of Service requests and responses. Part 4 (https://reference.opcfoundatio.....ocs/Part4/) in specific defines the Services that Servers provide to Clients and which StatusCodes Servers should be using when there are errors. Some specialized parts of the Specification such as Data Access (https://reference.opcfoundatio.....ocs/Part8/) and Alarms & Conditions (https://reference.opcfoundatio.....ocs/Part9/) also define additional StatusCodes and how to use them.

There are currently over 200 StatusCodes in the Specification (https://github.com/OPCFoundati.....usCode.csv). To understand how StatusCodes are used, you will need to read Part 4 for the StatusCodes used in common Client-Server communication and other parts that are relavant to your Client application, e.g. if your Client supports Historical Access, you will need to read Part 11 (https://reference.opcfoundatio.....cs/Part11/) for StatusCodes related to reading historical data and so on.

P.S.
This section of the forum is for discussion related to Prosys OPC Client application. The correct place for this topic would've been the OPC UA SDK for Java section.

Prosys OPC Client is not an OPC UA Client. What do you mean when you say "the OPC UA Client"? Do you mean OPC UA Clients in general or some specific OPC UA Client?

What do you mean with errors? Do you mean Bad StatusCodes? Some of them are listed in https://reference.opcfoundatio.....t4/7.39.2/ but more StatusCodes are defined in latter parts of the OPC UA Specification. If you mean something else with errors, please clarify what you mean.

I realized that no matter where I try to change the SecureChannelLifetime (to make it superior than the limit 4294967040 mentioned in the error message), my change does not take effect and it is always the value 3600000 that remains. Can you tell me where to really modify it or how to solve my problem please.

Thanks

is it possible to build an OPC UA Client using the .NET Client SDK targeting an Ubuntu based Docker image in Azure DevOps? Are there any restrictions I should be aware of? I assume that any Linux distribution being supported by .NET Core should be feasible as well in case it works with Ubuntu?

Best,

Pena67

As the name of the StatusCode suggests there has been a mismatch of data types. This StatusCode is returned by Write Service when attempting to Write a value with DataType that isn't the same or a subtype of the target Attribute's DataType. Verify that the value you're attempting to write has a proper DataType. See https://reference.opcfoundatio.....t4/5.10.4/ for more information on the Write Service.