Confirmed that our billing is current, last payment successfully remitted 2022-06-17
We’ve been using SonarCloud without interruption for over a year.
Was working fine on Friday
We’re using SonarCloud with Bitucket.
SonarScanner for MSBuild 5.7
Using the .NET Core version of the Scanner for MSBuild
Our developers in multiple code bases are reporting that when CICD attempts to call the SonarCloud CLI, the scan fails with an unhandled exception (stack trace below).
Stack Trace
Calling the SonarScanner CLI...
Unhandled exception. System.ComponentModel.Win32Exception (13): Permission denied
at System.Diagnostics.Process.ForkAndExecProcess(String filename, String[] argv, String[] envp, String cwd, Boolean redirectStdin, Boolean redirectStdout, Boolean redirectStderr, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec)
at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at SonarScanner.MSBuild.Common.ProcessRunner.Execute(ProcessRunnerArguments runnerArgs)
at SonarScanner.MSBuild.Shim.SonarScannerWrapper.ExecuteJavaRunner(AnalysisConfig config, IEnumerable`1 userCmdLineArguments, ILogger logger, String exeFileName, String propertiesFileName, IProcessRunner runner)
at SonarScanner.MSBuild.Shim.SonarScannerWrapper.InternalExecute(AnalysisConfig config, IEnumerable`1 userCmdLineArguments, ILogger logger, String fullPropertiesFilePath)
at SonarScanner.MSBuild.Shim.SonarScannerWrapper.Execute(AnalysisConfig config, IEnumerable`1 userCmdLineArguments, String propertiesFilePath)
at SonarScanner.MSBuild.PostProcessor.MSBuildPostProcessor.InvokeSonarScanner(IAnalysisPropertyProvider cmdLineArgs, AnalysisConfig config, String propertiesFilePath)
at SonarScanner.MSBuild.PostProcessor.MSBuildPostProcessor.Execute(String[] args, AnalysisConfig config, ITeamBuildSettings settings)
at SonarScanner.MSBuild.BootstrapperClass.PostProcess()
at SonarScanner.MSBuild.BootstrapperClass.Execute()
at SonarScanner.MSBuild.Program.Execute(String[] args, ILogger logger)
at SonarScanner.MSBuild.Program.Execute(String[] args)
at SonarScanner.MSBuild.Program.Main(String[] args)
at SonarScanner.MSBuild.Program.<Main>(String[] args)
As the new version was published to nuget only a short period of time before you tried again, it might be that it was still installing the 5.7.0 version of the dotnet-sonarscanner.
Other users with the same issue have reported that using the 5.7.1 version fixed the exact same problem they had.
Could you please check in the logs that you used indeed the 5.7.1 version of the dotnet-sonarscanner?
I’m going to send you a private message on this forum to better understand your pipeline setup and environment. It shouldn’t involve logs and sensitive info, still I’ll send a private message to feel safe.
The idea is that we want to add a regression test for such scenario and we first need to reproduce the problem (we currently don’t have a reproducer).