Hi,
This particular forum is a first for me. This seems to be a problem with setting up Windows 2003, but may in fact be a programming issue.
We are trying to implement what had been a working web service using SOAP 3.0 on a Windows 2003 Server. It seems like SOAP is not working--even though we've installed ASP.net support for IIS as well as the .net framework on the server. A suspicious symptom is that the "Uses SOAP" checkbox on the COM+ application properties is DISABLED. How do I enable that option?
A test call to the web service from another machine yields the following error message:
We think that the ASP listener (created by the SOAP 3 WSDL Generator) is what is actually failing. It looks like the offending line of code is likely to be:
Clearly, I'm missing something here, because there doesn't appear to be an MSSOAP.dll anywhere on the server!
Here's some more pertinent information:
The web service application is written in Visual Foxpro 7 and is installed on the server as a COM+ server application.
The WSDL Generator from the SOAP 3.0 Toolkit was used to generate the .WSDL, .WSML, and the ASP listener.
I'm using an ASP listener for the web service as a means to insure that global.asa fires when IIS handles the request. The web application components are instantiated in Global.asa.
We've installed (and reinstalled) ASP.Net for IIS, UDDI, the .net framework, and multiple Windows 2003 updates.
So, is there something that we should have installed on the 2003 server to support SOAP? Or does using SOAP via the .net framework look completely different?
Thanks in advance. Any help would be greatly appreciated.
Ron
This particular forum is a first for me. This seems to be a problem with setting up Windows 2003, but may in fact be a programming issue.
We are trying to implement what had been a working web service using SOAP 3.0 on a Windows 2003 Server. It seems like SOAP is not working--even though we've installed ASP.net support for IIS as well as the .net framework on the server. A suspicious symptom is that the "Uses SOAP" checkbox on the COM+ application properties is DISABLED. How do I enable that option?
A test call to the web service from another machine yields the following error message:
We think that the ASP listener (created by the SOAP 3 WSDL Generator) is what is actually failing. It looks like the offending line of code is likely to be:
Clearly, I'm missing something here, because there doesn't appear to be an MSSOAP.dll anywhere on the server!
Here's some more pertinent information:
The web service application is written in Visual Foxpro 7 and is installed on the server as a COM+ server application.
The WSDL Generator from the SOAP 3.0 Toolkit was used to generate the .WSDL, .WSML, and the ASP listener.
I'm using an ASP listener for the web service as a means to insure that global.asa fires when IIS handles the request. The web application components are instantiated in Global.asa.
We've installed (and reinstalled) ASP.Net for IIS, UDDI, the .net framework, and multiple Windows 2003 updates.
So, is there something that we should have installed on the 2003 server to support SOAP? Or does using SOAP via the .net framework look completely different?
Thanks in advance. Any help would be greatly appreciated.
Ron
