Amazon Q Language Server fails to start: "LSP failed to activate... initialize failed... The specified module could not be found."

[naeem-zenkoders]

Problem

starting of extension shows some errors:

2025-01-30 16:18:31.091 [info] LspController: LSP already installed
2025-01-30 16:18:31.467 [info] [Info  - 4:18:31 PM] LSP server starts
2025-01-30 16:18:32.361 [info] [Error - 4:18:32 PM] Server initialization failed.
2025-01-30 16:18:32.361 [info]   Message: Request initialize failed with message: The specified module could not be found.
\\?\c:\Users\naeem\.vscode\extensions\amazonwebservices.amazon-q-vscode-1.44.0\resources\qserver\dist\bin\napi-v3\win32\x64\onnxruntime_binding.node
  Code: -32603 
2025-01-30 16:18:32.363 [info] [Error - 4:18:32 PM] Starting client failed
2025-01-30 16:18:32.363 [info]   Message: Request initialize failed with message: The specified module could not be found.
\\?\c:\Users\naeem\.vscode\extensions\amazonwebservices.amazon-q-vscode-1.44.0\resources\qserver\dist\bin\napi-v3\win32\x64\onnxruntime_binding.node
  Code: -32603 
2025-01-30 16:18:32.364 [error] LspController: LSP failed to activate Error: Request initialize failed with message: The specified module could not be found.
\\?\c:\Users\naeem\.vscode\extensions\amazonwebservices.amazon-q-vscode-1.44.0\resources\qserver\dist\bin\napi-v3\win32\x64\onnxruntime_binding.node
2025-01-30 16:18:32.364 [info] [Error - 4:18:32 PM] Unhandled exception: Cannot access 'ONNX_NODE' before initialization
ReferenceError: Cannot access 'ONNX_NODE' before initialization
    at c:\Users\naeem\.vscode\extensions\amazonwebservices.amazon-q-vscode-1.44.0\resources\qserver\dist\extension.js:418:23585
2025-01-30 16:23:25.617 [info] telemetry: sent batch (size=8)

Steps to reproduce the issue

when starting VS Code IDE.

Expected behavior

should start normally.

System details (run AWS: About and/or Amazon Q: About)

Amazon Q extension

• OS: Windows 11
• Visual Studio Code version: 1.96.4
• AWS Toolkit version:
• Amazon Q version:
  OS: Windows_NT x64 10.0.26100
  Visual Studio Code extension host: 1.96.4
  Amazon Q: 1.44.0
  node: 20.18.1
  electron: 32.2.6

[jpinkney-aws]

Hi! In your Amazon Q VS Code settings, do you have the "Amazon Q: Workspace Index Use GPU" enabled? Alternatively, do you have "Amazon Q: Workspace Index" enabled? If so, is it possible for you to try turning those off and then restart or reload VS Code? Thank you!

[naeem-zenkoders]

I have un-checked both "Amazon Q: Workspace Index Use GPU" and "Amazon Q: Workspace Index" and then restarted the VS Code, but still same issue...

[leigaol]

Hi @naeem-zenkoders ,

Is it possible for you to remove this folder c:\Users\naeem\.vscode\extensions\amazonwebservices.amazon-q-vscode-1.44.0\resources\qserver entirely and then restart VS Code?

I was able to reproduce such issue by manually removing the onnxruntime_binding.node. It seems like the operation system removed this .node file for some reason or the download process went wrong at some point. By removing the folder entirely, at the time of extension restarts, the Q extension will download necessary libraries one more time to start the language server.

Seeing such error prompt of LSP not starting will not affect the majority of Amazon Q features.

Feel free to provide more logs for us to triage why the .node file is missing.

Thanks,
Lei

[naeem-zenkoders]

Thank you so much Lei, I have applied your suggestions and then started VS Code, it was good for a while but soon after the error came again.

[9techofficial]

Getting error while opning vs code.

2025-03-19 23:21:07.820 [info] Log level: info, beta=false
2025-03-19 23:21:07.820 [info] Telemetry product: Amazon Q For VS Code
2025-03-19 23:21:07.820 [info] Telemetry clientId: 8c525f72-6d2f-40f5-96e1-e78da72dd97b
2025-03-19 23:21:07.820 [info] Telemetry sessionId: 29dc5b7b-8db6-4c46-b002-513c01b437af
2025-03-19 23:21:07.851 [info] current client registration id=zkL1xdxT_VCmhaZCez-C_3VzLWVhc3QtMQ
    expires at Wed Jun 11 2025 16:09:24 GMT+0530 (India Standard Time)
    key = 817bc946-cb9e-4845-a9b9-5842af5fbec7
