Skip to main content

NU1301–Unable to load the service index for source

Today a colleague contacted me because she got an error when trying to build a specific solution inside Visual Studio. The compilation process failed on contacting the internal Azure DevOps Artifacts nuget feed.

Instead she got the following error message:

NU1301 Unable to load the service index for source 

I tried to load and build the same project but I couldn’t reproduce the issue.

There are multiple reasons why this error message appears. I suggested here to try any of the following:

  • Restart Visual Studio: always a good one to try first
  • Run dotnet restore in Interactive Mode: Run the dotnet restore command in interactive mode can help resolve the issue.
  • Clear NuGet Cache: Sometimes, clearing the NuGet cache can help. You can do this by running the following command in the terminal:
nuget locals all -clear

Neither of my suggestions seemed to help. In the end she was able to solve the issue by removing the local nuget.config file. As she had the package feeds also configured at the global nuget.config file, Visual Studio was able to fall back and use these feeds.

Could it be that there was an error in the local nuget.config file?

That would sound like an obvious explanation. However when comparing both the local and global configuration, we couldn’t find any difference. Strange…

All input is welcome!

More information

NuGet Error NU1301 | Microsoft Learn

Labels:

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more