Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
After doing an SVN merge, I had some conflicts. After resolving the conflicts, when I attempt to commit the project to the repository, I get the message 'The object GUID nnnnnnnn-nnnn-nnnn-nnnn-nnnnnnnnnnnn' is not valid' Clicking OK closes the window.
Does anyone know how to resolve this issue?
Using the equivalent of Codesys 3.5 SP15 Patch 5, with SVN add on 4.2.5.0
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's been almost exactly 2 years since your post with no follow up here. I feel your pain Tim, I had this happen to me today. The best I could do was to checkout the most recent copy to another file and manually copy/paste from my working copy to the checkout, commit and save over the working copy with the checkout. I didn't know what else to do - the error message is no good to anyone, I doubt even S3 could use it. Anyways, it was good to have the SVN working so I could at least see what the changes were, as well as the fact that I commit often because of issues like this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It was very painful, however we (me and the other on the project team - didn't want you to think I was referring to myself in the 3rd person) worked around it. And, like you, we all learned to commit early and commit often.
One of the thing we did notice was that SVN didn't always like it when we renamed objects like POUs, structures, etc. Refactoring variables didn't seem to cause any issues. So, we got in the habit of creating a copy of the object with the name we wanted, performing a commit, then deleting the object with the original name, then performing another commit.
Having said that, life with SVN is so much better than life without it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After doing an SVN merge, I had some conflicts. After resolving the conflicts, when I attempt to commit the project to the repository, I get the message 'The object GUID nnnnnnnn-nnnn-nnnn-nnnn-nnnnnnnnnnnn' is not valid' Clicking OK closes the window.
Does anyone know how to resolve this issue?
Using the equivalent of Codesys 3.5 SP15 Patch 5, with SVN add on 4.2.5.0
It's been almost exactly 2 years since your post with no follow up here. I feel your pain Tim, I had this happen to me today. The best I could do was to checkout the most recent copy to another file and manually copy/paste from my working copy to the checkout, commit and save over the working copy with the checkout. I didn't know what else to do - the error message is no good to anyone, I doubt even S3 could use it. Anyways, it was good to have the SVN working so I could at least see what the changes were, as well as the fact that I commit often because of issues like this.
It was very painful, however we (me and the other on the project team - didn't want you to think I was referring to myself in the 3rd person) worked around it. And, like you, we all learned to commit early and commit often.
One of the thing we did notice was that SVN didn't always like it when we renamed objects like POUs, structures, etc. Refactoring variables didn't seem to cause any issues. So, we got in the habit of creating a copy of the object with the name we wanted, performing a commit, then deleting the object with the original name, then performing another commit.
Having said that, life with SVN is so much better than life without it.
"me and the other on the project team - didn't want you to think I was referring to myself in the 3rd person" - 😄
"Having said that, life with SVN is so much better than life without it." - Totally agree!