Á
Ágúst
Hi
I have a webserver which is running a ASP.NET webservice
and a ASP.NET webapplication. The webservice is both used
by the webapplication and by ca.100 windowsforms clients
in our company. Several weeks ago the webservice stopped
working, the error displayed is:
---
Error message 401.2.: You do not have permission to view
this directory or page using the credentials you
supplied. Contact the Web server's administrator for help.
---
It seemed that when the server was virus-scanned the
webservice went down with the above error, the only way
to resume was to restore a previous system state from our
backup.
After some experiments we have found out that if the
virtual directory is configured to use a specific account
the webserivce works after a succsessful login. But we
have not been able to let it run under a anonymus
IUSR_MYMACHINE account, it always shows the above
security error.
What I find strange is that there are several ASP.NET
pages on this server, they all run ok, it is just this
webservice which is throwing this error.
Any hints warmly welcomed, Ágúst from Iceland
I have a webserver which is running a ASP.NET webservice
and a ASP.NET webapplication. The webservice is both used
by the webapplication and by ca.100 windowsforms clients
in our company. Several weeks ago the webservice stopped
working, the error displayed is:
---
Error message 401.2.: You do not have permission to view
this directory or page using the credentials you
supplied. Contact the Web server's administrator for help.
---
It seemed that when the server was virus-scanned the
webservice went down with the above error, the only way
to resume was to restore a previous system state from our
backup.
After some experiments we have found out that if the
virtual directory is configured to use a specific account
the webserivce works after a succsessful login. But we
have not been able to let it run under a anonymus
IUSR_MYMACHINE account, it always shows the above
security error.
What I find strange is that there are several ASP.NET
pages on this server, they all run ok, it is just this
webservice which is throwing this error.
Any hints warmly welcomed, Ágúst from Iceland