|
Home > Archive > IIS Server > December 2005 > HTTP 404 error when deploying an ASP.NET 2.0 Web Service
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
HTTP 404 error when deploying an ASP.NET 2.0 Web Service
|
|
| David Wang [Msft] 2005-12-28, 2:54 am |
| ASP.Net is not enabled in "Web Service Extensions". Enable it, either with
IIS Manager UI or aspnet_regiis.exe.
You may want to search for that log entry on the web, and you should also
find the answer.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Ray Stevens" <nfr@nospam.com> wrote in message
news:u0GK6vzCGHA.1816@TK2MSFTNGP11.phx.gbl...
>I am able to sucessfully build and test a ASP.NET 2.0 application on my
>local test machine. However, when I deploy it to a test server I get a 404
>error. Attached are IIS web log snippets showing the failed service.asmx
>web service query and a successful default.htm query, although BOTH are in
>the root directory.
>
> Anybody know what might be causing this?
>
>
| |
| Ray Stevens 2005-12-28, 6:10 pm |
| It appears that Windows Server 2003 is a little different. I did enable the
Web Service extension for v2.0 and am now getting the following error:
Server Error in '/' Application.
--------------------------------------------------------------------------------
The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write
access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
Files'.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.
Exception Details: System.Web.HttpException: The current identity (NT
AUTHORITY\NETWORK SERVICE) does not have write access to
'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
"David Wang [Msft]" <someone@online.microsoft.com> wrote in message
news:Ob8wiG3CGHA.4080@TK2MSFTNGP09.phx.gbl...
> ASP.Net is not enabled in "Web Service Extensions". Enable it, either with
> IIS Manager UI or aspnet_regiis.exe.
>
> You may want to search for that log entry on the web, and you should also
> find the answer.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> //
>
> "Ray Stevens" <nfr@nospam.com> wrote in message
> news:u0GK6vzCGHA.1816@TK2MSFTNGP11.phx.gbl...
>
>
| |
| Ray Stevens 2005-12-28, 6:10 pm |
| OK... I am becoming increasingly uncomfortable about the proper way to
configure IIS on Windows Server 2003 to support Web Services. However, I did
take a guess and granted Network Service write access to the temp directory.
Now the web service test does come up with the "Invoke" option when using
"//localhost" but comes up without the Invoke option when access remotely
using the server name.
I am not sure I am configuring this correctly.
"Ray Stevens" <nfr@nospam.com> wrote in message
news:uUpi2y8CGHA.3820@TK2MSFTNGP12.phx.gbl...
> It appears that Windows Server 2003 is a little different. I did enable
> the Web Service extension for v2.0 and am now getting the following error:
>
> Server Error in '/' Application.
>
> --------------------------------------------------------------------------------
>
>
>
> The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write
> access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
> Files'.
>
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about the error and where it originated in the code.
>
>
>
> Exception Details: System.Web.HttpException: The current identity (NT
> AUTHORITY\NETWORK SERVICE) does not have write access to
> 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.
>
>
>
> Source Error:
>
>
>
> An unhandled exception was generated during the execution of the current
> web request. Information regarding the origin and location of the
> exception can be identified using the exception stack trace below.
>
>
> "David Wang [Msft]" <someone@online.microsoft.com> wrote in message
> news:Ob8wiG3CGHA.4080@TK2MSFTNGP09.phx.gbl...
>
>
| |
| David Wang [Msft] 2005-12-29, 7:50 am |
| IIS6 Security is different from prior IIS versions. Just about everything
else should work the same.
It sounds like your server ran DCPROMO after installing IIS and ASP.Net
because that would wipe away a lot of ACLs and leave the installation in the
non-functional state you currently find.
You want to DCPROMO, then install IIS6, then install ASP.Net, and everything
should be automatically configured correctly. If you do not DCPROMO first,
random things can be broken and no good way to fix it.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Ray Stevens" <nfr@nospam.com> wrote in message
news:OzQXyP9CGHA.1124@TK2MSFTNGP10.phx.gbl...
> OK... I am becoming increasingly uncomfortable about the proper way to
> configure IIS on Windows Server 2003 to support Web Services. However, I
> did take a guess and granted Network Service write access to the temp
> directory. Now the web service test does come up with the "Invoke" option
> when using "//localhost" but comes up without the Invoke option when
> access remotely using the server name.
>
> I am not sure I am configuring this correctly.
>
> "Ray Stevens" <nfr@nospam.com> wrote in message
> news:uUpi2y8CGHA.3820@TK2MSFTNGP12.phx.gbl...
>
>
|
|
|
|
|