Welcome Guest Search | Active Topics | Sign In | Register

AJAX Uploader and IIS7 Options
Web Cotrols
Posted: Wednesday, August 4, 2010 4:40:30 PM
Rank: Member
Groups: Member

Joined: 5/6/2010
Posts: 18
Hello,
We used AJAX Uploader under IIS6 before and it's worked fine. Now we are migrating to server with IIS 7 and upload control stop to work. Looks like it doesn't sent post back or post back is blocked by IIS after clicking on upload start button. We reviewed all proposed solutions on this forum for fixing IIS 7 issue but without result.

Following code initiate postback instead of upload btn:

Code: HTML/ASPX
<form id="Form1" runat="server" 
    method="post" enctype="multipart/form-data">
    <input type="file" size="50"> 
    <input type="submit" value="Submit">
</form>


We are using now EO v 7.0.62.2 because of one not fixed critical for us issue in EO v8 .
Probably You already fixed the same configuration issues.


Could you please help us to fix this issue?
Thank you.

Here is our config file:
In IIS 7 we are using classic app pool.

Code: XML

<configuration>
	<configSections>
		<sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
			<sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
				<section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication" />
				<sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
					<section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="Everywhere" />
					<section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication" />
					<section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication" />
					<section name="roleService" type="System.Web.Configuration.ScriptingRoleServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication" />
				</sectionGroup>
			</sectionGroup>
		</sectionGroup>
  </configSections>   
    
  	<system.web>

		<httpRuntime maxRequestLength="2097151" executionTimeout="21600" useFullyQualifiedRedirectUrl="true" />
		<!-- 
            Set compilation debug="true" to insert debugging 
            symbols into the compiled page. Because this 
            affects performance, set this value to true only 
            during development.
        -->
		<compilation debug="true">
			<assemblies>
				<add assembly="System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
				<add assembly="System.Data.DataSetExtensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
				<add assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
				<add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
			</assemblies>
		</compilation>
		<!--
            The <authentication> section enables configuration 
            of the security authentication mode used by 
            ASP.NET to identify an incoming user. 
        -->
		<authentication mode="Windows" />
		<!--
            The <customErrors> section enables configuration 
            of what to do if/when an unhandled error occurs 
            during the execution of a request. Specifically, 
            it enables developers to configure html error pages 
            to be displayed in place of a error stack trace.                  
        
        -->
		<customErrors mode="Off" />
		<trace enabled="false" />
		<pages>
			<controls>
				<add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
				<add tagPrefix="asp" namespace="System.Web.UI.WebControls" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
			</controls>
		</pages>
		<httpModules>
			<add name="EOWebRuntime" type="EO.Web.Runtime,EO.Web" />
		</httpModules>
		<httpHandlers>
			<remove verb="*" path="*.asmx" />      
			<add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
			<add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
			<add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" validate="false" />
		</httpHandlers>
	</system.web>
	<system.codedom>
		<compilers>
			<compiler language="c#;cs;csharp" extension=".cs" warningLevel="4" type="Microsoft.CSharp.CSharpCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
				<providerOption name="CompilerVersion" value="v3.5" />
				<providerOption name="WarnAsError" value="false" />
			</compiler>
		</compilers>
	</system.codedom>

	<!-- 
        The system.webServer section is required for running ASP.NET AJAX under Internet
        Information Services 7.0.  It is not necessary for previous version of IIS.
    -->
	<system.webServer>
    <security>
      <requestFiltering>
        <!-- Increased maxAllowedContentLength from default of 300MB. -->
        <requestLimits maxAllowedContentLength="2147483647"></requestLimits>
      </requestFiltering>
    </security>
		
		<modules>
			<add name="EOWebRuntime" type="EO.Web.Runtime,EO.Web" />
			<remove name="ScriptModule" />
			<add name="ScriptModule" preCondition="managedHandler" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
		</modules>
		<handlers>
			<remove name="WebServiceHandlerFactory-Integrated" />
			<remove name="ScriptHandlerFactory" />
			<remove name="ScriptHandlerFactoryAppServices" />
			<remove name="ScriptResource" />
			<add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
			<add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
			<add name="ScriptResource" preCondition="integratedMode" verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
		</handlers>
	</system.webServer>
	<runtime>
		<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
			<dependentAssembly>
				<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" />
				<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
			</dependentAssembly>
			<dependentAssembly>
				<assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" />
				<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
			</dependentAssembly>
		</assemblyBinding>
	</runtime>
</configuration>
eo_support
Posted: Wednesday, August 4, 2010 4:46:02 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,194
Hi,

Your configuration file looks fine. Do you have the website online so that we can take a look?

Thanks!
Web Cotrols
Posted: Wednesday, August 4, 2010 4:54:56 PM
Rank: Member
Groups: Member

Joined: 5/6/2010
Posts: 18
eo_support wrote:
Hi,

Your configuration file looks fine. Do you have the website online so that we can take a look?

Thanks!


Please use this URL:

eo_support
Posted: Wednesday, August 4, 2010 5:14:26 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,194
Hi,

The original error message is:

Access to the path 'C:\inetpub\wwwroot\WellEZ_FUDASite_Test\eo_upload\eouploader.5b33a4e1-f99f-4a65-a09c-0e5256b0a84f.status' is denied.

Please check your file system permission to correct that issue. For troubleshooting purpose, you may also want to try the uploader in a blank page without any other code. That way it should give you the clear message when it fails.

Thanks!
Web Cotrols
Posted: Wednesday, August 4, 2010 5:17:41 PM
Rank: Member
Groups: Member

Joined: 5/6/2010
Posts: 18
Thanks for Quick answer.
Which folder permissions should be for eo_upload ?
With IIS 6 it works with the following:

Write access for System
IIS_USER and IIS_WPG - read access

Is this correct ?

Thank you!
eo_support
Posted: Wednesday, August 4, 2010 5:22:06 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,194
Web Cotrols wrote:
Thanks for Quick answer.
Which folder permissions should be for eo_upload ?


Your application needs to be able to write that folder and currently it can not. You can write some test code to create files in that directory. If that works, then the uploader should work. Otherwise it won't.

Thanks
Web Cotrols
Posted: Wednesday, August 4, 2010 5:27:55 PM
Rank: Member
Groups: Member

Joined: 5/6/2010
Posts: 18
It's working now!

Probably following will be helpful for someone:

WSS_WPG should be added in case IIS 7 with full access permissions.
In IIS 6 it works without it.

Thank You a lot for your help!


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.