NeatUpload-trunk.746 Progress.aspx returns 404 Not Found

[Don Adams]

We're trying to upgrade from version 1.2 to 1.3 so we can continue to use the IIS 7.0 Integrated pipeline mode. We're on Windows Server 2008 running IIS 7.0 and .Net 3.5 SP1. We've also had this same problem on IIS 6.0, Windows Server 2003, .Net 3.5 SP1. We're using IE 7.0 for both servers.

I modified the web.config where Progress.aspx is located so that the neatupload element is under system.web element since I was getting the same web.config configuration error as per a previous post on this forum.

We get the following error in our page but part of the output is clipped so I just tried to load the Progress.aspx page directly to get more detailed info. This page loads fine with version 1.2.

On both servers, I see an app_data/NeatUpload_temp directory that was created when I first tried to use this new version.

Any idea what's going on with this error?

Thanks for your help.

 

Server Error in '/' Application.

---

The remote server returned an error: (404) Not Found.

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.Net.WebException: The remote server returned an error: (404) Not Found.

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.

Stack Trace:

[WebException: The remote server returned an error: (404) Not Found.]
            System.Net.WebClient.UploadValues(Uri address, String method, NameValueCollection data) +480
            System.Net.WebClient.UploadValues(String address, NameValueCollection data) +34
            Brettle.Web.NeatUpload.SimpleWebRemoting.MakeRemoteCall(Uri uri, Object[] methodCall) +429
            Brettle.Web.NeatUpload.AdaptiveUploadStateStoreProvider.get_Provider() +211
            Brettle.Web.NeatUpload.AdaptiveUploadStateStoreProvider.Load(String postBackID) +11
            Brettle.Web.NeatUpload.UploadHttpModule.Brettle.Web.NeatUpload.IUploadModule.BindProgressState(String postBackID, String controlUniqueID, IUploadProgressState progressState) +36
            Brettle.Web.NeatUpload.UploadModule.BindProgressState(String postBackID, String controlUniqueID, IUploadProgressState progressState) +40
            Brettle.Web.NeatUpload.ProgressPage.SetupContext() +111
            Brettle.Web.NeatUpload.ProgressPage.OnLoad(EventArgs e) +112
            System.Web.UI.Control.LoadRecursive() +50
            System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627
            

---

Version Information: Microsoft .NET Framework Version:2.0.50727.3031; ASP.NET Version:2.0.50727.3031

[Dean Brettle]

I came across that issue myself a few days ago and have a fix in SVN that will be included in RC2.  In the meantime, if you aren't using a web garden/farm, a workaround is to remove the defaultStateStoreProvider attribute of the <neatUpload> element.

--Dean

[Guest-767]

Thanks for the quick reply.

We aren't running a web garden/farm and we don't have that attribute set. Here is our web.config.

BTW, it looks like the web.config doesn't have CR/LF line endings, but only CR. When using Notepad

 to edit it, I had to manually add in line endings and tabs.

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
 <location path="MultiRequestUploadHandler.ashx">
  <system.web>
   <httpRuntime maxRequestLength="2097151" executionTimeout="3600" useFullyQualifiedRedirectUrl="true" />
   <neatUpload xmlns="http://www.brettle.com/neatupload/config/2008" useHttpModule="true" />
  </system.web>
 </location>
</configuration>

[Dean Brettle]

Sorry, I misspoke.  The workaround is to add the InProcUploadStateStoreProvider in neatUpload/providers in your top-level Web.config and use it as the defaultStateStoreProvider, like this:

<neatUpload ... defaultStateStoreProvider="InProcUploadStateStoreProvider">
  <providers>
    <add name="InProcUploadStateStoreProvider" type="Brettle.Web.NeatUpload.InProcUploadStateStoreProvider,Brettle.Web.NeatUpload" />
  </providers>
</neatUpload>

Again, that belongs in your app's top-level Web.config.

--Dean

[Don Adams]

That didn't seem to have any effect. Here is part of our web.config. Please let me know if I have something missing or incorrect. I also tried making this update in the web.config where the Progress.aspx file is located, but that didn't work either.

Thanks.

 

 <system.web>
     <neatUpload useHttpModule="false" />
     <httpModules>
        <add name="UploadHttpModule" type="Brettle.Web.NeatUpload.UploadHttpModule, Brettle.Web.NeatUpload"   />
     </httpModules>
