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

“Error! Server responded with: Error: Error status: 409” by usage of IDTA 02006-2-0_Template_Digital Nameplate #537

Open
MartinRudolph96 opened this issue Nov 11, 2024 · 2 comments

Comments

@MartinRudolph96
Copy link

Hello,

when we, the energy informatics group of the Fraunhofer IOSB-AST, built an AASX file together with a project partner, based on the IDTA 02006-2-0_Template_Digital Nameplate given via http://smt-repo.admin-shell-io.com/, we get the error “Error! Server responded with: Error: Error status: 409”, even though there is guaranteed no network issue, as it works with different files at any given time. We reviewed the generated files multiple times via different programs like the Package Explorer. The errors seems to based on some serialization error, even though all the needed concept descriptions are given.

This stops us from using BaSyx as our AAS framework for the continuous development of an energy market data space. We could also review the files individually.

@FrankSchnicke
Copy link
Contributor

Hi,

are you using BaSyx Java V1 or V2? This repository is about V1. If you are still using V1, the error may be due to this. For V2, see https://github.com/eclipse-basyx/basyx-java-server-sdk

@MartinRudolph96
Copy link
Author

Hallo,

we are using a BaSyx Setup based on the provided docker example, using aas-env., aas-reg, aas-disc., and aas-web-ui all based on Version 2. Therefore, I assume we are using the V2 already.

@aaronzi aaronzi transferred this issue from eclipse-basyx/basyx-java-sdk Nov 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants