Problems after upgrading to VS 2008 SP1 (& .Net 3.5 SP1)

Vote:
 

After I installed VS2008SP1 I got this an error in Vista/IIS7.

 I get this when running in Integrated Pipeline:

[PlatformNotSupportedException: The DefaultHttpHandler.BeginProcessRequest method is not supported by IIS integrated pipeline mode.]
System.Web.DefaultHttpHandler.BeginProcessRequest(HttpContext context, AsyncCallback callback, Object state) +2871035
EPiServer.Web.StaticFileHandler.BeginProcessRequest(HttpContext context, AsyncCallback callback, Object state) +120
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +8674594
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155

Integrated have alway worked before... I dont know what else has changed (than installing VS2008SP1/.Net 3.5SP1)

 When changing to Classic mode, I get this:

[HttpException (0x80004005): Failed to Execute URL.]
System.Web.Hosting.ISAPIWorkerRequestInProcForIIS6.BeginExecuteUrl(String url, String method, String childHeaders, Boolean sendHeaders, Boolean addUserIndo, IntPtr token, String name, String authType, Byte[] entity, AsyncCallback cb, Object state) +2004965
System.Web.HttpResponse.BeginExecuteUrlForEntireResponse(String pathOverride, NameValueCollection requestHeaders, AsyncCallback cb, Object state) +390
System.Web.DefaultHttpHandler.BeginProcessRequest(HttpContext context, AsyncCallback callback, Object state) +223
EPiServer.Web.StaticFileHandler.BeginProcessRequest(HttpContext context, AsyncCallback callback, Object state) +120
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +8674594
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155


 Any ideas?

#22685
Aug 12, 2008 12:37
Vote:
 

I forgot to specify that this is occuring only on files that is handled by the StaticFileHandler.

Normal requests to .aspx-pages is OK.

#22686
Aug 12, 2008 12:38
Vote:
 
And after some more investigation it seems that this error only occurs when there is a request to a file that exists on the filesystem. Files in EPiServers FileManager is ok.
#22689
Aug 12, 2008 13:25
Vote:
 
Have you had a look at Ruwn Jin's blog about EPiServer File links on Vista? http://labs.episerver.com/en/Blogs/Ruwen/Dates/112201/112202/112449/
#22722
Aug 13, 2008 11:46
Vote:
 
I have the same problem after upgrading to SP1 :-(
#22770
Aug 15, 2008 10:42
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.