12 Jun 2024 05:59 AM - last edited on 12 Jun 2024 08:26 AM by MaciejNeumann
Hi everyone,
I am trying to initialize workspace in Visual Studio Code but I got an error message of "Cannot initialize workspace without certificates":
But I got previous notification of Certificate successfully uploaded to Credentials Vault. So there is a certificate uploaded, how come Visual Studio Code cannot initialize workspace?
Best Regards,
Rudy
12 Jun 2024 03:43 PM
I believe you have generated your certificates, according to:
https://docs.dynatrace.com/docs/extend-dynatrace/extensions20/sign-extension
Besides configuring them in Dynatrace, the extension signing occurs in your development environment, so you then should have to configure them in Visual Studio, if you haven't done so.
Check out the following video, and check if you have done the certificate part, slightly after minute 25:
https://www.youtube.com/watch?v=Qy4Ge8HIzEk&t=137s
13 Jun 2024 01:08 AM
I was following this video step by step but I failed. Here is the log:
2024-06-13 06:46:10.577 [info] Extension host terminating: renderer closed the MessagePort
2024-06-13 06:46:10.678 [info] Extension host with pid 10008 exiting with code 0
2024-06-13 06:46:12.327 [info] Extension host with pid 11520 started
2024-06-13 06:46:12.327 [info] Skipping acquiring lock for c:\Users\Lenovo\AppData\Roaming\Code\User\workspaceStorage\e5937d6d5a174155d5a6a913c6c6b207.
2024-06-13 06:46:12.367 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: true, activationEvent: '*', root cause: vscode.git
2024-06-13 06:46:12.376 [info] ExtensionService#_doActivateExtension vscode.git, startup: true, activationEvent: '*'
2024-06-13 06:46:12.413 [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
2024-06-13 06:46:12.514 [info] Eager extensions activated
2024-06-13 06:46:12.555 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2024-06-13 06:46:12.563 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'
2024-06-13 06:46:12.579 [info] ExtensionService#_doActivateExtension redhat.vscode-yaml, startup: false, activationEvent: 'onStartupFinished', root cause: DynatracePlatformExtensions.dynatrace-extensions
2024-06-13 06:46:12.870 [info] ExtensionService#_doActivateExtension DynatracePlatformExtensions.dynatrace-extensions, startup: false, activationEvent: 'onStartupFinished'
2024-06-13 06:46:13.343 [warning] [redhat.vscode-yaml] Accessing a resource scoped configuration without providing a resource is not expected. To get the effective value for '[yaml]', provide the URI of a resource or 'null' for any resource.
2024-06-13 06:46:13.346 [warning] [redhat.vscode-yaml] Accessing a resource scoped configuration without providing a resource is not expected. To get the effective value for '[yaml]', provide the URI of a resource or 'null' for any resource.
2024-06-13 06:46:14.107 [warning] [redhat.vscode-yaml] Accessing a resource scoped configuration without providing a resource is not expected. To get the effective value for '[yaml]', provide the URI of a resource or 'null' for any resource.
2024-06-13 06:48:02.186 [info] ExtensionService#_doActivateExtension vscode.json-language-features, startup: false, activationEvent: 'onLanguage:jsonc'
2024-06-13 06:48:02.219 [info] ExtensionService#_doActivateExtension vscode.typescript-language-features, startup: false, activationEvent: 'onLanguage:jsonc'
2024-06-13 06:48:02.254 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onLanguage'
2024-06-13 06:48:02.328 [warning] [redhat.vscode-yaml] Accessing a resource scoped configuration without providing a resource is not expected. To get the effective value for '[yaml]', provide the URI of a resource or 'null' for any resource.
2024-06-13 06:48:19.304 [warning] [redhat.vscode-yaml] Accessing a resource scoped configuration without providing a resource is not expected. To get the effective value for '[yaml]', provide the URI of a resource or 'null' for any resource.
2024-06-13 06:48:19.347 [warning] [redhat.vscode-yaml] Accessing a resource scoped configuration without providing a resource is not expected. To get the effective value for '[yaml]', provide the URI of a resource or 'null' for any resource.
The log showed the root causes are : DynatracePlatformExtensions.dynatrace-extensions
Best Regards,
Rudy
27 Jun 2024 07:31 PM
You ever get a solution to this?
I too have followed the video step by step and am getting the same thing. Certificate successfully uploaded to Credentials Vault message followed by a Cannot initialize workspace without certificates...
I've deleted and retried initializing new workspaces.
My Environment shows connected, is green, and I can freely browse the entire environment schema in vsCode.
My token used to connect to the environment was generated using the Extension Development template (I've also tried using another token that has full read/write to the entire environment as well).
I've even tried completely removing the Dynatrace vsCode extension and starting over from scratch.
Still, nothing works... Cert successfully uploaded followed by cannot initialize workspace. Very frustrating.
13 Jun 2024 02:25 AM
It is Dynatrace Extension version 2.6.1 that cannot initialize workspace. If I use version 2.3.1 (exactly the same as the video) and schema version 1.275.0 used by the video, then my Visual Studio Code is working now
Best Regards,
Rudy