microsoft / azuredatastudio

Azure Data Studio is a data management and development tool with connectivity to popular cloud and on-premises databases. Azure Data Studio supports Windows, macOS, and Linux, with immediate capability to connect to Azure SQL and SQL Server. Browse the extension library for more database support options including MySQL, PostgreSQL, and MongoDB.
https://learn.microsoft.com/sql/azure-data-studio
MIT License
7.53k stars 896 forks source link

No visible connections #25740

Open charymarinas opened 1 month ago

charymarinas commented 1 month ago

Issue Type: Bug

From one day to the next all the servers and databases that I had saved in the connection tab disappeared and I cannot create any new ones, which means I cannot use Azure Data Studio :(

Azure Data Studio version: azuredatastudio 1.25.1 (e7eacc32c0d20bd4da843320c3bfac231b308c98, 2020-12-11T01:59:24.271Z) OS version: Windows_NT x64 10.0.19045

System Info |Item|Value| |---|---| |CPUs|12th Gen Intel(R) Core(TM) i5-1245U (12 x 2496)| |GPU Status|2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
opengl: enabled_on
protected_video_decode: enabled
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled| |Load (avg)|undefined| |Memory (System)|15.67GB (3.51GB free)| |Process Argv|| |Screen Reader|no| |VM|0%|
Extensions: none
kburtram commented 1 month ago

@charymarinas are you able to update a newer version of Azure Data Studio? If the issue description is correct you're using 1.25.1, and there have been many connectivity related improvements in more recent releases.

charymarinas commented 1 month ago

Hello Karl,

I have updated now to the 1.48.1 and I'm facing the same issue... Any idea?

Thank you.

Best regards,

Chary Mariñas.

From: Karl Burtram @.> Sent: viernes, 12 de julio de 2024 20:10 To: microsoft/azuredatastudio @.> Cc: MARIÑAS Chary @.>; Mention @.> Subject: Re: [microsoft/azuredatastudio] No visible connections (Issue #25740)

External email. Think before clicking links or opening attachments

@charymarinashttps://github.com/charymarinas are you able to update a newer version of Azure Data Studio? If the issue description is correct you're using 1.25.1, and there have been many connectivity related improvements in more recent releases.

- Reply to this email directly, view it on GitHubhttps://github.com/microsoft/azuredatastudio/issues/25740#issuecomment-2226123797, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BG43HWFVATGRU5JP2USBXJTZMALZLAVCNFSM6AAAAABKYMGFCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRWGEZDGNZZG4. You are receiving this because you were mentioned.Message ID: @.**@.>>

lewis-sanchez commented 2 weeks ago

Hi @charymarinas, I haven't been able to successfully repro this issue. Is it possible for you to attach console or application logs to help me identify what could be causing this for you?

github-actions[bot] commented 2 weeks ago

We need more info to debug your particular issue. If you could attach your logs to the issue (ensure no private data is in them), it would help us fix the issue much faster.

  1. First open the Settings page, find the Mssql: Tracing Level setting and change that to All then restart Azure Data Studio.
  2. Open command palette (Click View -> Command Palette) and run the command Developer: Set Log Level... and set the level to Trace.
  3. Run the repro scenarios.
  4. Collect the following logs:

    Console Logs

    • Open Developer Tools (Help -> Toggle Developer Tools)
    • Click the Console tab
    • Click in the log area and select all text (CTRL+A)
    • Save this text into a file named console.log and attach it to this issue.
    • Developer Tools can be closed via Help -> Toggle Developer Tools

    Application Logs

    • Open command palette (Click View -> Command Palette)
    • Run the command: Developer: Open Logs Folder
    • This will open the log folder locally. Please zip up this folder and attach it to the issue.
  5. Now you can revert the Log/Tracing levels changes made in step 1 and step 2.