SQL Server Management Studio (SSMS) 19.0 Released!

erinstellato 

I'm still having problems with SSMS 19.0.2 and looking at publication details, connecting to SQL 2017 Standard Edition server if that makes a difference.

Here is the text of the pop-up screen:

Could not find any resources appropriate for the specified culture or the neutral culture. Make sure "Microsoft.SqlServer.Management.UI.PublicationAccessListPage.resources" was correctly embedded or linked into assembly "CreatePubWizard" at compile time, or that all the satellite assemblies required are loadable and fully signed. (mscorlib)

I also get that same message when trying to use Replication Monitor.

Thanks

Both still work with the previous version of SSMS 18.12.1

@erinstellato

I also confirmed the ability to view Publication properties in SSMS 19.0.2, but viewing conflicts is still having an issue.

Logging into SQL Server locally, whether with Windows auth. or a SQL Server user, I still CANNOT view replication conflicts (by right-clicking the Publication > clicking View Conflicts).

HOWEVER...connecting to SQL Server remotely, using an alias, I am able to view conflicts.

Also, using an alias allows me to connect to a remote SQL Server instance regardless if "Trust server certificate" is checked, during the login. I don't know the internals for the SQL Server security and aliases, so I am unaware if this is unwanted behavior.

Thanks again!!

I confirm that the issue related to sql publication properties is now gone and can again edit my publications in SQL Server 2022. erinstellato  Thanks for the fast reaction.

I am now looking into the update of chocolatey package to include this release:)

Hey all - we have released SSMS 19.0.2 (https://learn.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver16) which contains fixes for the AAD issue, viewing properties on a publication, PowerBI, and restarting the Agent from within SSMS.  Please check out the release notes (Release notes for (SSMS) - SQL Server Management Studio (SSMS) | Microsoft Learn) for additional details.  Thanks!

@erinstellato

When you right-click a Publication, you can click View Conflicts. As described previously, you're then prompted for the Connect to Server login window. After login, the error window pops. The error details are...

===================================

Could not show Conflict Viewer.

------------------------------
For help, click: https://go.microsoft.com:80/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=16.200.20200.0&Evtsrc=Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.Replication.ReplicationMenuItem&EvtID=CantShowConflictViewer&LinkId=20476

===================================

Exception has been thrown by the target of an invocation. (mscorlib)

------------------------------
Program Location:

at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.Replication.ReplicationMenuItem.OnCreateAndShowConflictViewer(IServiceProvider sp, XmlDocument doc)

===================================

A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The target principal name is incorrect.) (Framework Microsoft SqlClient Data Provider)

------------------------------
For help, click: https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver--2146893022-database-engine-error

------------------------------
Server Name: [the server name]
Error Number: -2146893022
Severity: 20
State: 0

------------------------------
Program Location:

at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at Microsoft.Data.SqlClient.TdsParserStateObject.SNIWritePacket(SNIHandle handle, SNIPacket packet, UInt32& sniError, Boolean canAccumulate, Boolean callerHasConnectionLock)
at Microsoft.Data.SqlClient.TdsParserStateObject.WriteSni(Boolean canAccumulate)
at Microsoft.Data.SqlClient.TdsParserStateObject.WritePacket(Byte flushMode, Boolean canAccumulate)
at Microsoft.Data.SqlClient.TdsParser.TdsLogin(SqlLogin rec, FeatureExtension requestedFeatures, SessionData recoverySessionData, FederatedAuthenticationFeatureExtensionData fedAuthFeatureExtensionData, SqlClientOriginalNetworkAddressInfo originalNetworkAddressInfo)
at Microsoft.Data.SqlClient.SqlInternalConnectionTds.Login(ServerInfo server, TimeoutTimer timeout, String newPassword, SecureString newSecurePassword)
at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover, Boolean isFirstTransparentAttempt, Boolean disableTnir)
at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, ServerCertificateValidationCallback serverCallback, ClientCertificateRetrievalCallback clientCallback, DbConnectionPool pool, String accessToken, SqlClientOriginalNetworkAddressInfo originalNetworkAddressInfo, Boolean applyTransientFaultHandling)
at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
at Microsoft.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at Microsoft.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at Microsoft.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry, SqlConnectionOverrides overrides)
at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides)
at Microsoft.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.UI.ConflictViewer.PublicationForm.InitForm(String servername, Boolean ntAuth, String username, String password, ViewerForm viewform)
at Microsoft.SqlServer.Management.UI.ConflictViewer.PublicationForm.InitFormFromOE(SqlConnectionInfo sqlConn, ViewerForm viewform)

===================================

The target principal name is incorrect

I'm wondering if the problem proboszcz describes isn't related, as I get the same error trying to view Publication properties.

Also, are you running SSMS as Administrator, because doing so allows you to restart the SQL Server service from SSMS.

Thanks!!

proboszcz It will be fixed in the next release, which is very soon, I promise 🙂

erinstellato 

Are there any updates on the issue with SQL Publication dialog strange "culture/ neutral culture" related error message?

@NeilK-PDC I had another user report the issue with not being able to restart the service from SSMS, but I cannot recreate that behavior.   Trust server certificate is improved security configuration.  For the third item, View Conflicts, I'm not familiar with that, can you please provide the steps to recreate the issue so I can try it locally?  Thanks.

SQLBIDEV Thank you for the update, I'm glad the team was able to help find the resolution, I appreciate you sharing that here.

Urban_Svensson thank you for helping out @SBMMedhost!

luistorres thanks for helping out Jason2310.

Turns out I only get that installer error when trying to install using winget. The standalone installer completed without issue.

I have the same windows version as you, and no problem installing or working with it.
Edition Windows 10 Enterprise
Version 21H2
Installed on ‎10/‎21/‎2021
OS build 19044.2604
Experience Windows Feature Experience Pack 120.2212.4190.0

I have SQL Server Management Studio installed on my laptop:

SQL Server Management Studio 19.0.20200.0+9286509b
SQL Server Management Objects (SMO) 16.200.48036.0+7d3b143d945e1aa638acdb02c0364e263d5ec973
Microsoft T-SQL Parser 16.0.22524.0+62eedb15cd3cde34e51c8fbbdf9b06e575ec912e
Microsoft Analysis Services Client Tools 16.0.19970.0
Microsoft Data Access Components (MDAC) 10.0.19041.2604
Microsoft MSXML 3.0 6.0
Microsoft .NET Framework 4.0.30319.42000
Operating System 10.0.19044