Acquire packages Fails for One Deployment on One Environment

We just recently upgraded to octopus 3.0 and now have one environment which fails to aquire the packages. All of the other environments work fine and we even have other deployments to this environment that are working fine.

Below is the error message:
The remote script failed with exit code 100

Running: Download package Hudson.SalesCommission.Web 4.6.0.9 from \ServerName\NuGet\Octopus\Hudson.SalesCommission
10:14:34 Verbose | Checking package cache for package Hudson.SalesCommission.Web 4.6.0.9
10:14:34 Info | Downloading NuGet package Hudson.SalesCommission.Web 4.6.0.9 from feed: 'file://ServerName/NuGet/Octopus/Hudson.SalesCommission’
10:14:34 Verbose | Downloaded package will be stored in: 'D:\Octopus\Files\feeds-35’
10:14:34 Verbose | Finding package (attempt 1 of 5)
10:14:41 Verbose | Attempt 1 of 5: Unable to download package: Could not find package Hudson.SalesCommission.Web 4.6.0.9 in feed: 'file://ServerName/NuGet/Octopus/Hudson.SalesCommission’
10:14:42 Verbose | Finding package (attempt 2 of 5)
10:14:49 Verbose | Attempt 2 of 5: Unable to download package: Could not find package Hudson.SalesCommission.Web 4.6.0.9 in feed: 'file://ServerName/NuGet/Octopus/Hudson.SalesCommission’
10:14:49 Verbose | Finding package (attempt 3 of 5)
10:14:56 Verbose | Attempt 3 of 5: Unable to download package: Could not find package Hudson.SalesCommission.Web 4.6.0.9 in feed: 'file://ServerName/NuGet/Octopus/Hudson.SalesCommission’
10:15:01 Verbose | Finding package (attempt 4 of 5)
10:15:06 Verbose | Attempt 4 of 5: Unable to download package: Could not find package Hudson.SalesCommission.Web 4.6.0.9 in feed: 'file://ServerName/NuGet/Octopus/Hudson.SalesCommission’
10:15:11 Verbose | Finding package (attempt 5 of 5)
10:15:16 Verbose | Attempt 5 of 5: Unable to download package: Could not find package Hudson.SalesCommission.Web 4.6.0.9 in feed: 'file://ServerName/NuGet/Octopus/Hudson.SalesCommission’
10:15:21 Error | Unable to download package: Could not find package Hudson.SalesCommission.Web 4.6.0.9 in feed: 'file://ServerName/NuGet/Octopus/Hudson.SalesCommission’
10:15:21 Error | Failed to download package Hudson.SalesCommission.Web 4.6.0.9 from feed: '\ServerName\NuGet\Octopus\Hudson.SalesCommission’
10:15:21 Error | System.Exception: The package could not be downloaded from NuGet. If you are getting a package verification error, try switching to a Windows File Share package repository to see if that helps.
10:15:21 Error | at Calamari.Integration.PackageDownload.PackageDownloader.AttemptToDownload(String packageId, SemanticVersion version, Uri feedUri, String cacheDirectory, String& downloadedTo, IPackage& downloaded) in Y:\work\b1fd300731d5f2fc\source\Calamari\Integration\PackageDownload\PackageDownloader.cs:line 153
10:15:21 Error | at Calamari.Integration.PackageDownload.PackageDownloader.DownloadPackage(String packageId, SemanticVersion version, String feedId, Uri feedUri, Boolean forcePackageDownload, String& downloadedTo, String& hash, Int64& size) in Y:\work\b1fd300731d5f2fc\source\Calamari\Integration\PackageDownload\PackageDownloader.cs:line 47
10:15:21 Error | at Calamari.Commands.DownloadPackageCommand.Execute(String[] commandLineArguments) in Y:\work\b1fd300731d5f2fc\source\Calamari\Commands\DownloadPackageCommand.cs:line 60

Hi Matthew,

Thanks for getting in touch, and sorry to hear that you’re having these issues.

Can you go to the External Feeds tab under Library and click the Test link next to that feed, this should tell us if it’s something wrong with the setup of the feed.

And, is this same feed used in the other environments that do not excibit these issues?

Thank you and kind regards,
Henrik

Yes it is the same feed the testing works fine. We have 5 environments and have been able to deploy this project successful in all but one of the environments after the upgrade to 3.1.

image004.png

image003.gif

image002.png

image001.gif

Just wanted to follow up on this. We are still not able to deploy to this environment.

Hi Matthew,

Sorry for the delay in getting back to you!

The only thing that springs to mind would be if the permissions for the account the Tentacle is running under in that 1 failing environment have changed so that it no longer has permissions to the folder that is used for that feed.

Did the Tentacle service in that environment run as a specific user before the update or was it just using the default system account?

Thank you and kind regards,
Henrik

It was using the default account but we updated it to an account with more permissions just incase with no change.

Thanks,
Matt


Hi Matthew,

I’m sorry for the long delay in getting back to you, I’m running out of ideas as to what could be causing this issue.

One thing you could try, if you log on to the Tentacle server using the same user as the service is running as, are you able to access the fileshare where the packages are stored?

Thank you and kind regards,
Henrik