Ok confirmed : it works with only one feed, but as soon as I have two feeds, things mess up and I have the error above.

Is this more on Azure Devops or ProGet do you think ?

Best Regards,
Bruno Juste

Hello,

thank you for your quick response, I setup a quick
more isolated reproduction setting and it seems the problem
is when there are two feeds.

When I specify an API key, I do not have the possibility
to specify a username.

I can only specify one set of credentials in the Azure Devops
task, even if the account used has the rights on both feeds.
It then fails with the above error message.

If I make a small project with only one of the two feeds, it works.

I'll try on my big project to have only one feed.

Best Regards,
Bruno Juste

Hello,

I'm using a ProGet server to store our NuGet packages,
and we run into a problem when restoring packages in an
Azure Devops Server 2019 build pipeline.

The servers answers with HTTP 500 when restoring packages :

Retrying 'FindPackagesByIdAsyncCore' for source 'https://../nuget//FindPackagesById()?id='..**'&semVerLevel=2.0.0'.
Response status code does not indicate success: 500 (Internal Server Error).

We are using API Key authentication and this is the error message in the ProGet console :

An error occurred in the web application: Value cannot be null. Parameter name: userName
Details:
URL: http://../nuget//FindPackagesById()?id='..**'&semVerLevel=2.0.0
Referrer: (not set)
User: (unknown)
User Agent: NuGet .NET Core MSBuild Task/5.7.0 (Microsoft Windows 6.3.9600)
Stack trace: at Inedo.ProGet.Extensions.UserDirectories.BuiltInUserDirectory.TryGetAndValidateUser(String userName, String password)
at Inedo.ProGet.WebApplication.ProGetHttpModule.ValidateUser(HttpApplication app, String userName, String password)
at Inedo.Web.InedoHttpModule.AuthenticateRequestAsync(HttpApplication app)
at Inedo.Web.InedoHttpModule.ProcessBegin(Object sender, EventArgs e, AsyncCallback cb, Object extraData)
at System.Web.HttpApplication.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

There is no problem in Visual Studio or for publishing packages.

We are using ProGet 3.2.

Do you have any clue ?

Best Regards,
Bruno Juste