Nuget path on network share

Hi,

I am running Proget on a small server and it runs fine if i use the local drive (c) to host nuget packages. I want to move the package paths to a network share which is basically a nas to allow us space to grow however publishing from teamcity succeeds but fails to show any nuget packages in proget. Additionally ,there is a drop path on the same share with nuget packages there but they dont get picked up.

I suspect its a permissions thing so I changed the service to use local system and it has not made a difference.

I have seen various posts talking about running progetservice manually to diagnose the issue but I am yet to find a complete post about how to do it.

Product: ProGet
Version: 3.8.6

I suspect this is still a file system privileges issue. Local System has full control over the local machine, but cannot access file shares, since the credentials are only valid on the local server. You will need to configure the service to run as a domain/workgroup account which can then be assigned privileges on your network resource.

Errors/warnings encountered will generally be logged to the Admin->Error Log page. This will generally be the same information that you will see running interactively. If the above doesn't help, try looking there to see if there is anything relevant.

Hi ,

To further investigate , I set the service to run as me, I am on the domain and can access the network share. However the nuget packages are still not being picked up from the network location either by pushing from teamcity or from the drop folder.

I have checked the error log, debug log , all the available logs on the admin page and there is nothing to suggest anything is wrong

This is a very common set-up, so it's hard to say why it doesn't work on your system/server... it's likely something to do with the way it's being run as a service, some user profile setting, or something like that.

Clearly, there are no errors detected on the ProGet side, so there would be nothing to report as a problem. I would also check Windows event logs for Service or other network issues.

See KB#1015 for instructinos on how run the service manually.

please do share what you find, as there are a lot obscure settings that can cause this not to work.

Hi

Thanks for the link.

Running the service interactively this is what comes up
c:\Program Files\ProGet\Service>ProGet.Service.exe run

Interactive Mode
Press CTRL+C to quit.
Starting the service...
Starting the messenger...
IntegrationUrl: http://inedo.com/pg/
Starting ServiceHeartbeatExecuter...
Starting ProxyConfigurationExecuter...
Starting ExtensionsLoaderExecuter...
Starting WebServerExecuter...
Starting LegacyFeedIndexerExecuter...
Starting DropPathMonitorExecuter...
Starting MyGetSyncExecuter...
Starting ScheduledTaskExecuter...
Executing ServiceHeartbeatExecuter...
Executing ExtensionsLoaderExecuter...
Extensions Path is not defined; no extensions will be loaded.
Extensions Path:
ServiceHeartbeatExecuter executed
Executing ProxyConfigurationExecuter...
Initializing Extensions Manager...
Initializing Assemblies...
Initializing Masked Persistent Types...
ExtensionsManager Initializing Complete.
ExtensionsLoaderExecuter executed
Executing ScheduledTaskExecuter...
ProxyConfigurationExecuter executed
Executing MyGetSyncExecuter...
Checking for scheduled tasks...
MyGetSyncExecuter executed
Executing DropPathMonitorExecuter...
Getting list of feeds with a drop path...
Found 1 feeds with a drop path.
Scanning for packages in \servername\MSYSNAS\MsysNAS\Nuget\Drop...
No scheduled tasks are ready to run.
ScheduledTaskExecuter executed
DropPathMonitorExecuter executed
Executing LegacyFeedIndexerExecuter...
Executing WebServerExecuter...

Unhandled Exception: Packages root path has changed; rechecking all feeds...
System.InvalidOperationException: No server URL's specified; web server cannot s
tart.
at Inedo.ProGet.Service.WebServerExecuter.GetWebServerConfig(String[] urls)
at Inedo.ProGet.Service.WebServerExecuter.Execute()
at Inedo.TimedExecuterBase.ExecuteMethodHost(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionCo
ntext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, C
ontextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWor
kItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
Scanning for feeds...
0 feeds found; checking for differences...
0 feeds added; 0 feeds deleted; 0 feeds changed
LegacyFeedIndexerExecuter executed
Executing LegacyFeedIndexerExecuter...

c:\Program Files\ProGet\Service>

Not sure how much this helps because it loads up fine when I run it as a service,am i missing a parameter to add?

Note that you will need to specify the "Urls" argument when running the service, to indicate which url you intend to bind to.