PDA

View Full Version : IIS 404 error when accessing wso on Windows 2003 Server



Coby Sparks
9-Mar-2005, 09:08 AM
We have just loaded a webapp on a Windows 2003 server. The .asp pages run
fine but when we try to access a .wso it gets a 404 page not found error.

It does this on the DAC sample testservice.wso also.

I found some articles in the knowledge base about making sure you use the
Web Application Adminstrator to create the virtual directory so that IIS
understands the .wso extension. I recreated the application in the
adminstrator but it didn't change the results.

Any help would be appreciated.

Coby

Knut Sparhell
9-Mar-2005, 09:20 PM
Coby Sparks wrote:
> We have just loaded a webapp on a Windows 2003 server. The .asp pages run
> fine but when we try to access a .wso it gets a 404 page not found error.

You have to map the .wso extension to the "X:\Program Files\Visual
DataFlex <version>\Bin\waswsvc.dll" under the configuration button for
the application, in IIS Manager. This must be done for each application
root for each web site that uses VDF Web Services.

--
Knut Sparhell, Norway

Coby Sparks
10-Mar-2005, 08:48 AM
Knut,

I checked and the .wso was already under the configuration button. This must
have been setup with DAC's wizard.

Any other ideas of what I can check for?

Thanks,
Coby


"Knut Sparhell" <knut@sparhell.no> wrote in message
news:sAzDAfRJFHA.1912@dacmail.dataaccess.com...
> Coby Sparks wrote:
>> We have just loaded a webapp on a Windows 2003 server. The .asp pages run
>> fine but when we try to access a .wso it gets a 404 page not found error.
>
> You have to map the .wso extension to the "X:\Program Files\Visual
> DataFlex <version>\Bin\waswsvc.dll" under the configuration button for the
> application, in IIS Manager. This must be done for each application root
> for each web site that uses VDF Web Services.
>
> --
> Knut Sparhell, Norway

Knut Sparhell
10-Mar-2005, 10:14 PM
Coby Sparks wrote:

> I checked and the .wso was already under the configuration button. This must
> have been setup with DAC's wizard.
>
> Any other ideas of what I can check for?

Forgive me for being a little sceptical here. Did you look under the
right virtual folders application? Status 404 is exactly the status one
would expect if is this .wso is not mapped. Try removing it and
remapping, using the browse button to locate the dll.

Then use IIS Manager itself to find the .wso file, then choose browse
from the right click menu.

When you do this browse, IIS will first look at the extension. If the
extension is allowed, then it will either handle it internally (.html)
or load the mapped executable. If not mapped, it will give a 404, even
if the file is actually there.

Other rare possibilities is that the file is not allowed to read by
IUSR_<machine>, but then it would ask for credentials.

Try renaming the file to .txt, and the contents will show i the browser.
If then renamed back to .wso and it gives 404, it just has to be the
mapping that causes this. .txt is a known extension, .wso is not.

--
Knut Sparhell, Norway

Coby Sparks
11-Mar-2005, 07:58 PM
Hi Knut,

I removed the virtual directory and added it again with the Web Wizard. It
still didn't work. I then uninstalled VDF10.1 and re-installed it.

Things started working fine after the re-install. I am not sure what I did
to cause it to not work but all is fine now.

Thanks for the help!
Coby
"Knut Sparhell" <knut@sparhell.no> wrote in message
news:OzP8yheJFHA.7560@dacmail.dataaccess.com...
> Coby Sparks wrote:
>
>> I checked and the .wso was already under the configuration button. This
>> must have been setup with DAC's wizard.
>>
>> Any other ideas of what I can check for?
>
> Forgive me for being a little sceptical here. Did you look under the
> right virtual folders application? Status 404 is exactly the status one
> would expect if is this .wso is not mapped. Try removing it and
> remapping, using the browse button to locate the dll.
>
> Then use IIS Manager itself to find the .wso file, then choose browse from
> the right click menu.
>
> When you do this browse, IIS will first look at the extension. If the
> extension is allowed, then it will either handle it internally (.html) or
> load the mapped executable. If not mapped, it will give a 404, even if
> the file is actually there.
>
> Other rare possibilities is that the file is not allowed to read by
> IUSR_<machine>, but then it would ask for credentials.
>
> Try renaming the file to .txt, and the contents will show i the browser.
> If then renamed back to .wso and it gives 404, it just has to be the
> mapping that causes this. .txt is a known extension, .wso is not.
>
> --
> Knut Sparhell, Norway