Ernesto has it right -
I can help you manually clean it up. Usually, I see this issue if for some reason the Qdabra Rules data source has been manually walked through in the form and then the form has been re-injected.
So, if you'd like to have me clean up the form, you can attach it here or send it to support. If you'd like to try it yourself, first, back up your form. Then, save the form as source files (from the Publish menu in IP 2010, Export Source Files).
Check the source files - are there two QdabraRules.xsd files? Usually, one is named QdabraRules1.xsd. Delete any QdabraRules.xsd that isn't named QdabraRules.xsd - that is, delete the one named QdabraRules1.xsd or QdabraRules2.xsd.
Then, open manifest.xsf in a text editor. Search for the name of the file you deleted - for example, QdabraRules1.xsd. You'll find a file reference:
<xsf:file name="QdabraRules1.xsd">
<xsf:fileProperties>
<xsf:property name="dataObject" type="string" value="QdabraRules"></xsf:property>
<xsf:property name="rootElement" type="string" value="QdabraRules"></xsf:property>
<xsf:property name="useOnDemandAlgorithm" type="string" value="yes"></xsf:property>
</xsf:fileProperties>
</xsf:file>
Delete the entire xsf:file node.
You'll also find a data object reference:
<xsf:dataObject name="QdabraRules" schema="QdabraRules1.xsd" initOnLoad="yes">
Where the schema is set to use that file. Simply change that:
<xsf:dataObject name="QdabraRules" schema="QdabraRules.xsd" initOnLoad="yes">
So it uses the correct file.
Save your changes. Then right click on the manifest.xsf and select Design to open in design mode. From there, File --> Save As will save the form files as a template again.