silly me it is 2003. Mapping then. do a search on web service 2003 on leafe.com profox archives and I think something there may shed a light on the problem Allen
This was a reply from Derek in the Archives that fixed me up. MSSOAP was never included in a Windows server product, I don't believe-- it's always something you have to install on W2K, XP, and 2003. It is installed by your development environment(VFP), however... Anyways, put that mapping back in(you need it). Also, in IIS, set 'allow unknown isapi extensions' to 'allow'. This will allow it to work. Without it, IIS6 returns INCORRECT 404's with absolutely NO CLUE ANYWHERE what is happening(not the event log, the W3SVC log, or to the end user!)-- it should be returning 500's and not 404's... Anyways, this is likely your problem. I'm well-versed on the tribulations of VFP web services, so if you have any other questions, please ask-- I've been on vacation, hence the long time to reply. Thanks. No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.503 / Virus Database: 269.16.8/1153 - Release Date: 26/11/2007 21:08 _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