2025-03-19 23:21:07.851 [info] auth: Connection is valid: 817bc946-cb9e-4845-a9b9-5842af5fbec7
2025-03-19 23:21:07.851 [info] auth: Updating connection state of 817bc946-cb9e-4845-a9b9-5842af5fbec7 to valid
2025-03-19 23:21:07.851 [info] codewhisperer: active connection changed
2025-03-19 23:21:07.851 [info] secondaryAuth: connectionId=817bc946-cb9e-4845-a9b9-5842af5fbec7, connectionStatus=valid
2025-03-19 23:21:07.851 [info] codewhisperer: connection states
    connection isValid=true,
    connection isValidCodewhispererCoreConnection=true,
    connection isExpired=false,
    secondaryAuth isExpired=false,
    connection isUndefined=false
2025-03-19 23:21:07.904 [info] auth: Connection is valid: 817bc946-cb9e-4845-a9b9-5842af5fbec7
2025-03-19 23:21:07.904 [info] auth: Updating connection state of 817bc946-cb9e-4845-a9b9-5842af5fbec7 to valid
2025-03-19 23:21:07.904 [info] codewhisperer: active connection changed
2025-03-19 23:21:07.928 [info] using codewhispererService service configuration: default
2025-03-19 23:21:07.983 [info] initialized 'submitFeedback' command with default feedback id: Amazon Q
2025-03-19 23:21:07.988 [info] auth: Connection is valid: 817bc946-cb9e-4845-a9b9-5842af5fbec7
2025-03-19 23:21:07.988 [info] auth: Updating connection state of 817bc946-cb9e-4845-a9b9-5842af5fbec7 to valid
2025-03-19 23:21:08.183 [info] auth: Connection is valid: 817bc946-cb9e-4845-a9b9-5842af5fbec7
2025-03-19 23:21:08.184 [info] auth: Updating connection state of 817bc946-cb9e-4845-a9b9-5842af5fbec7 to valid
2025-03-19 23:21:08.354 [warning] AwsContext: no default region in credentials profile, falling back to us-east-1:
2025-03-19 23:21:08.386 [info] auth: Connection is valid: 817bc946-cb9e-4845-a9b9-5842af5fbec7
2025-03-19 23:21:08.386 [info] auth: Updating connection state of 817bc946-cb9e-4845-a9b9-5842af5fbec7 to valid
2025-03-19 23:21:09.282 [info] AB Testing Cohort Assignments []
2025-03-19 23:21:09.295 [info] AB Testing Cohort Assignments []
2025-03-19 23:21:13.026 [info] LspController: LSP already installed
2025-03-19 23:21:13.085 [info] [Info  - 11:21:13 PM] LSP server starts
2025-03-19 23:21:13.206 [info] [Error - 11:21:13 PM] Server initialization failed.
2025-03-19 23:21:13.206 [info]   Message: Request initialize failed with message: The specified module could not be found.
\\?\c:\Users\Home\.vscode\extensions\amazonwebservices.amazon-q-vscode-1.51.0\resources\qserver\dist\build\Release\faiss-node.node
  Code: -32603 
2025-03-19 23:21:13.206 [info] [Error - 11:21:13 PM] Starting client failed
2025-03-19 23:21:13.206 [info]   Message: Request initialize failed with message: The specified module could not be found.
\\?\c:\Users\Home\.vscode\extensions\amazonwebservices.amazon-q-vscode-1.51.0\resources\qserver\dist\build\Release\faiss-node.node
  Code: -32603 
2025-03-19 23:21:13.206 [error] LspController: LSP failed to activate Error: Request initialize failed with message: The specified module could not be found.
\\?\c:\Users\Home\.vscode\extensions\amazonwebservices.amazon-q-vscode-1.51.0\resources\qserver\dist\build\Release\faiss-node.node

[diogozedan]

I encountered a similar issue where the language server was not initializing because Node failed to run a process. In my case, the root cause was misconfigured AWS profiles in my ~/.aws folder. After correcting the profile configurations, the language server started working as expected.

If anyone else runs into this, I recommend double-checking your AWS profile setup in the .aws directory.