InfoPath Dev

Ok, one more problem.  And this is a doozy.  I pray someone can help me as this is a show stopper for me.  I have tried every which way around this and I am at a dead end.  Is this an InfoPath bug?

 I have a form that has been signed (entire form).  Since signing I have changed the template and modified the data source.  When I attempt to reopen the form a get a message that says: "This form is digitally signed, but was created with an older version of the form template.  This form will be upgraded to work with the new template, but this may remove its signatures..."

Great, so it should remove the signature and update the xml?  Nope.  I get the error, "There was an error in the custom validation code."..."The value has been digitally signed and cannot be changed."

I do not have custom validation.  I have disabled all pertinent managed code.  It seems to me InfoPath should strip the signature and run upgrade.xsl, which is what I want it to do.  What is it trying to run while the signature is still attached?

 Any help would be greatly appreciated.

Custom validation does not just include code. On the fields themselves, you can assign a custom validation. Use the logic inspector to see if you have any field-specific custom validation in your form template.

Yep, I checked those too.  I never use them so I wasn't expecting to find anything...

I have two forms, one where this behavior appears, one which doesn't.  So when I get some time (hehe, yea right) I will dive into this and figure out what is going on.

No matter of I missed something, or this is a bug, this is some really bad design...Making forms essentially useless like this.

Good luck. Let us know what you find after you've diff'd the two forms.

Djay:

 Did you ever get a resolution to this problem?  I am experiencing the same problem on many signed forms from last year.  The problem appears to be related to two dates when the template was updated.  The first time I created a new library for the new template, but some of the forms still fail.  Second time was just a template update.

Did the suggestion to diff the two templates help at all?  I have looked at the xml and could probably remove the digital signatures with Notepad or Word, but that doesn't make much sense and probably get me in deeper.  Do you know if Microsoft has any repair tools?

This is pretty awful!!  I can imagine how you felt.

Thanks

Hallo ,

 Did someone found this problem solution ? I had encounter same error over and over in Infopath 2003 i had aplied also the necessary patches that they said will fix the problem from http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=917510&kbln=en-us , (office2003-KB917510-GLB.exe) but same error is trowing.I had check also with code inspector and i had NO any  validation code in my form.I had check every filed also.So every time when i digitaly signed the error is trow in a pop-up"There was an error in custom validation code".

Thank you, any new ideas will be appreciated!

Usually, the full error message contains the name of the problem field.  The next step is to browse the XML file to find this field and its context.  From there, it depends on what changes were made to that specific form template.  I have also found that, depending on the change, just the new version number on the template can throw these errors.  Try changing the version number in the xml file to the latest version number of the template.  In a couple of forms, I had to create entire new libraries and freeze the old ones.

After going through several of these situations, I take extreme caution when creating new versions and changing/deleting signatures and other variables.  Wish I could provide more specific help.  InfoPath is great, but this is a very frustrating area.  I have not found much info from Microsoft explaining any procedure to resolve.