Hi Robert, Admittedly I haven't followed this thread word-for-word, but don't forgot you have to enable access to the plugin under Windows 2003/IIS 6.0
http://custom.softwarefor.net/projects/screenshots/539.aspx Otherwise IIS will return a 404. Hope that helps. ~ Scott Cadillac ~ 403-254-5002 ~ [EMAIL PROTECTED] ~ Custom Software for Business http://custom.softwarefor.net ~ The XML-Extranet Partnership ~ P.O. Box 69006 RPO Bridlewood SW Calgary, Alberta Canada T2Y 4T9 > -----Original Message----- > From: Robert Garcia [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 22, 2005 1:07 AM > To: [email protected] > Subject: Re: Witango-Talk: Simple SOAP instructions > > It is pretty much a default install of IIS on Enterprise, no PHP or > anything else, just witango. I will try to setup on a clean machine > tomorrow, just to see. > > I know that the response envelope I pasted is wrong below, I can hit > the webservice correct with the taf, and from realbasic, and get the > current time, and all works as promised no problem. But only when > using apache. Once I got apache/witango running, it took me about 10 > mins to get the webservices working. > > No matter how I setup IIS, I just keep getting page not found error, > when I try to hit the URL, http://domain/whatsthetime.wws. When I > have it working in apache, if I just open a web browser and put in > that URL, I know it is a malformed soap request, but it doesn't give > me a Page Not Found error. It gives me a soap request error. So now > that gives me at least a quick test. If I set up right, and just hit > the webservice url, I should AT LEAST get a soap request error, and > not a page not found. > > I just hit www.witango.com and developer.witango.com, and they are > both running IIS 5.0. Has this been tested and run on IIS 6, with > windows 2003? > > I even turned the default web site in IIS 6 back to c:\inetpub > \wwwroot, and put the webservices in there, and used localhost, and > it still doesn't work. > > Anyway, I am not new to webservices, or soap requests/responses. > Either there is something about my IIS 6 installation that is a > problem, or maybe a bug with IIS 6. The only thing I can think of > trying next is to load witango on a clean server, without any > alteration to IIS. > > -- > > Robert Garcia > President - BigHead Technology > VP Application Development - eventpix.com > 13653 West Park Dr > Magalia, Ca 95954 > ph: 530.645.4040 x222 fax: 530.645.4040 > [EMAIL PROTECTED] - [EMAIL PROTECTED] > http://bighead.net/ - http://eventpix.com/ > > On Jun 21, 2005, at 11:44 PM, Customer Support wrote: > > > Robert, > > It is the exact setup we are running. See the last email > we sent. > > You can try it against the www.witango.com and > > developer.witango.com sites both running on the same machine in > > separate virtual directories. > > > > If you are getting the Fault element returned in the SOAP envelope > > then the SOAP request is being passed through from IIS to the > > server but it would seem to be malformed. The Witango server is > > trying to process it but cannot understand the request. Is there > > anything that is installed in IIS that may be changing headers or > > doing a rewrite on anything. Custom headers, etc. > > > > > > Witango Support > > > > > > On 22/06/2005, at 4:26 PM, Robert Garcia wrote: > > > > > >> Well, no matter what can't get to work on IIS 6, windows 2003, > >> anyone get it to work in that environment? > >> > >> I quickly setup apache2, and put the webservice in the htdocs > >> folder, and so the webservices.ini file was relative to > the htdocs > >> folder, and everything worked. > >> > >> If you just hit the url http://www.mysite.com/myws.wws it returns > >> page not found with IIS, but returns: > >> > >> > >> <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope"> > >> > >> <env:Body> > >> <env:Fault> > >> <mns:faultstring xmlns:mns="witangowebservice">Error > in soap > >> request.No soap request</mns:faultstring> > >> </env:Fault> > >> </env:Body> > >> > >> </env:Envelope> > >> > >> > >> with apache2. > >> > >> It seems that to work, the webservices.ini needed to be relative > >> to the main server root, like htdocs. But IIS has a > different root > >> for every site. > >> > >> Is it possible that witango reads a DEFAULT directory from the > >> registry? Like c:\inetpub\wwwroot? > >> > >> > > > > > ______________________________________________________________ > ________ > > __ > > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > > > > > ______________________________________________________________ > __________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
