Uploading (0%)...

[Guest]

I'm attempting to upload a 1.87GB upack file and the upload progress is stuck at 0%.

I can successfully upload a smaller upack file.

I've checked the IIS and PorGet web.config file size restrictions are set to 2GB.

I've increased the IIS Connection Time-out (seconds) to 10 minutes.

Any ideas?

Product: ProGet
Version: 4.3.1

[Guest]

Are you using the browser? That might be an issue, since browsers don't handle such large uploads so great. We will eventually implement a staged/chunk uploading process for the web UI.

The upack client (or a HTTP push) should work however.

[Guest]

I'm using Chrome but have also tried IE.

I've tried the upack client v1.0.0 and I get the following error,

H:\Downloads\OneSumX>upack push --package=OneSumX_FS_2.0.63353.upack --target=http://tdc2sql026:9797
Package: :OneSumX_FS
Version: 2.0.63353
Unhandled exception: System.Net.WebException: The request was aborted: The request was canceled.
at System.Net.ConnectStream.InternalWrite(Boolean async, Byte[] buffer, Int32 offset, Int32 size, AsyncCallback callb
ack, Object state)
at System.Net.ConnectStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.IO.Stream.InternalCopyTo(Stream destination, Int32 bufferSize)
at ProGet.Client.Program.push(String package, String target, String user)

The error appears to be "The request was aborted", some Googling around suggests a solution might be "The solution was to disable HTTP Keep Alive for posting the Requests".

Is this possible with the upack client?

Any help greatly appreciated.

[Guest]

It might be the server that's disconnecting; you could also just use powershell to push this as well, to see where issue is.

There is a timeout in v1.0.0 of upack, but you can try 1.0.1 of the upack client that doesn't have the timeout: http://cdn.inedo.com/downloads/proget/upack1.0.1.zip
.

[Guest]

Thanks for helping, I tried upack v1.0.1, which completed without errors.

H:\Downloads\OneSumX>upack.exe push --package=OneSumX_FS_2.0.63353.upack --target=http://tdc2sql026:9797/proget-feeds/Wo
lters.Kluwer.OneSumX
Package: :OneSumX_FS
Version: 2.0.63353
:OneSumX_FS 2.0.63353 published!

However, I can't find where this has uploaded to.

It doesn't show in the Web UI or on the file-system on the server?

Any thoughts?

[Guest]

That's hard to say... it should work, but it's a large package, so it might take a little while to process. If an error occurred during processing, it would be logged in Admin > Errors. youy can also check the internal package disk store (default is %ProGramData%\ProGet) to see if it's there...

You could also put it in the drop folder to see if it picks up as well, though upload should also work.

[Guest]

I noticed that I had the URL wrong in my last attempt, so I retried using the URL displayed by ProGet.

This time I got "The remote server returned an error: (500) Internal Server Error."

H:\Downloads\OneSumX>upack.exe push --package=OneSumX_FS_2.0.63353.upack --target=http://tdc2sql026:9797/upack/Wolters.K
luwer.OneSumX --user=Admin:Admin
Package: :OneSumX_FS
Version: 2.0.63353
Unhandled exception: System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
at System.Net.HttpWebRequest.GetResponse()
at ProGet.Client.Program.push(String package, String target, String user)

I believe this to be "A generic error message, given when an unexpected condition was encountered and no more specific message is suitable".

Which made me wonder if ProGet has any logging that can be turned on, like Log4Net

[Guest]

Further information about "The remote server returned an error: (500) Internal Server Error"

As Admin user looking at the Recent Errors on the Administration Overview page.

[Guest]

Look like my image upload failed, so here the text from the Recent Error: Maximum request length exceeded.

Logged: 14/11/2016 09:04:57
Level: Error
Category: N/A
Message: Unhandled exception processing /upack/Wolters.Kluwer.OneSumX
Details:
System.Web.HttpException (0x80004005): Maximum request length exceeded.
at System.Web.HttpRequest.GetEntireRawContent()
at System.Web.HttpRequest.get_InputStream()
at Inedo.ProGet.WebApplication.SimpleHandlers.Universal.UniversalRepositoryHandler.<ProcessUploadRequestAsync>d__14.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.ProGet.WebApplication.SimpleHandlers.ApiHandlerBase.<ProcessRequestAsync>d__0.MoveNext()

[Guest]

SOLVED

See the following Stack Overflow question fro the solution.

http://stackoverflow.com/questions/3853767/maximum-request-length-exceeded

In summary:

in the web.config

<configuration>
    <system.web>
        <httpRuntime maxRequestLength="2147484" />
    </system.web>
</configuration>

and

 <system.webServer>
   <security>
      <requestFiltering>
         <requestLimits maxAllowedContentLength="2147483648" />
      </requestFiltering>
   </security>
 </system.webServer>

Note: maxAllowedContentLength is measured in bytes while maxRequestLength is measured in kilobytes, which is why the values differ in this config example. (Both are equivalent to 2 GB.)