Shared folder nuget issues


We upgraded to, and now we’re running into an issue where octopus doesn’t seem to be able to properly search nuget feeds that are located on network shares. Copying the nupkg files from a network share to a local folder results in a successful deployment. Also, I did try to adjust the feed credentials and that did not make a difference.

From what I can tell, it is an octopus server problem, as I had the issue in the following scenarios:

  • Using a compiled version of octo.exe on the build server
  • Using the TeamCity plugin on the build server
  • Testing the nuget feed directly in the configuration page

See my TeamCity log below for details:

[12:51:42]Step 2/2: Deploy (OctopusDeploy: Release) (3s)
[12:51:42][Step 2/2] Octopus Deploy (3s)
[12:51:42][Octopus Deploy] Running command: octo.exe create-release --server=“http://eacbldoctopus01/api” --apikey=SECRET --project=“Genesis Reporting” --enableservicemessages --version=“2013.2.0.169” --deployto=“Dev” --waitfordeployment
[12:51:42][Octopus Deploy] Creating Octopus Deploy release
[12:51:42][Octopus Deploy] Octopus Command Line Tool, version
[12:51:42][Octopus Deploy]
[12:51:42][Octopus Deploy] Finding project: Genesis Reporting
[12:51:42][Octopus Deploy] Handshaking with Octopus server: http://eacbldoctopus01/api
[12:51:44][Octopus Deploy] Handshake successful. Octopus version:; API version: 2.0.0
[12:51:44][Octopus Deploy] Finding environments…
[12:51:44][Octopus Deploy] Finding steps for project…
[12:51:44][Octopus Deploy] Resolving NuGet package versions…
[12:51:44][Octopus Deploy] - Finding latest NuGet package for step: GenesisReporting
[12:51:45][Octopus Deploy] There are no available packages named ‘GenesisReporting’.
[12:51:45][Octopus Deploy] System.Exception: There are no available packages named ‘GenesisReporting’.
[12:51:45][Octopus Deploy] at ProjectExtensions.GetLatestPackageForStep(IOctopusSession session, Step step)
[12:51:45][Octopus Deploy] at OctopusTools.Commands.CreateReleaseCommand.Execute()
[12:51:45][Octopus Deploy] at OctopusTools.Infrastructure.CommandProcessor.Process(String[] args)
[12:51:45][Octopus Deploy] Octo.exe exit code: 2
[12:51:45][Step 2/2] Unable to create or deploy release. Please check the build log for details on the error.
[12:51:45][Step 2/2] Step Deploy (OctopusDeploy: Release) failed


Can you remember what Octopus version you were using prior to upgrading?

We introduced a change (in 1.3.5 IIRC) to the way we query NuGet feeds. Can you check the Windows Event Viewer to see if any warnings or errors are being logged on the Octopus server?


We were running previously. Here’s the one thing that I saw in the event log that seems to be related to the issue:

2013-03-05 12:55:42,367 [5] ERROR Octopus [(null)] - Unhandled error on web server: The controller for path ‘/configuration/easdevfiler/eavsmpbuild01UNC/packages-research’ was not found or does not implement IController.
System.Web.HttpException (0x80004005): The controller for path ‘/configuration/easdevfiler/eavsmpbuild01UNC/packages-research’ was not found or does not implement IController.
at System.Web.Mvc.DefaultControllerFactory.GetControllerInstance(RequestContext requestContext, Type controllerType)
at System.Web.Mvc.DefaultControllerFactory.CreateController(RequestContext requestContext, String controllerName)
at System.Web.Mvc.MvcHandler.ProcessRequestInit(HttpContextBase httpContext, IController& controller, IControllerFactory& factory)
at System.Web.Mvc.MvcHandler.BeginProcessRequest(HttpContextBase httpContext, AsyncCallback callback, Object state)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

The share that I was previously using was


Hi Kevin,

If you go to the Configuration section in Octopus, and then the NuGet tab, and click “test” on your feed, can you try searching the feed?

Also on the Create Release screen in Octopus, do you see a list of versions?


I’ll check the create release screen in a bit, since I’m not on my box. But I do know that I did test the feed, and had got no results when searching. That’s what lead me down the road to notice that all the local folders were operating correctly.

I’ll reply a bit later when after I can reconfigure stuff on the server and will let you know what I find.

I’ve this problem too :stuck_out_tongue: When i test the nuget feed on a local folder i get no results.

i Andrea,

The local NuGet folder search is case sensitive - can you try searching for
the casing exactly?


Paul Stovell
Octopus Deploy
W: | T: @octopusdeploy

I’ve 2 servers i’m testing (on/off premise):

On the first one I fixed this issue by putting the folder in a location where the applicationpool user can actually read it.

For the onpremise server it does not work though even if it has the permessions to read/write the folder. I did the case sensitive search as well.

Is there a log file I can check for more info?

Ps: i’m having some problems with that server, windows authentification fails on it.
We’re investigating :slight_smile:

Hi Andrea,

You can check the Windows event viewer on the Octopus server - any
errors/warnings will appear there.


Paul Stovell
Octopus Deploy
W: | T: @octopusdeploy

I’ve fixed this: the application user must have the permissions to read the folder (as showed in the gui)

Thanks :smiley: