SonarQube Scanning Error

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
  • what are you trying to achieve
  • what have you tried so far to achieve this

Hello
I tried Code analysis was performed using SonarQube.
However, the following error occurs.
What is the cause and is there a solution?

-------------------------------------------------------------------
ERROR: Error during SonarScanner execution
java.lang.IllegalStateException: C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\um\Mmsystem.h.
	at com.sonar.cpp.jni.FileSystemOperations.realPath(FileSystemOperations.java:57)
	at java.base/java.util.HashMap.computeIfAbsent(HashMap.java:1133)
	at com.sonar.cpp.fs.CanonicalPathCache.computeIfAbsent(CanonicalPathCache.java:17)
	at com.sonar.cpp.plugin.CFamilySensor.canonicalizeFilename(CFamilySensor.java:1189)
	at com.sonar.cpp.plugin.CFamilySensor.lambda$save$20(CFamilySensor.java:1065)
	at java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
	at java.base/java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:658)
	at com.sonar.cpp.plugin.CFamilySensor.save(CFamilySensor.java:1065)
	at com.sonar.cpp.plugin.CFamilySensor.lambda$process$19(CFamilySensor.java:1039)
	at com.sonar.cpp.analyzer.AnalysisExecutor.lambda$submit$0(AnalysisExecutor.java:59)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)
ERROR: 
The SonarScanner did not complete successfully

SonarQube version: 9.6.1.59531
SonarScanner version: sonar-scanner-msbuild-5.8.0.52797-net46

Hey there.

Can you provide a wider range of logs? It’s hard to tell what was going on in the scanner when you got this specific stacktrace.