Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After Upgrading SQL Server Management Studio winget see three of it's packages as out-of-date. #2269

Closed
camckee opened this issue Jun 22, 2022 · 3 comments
Labels
Resolution-Duplicate Issue is a duplicate
Milestone

Comments

@camckee
Copy link

camckee commented Jun 22, 2022

Brief description of your issue

When upgrading Microsoft SQL Management Studio to 18.12 using winget, something went wrong. The tool installed two instances of the application. After manually uninstalling the two instances and related packages, I reinstalled the latest version. The installation went fine, and Management Studio is operating normally. Now winget sees three packages installed by SSMS as out-of-date and related to Microsoft.SQLServerManagementStudio product. The version installed is correct, but it's comparing the version number to the version number of SSMS.

image

Steps to reproduce

  1. Manually upgrade SSMS to version 18.12.
  2. Run winget upgrade.
  3. Notice the related packages associated with the SSMS version and not to their own package version.

Expected behavior

Microsoft Help View 2.3, Azure Data Studio (User), and Microsoft SQL Server 2012 Native Client are not to be associated with the SSMS Version but with their own product version.

Actual behavior

Microsoft Help View 2.3, Azure Data Studio (User), and Microsoft SQL Server 2012 Native Client are related to the SSMS version.

Environment

Windows Package Manager (Preview) v1.3.1391-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19044.1766
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.18.1391.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale
@ghost ghost added the Needs-Triage Issue need to be triaged label Jun 22, 2022
@ItzLevvie
Copy link

ItzLevvie commented Jun 22, 2022

@denelon
Copy link
Contributor

denelon commented Jun 22, 2022

Duplicate of #2152

@denelon denelon marked this as a duplicate of #2152 Jun 22, 2022
@ghost
Copy link

ghost commented Jun 22, 2022

@camckee we've identified this Issue as a duplicate of another one that already exists. This specific instance is being closed in favor of tracking the concern over on the referenced Issue. Thanks for your report! Be sure to add your 👍 to the other issue to help raise the priority.

@ghost ghost closed this as completed Jun 22, 2022
@ghost ghost added Resolution-Duplicate Issue is a duplicate and removed Needs-Triage Issue need to be triaged labels Jun 22, 2022
@denelon denelon added this to the v1.4-Client milestone Nov 22, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate Issue is a duplicate
Projects
None yet
Development

No branches or pull requests

3 participants