Register for ModelChangeEvents failed: CreateMonitoredItems returned BadAttributeIdInvalid for item

[leonberger-m]

Hello, 

since updating our "OPC UA Server" App from version 2.4.0 to 2.6.3 something went wrong with connecting to the OPC Server, e.g. from UA Expert. 

Error-Message: Register for ModelChangeEvents failed: createMonitoredItems returned BadAttributeIdInvalid for item 0

Unfortunately it seems that this error has an impact to our MES. 
So we try to analyze what has been changed or what has to be configured in addition? Is there a way to fix or configure it? 

In the example below the OPC UA Server has been completely re-installed on the core. Even the configuration has been resetted. 

Version 2.4.0 

Version 2.6.x (tested with 2.6.1 as well as 2.6.2) 

Thanks for your support, 
Markus

[CodeWasi]

Hello!
informed the developer colleagues, they will return to you.
Please confirm, that UA_Expert is able to browse with ctrl-OPCUA_Server 2.4 but not with 2.6 .

The message you added with "addressSpaceModel ... is listed in the UA_EXpert? Could you please tell the version you operate with for completeness. 
Bye

[leonberger-m]

Hello @CodeWasi ,

we are able to browse the nodes with 2.4 as well as 2.6.x. 
The only difference is the error message and the possibility that the UA Expert is not able to register to the ModelChangeEvents. 
This message is listed in the UA Expert. 
Normally this is not a big issue but in that case we got some troubles with the connection to our MES (toolkit).
That's why we want to understand where the different behaviour between 2.4 and 2.6.x comes from? 

UA Expert is used in version 1.5.0.319

Regards Markus

[smueller]

Hello @leonberger-m,

we can reproduce the issue. The problems comes with the new event feature supported by our OPC UA Server. Unfortunately, the error occurs if a OPC UA Client wants to subscribe to ModelChangeEvents on our Server. Currently we are working on bugfixing the issue.

The only know workaround currently is to ignoring the error or to not subscribe to ModelChangeEvents.

Best regards

smueller

[leonberger-m]

Hello @smueller , 

thank you for the information. Since we are not able to influence the way the MES is subscibing to the CtrlX OPC UA server we have downgraded the OPC UA server to version 2.4 until there is a bugfix provided. This workaround seems to work quite well, too. 

best regards

Markus 

[leonberger-m]

Hello @smueller , 

any news on this issue? Is there already a planned fix for the problem? 

Best regards
Markus

[NoRisk4Project]

Hello,

the bugfix for the error, that occurs inside the UA-Expert, is included inside the next release 3.4.

It can be included into the next patch of the version 2.6 (scheduled for november) as well, if you are sure, that it will also solve the problem with you MES system.
Maybe you could send us a WireShark trace that contains the MES problem (with version 2.6) so we can be sure that we also have solve this problem.

[NoRisk4Project]

Hello,

the bug (that causes the error inside the UA-Expert), will be fixed with the upcoming patch for the version 2.6. The patch is scheduled for middle/end of November. Hopefully it will also fix your problem with the MES system ...

[NoRisk4Project]

Hello,

Patch 5 for the version 2.6 of the ctrlX CORE OS was released. This release 2.6.5 of the ctrlX CORE OS should soon be available inside the collaboration room. It contains a new release of the OPC UA server app (2.6.4), that solves the "Register for ModelChangeEvents failed" error.

OPC UA server app 2.6.2:

 

OPC UA Server app 2.6.4: