Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node in ReferenceServer is tagged as historizing, but does not allow historical access #2520

Open
1 of 5 tasks
ThomasNehring opened this issue Feb 14, 2024 · 0 comments
Open
1 of 5 tasks
Labels
bug A bug was identified and should be fixed. server

Comments

@ThomasNehring
Copy link
Contributor

Type of issue

  • Bug
  • Enhancement
  • Compliance
  • Question
  • Help wanted

Current Behavior

The Reference Server offers a node with node id ns=3;i=2808 with browse path:
Objects -> Data -> Dynamic -> Scalar -> Int32Value
which has the attribute 'Historizing' set to true, but which does not allow access to historical data. When you try to look at the history in UAExpert in the History Trend View the error "Added item does not support historizing" comes up.
The node is configured as historizing in the TestDataNodeManager.cs file in the Quickstarts.Servers project,
line 198ff (method CreateAddressSpace).

Expected Behavior

The expected behaviour is that the node is recognized as history enabled by a client.

Steps To Reproduce

No response

Environment

- OS:
- Environment:
- Runtime:
- Nuget Version:
- Component:
- Server:
- Client:

Anything else?

Just a guess why it does not work: the HistoricalAccessServer in the Samples solution provides history enabled nodes. If you look at the source code you will note that the nodes are created as ArchiveItems/ArchiveItemStates, while, in the reference server, they aare created as ScalarValues/ScalarValueObjectStates.

@ThomasNehring ThomasNehring changed the title Node in ReferenceServer is tagged as historizing, but does allow historical access Node in ReferenceServer is tagged as historizing, but does not allow historical access Feb 14, 2024
@mregen mregen added bug A bug was identified and should be fixed. server labels Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A bug was identified and should be fixed. server
Projects
None yet
Development

No branches or pull requests

2 participants