Conflict Resolution

[3286]

Alan, Mark...THANK YOU VERY MUCH, thank everyone who replied. We have had a huge exercise in wondering " WHY " because we had a successful deploy and run and then we didnt, and we chased everything that seemed logical wondering if it was something we had changed or not. That was why we tried several re imaging and re deploying, even to the point of uninstalling and reinstalling the software and updates.

My size 13 boot would love to stop kicking myself in the backside, was this generally well known and did we miss it in a update or post somewhere along the way or was this discovered the hard way and result in lots of other teams having the same frustration and lost time? Theres that part of me that would love to pass the blame somewhere , but that wont help anything now, so I guess Ill pull my big boy pants up and move along.

Mike

EDIT: We have been getting the same error message over and over again. From the picture on the first post there says there is a conflict but we can't locate the conflicts. Is there any way to check where the conflicts are located? We've tired backtracking them manually but to no avail.

[Alan Anderson]

Originally Posted by 3286

EDIT: We have been getting the same error message over and over again. From the picture on the first post there says there is a conflict but we can't locate the conflicts. Is there any way to check where the conflicts are located? We've tired backtracking them manually but to no avail.

The "conflict" is between the code that's already running on the cRIO and the code that you're deploying to it. You're telling the system to accept a "Real-Time Startup Application", and it's letting you know that there are things running that it will have to stop in order to continue. That is a normal part of the process. It isn't an error message. Don't worry about it.