Deleting the problem component part and re-adding it to the template solved the problem.
Can you delete all the components associated with the audit, the job also, and then rediscover the components and re-run the audit job.. just to be safe... if that still fails, call support...
What I found was that I added a "Discovery Signature"
to the component template saying that the parent "bin" directory of my
component files must exist.
That Discovery Signature added the "bin" directory
as an additional part of the component; which I didn't want.
There are some files in the bin that I don't
want to be part of the component.
Once I removed that Discovery Signature, I know longer got the error.
But now my Discovery job finds additional components I dont
want so I deleted them manually.
My point is that I don't know why the Discovery Signature would automatically
become a "Part" of the template.
I've opened a ticket and I'm working with Tim Biron on it.
you can add bin as a part, but uncheck its use in browse, snapshot, compliance, so it's only used in discovery. anything used in the template is a part, but you can control what specifically the parts are used in.
Now I see. The Discover Signature directory was added to the Parts. Then
I go back to the Parts and adjust the Discover Signature directory by unchecking Discover.
Well, you still usually want to have some kind of discovery condition set.
Agreed, the directory must exist for my Discovery Condition.
I had confusion when the directory was turning up in PARTS and became
part of Snapshot/Audit .
I verified that the dir can be a "PART" of the component and can be used in my Discover Signature.
I made sure that the directory PART was not being used for Browse or Snapshot/Audit.
Your's and Jim A's input cleared up my confusion.