Share
Reportdocs.microsoft.com/.../download-tools-nuget
Works fine on my other desktop (and many others). Any thoughts?
You’re offline. This is a read only version of the page.
docs.microsoft.com/.../download-tools-nuget
Works fine on my other desktop (and many others). Any thoughts?
Hi have you got the issue. same error facing me also
Years ago (somewhere around 2013 I think), I read an anecdote from Dan Holme (very well known is the SharePoint space) about a time he was creating a training course under contract from MS (he joined MS directly a few years ago now) in how to install SP (this was either shortly before or after SPO was launched). As he was going along doing the install and capturing shots and videos and such, he got to the point where he needed to synch what was called the UPS (User Profile Store) with AD. And the process failed. And kept failing no matter what he tried. This was an infamous challenge point for SP for a number of years, but Dan was/is one of the most knowledgeable people there is in SP. Try as he might though, wouldn't work. Since he had such a close relationship with MS though, he had direct contacts in a number of core product dev teams. So, frustrated, he reached out to the SP dev team. They remoted into the test farm Dan was using. They ran tools. And looked at logs. Couldn't see any reason for the failure. So, they called in some folks from the IIS Sever team. Process repeated. Nothing. Then the SQL Server team. You guessed it; nothing. With everyone baffled they tried with folks from the AD team and even the actual Windows Server team including hyper-v. Not ONE person from all those core product dev teams could figure out why.
Eventually, since Dan had to get the course completed and couldn't waste more time, he grabbed a VM snapshot he had taken before doing the UPS step and restored it. And tried the UPS synch again. Worked flawlessly. Now, keep in ind this was exactly the same hardware and, theoretically from a bits and bytes perspective, the SAME VM (snapshots were supposed to be exact true copies, right?).
Moral of the story? There ARE "ghosts in the machine". Well, ok, that's my moral. Dan's summation of the experience (remeber this was at the very start of what has now become the globe spanning mega-service of SPO), was that the technology then had so many layers and interconnects that it was nearly impossible to trace down a true root cause. Add a fw orders of magntidue now for the current M365 and D365 clouds.
Just thought I would share that as I have remembered that story for a long time as guidance.
Upon success on my other computer it looks like this:
For some reason, the highlighted below (truncated by the editor), my desktop cannot connect to. Still baffled.
*****************
Installing package 'Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool' to 'C:\Test\Tools'.
GET api.nuget.org/.../index.json
OK api.nuget.org/.../index.json 141ms
Attempting to gather dependency information for package 'Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool.9.1.0.24' with respect to project 'C:\Test\Tools', targeting 'Any,Version=v0.0'
Gathering dependency information took 22 ms
Attempting to resolve dependencies for package 'Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool.9.1.0.24' with DependencyBehavior 'Lowest'
Resolving dependency information took 0 ms
Resolving actions to install package 'Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool.9.1.0.24'
Resolved actions to install package 'Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool.9.1.0.24'
Retrieving package 'Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool 9.1.0.24' from 'nuget.org'.
Adding package 'Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool.9.1.0.24' to folder 'C:\Test\Tools'
Added package 'Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool.9.1.0.24' to folder 'C:\Test\Tools'
Successfully installed 'Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool 9.1.0.24' to C:\Test\Tools
Executing nuget actions took 276 ms
Sorry this still did not work for me. Please let me know if there are any other thoughts.
I have tried this on multiple drives.
You are welcome.
To make it easier for other readers, please mark the appropriate answers as verified (click 'Yes' under 'Did this answer your question').
I think the community site shortened it. Here is a screenshot of what the final paste is.
Thanks so much for the time guys!
Hi,
I tried this script and gave me the same error.
The next I tried copying the script from Microsoft Docs and it worked, comparing both scripts, I see some difference, specially:
Your script NuGet package path: "dist.nuget.org/.../nuget.exe"
Microsoft script: "">dist.nuget.org/.../nuget.exe"
It is possible while copying script the link got shorten.
To make it easy, why don't you copy the script from the following link and run it (simply click on the copy button and right-click on the PowerShell window), it worked.
Download tools from NuGet (Developer Guide for Dynamics 365 Customer Engagement) | Microsoft Docs
I had the same error as you ... I suggest you to use the script from the documentation using "Copy" utility: https://docs.microsoft.com/en-us/powerapps/developer/data-platform/download-tools-nuget#download-tools-using-powershell
Then, use Ctrl + v to paste the script into your PowerShell console and press Enter
This might sound awkward...but it is possible that your script is broken because of a mistake when copying it..
I used this same one on another machine.
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
$sourceNugetExe = "dist.nuget.org/.../nuget.exe"
$targetNugetExe = ".\nuget.exe"
Remove-Item .\Tools -Force -Recurse -ErrorAction Ignore
Invoke-WebRequest $sourceNugetExe -OutFile $targetNugetExe
Set-Alias nuget $targetNugetExe -Scope Global -Verbose
##
##Download Plug-in Registration tool
##
./nuget install Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool -O .\Tools
md .\Tools\PluginRegistration
$prtFolder = Get-ChildItem ./Tools | Where-Object {$_.Name -match 'Microsoft.CrmSdk.XrmTooling.PluginRegistrationTool.'}
move .\Tools\$prtFolder\tools\*.* .\Tools\PluginRegistration
Remove-Item .\Tools\$prtFolder -Force -Recurse
##
##Download CoreTools
##
./nuget install Microsoft.CrmSdk.CoreTools -O .\Tools
md .\Tools\CoreTools
$coreToolsFolder = Get-ChildItem ./Tools | Where-Object {$_.Name -match 'Microsoft.CrmSdk.CoreTools.'}
move .\Tools\$coreToolsFolder\content\bin\coretools\*.* .\Tools\CoreTools
Remove-Item .\Tools\$coreToolsFolder -Force -Recurse
##
##Download Configuration Migration
##
./nuget install Microsoft.CrmSdk.XrmTooling.ConfigurationMigration.Wpf -O .\Tools
md .\Tools\ConfigurationMigration
$configMigFolder = Get-ChildItem ./Tools | Where-Object {$_.Name -match 'Microsoft.CrmSdk.XrmTooling.ConfigurationMigration.Wpf.'}
move .\Tools\$configMigFolder\tools\*.* .\Tools\ConfigurationMigration
Remove-Item .\Tools\$configMigFolder -Force -Recurse
##
##Download Package Deployer
##
./nuget install Microsoft.CrmSdk.XrmTooling.PackageDeployment.WPF -O .\Tools
md .\Tools\PackageDeployment
$pdFolder = Get-ChildItem ./Tools | Where-Object {$_.Name -match 'Microsoft.CrmSdk.XrmTooling.PackageDeployment.Wpf.'}
move .\Tools\$pdFolder\tools\*.* .\Tools\PackageDeployment
Remove-Item .\Tools\$pdFolder -Force -Recurse
##
##Remove NuGet.exe
##
Remove-Item nuget.exe
#1
André Arnaud de Cal...
291,759
Super User 2024 Season 2
#2
Martin Dráb
230,468
Most Valuable Professional
#3
nmaenpaa
101,156
All responses (
Answers (
