search

Azure / bicep

Bicep is a declarative language for describing and deploying Azure resources
MIT License
3.27k stars 755 forks source link

dotnet.exe access denied because of this error #15276

Open msjo66 opened 1 month ago

msjo66 commented 1 month ago

Does this occur consistently? Repro steps:

1. 2.

Action: bicep.activate Error type: EPERM Error Message: spawn EPERM

Version: 0.30.23 OS: win32 OS Release: 10.0.19045 Product: Visual Studio Code Product Version: 1.94.1 Language: en

Call Stack ``` extension.js:2:2079644extension.js:2:2079644 async LanguageClient.createConnection extension.js:2:1899159 async LanguageClient.start extension.js:2:1889513 extension.js:2:2704251extension.js:2:2704251 ```
majastrz commented 1 month ago

@msjo66 Does the user that's launching VS code (and the Bicep extension) have access to dotnet on the same machine?

Also, did you use a custom dotnet installation path with our extension?

msjo66 commented 1 month ago

@majastrz Frankly speaking, the problem is not Bicep but dotnet.exe. I'm the owner of dotnet.exe but when I execute dotnet.exe, it returns 'access denied' and it causes following

2024-10-20T23:16:43.113Z debug: Found language server at 'c:\Users\10156166.vscode\extensions\ms-azuretools.vscode-bicep-0.30.23\bicepLanguageServer\Bicep.LangServer.dll'. [Error - 8:16:43 AM] Bicep client: couldn't create connection to server. Error: spawn EPERM at ChildProcess.spawn (node:internal/child_process:421:11) at Object.spawn (node:child_process:795:9) at c:\Users\10156166.vscode\extensions\ms-azuretools.vscode-bicep-0.30.23\out\extension.js:2:2079644 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async LanguageClient.createConnection (c:\Users\10156166.vscode\extensions\ms-azuretools.vscode-bicep-0.30.23\out\extension.js:2:1899159) at async LanguageClient.start (c:\Users\10156166.vscode\extensions\ms-azuretools.vscode-bicep-0.30.23\out\extension.js:2:1889513) at async c:\Users\10156166.vscode\extensions\ms-azuretools.vscode-bicep-0.30.23\out\extension.js:2:2704251 8:16:43 AM: Error: spawn EPERM 2024-10-20T23:16:43.163Z error: spawn EPERM

majastrz commented 3 weeks ago

@msjo66 Agreed. The part that's not clear is what makes your machine different from others where this is working. Can you share any details about how it's setup? What's the OS distribution or any other details that may potentially be relevant?