What is your question to the community exactly? I do ofcourse understand your frustration a little.
Editing model geometry can scramble up the referencing of the loads/connectors/fixtures and may lead to errors like the one you encounter above.
It indeed can take a lot of time if you have to setup a study again. Copy pasting them can work, but usually you have to reselect all the surfaces again, due to change in geometry (referencing).
Usually if there are that many contacts and connectors present you should consider if you can narrow down your scope to a more simplified (part of the) problem.
Don't forget that in most other software you can't edit your geometry. So every time you change it, you will have to setup the entire study again anyway. So there will not be that much advantage there.
I just ran into the same issue. It turns out, I had a mesh control that was no longer valid after a geometry change, but the Mesh item was collapsed and it didn't show the red exclamation mark. I deleted the mesh control and recreated it with the new geometry, and the simulation ran just fine. Hope you were able to figure it out.
FWIW, I have also found that once a fixture has the red X error icon, even if I suppress that fixture, the solver will still not run. I have to actually delete that erroneous fixture in order for it to solve.
I'm guessing the same goes for everything--if there's an error, it needs to be deleted, not just suppressed.
This solved my problem when duplicating a study as well. Thanks.
***HEY FUTURE PEOPLE WHO FIND THIS THREAD, CHRIS HAS THE ANSWER RIGHT ^UP THERE^ ***
Unfortunately I am not the original poster so I can't mark the question as answered
I had the same issue and this fixed it right away. I just had to expand the "Mesh" item in the simulation tree and delete the old mesh controls
Me too got same error several times in my model.i checked for every contact set/connector/load /fixture individually by supressing each and checking weather i get same error. but i didn't get till last.
At last what i have found is the simple way to get rid of this error is.
Girish, this also worked for me!