Sql-server – Transactional Data Replication, SQL Server version compatibility

If you're sure the user in question has View Server State (and it looks like in your screenshot he does).

Then there are a number of reasons previously put into an msdn blog. Ranging from:

1. Performance Objects and counters set-up during the SQL Server installation failed.
2. A mixture of 64 and 32 bit platforms.
3. Registry permissions have been skewed

To resolve this we can use the same steps outlined in the guidelines for reinstalling the performance counters in a different stack-exchange post:

Using an elevated administrator command prompt perform the following steps.

1. Change the path to the BINN directory of the SQL Server instance you desire to correct.
   (Ex: C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2008\MSSQL\Binn)
2. Execute unlodctr <<REGISTERED SERVER NAME>>
   For example: unlodctr MSSQL$SQL2008 or SQLAgent$SQL2008 ...
3. Execute lodctr /T:<<perf-sql* matching the counters you desire to load>>
   For example: perf-MSSQL$SQL2008sqlctr.ini or perf-SQLAgent$SQL2008sqlagtctr.ini for SQLAgent. The /T is important to load the SQL Server performance counter provider as a trusted provider.
4. Cycle the remote registry service:
   net stop "Remote Registry" then net start "Remote Registry"
5. Force a WMI synchronization using winmgmt /resyncperfctr "<<PID>>"
   where PID is the process id of the WinPriv.exe (you can get this from Task Manager)

The following may also be required:

• Make sure that the correct security permissions have been granted to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009
  registry key:

  1. Grant Full Control permissions to the Creator Owner account.
  2. Grant Full Control permissions to the Administrators account.
  3. Grant Read permissions to the SQL Administrators on that box/Node.
  4. Grant Full Control permissions to the System account

You can no longer use SOAP/HTTP endpoints. This isn't a SQL Server 2016 problem, since this would not have worked in 2014 either. From the documentation on CREATE ENDPOINT:

NOTE: Native XML Web Services (SOAP/HTTP endpoints) was removed in SQL Server 2012.

It has been deprecated for at least 8 years (this is the oldest version of the current document I could find):

• Deprecated Database Engine Features in SQL Server 2008

If you look at that document, you will see that "The CREATE ENDPOINT or ALTER ENDPOINT statement with the FOR SOAP option" was deprecated at that time. Their suggestion for a replacement is to "Use Windows Communications Foundation (WCF) or ASP.NET instead."

Arguably, there could be a better error message, like the following (emphasis mine):

Msg 7877, Level 16, State 1
SOAP/HTTP endpoints are no longer supported in this version of SQL Server.

But your workarounds remain the same:

1. Continue using an older version of SQL Server.
2. Find another source for this information that doesn't require this type of information.
3. As the docs suggest, don't try to make SQL Server perform this work (it's not a web browser) - e.g. create an application or service that stores the data in SQL Server.