NeatUpload control not working on server with Asp.net 3.5

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

NeatUpload control not working on server with Asp.net 3.5

Guest-1136

Hi , i have tested the neatupload control sample code individally on windows server 2008 with IIS7, the sample provided by the site was working fine for large file upload.

But when i integrate this project my asp.net 3.5 application on server , there is no build error and when i upload tha file of 5 MB file , the application raise the following error.

 

***************************

Server Error in '/' Application.

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 97.74.195.130:80

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.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 97.74.195.130:80

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:

[SocketException (0x274c): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 97.74.195.130:80]
            System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) +239
            System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP) +35
            System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception) +224
            [WebException: Unable to connect to the remote server]
            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, HttpCookieCollection httpCookies, Byte[] encryptionKey, Byte[] validationKey, String encryptionAlgorithm, String validationAlgorithm, Object[] methodCall) +1280
            Brettle.Web.NeatUpload.SimpleWebRemoting.MakeRemoteCall(Uri uri, Object[] methodCall) +177
            Brettle.Web.NeatUpload.SessionBasedUploadStateStoreProvider.MakeRemoteCall(Object[] methodCall) +106
            Brettle.Web.NeatUpload.SessionBasedUploadStateStoreProvider.Load(String postBackID) +172
            Brettle.Web.NeatUpload.AdaptiveUploadStateStoreProvider.Load(String postBackID) +54
            Brettle.Web.NeatUpload.UploadStateStore.OpenReadWrite(String postBackID) +65
            Brettle.Web.NeatUpload.UploadStateStore.OpenReadWriteOrCreate(String postBackID) +56
            Brettle.Web.NeatUpload.Internal.Module.FilteringWorkerRequest.ParseOrThrow() +4528
            Brettle.Web.NeatUpload.Internal.Module.FilteringWorkerRequest.ParseMultipart() +1907
            Brettle.Web.NeatUpload.UploadHttpModule.WaitForUploadToComplete() +87
            Brettle.Web.NeatUpload.UploadHttpModule.Application_ResolveRequestCache(Object sender, EventArgs e) +138
            System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68
            System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75
            


Version Information: Microsoft .NET Framework Version:2.0.50727.3603; ASP.NET Version:2.0.50727.3601

***************************

Please suggest...

 

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: NeatUpload control not working on server with Asp.net 3.5

Dean Brettle
Administrator
Looks like NeatUpload is unable to make a web request from your server to http://servers_internet_name/path_to_your_app/NeatUpload/UploadStateStoreHandler.ashx to maintain upload state in the session.  That is probably due to some firewall or DNS settings specific to your server.  You can either:
  • change the relevant firewall/DNS settings, or
  • set the handlerUrl attribute of the <add> element that adds the AdaptiveUploadStateStoreProvider to the <neatUpload> section's <providers> section so that it refers to the new location, or
  • use the InProcUploadStateStoreProvider as described in Reducing Server Load if you are not using a web garden/farm and don't mind losing upload state when the server restarts.
Loading...