I am having trouble getting the latest version of Nsight Systems (2023.1.1) to work on my Windows 10 x64 system. The error I am getting is as follows and appears to be related to permissions:
RuntimeError (120) {
TargetSideError (1100) {
ErrorText: C:\dvs\p4\build\sw\devtools\Agora\Rel\QuadD_Main\QuadD\Common\ProcessResumer\Windows\ProcessResumerImpl.cpp(45): Throw in function __cdecl QuadDCommon::ProcessResumer::WindowsProcessResumer::WindowsProcessResumer(class QuadDCommon::StrongType<class QuadDCommon::LimitedNumber<unsigned int,4294967295>,class QuadDCommon::ProcessIdTag>)
Dynamic exception type: struct boost::wrapexcept<class QuadDCommon::SystemException>
std::exception::what: SystemException
[struct QuadDCommon::tag_errno_text * __ptr64] = Access is denied
[struct QuadDCommon::tag_message * __ptr64] = Failed to open thread 19884 from process 10604
[struct QuadDCommon::tag_winapi_error_code * __ptr64] = 5
[struct boost::errinfo_api_function_ * __ptr64] = OpenThread
ServiceName: AnalysisService
MethodName: Init
SystemError (124) {
ErrorText: Failed to open thread 19884 from process 10604
ApiFunction: OpenThread
OriginalFile: C:\dvs\p4\build\sw\devtools\Agora\Rel\QuadD_Main\QuadD\Common\ProcessResumer\Windows\ProcessResumerImpl.cpp
OriginalLine: 45
OriginalFunction: __cdecl QuadDCommon::ProcessResumer::WindowsProcessResumer::WindowsProcessResumer(class QuadDCommon::StrongType<class QuadDCommon::LimitedNumber<unsigned int,4294967295>,class QuadDCommon::ProcessIdTag>)
OriginalExceptionClass: struct boost::wrapexcept<class QuadDCommon::SystemException>
}
}
}
I updated to the latest driver and tried running as administrator but no difference. Interestingly, I can get the 2020.3.4 version to start profiling, but this now complains about a driver mismatch and fails to collect any CUDA events. I would appreciate any insight into what could be going on here.
I’ll ping Doron on this again, but as he is in Israel, he will not be responding today. Meanwhile, can you give me some details on the OS version and Nsys version you are using?
Are you running from the CLI or from the GUI? If CLI, can you give me the exact command line you used?
Thanks @hwilper. To answer your question @rinkertt, no the issue is still ongoing. It’s been a couple of months since I last tried to get this working, I can still use Nsight Compute so managing with that for now.
Additional details:
OS: Windows 10 Enterprise 22H2
Nsight Systems 2023.1.1 GUI
This is a company managed system, my regular user account does not have admin rights but I have a separate admin account that usually gives me privileges when required.
This is indeed a permissions issue. nsys.exe expects to have permission to launch target processes and suspend/resume their threads. This is why it requires administrative privileges to run. Running from an admin account should provide such permissions. Is there anything special about the target process that nsys.exe is trying to launch, or its location?
I use the GUI, when selecting the local PC as target, I get a UAC prompt, and proceed with a localadmin account.
GPU: RTX A4500
Thanks @dofek, some additional info on the target process:
I’m trying to profile a C++ program that I can from Matlab using MEX. So I start a Matlab session without GUI, and run the script that will call the MEX routine with GPU accelerated code. So the target application with arguments is
and the working directory is the location of the script and mex file. This worked fine in the past on a different pc, and works for Nsight Compute. Nsight Systems cannot start Matlab. When I press start I immediately get:
RuntimeError (120) {
TargetSideError (1100) {
ErrorText: C:\dvs\p4\build\sw\devtools\Agora\Rel\QuadD_Main\QuadD\Common\ProcessResumer\Windows\ProcessResumerImpl.cpp(45): Throw in function __cdecl QuadDCommon::ProcessResumer::WindowsProcessResumer::WindowsProcessResumer(class QuadDCommon::StrongType<class QuadDCommon::LimitedNumber<unsigned int,4294967295>,class QuadDCommon::ProcessIdTag>)
Dynamic exception type: struct boost::wrapexcept<class QuadDCommon::SystemException>
std::exception::what: SystemException
[struct QuadDCommon::tag_errno_text * __ptr64] = Access is denied
[struct QuadDCommon::tag_message * __ptr64] = Failed to open thread 17616 from process 17612
[struct QuadDCommon::tag_winapi_error_code * __ptr64] = 5
[struct boost::errinfo_api_function_ * __ptr64] = OpenThread
ServiceName: AnalysisService
MethodName: Init
SystemError (124) {
ErrorText: Failed to open thread 17616 from process 17612
ApiFunction: OpenThread
OriginalFile: C:\dvs\p4\build\sw\devtools\Agora\Rel\QuadD_Main\QuadD\Common\ProcessResumer\Windows\ProcessResumerImpl.cpp
OriginalLine: 45
OriginalFunction: __cdecl QuadDCommon::ProcessResumer::WindowsProcessResumer::WindowsProcessResumer(class QuadDCommon::StrongType<class QuadDCommon::LimitedNumber<unsigned int,4294967295>,class QuadDCommon::ProcessIdTag>)
OriginalExceptionClass: struct boost::wrapexcept<class QuadDCommon::SystemException>
}
}
}
Going to the NVIDIA control panel and setting “allow acces to the GPU performance counters to all users”, and then starting Nsight systems 2022.4.2 as admin did the trick.
So using 2022 i can do my profiling.
For whatever reason I cannot start nsight systems 2023.2.1 as adminstrator from my normal user account nor the localadmin account. Nothing happens.
Thanks for looking into this @dofek. I had actually all but given up on this but just tried again running as administrator. This was not working before but it will now start profiling. However, after the profiling run has finished it now reports an error saying it has failed to collect any CUDA events. The application ran as normal and produced the expected output.
Got exactly the same issue. Access to counters for all users is on and I run Systems as an admin.
Downloading 2022.5 didn’t help and I don’t have access to older versions unfortunately.
(Edit: Ok, joined Developer Program, thought it will take more than just one click. :) But it seems that installing 2022.4.1.21-0db2c85 did not help at all and the issue persists.)