Closed zerox1212 closed 8 years ago
I think I found the root cause, but i'm not sure how to solve it yet... During import of extension object the code creates a TwoByteNodeId, then assigns it a NumericNodeId:
This is now solved, but it should be mentioned that it appears if any binary issue occures it throws opcua.common.uaerrors._base.UaError: Wrong sequence 81 -> 83 (server bug or replay attack)
. This seems like a side affect of refactoring ua errors.
That is a very interesting information @zerox2121 !!! Can you open a bug report?
On Thu, Oct 13, 2016, 18:36 Andrew notifications@github.com wrote:
Closed #317 https://github.com/FreeOpcUa/python-opcua/issues/317.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/FreeOpcUa/python-opcua/issues/317#event-822773342, or mute the thread https://github.com/notifications/unsubscribe-auth/ACcfzrTs3bkbfvYOLrHzwWJmQwYBNMCeks5qzl3pgaJpZM4KSHBV .
This one has me very confused. I make a very basic address space in OPCUA Modeler, since it's running a server in the background I connect to it via UA Expert. Modeler: UA Expert connected:
This has no issues, clicking on the Input or Output Arguments returns node information as expected. I can even call the method (even though it just returns nothing to do).
I then export these 3 nodes to XML to method.xml. Then I start a server and call
server.import_xml("method.xml")
. The importer migrates everything to namespace 3, which should be fine. I connect UA Expert and I can browse the object and method nodes with no problems. Browsing upper nodes with UA Expert:However, as soon as I click on the InputArgument or OutputArgument nodes, the server crashes with this:
Any ideas?