WCF not working on Windows 2003 IIS
Hi, I downloaded the latest September CTP WinFX Runtime Components and WinFX SDK, and tried to run an Indigo simple sample. However, when I use IIS I receive 404 error when browsing to the service.svc file.
I found that I needed to do:
* aspnet_regiis -i
* xws_reg -i
* cscript InstallIndigo.js c:\windows\microsoft.net\framework\v2.0.50215
However, the last step gives me an error like this:
Reserving the HTTP namespace...
Error *** : A runtime error occurred executing command - Some or all identity references could not be translated.
...Deleting registry keys.
And I cannot get my Indigo services running. What can I do to make it run? Is there any other way to register Indigo with IIS?
[835 byte] By [
serras] at [2008-2-15]
Hi Serras,
This sounds like a configuration problem on your machine. Let's try to narrow it down.
What I would do is the following:
1) Create a new vdir
2) Add a simple aspx page to it
3) Try to Browse to the aspx page using IE
Once you have done this, either you will be able to browse to the aspx page or not. If you are not able to, then that would mean that ASP .NET is not configured correctly on your machine. Here is what I would do to configure ASP .NET on the machine.
1) make sure IIS is running
2) Run aspnet_regiis -i (as you have indicated below)
3) In the MMC, Traverse to Web Service Extensions under IIS and change the status of ASP.NET vX.X.XXXXX to Allowed
4) And then try traversing to the aspx page.
If after these steps you are able to traverse to the .aspx page, try traversing to the .svc. If not, please reply back with your experience and we'll try to debug it further.
Thanks,
ash
I finally solved the problem by creating a new web site using Visual Studio 2005. However, I cannot realize why it continues not working even though I changed the runtime version in MMC, and re-run aspnet_regiis. The ASPX pages work OK, the only problem is with .SVC files.
I have replied this question on the newsgroup microsoft.public.windows.developer.winfx.indigo. The original problem was because ASP.NET ISAPI was not enabled by default. The documentation was not accurate. There are two ways to fix the problem:
1) Rerun aspnet_regiis.exe -i -enable
Or
2) Going through the following steps:
(1) Open IIS Manager.
(2) Expand your machine node.
(3) Click on "Web Service Extensions".
(4) Find "ASP.NET v2.0.xxxxx". The current state would be "Prohibited". Click on "Allow" will resolve the issue.
It's weird that "creating a new web site" would solve the problem.
Please let me know if this works.
Thanks,
Wenlong