. . .

 </system.web>

 <location path="Core/Item/upload.aspx">
     <system.web>
        <neatUpload              
                  useHttpModule="true"
                  maxNormalRequestLength="4096"
                  maxRequestLength="10240"
                  defaultStateStoreProvider="InProcUploadStateStoreProvider">
             <httpRuntime maxRequestLength="10240" executionTimeout="900" />
             <providers>
                 <add name="InProcUploadStateStoreProvider" type="Brettle.Web.NeatUpload.InProcUploadStateStoreProvider,Brettle.Web.NeatUpload" />
             </providers>
        </neatUpload>
     </system.web>
   </location>

 

[Dean Brettle]

You want the following (change in bold):

<system.web>
     <neatUpload useHttpModule="false" defaultStateStoreProvider="InProcUploadStateStoreProvider">
             <providers>
                 <add name="InProcUploadStateStoreProvider" type="Brettle.Web.NeatUpload.InProcUploadStateStoreProvider,Brettle.Web.NeatUpload" />
             </providers>
     </neatUpload>
     <httpModules>
        <add name="UploadHttpModule" type="Brettle.Web.NeatUpload.UploadHttpModule, Brettle.Web.NeatUpload"   />
     </httpModules>
. . .

 </system.web>

 <location path="Core/Item/upload.aspx">
     <system.web>
        <httpRuntime maxRequestLength="10240" executionTimeout="900" />
        <neatUpload              
                  useHttpModule="true"
                  maxNormalRequestLength="4096"
                  maxRequestLength="10240"
                  defaultStateStoreProvider="InProcUploadStateStoreProvider">
             <httpRuntime maxRequestLength="10240" executionTimeout="900" />
             <providers>
                 <add name="InProcUploadStateStoreProvider" type="Brettle.Web.NeatUpload.InProcUploadStateStoreProvider,Brettle.Web.NeatUpload" />
             </providers>
        </neatUpload>
     </system.web>
   </location>

[Don Adams]

That fixed it. Thanks!

Now, on to trying to get it working on Windows Server 2008 and IIS 7.0.

[Don Adams]

I got it working on Windows Server 2008 and IIS 7.0 too. The web.config is slightly different due to IIS7.0 and it's Integrated Pipeline mode.

If you see anything wrong in this configuration, please let me know.

Thanks again!

Partial web.config:

 <system.web>
  <neatUpload useHttpModule="false" defaultStateStoreProvider="InProcUploadStateStoreProvider">
              <providers>
                  <add name="InProcUploadStateStoreProvider" type="Brettle.Web.NeatUpload.InProcUploadStateStoreProvider,Brettle.Web.NeatUpload" />
              </providers>
  </neatUpload>
. . .

</system.web>

 <location path="Core/Item/upload.aspx">
      <system.web>
   <httpRuntime maxRequestLength="10240" executionTimeout="900" />
    <neatUpload useHttpModule="true" maxNormalRequestLength="4096" maxRequestLength="10240" />
     </system.web>
 </location>
 
 <system.webServer>
         <modules>
             <add name="UploadHttpModule" type="Brettle.Web.NeatUpload.UploadHttpModule, Brettle.Web.NeatUpload" preCondition="managedHandler" />
         </modules>
         <validation validateIntegratedModeConfiguration="false" />
 </system.webServer>

 

[Dean Brettle]

Looks right to me.

--Dean

[Guest-767]

have the same problem and unable to fix, any help?

[Dean Brettle]

First, make sure you are running the latest version of NeatUpload.  If that doesn't fix it, the problem is probably that the server can't access itself using the same hostname as the client uses.  Try running a browser on the server and using it to access your app.  What URL do you need to use to make that work?  You can either change your server/network/DNS so that you can use the same URL on the server that you use on a client machine or, set the handlerUrl attribute of the <add> element that adds the AdaptiveUploadStateStoreProvider.  For details on the second method, see Changing the Location of NeatUpload's Files.

--Dean

[Guest-767]

i am having the same issue, any solutions?

[Dean Brettle]

There are several solutions discussed in this thread.  Have you tried those?  If you have and are still having a problem, please start a new thread and include the exact error message you are getting (including stack trace).  Also, please make sure you are using the latest stable version of NeatUpload (currently 1.3.21) and indicate what version of Windows, IIS, and browser you are using.

Thanks!