SSMS 2016 CTP3.1 November Preview (v13.0.800.111) bug? properties error: missing column federated_service_account Using SSMS 2016 CTP3.1 November Preview (v13.0.800.111) on my laptop, whenever I right click any database object (the database, a table, etc.) I get the below error.


  TITLE: Microsoft SQL Server Management Studio
  
  Cannot show requested dialog.
  
  
  
  ADDITIONAL INFORMATION:
  
  Cannot show requested dialog. (SqlMgmt)
  
  Attempt to retrieve data for object failed for Server ''.  >(Microsoft.SqlServer.Smo)
  
  For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&amp;ProdVer=13.0.800.111+((SQL_Main).151121-1556)&amp;EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&amp;EvtID=Attempt+to+retrieve+data+for+object+Server&amp;LinkId=20476
  
  
  
  An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)





  Invalid column name 'federated_service_account'.
  Invalid column name 'federated_service_account'. (Microsoft SQL Server, Error: 207)
  
  For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&amp;ProdVer=13.00.0700&amp;EvtSrc=MSSQLServer&amp;EvtID=207&amp;LinkId=20476
  
  
  
  BUTTONS:
  
  OK


I was able to run a Profiler trace to determine the query that's being run to throw this error:

SELECT
eds.location AS [RemoteDataArchiveEndpoint],
eds.name AS [RemoteDataArchiveLinkedServer],
rdad.remote_database_name AS [RemoteDatabaseName],
rdad.federated_service_account AS [RemoteDataArchiveUseFederatedServiceAccount],
case when rdad.federated_service_account = 1 then null else cred.name end AS [RemoteDataArchiveCredential]
FROM
sys.remote_data_archive_databases rdad
INNER JOIN sys.external_data_sources eds ON rdad.data_source_id = eds.data_source_id
LEFT OUTER JOIN sys.database_scoped_credentials cred ON eds.credential_id = cred.credential_id


Anyone recognize this query? Where is it coming from, what's the source? Anyone else experiencing a similar error? Is this an SSMS bug?

Some interesting repro notes:


This error happens while connecting from my laptop to the database that's on a VM in my organization.
While RDP'd in to the VM and running SSMS locally on the VM and connecting to localhost, the error does not repro.
The SSMS version on the VM (v13.0.700.242) is lower than the SSMS version on my laptop (v13.0.800.111). Hence, I'm afraid to update the SSMS on the VM to latest version as this error might throw there too.
Running the profiler trace directly on the VM and doing the repro steps does not generate the same SQL that the newer SSMS version seems to generate from my laptop.
Updating the VM's engine to CTP 3.1 resolved the issue. I no longer get the error on my laptop's SSMS.