search

intel / vscode-oneapi-environment-configurator

Other
9 stars 4 forks source link

VSCode environment configurator fails fresh install oneAPI basekit. #5

Closed AdamMiltonBarker closed 2 years ago

AdamMiltonBarker commented 3 years ago

Posted in forum also https://community.intel.com/t5/Intel-oneAPI-Base-Toolkit/VSCode-environment-configurator-fails/m-p/1297614#M1625

Not a question just letting you know the environment configurator for VSCode does not work. Fresh install of basekit on Windows 10, command prompt works fine, when trying to start the environment in vscode it pops up with Error 1, then after that window is closed it pops up as if it has worked but it hasn't.

oneapi-bug oneapi-bug-2 oneapi-bug-3

sbobko commented 3 years ago

@AdamMiltonBarker Hi, Could you run setvars in PS directly, without our extension? something in the form of .\setvars.bat image

The problem that you are facing is quite difficult to debug, as there can be many reasons. In short, the exec function could not run setvars. The most likely reasons are: a problem with execution rights, PowerShell or something like that. Our experiment with manual launch will allow us to narrow down the range of possible defects.

AdamMiltonBarker commented 3 years ago

I didn't remember posting here :) Yes that works and I can run that command with VS terminal also.

sbobko commented 3 years ago

@AdamMiltonBarker okay, copy that. It is most likely that you have PowerShell version 5.1 (or so) , which is not detected by our extension. This is definitely our problem and it will be fixed soon, but you can install a newer version of PowerShell to make everything work right now: https://github.com/PowerShell/PowerShell/releases/tag/v7.1.3

AdamMiltonBarker commented 3 years ago

Hi the path is now found after the update (See bottom right of screen shot) but I still get an error.

Capture

sbobko commented 3 years ago

@AdamMiltonBarker Okay, then there may be a problem with access rights. Try running VSCode as an Administrator. I think this will solve the problem.

AdamMiltonBarker commented 3 years ago

@sbobko thank you I will do later tonight and will let you know.

AdamMiltonBarker commented 3 years ago

Nope sorry that isn't it either I have a new error now :( nope

AdamMiltonBarker commented 3 years ago

OK hang on, after that I tried again and it worked. It looks the permissions is the issue. No output in terminal though, should there be ? I can't access any of my network drives now through code when running as admin.

sbobko commented 3 years ago

Unfortunately, I do not know what the problem is with network drives, since it is not related to the extension. While there are no reports of insufficient permissions, however, I expect that we will add it in the near future or solve the problem differently. Thank you for your assistance in the search :).

AdamMiltonBarker commented 3 years ago

No problem was just letting you know to resolve the issue it means I cannot use VS code in the usual way. Hope the issue helped.

xmnboy commented 2 years ago

Adding reference to internal bug report > DEV1A-3312.

sbobko commented 2 years ago

@AdamMiltonBarker The issue has been fixed. Please reopen if necessary