SSMS 2016 CTP2 cannot open properties of SQL 2014 availability group - by Trayce Jordan

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


5
0
Sign in
to vote
ID 1609719 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 7/30/2015 9:41:34 AM
Access Restriction Public

Description

Using SSMS 2016 CTP2, when you right click on an availability group to see it's properties you receive an error:

TITLE: Microsoft SQL Server Management Studio
------------------------------

Cannot show requested dialog.

------------------------------
ADDITIONAL INFORMATION:

Cannot show requested dialog. (SqlMgmt)

------------------------------

Cannot read property BasicAvailabilityGroup.This property is not available on SQL Server 2014. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=13.0.400.91+((SQL_Main).150716-0357)&EvtID=BasicAvailabilityGroup&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------
Sign in to post a comment.
Posted by AmarKadenic on 11/3/2015 at 1:07 AM
I just discovered this today, good thing it was before the presentation. I am using the latest SSMS update for SQL Server 2016 CTP3 (13.0.700.242) and I cannot access the properties menu on any Availability Group of version SQL Server 2012 or 2014.

Please advise on a workaround or a permanent soultion, the later to be preferred.



TITLE: Microsoft SQL Server Management Studio
------------------------------

Cannot show requested dialog.

------------------------------
ADDITIONAL INFORMATION:

Cannot show requested dialog. (SqlMgmt)

------------------------------

Cannot read property BasicAvailabilityGroup.This property is not available on SQL Server 2012. (Microsoft.SqlServer.Smo)
------------------------------
BUTTONS:

OK
------------------------------
Posted by Ryan J. Adams on 8/31/2015 at 3:18 PM
I just ran into this today and I get the same thing using SSMS 13.0.400.91.