Schema Validation Error

[RoyW]

At the company I work for, we are having a relatively major issue with
Infopath. The infopath documents shared from our server were somehow
altered. Users began getting a message saying that they needed to update
Office 2003 to service pack 1 in order to open infopath documents. Well that
is all fine and dandy, but now when they try to open previously saved
infopath documents, they receive an error that says the have a "this form
contains a schema validation error". Here are the details from the error:

Element
'{http://schemas.microsoft.com/office/infopath/2003/myXSD/2003-10-14T15:52:36}field305'
is unexpected according to content model of parent element
'{http://schemas.microsoft.com/office/infopath/2003/myXSD/2003-10-14T15:52:36}clinicalProgresstoDateNote'.
Expecting:
{http://schemas.microsoft.com/office/infopath/2003/myXSD/2003-10-14T15:52:36}field400, {http://schemas.microsoft.com/office/....

We really need to be able to open these previously saved infopath documents
and reverting back to Office 2003 without SP1 does not fix the issue as we
cannot open the documents without SP1. I checked the microsoft knowledge base
and this is a known issue, but there is no suggestion on how to resolve it or
even whether it is resolvable at all. If there is a fix for it, I would
greatly appreciate any help.

Thanks,
Roy

 

[Brian Teutsch [MSFT]]

Is the chance of someone removing fields from the form a possibility? It
would result in the errors you've seen.

That could be why InfoPath is complaining that it expected field400 (the new
old) but found clinicalProgresstoDateNote (the exisitng node).

The error about SP1 you are getting is caused when someone opens the form in
an SP1 version of InfoPath and updates the form to use new features. The
second message about schema validation is not directly related to the first,
but is related to the changes to the fields in the form.

Brian

 

[royw]

Is the chance of someone removing fields from the form a possibility? It
would result in the errors you've seen.

That could be why InfoPath is complaining that it expected field400 (the new
old) but found clinicalProgresstoDateNote (the exisitng node).

The error about SP1 you are getting is caused when someone opens the form in
an SP1 version of InfoPath and updates the form to use new features. The
second message about schema validation is not directly related to the first,
but is related to the changes to the fields in the form.

Brian

 

[royw]

Thanks Brian for your reply. I still have a question though. Is it possible
to fix this problem? I'm not to savy when it comes to XML and programming so
if it invovles that, I might as well tell the end users to suck it up.

Also, I think what my have happened was that someone opened the infopath
templates on the server (another admin???) and converted the templates to sp1
version by mistake. This then hosed the previously saved forms that
contained patient information since even locally saved forms are pointed at
the templates on the server (i.e. if i understand it right, the forms are
really just data that is applied to the template on the server when the end
user opens it.)

So I imagine the only possible way to fix this would be to revert the
templates on the server from sp1 version to pre-sp1 versions. All the users
that have already updated their office to sp1 should still be able to work
with infopath forms no matter which version, right?

 

[Brian Teutsch [MSFT]]

My answers are inline...

Thanks Brian for your reply. I still have a question though. Is it
possible
to fix this problem? I'm not to savy when it comes to XML and programming
so
if it invovles that, I might as well tell the end users to suck it up.

It won't be easy, and it definitely requires knowledge of XML.

Also, I think what my have happened was that someone opened the infopath
templates on the server (another admin???) and converted the templates to
sp1
version by mistake. This then hosed the previously saved forms that
contained patient information since even locally saved forms are pointed
at
the templates on the server (i.e. if i understand it right, the forms are
really just data that is applied to the template on the server when the
end
user opens it.)

If you can find someone whose computer hasn't opened the form since it's
been updating, unplug their ethernet connection and create a new blank form.
Then choose Tools-Design This Form. You'll be able to save the file to your
desktop, and "Re-publish" the form back to the server.

Each computer keeps a backup of the forms, in case the network isn't
available. This is, like you say, because the XML files are just data, and
the XSN form template is applied to display that form (on the local machine,
not on the server, though).

So I imagine the only possible way to fix this would be to revert the
templates on the server from sp1 version to pre-sp1 versions. All the
users
that have already updated their office to sp1 should still be able to work
with infopath forms no matter which version, right?

Users who have udpated will be able to work, you're right. That's probably
the easiest.

Brian