We have had an working installation of R2 CTP before. But due to some visual studio crashes, we tryed to get a fresh install of the R2 CTP, and now this error shows up.
Could it be a IIS issue? we tryed to install the CMS SP2 and it works perfectly.
Also using Win XP SP2, with IIS5.1
Ah... reading the fine print helps - see download page and Known Limitations:
"We only support IIS 6 installation using EPiServer CMS Manager 126.96.36.199"
It seems that we fixed a bug with a similar description yesterday so hopefully this will not be an issue any more with the next release.
I use "XP PRO IIS Admin" tool to enable creation of sites within XP. I was using it for installation of EPiServer 4.x and 5 R1 without any problem.
After few testing I succeded to avoid this kind of error:
- Install R2 CTP site via EPiServer Manager 188.8.131.52. For site URL I put for example "http://testsite".
- Open it in VS 2008, and adjust it to use ".NetFramework 3.5" and fix errors related to project references
- Save and rebuild project
- Create user within "ASP Net Configuration" site from VS 2008
- Open IIS, stop all sites and start adequate site that you created during step 1
- Open IIS and delete the .* mapping and set 404 error to point on "/util/notfound.aspx"
- Open admin site and continue installation of public templates (don't worry about errors related to "Page not found")
- Open admin site again and do "Rebuild Name for Web Addresses"
- Open IIS and insert .* mapping
- Restart IIS
- Open site in new browser (it should be displayed without problems)
By this you can continue with testing and developing of web application based on R2 CTP in XP (IIS 5.1). I tested this way at 2nd September - today (used installation of R2 CTP from http://world.episerver.com/en/Download/Items/EPiServer-CMS/Version-5/EPiServer-CMS-5-R2-CTP/).
Using Fiddler to debug: I get 500 errors on css-files and on episerverscriptmanager.js.
If I try to browse a css file directly, I get the following error:
System.InvalidOperationException: Etag is already set.
The problem seems to be related to IIS caching.
Any tips to what could cause the error?
- I'm developing on Win XP
- .NET 3.5 is installed
- Wildcard mapping is set in IIS