Common Issues

Common configuration issues

Issue	Workaround
On Windows, VS Code might default to using the bash shell profile for the terminal, which can cause Liberty Start and other Liberty actions to fail:	Remove the following setting from the settings.json file: "terminal.integrated.shell.windows": "[path to bash shell]". Removing this setting enables the terminals in VS Code to run with Windows PowerShell or Command Prompt and allows the Liberty Dashboard actions to run.
On Windows, VS Code might default to using the PowerShell profile for the terminal. If permissions are not set up correctly with PowerShell, permission issues can occur when you try to run Liberty actions, as shown in the following example:	Change the launch profile of the terminal from PowerShell to Command Prompt. You can make the change on a per-terminal instance, or you can change the Default Profile as shown in the following screen shot:
Completion suggestions are sometimes missing for Liberty features in the server.xml file. Suggestions that begin with an 'abc' tag are not valid feature suggestions.	To resolve this issue, disable the IntelliSense text-suggestions in VS Code, either by using the Settings menu or by editing the settings.json file. To disable IntelliSense text-suggestions from the Settings menu, click File > Preferences > Settings and type show words in the search box at the beginning of the menu. Then, uncheck the Editor > Suggest: Show Words setting. Alternatively, add the following code to the settings.json file: "editor.suggest.showWords": false Unfortunately, this workaround causes property value suggestions to be unavailable in both bootstrap.properties and server.env. You will need to re-enable the Show Words setting in order to receive property value suggestions in bootstrap.properties and server.env.