Setsite Failed For Package Global Hub Client Package

85 views

Skip to first unread message

Jordan Tucker

unread,

Aug 3, 2024, 5:02:52 PM8/3/24

to psilmetttorchpa

If Yes option is selected in error dialog, VS throws two additional error that Feature 'Process telemetry' is currently unavailable due to an error and that the 'VSPackage' package did not load correctly. The application then crashes.

Found the issue here, the GlobalHubClientPackage permissions issue with was related to user permissions managed by my organization's privilege management software. Resolved the permissions issue with them, repaired VS through the installer, and then following restart VS v17.8.4 opened without issue. Thank you for your assistance Tianyu Sun.

Thank you for the response, I will ask my organization about privilege management software that may be installed on my machine. I did have VS2022 installed and running without issue prior to the 17.8.4 upgrade however so at least prior to this point there was not any software on my machine that appeared to be interfering with VS permissions. In the meantime are you aware of any other steps I could take to troubleshoot this issue? Let me know if additional information is needed.

"SetSite failed for package [GlobalHubClientPackage]Source: 'System.Core' Description: Access to the path is denied.System.UnauthorizedAccessException: Access to the path is denied. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.Pipes.NamedPipeClientStream.ConnectInternal(Int32 timeout, CancellationToken cancellationToken, Int32 startTime) at System.Threading.Tasks.Task.Execute()--- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at "

So that's pretty.. Attempted to google "The supplied user buffer is not valid for the requested operation" nothing relevant.. says memory issue (i have enough) or security setting (which isn't switched on)

Tried installing with no work flows.. that seemed to work..
Went back in to the installer and tried adding the ASP.NET and web development workflow.. again that seemed to work.. project templates all exist. so at least I can get work done..
Tried installing MAUI -

SetSite failed for package [Global Hub Client Package]Source: 'mscorlib' Description: The supplied user buffer is not valid for the requested operation. (Exception from HRESULT: 0x800706F8) System.Runtime.InteropServices.COMException (0x800706F8): The supplied user buffer is not valid for the requested operation. (Exception from HRESULT: 0x800706F8) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at Microsoft.ServiceHub.Utility.Shared.Common.StartProcessWindows(ProcessStartInfo startInfo, EventHandler onExited, EventHandler onDisposed) at Microsoft.ServiceHub.Client.HubControllerClient.d__5.MoveNext()

If you load 2022 with code (i.e. opening a solution from windows explorer) then it works.. this happens on the front screen (open recent/Get started) if you open 2022 from the windows menu .. but it's every time.. and not just me either

Welcome to Microsoft Q&A forum. In this situation, does repairing Visual Studio from VS installer work? And for this error "The supplied user buffer is not valid for the requested operation", does running the VS setup file as administrator(to install VS) work?

Like I say, we've been having this problem for months.. tried repairing, updating, remove and re-install.. nothing seems to work.. first time I installed 2022 back in March I think it was it was a pain getting the workloads installed.. apparently it's still a problem..

On a system with existing VS2022-17-3 the upgrade worked ok.On a clean 22621.1485 OS install, using Visual Studio Installer 3.5.2145.59678, after installing 17.5, 17.5.3, 17.4, 17.2 all have the issue listed and VS2022 does not successfully launch.Log xml reportsSetSite failed for package [Feature Flags Package]Source: 'mscorlib' Description: The satellite assembly named "Microsoft.VisualStudio.Shell.UI.Internal.resources.dll, PublicKeyToken=b03f5f7f11d5a3a" for fallback culture "en" either could not be found or could not be loaded.On exporting configuration from working system and importing on non-working system I get this messageMicrosft.VisualStudio.Component.VC.CoreBuildTools: No matching workload or component found.This can be easily duplicated on a system that has not had and VS installed.This is a serious issue as VS2022 cannot launch and cannot be installed on a new dev system.

Repaire and reinstall didn't help.
Then I installed StreamJsonRpc manully in GAC. That error dissapeared, but I got another errors:
The 'Settings Package' package did not load correctly
The 'Environment Package Window Management' package did not load correctly

