FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
Dear Community User! We are updating our platform to a new
system.
Read more: Important
information on the platform change.
03-08-2024 07:33 AM - edited 03-08-2024 07:38 AM
Currently in the ctrlX PLC Engineering version 2.4.1 when trying to open the GIT history of a test project the error "Unbehandelte Ausnahme in der Anwendung..." appears:
Necessary CODESYS - Professional Developer Edition licenses is available and working fine.
By clicking on continue the same message keeps showing up so the only possible way is to end the program.
Detailed error message text and system report of the ctrlX WORKS attached. Are there any other information that can be gathered?
03-11-2024 01:29 PM
Can you please also submit a project archive and the steps to repeat to reproduce the error?
03-12-2024 11:31 AM - edited 03-12-2024 11:33 AM
Hi There,
I'm the user CodeShephard created this tread for.
It seems that we've solved the problem by our own.
The error occured during the git handling of an example project.
This project was connected to a local git and a remote (orgin) repo connected to a MS-Azure-DevOps cloud repo.
We did some changes with two developers and got conflicts.
I was able to resolve the conflict and merge the changes.
After that I wasn't able to get the history of the repo. Trying to do this the described error occured.
Getting the history by Tortoise-Git worked well.
During preparation of the the plc code and the repo to share it in this thraed I removed the remote repo.
After that a was able to get the history again.
Adding the remote repo once more to the project everything is fine again.
So, I think it doesn't make any sense to share the code anymore, does it?
03-13-2024 11:40 AM
Glad you have found a solution
So far we have only received theoretical inquiries and error reports describing its status - we have not yet been able to reproduce this.
Therefore, a project archive with the status in which the error occurred would be very interesting - also for future error reports and fixes in this direction.
So, if possible, please share them with us.