Octopus Deploy is not able to download the Package

We are using TeamCity 10.x with Octopus Plugin 3.4.2 Octopus Deploy 3.4 Octopus Tentacle 3.4 (polling)
I am not able to get the Build. This was working until I upgraded to these latest versions, including 3.3.27

Below is the Error message, we are getting
Acquiring packages

August 24th 2016 21:49:02

Making a list of packages to download

August 24th 2016 21:49:02

Downloading package xxxxxxxxxxxxxxxxxxxxxxx version 10.1.088 from feed: ‘http://localhost:8090/httpAuth/app/nuget/v1/FeedService.svc/

August 24th 2016 21:49:17

Unable to download package:
Could not find package xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx in feed: 'http://localhost:8090/httpAuth/app/nuget/v1/FeedService.svc/'
Octopus.Shared.ControlledFailureException: Could not find package xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx in feed: 'http://localhost:8090/httpAuth/app/nuget/v1/FeedService.svc/'
at Octopus.Core.Packages.PackageDownloader.FindPackage(Int32 attempt, PackageIdentifier packageIdentifier, IFeed feed) in Y:\Work\refs\tags\3.4.0\source\Octopus.Core\Packages\PackageDownloader.cs:line 171
at Octopus.Core.Packages.PackageDownloader.AttemptToFindAndDownloadPackage(Int32 attempt, PackageIdentifier packageIdentifier, IFeed feed, String cacheDirectory, IPackage& downloadedPackage, String& path) in Y:\Work\refs\tags\3.4.0\source\Octopus.Core\Packages\PackageDownloader.cs:line 147
at Octopus.Core.Packages.PackageDownloader.AttemptToDownload(PackageIdentifier packageIdentifier, IFeed feed) in Y:\Work\refs\tags\3.4.0\source\Octopus.Core\Packages\PackageDownloader.cs:line 102
Octopus.Server version 3.4.0 (3.4.0+Branch.master.Sha.d4504103f2c91984e971b32865aedd3f6007346d)

August 24th 2016 21:49:17

The step failed: Activity failed with error ‘The package could not be downloaded. If you are getting a package verification error, try switching to a Windows File Share package repository to see if that helps.’.

Hi Aruloli,

I’m sorry to hear you’re experiencing this issue.

I have just attempted to replicate the problem (using the same components), but I was unable to.

Could you possibly take a few steps to help us determine the problem?

  1. Could you please attach a full task log.
  2. If you browse to http://localhost:8090/httpAuth/app/nuget/v1/FeedService.svc/FindPackagesById()?id=‘YourPackageId’ do you see your package version returned in the XML?
  3. If you create a new release in Octopus, and in the ‘Packages’ section click the ‘Search’ link in the ‘Specific’ column of the version table for your package, can you see the required version returned?

We do apologize for any inconvenience this has caused. Hopefully we’ll determine the issue and get it resolved quickly.


Hi Michael,

I am having what appears to be the exact same problem.

With regard to 2. the package is found in the feed.

With regard to 3. the packages shows up in the search.

If I click “Try again” the deploy works.

Hi Øystein,

Did you also only begin seeing this after an upgrade?

Often there is a delay in packages appearing in the TeamCity NuGet feed. Have you seen the “Tip: Delayed Package Publishing” section in our TeamCity documentation?

Yes, this happend after an upgrade of TeamCity and also Octopus Deploy.

I have added new build step between the NuGet creation and the deploy that just sleeps for 10 seconds and then it seems to work.

The sleep approach turn out to be so unstable that we just switched over to using the internal Octopus Deploy NuGet feed instead.


I’m glad to hear you were successful.

Using the built-in Octopus NuGet feed also brings some additional benefits, such as retention-policies and improved performance.

Happy Deployments!

I am having the same issue since team-city upgrade. Switching to Octopus NuGet feed is not an easy option for us. Can you please guide if there is any fix for that.

Hi Saba,

We are going to investigate making our package acquisition more patient, to hopefully resolve this issue with TeamCity feeds.
We have an issue which you can follow.

We realize this must be annoying.


This issue has been closed due to inactivity. If you encounter the same or a similar issue and require help, please open a new discussion (if we asked for logs or extra details in this thread, consider including them in the new thread). If you are the creator of this thread and believe it should not be closed let us know via our support email.