Seismosoft | Earthquake Engineering Solutions

Everytime I export my XML file is shows me this error:
https://i.postimg.cc/85FQpfZY/image.png
I've some work trying to identify where the problem is, and it turned out that the program has some troubles reading a CONSTRAINT from my list.
Here's how I fixed the issue, What I've done is take another XML file from the imported XML file (after saving it to a .spf format).
Here's the two files compared together. It seems some of the information is missing.
https://i.postimg.cc/0jg39WM6/image.png
I hope you release a hotfix for this. Thanks.

For more clarity:
https://i.postimg.cc/W4BSZD2C/image.png
This is how the constraints should look like inside Seismostruct.

Have you tried downloading and installing v2021 Release-3?

This issue started with me a while back. I'm using release 2 build 50. I will try release 3 and tell you what I find.

I have tried release 3. the same issue keeps happening. although running the file through seismobatch does not produce any abnormal results.
I hope you find the cause of this problem. Thanks.

Thanks for the detailed report, we will try to fix this bug in v2022.
Seismosoft Support

Here's a more detailed video for another file that is exported from seismostruct (once on the right and twice on the left).
exporting to an xml file then importing it and then exporting it again produces no errors when running the file in either seismostruct or seismobatch.
exporting to an xml only once produces errors.
Video link:
https://youtu.be/MoifxT9djLw

humam2014,

We could not reproduce the error with v2021 Release-3. Please make sure that you are using the latest release of the program, and if the problem persists, please send your model to support@seismosoft.com

Seismosoft Support

I was able to identify the source of the issue:
It was a group of elements that had their names changed outside of seismostruct (In excel and pasted back).
So the error was telling me that these elements were not there in the model. It indicated the first element name.
I'm sorry for any inconvenience.

One thing to note is that seismostruct can't understand that the model was extracted from an academic license and still gives errors related to the use of a commercial license (Structural code errors). This creates an error every time the analysis is ran in seismobatch or seismostruct.