V
Vince Sefcik
I built a web service for an Infopath form on my development machine
(running XP with SP1), built the Infopath form using a web service data
connection and developed the form. Everything worked fine. I then
replicated the web service on one of our servers (running Windows Server
2003) by executing VS.Net 2003 on that server (logged in as Administrator)
and typing in all of the code (instead of copy/paste), built the web service
and tested it with a sample VB.net program. The web service worked fine.
My problem is that whenever I try to build an Infopath form pointing to the
web service on the server, after entering the location of the WSDL file in
the Data Connection Wizard, I get the error messages:
The file is not a valid XML file
The file is not a valid XML document.
Illegal qualified name character.
Line 1, Position 2.
I can build the Infopath form using a web service if I use the WSDL on my
test machine, but not if I use the WSDL on the server. I know the Web
service on the server works, because I can access it via a test program and
read/write data. Does anyone have any ideas what might be causing the above
error messages? Thanks.
(running XP with SP1), built the Infopath form using a web service data
connection and developed the form. Everything worked fine. I then
replicated the web service on one of our servers (running Windows Server
2003) by executing VS.Net 2003 on that server (logged in as Administrator)
and typing in all of the code (instead of copy/paste), built the web service
and tested it with a sample VB.net program. The web service worked fine.
My problem is that whenever I try to build an Infopath form pointing to the
web service on the server, after entering the location of the WSDL file in
the Data Connection Wizard, I get the error messages:
The file is not a valid XML file
The file is not a valid XML document.
Illegal qualified name character.
Line 1, Position 2.
I can build the Infopath form using a web service if I use the WSDL on my
test machine, but not if I use the WSDL on the server. I know the Web
service on the server works, because I can access it via a test program and
read/write data. Does anyone have any ideas what might be causing the above
error messages? Thanks.