Listener URI Problem Publishing a web service in VFP 8.
Dane Karcher
I'm trying to use the VFP 8.0 XML Web Service Tools in the task pane to
publish my XML Web Service. The process creates the wsdl and other
components fine, but ends with:
"Registered: There was a problem accessing the Listener URI specified for
the WSDL file."
I believe this is probably a problem in my IIS setup, but I have searched
the configuration. The wsdl extension is set to the SOAPIS30.DLL which
works on other machines.
The project itself works when generated and published on another computer. I
also tried the walk though example with identical results on my troubled
laptop. I am running XP Professional, VFP 8.0, and IIS 5.1
Help...
Eric den Doop
You wrote on Wed, 7 May 2003 14:13:13 -0400:
DK> I'm trying to use the VFP 8.0 XML Web Service Tools in the task pane to
DK> publish my XML Web Service. The process creates the wsdl and other
DK> components fine, but ends with:
DK> "Registered: There was a problem accessing the Listener URI specified
DK> for the WSDL file."
DK> I believe this is probably a problem in my IIS setup, but I have
DK> searched the configuration. The wsdl extension is set to the
DK> SOAPIS30.DLL which works on other machines.
DK> The project itself works when generated and published on another
DK> computer. I also tried the walk though example with identical results
DK> on my troubled laptop. I am running XP Professional, VFP 8.0, and IIS
DK> 5.1
I am running into a similar problem. My SOAP service is working fine on my
WinXP development box, but I get the same error when I try to publish this
thing on a Win2k Advanced Server which has a full copy of VFP8 installed.
Did you find a solution to this problem?
--
Eric den Doop
www.foxite.com - The Home Of The Visual FoxPro Experts - Powered By VFP8
Robert Hoogstraat
is set to x:\Program Files\Common Files\MSSoap\Binaries\SOAPISAP.dll, with
verbs limited to GET, POST, HEAD and script engine checked.
On our W3K Enterprise Server with IIS6 and Soap v3/VFP8, the IIS App mapping
for .wsdl is set to x:\Program Files\Common
Files\MSSoap\Binaries\SOAPIS30.dll, with verbs limited to GET, POST, HEAD
and script engine checked.
These settings works for me.
--
Robert Hoogstraat
Eric den Doop
You wrote on Wed, 14 May 2003 18:13:17 -0400:
RH> On our W3K Enterprise Server with IIS6 and Soap v3/VFP8, the IIS App
RH> mapping for .wsdl is set to x:\Program Files\Common
RH> Files\MSSoap\Binaries\SOAPIS30.dll, with verbs limited to GET, POST,
RH> HEAD and script engine checked.
RH> These settings works for me.
I used the soapvdir (or something) batch program that is in the
\mssoap\binaries folder to 'register' a virtual web with Soap. This approach
is described in the documents that are part of the Web Services sample that
ship with VFP. I checked the mappings on the server and they are identical
to your W2K3 settings. Any other ideas?
Robert Hoogstraat
What exactly is the error and where/when does this error surface? Is it in
VFP8 when building your dll, or in the VFP8 web services publisher wiazrd ,
or the SoapVDri batch file, or ? Can you provide the steps to re-create the
error?
--
Robert
Eric den Doop
You wrote on Thu, 15 May 2003 09:43:08 -0400:
RH> Hi Eric,
RH> What exactly is the error and where/when does this error surface? Is
RH> it in VFP8 when building your dll, or in the VFP8 web services
RH> publisher wiazrd , or the SoapVDri batch file, or ? Can you provide
RH> the steps to re-create the error?
Yes I can.
On my WinXP dev box, I have a small test project called Test. In the
project, there is only one small PRG called webservices.prg.
<vfp_code>
* Class Hierarchy
* ***************
* XMLAdapter
* --- TESTXMLAdapter
* --- SoapService
DEFINE CLASS TESTXMLAdapter AS XMLAdapter
c_database = "\\andromeda\testsoap\data\testsoap.dbc"
PROCEDURE Init
SET EXCLUSIVE OFF
SET DATE MDY
SET DELETED ON
ENDPROC
PROCEDURE OpenDatabase AS Boolean
OPEN DATABASE (this.c_database) SHARED
RETURN .T.
ENDPROC
ENDDEFINE
DEFINE CLASS SoapService AS TESTXMLAdapter OLEPUBLIC
PROCEDURE GetSomeData as String
LOCAL lcRetval as String
this.OpenDatabase()
SELECT * FROM customer INTO CURSOR curCustomer NOFILTER READWRITE
this.addtableschema("curCustomer")
lcRetval = ""
this.ToXML("lcRetval")
USE IN SELECT("curCustomer")
RETURN lcRetval
ENDPROC
ENDDEFINE
</vfp_code>
As you can see, there are no fancy things in the class.
I compile this code to a MTDLL and copy the test.dll file to
\\andromeda\testsoap. On the Win2k server (SP3, latest hotfixes, Exchange
2000 latest SP, VS.NET2003 and VFP8), I issue REGSVR32 test.dll to register
the com server. Note: this server has a full copy of VFP8 and the SOAP 3.0
Toolkit, and I am the Administrator on that box. Also note that the IIS web
services are running fine on this machine. The DLL and SOAP are working fine
on the XP box.
On the Win2k IIS, I created a Virtual Directory called "soap" which points
to the c:\testsoap\wsdl folder. This is the same folder as
\\andromeda\testsoap. The server folder looks like this:
c:\testsoap
c:\testsoap\test.dll
c:\testsoap\wsdl
c:\testsoap\data\*.dbf / *.fpt etc.
I registered this Virtual Dir with the soapvdir command.
On the server, I launced VFP8 and opened the Web Services wizard from the
Tools\Wizards menu. In the Wizard, I located the test.dll and selected the
SoapService class. The Listener URI is set to http://andromeda/soap/ and the
Files Location is set to c:\testsoap\wsdl, ISAPI and I selected only the
GetSomeData() on the Methods tab. If I don't get the error "Error generating
WSDL files", then I get the error that was posted in a previous message in
this thread. Now the really weird thing is that I was able to run a VFP8 web
service when I copied the WSDL files from my development machine on to the
server. I did hack the WSDL file contents so that they were pointing to the
andromeda server instead of the dev box. This did not work with VFP8 as the
SOAP client, but it did work with a small VB.NET test program that I wrote.
Anyway, if I try to access the wsdl file by entering it in the IE address
bar or when I try to connect to it using VFP, I get this error in the Win2k
event log:
"The server failed to load application '/LM/W3SVC/1/Root/soap'. The error
was 'The application called an interface that was marshalled for a different
thread"
I talked to a few other SOAP+VFP programmers and they all downgraded to
SOAP2 and VFP7. This is not an option for me because I need to use some of
the new VFP8 features.
One more thing: compiling the project on the server box didn't help either.
Robert Hoogstraat
server? Robert.
Eric den Doop
You wrote on Thu, 15 May 2003 12:41:22 -0400:
RH> Thanks Eric. What happens if you compile test.dll as a single threaded
RH> com server? Robert.
That made no difference. Even when I try to access the WSDL in a browser
window, just like you can access http://www.foxcentral.net/foxcentral.wsdl,
nothing happens. But when I remove the mapping to the SOAPISAP.dll file in
IIS, then I can access the WSDL file. Of course, my web services don't work.
I think this is a SOAP 3 issue and not related to VFP.
Robert Hoogstraat
to is then soapis30.dll. SOAP v2 uses soapisap.dll.
Btw, I tested your sample on a W3KE server with SOAP3 and VFP8 without
errors.
Robert
"Eric den Doop" <ericd...@xspamblockxfoxite.com> wrote in message
news:u1$NgnwGD...@TK2MSFTNGP12.phx.gbl...
Eric den Doop
You wrote on Thu, 15 May 2003 14:10:44 -0400:
RH> Did you not say you are using SOAP v3? The corresponding dll to map
.wsdl
RH> to is then soapis30.dll. SOAP v2 uses soapisap.dll.
Yeah sorry you're right. My mistake. I am using SOAP3.
RH> Btw, I tested your sample on a W3KE server with SOAP3 and VFP8 without
RH> errors.
Do you have any special settings for the IUSR / IWAM accounts?
Robert Hoogstraat
I did discover the error "Registered: There was a problem accessing the
Listener URI specified for
the WSDL file." when processing the Web Service Publisher, can be caused by
a file path mismatch between the virtual directory and file location
settings on the advanced/options tab.
Robert
Eric den Doop
You wrote on Thu, 15 May 2003 14:40:28 -0400:
OK, I managed to fix this problem.
FIX: ASP.NET Does Not Work with the Default ASPNET Account on a Domain
Controller
http://support.microsoft.com/default.aspx?scid=kb;enus;q315158
The error message that is discussed in this article, showed up when I tried
to use some ASP.NET pages on the same server. For some reason, the fix that
is provided in this article, also fixed the SOAP issue. Great! I'm gonna
have a lot of fun with SOAP.
datal...@gmail.com
I have the same problem, when i try to publish the web service the wizard say:
Guillermo Gimenez
Luque - Paraguay