Hello,
has anyone here ever encountered the following issue: Rebuilding a project always completes successfully. However, a regular build always results in the following error:
I should mention that this project has a certain conversion history. Originally created with AS4.11, it was upgraded to AS4.12. During this process, ARNC0/ACP10 was replaced with MappMotion. Finally, it was converted to AS6.1 to utilize MappMotion 6.2 (for multi-core support).
There’s probably something left over from earlier versions causing the issue. But how do you figure out what it is? I’ve already deleted the Temp folder, but I doubt the B&R support will quickly tell me what’s going on…
At first glance, everything seems to be running fine on the PLC after I let it create the CF card following the rebuild. The controller is in run mode.
Hi,
it looks like the error is thrown after analyzing VC4.
Did you open and save the VC object with VC editor after converting to AS 6 ?
Otherwise the VC object could be still be stored in an older file format.
Open and close with the AS6 editor doesn’t change anything in the files. Only when I actually make a change in the visualization the file has to be saved and the new AS version is included.
I observed something similar with a project that went AS4.x → AS4.12 → AS6.1:
I got internal error 9499 on both build and rebuild. In my case running “Clean configuration…” resolved the issue.
However, the error occurred again later and had to be resolved again with “Clean solution…”. My impression was that this happened after some version control commands (something like git switch or git stash) but I didn’t track this and didn’t investigate further. I also think (but didn’t check thoroughly) that the projects .gitignore is compatible with the help page Einsatz von Versionskontrollsystemen (English page Using source control systems does not have the “exceptions” section).
Not sure if this is relevant, perhaps there is some (remote) relation?
Hello @Steffen_Herderich ,
It could be that there is a special character in the path? Please doublecheck it. It could be e.g. in the user name which is “blacked” in your picture?
i got the hint from our local B&R support to deactivate the option “Transfer objects only if relevant changes have been made” in the transfer settings.
Now also the normal build run through without error. That’s a bug in Automation Studio and should be fixed in AS 6.3…