Please first open Developer Command Prompt for Visual Studio 2022, type and run this command devenv /SafeMode. After running this command, VS 2022 will be opened automatically, please check if the same error appears.

SetSite failed for package [OneApiPackage]Source: 'OneAPI' Description: Could not load file or assembly 'Microsoft.VisualStudio.Threading, Version=17.8.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.Threading, Version=17.8.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. File name: 'Microsoft.VisualStudio.Threading, Version=17.8.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' at OneApi.OneApiPackage.InitializeAsync(CancellationToken cancellationToken, IProgress`1 progress) at Microsoft.VisualStudio.Shell.AsyncPackage.c__DisplayClass21_0.d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Microsoft.VisualStudio.Services.VsTask.RethrowException(AggregateException e) at Microsoft.VisualStudio.Services.VsTask.InternalGetResult(Boolean ignoreUIThreadCheck) WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

I also got this message and put it on this forum yesterday along with numerous other issues but my post got moved to Intel Installation forum by Ron Green without any reason thus blocking anyone from accessing it. I must have written something controversial and been cancelled!

The reply I got on this matter on the installation was to get onto Microsoft or try Repairing by reinstalling. I tried the repair but it didn't fix it and I have no desire to contact Microsoft on this matter. So far I've not had any adverse effects though not fully tested it yet.

My post also highlighted some IFX FORTRAN issues relating to ICEs in release mode with optimisation set (only fixed by turning it off with /Od for offending files) and a warning to say that /check:uninit (set in my debug version) is not currently available on Windows.

@Stephen_Sutcliffe I moved your issue to the Startup Support team who have a lot more experience with VS integration issues. I thought you have a better chance of getting it resolved over there. I will see if they have made any progress. I'm happy to move it back to this Forum if you want.

@Ron_Green My post was in 2 parts, the first relating to VS integration and second to IFX Fortran specific issues which are the more critical for me. I mentioned the VS observations to just see if anyone else had seen similar behaviour and point out that VS seems to update itself without you, the user, having any control even if it is not deemed validated for the Intel integration. Why doesn't the Intel installer warn you if your current VS version has not been validated for the OneAPI version being installed? This check should maybe be added to the installer page relating to VS version.

The Fortran IFX ICE issues were investigated on previous version via Premier Support and as they are still there, I wondered if/when these are due to be fixed. The suggested workaround, by Barbara, was to disable optimisation /Od in affected files which did work, but is not ideal as it may affect performance and would have to be reset once a fix has been completed.

I have still to successfully compile and link my full project solutions without compromises (which contains 36 projects) in IFX so will have to keep on using IFORT until these get resolved. I am only using the x64 compilers.

1) The Release build won't compile many files unless the Optimisation (/Od) is fully disabled in some (though not all of the files). None of the other optimisation options work. I have previously reported these ICEs (with example reproducer) after trying previous issue back in December to Premier Support, so sadly it appears that this issue has still not been resolved. I did use the suggested workaround (to disable the optimisation) so some progress of sorts. The change in this setting could well have a detrimental affect the speed of the program compared to IFORT. After changing to /Od the program does actually link and run in Release mode from within VS.

2) The Debug compilation build is issuing messages saying that the /check:uninit is not currently available on Windows. Is there an alternative to this compiler option in IFX or will it be made available in a later release or has it been deprecated?

I don't believe having to go through the pain of creating a reproducer (again) will be of much benefit in these cases as they seem to relate to potentially unsupported features or issues I have had looked at before (with reproducer etc.) via Premier Support.

@Devorah_H_Intel I tried repairing the HPC Toolkit to no avail. I note from the log message that it's looking for Microsoft.VisualStudio.Threading, Version=17.8.0.0. My version of Visual Studio is 17.7.5 (too early?). I was planning to upgrade to 17.9.2, which is the validated version for OneAPI 2024.1, rather than the latest available version.