> It is to run on a windows 2003 server. It seems that Microsoft in their > wisdom are trying like mad to force us to use .net, and they have removed > the Soap ability, at least as standard, from that server. I have googled and > it says in one place to add .wsdl to the mapping and point it to the > mssoapis30.dll. Ive tried that and you can no longer even see the wsdl file
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. -- Derek _______________________________________________ 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.
