SQL Server Error 0x8004100e

You might be forgiven for thinking that SQL Server 2014 components, every single one of them, should be backwards compatible with 2012.

For example, let's say I have a test Active Directory (AD) lab made up of two servers.

The first is the domain controller and has the SQL Server 2014 Management Tools - Complete installed on it.

The second server is the SQL 2012 machine, and it has only the database engine, although I've seen the same issue with the machines where more than just the engine is installed.

The good part of all this is that, using SQL Server Management Studio (SSMS), I'm able to use my test domain credentials and connect to the SQL Server 2012 instance, so I know SQL's working, the firewall is either proper or turned off (This IS a lab setup), and run queries, which return the expected results. That's the good news - to everyone else (users, clients, etc.) this machine looks and acts online.

The downside is that I need to administer this machine remotely, using Computer Management via Server Manager's "All Servers" tab.

And I can't, because I get the following error in Computer Management when I navigate to Server Manager >> All Servers >> *ServerName* >> Computer Management >> Services And Applications >> SQL Server Configuration Manager.

error 0x8004100e

Cannot connect to WMI provider. You do not have permission or the server is unreachable. Noe that you can only manage SQL Server 2005 and later servers with SQL Server Configuration Manager. Invalid Namespace (0x8004100e)

If you right click the message, and click "Help", what you get isn't really all that helpful:

Microsoft has moved the documentation for this product online in order to provide the most current information to our customers. See the Microsoft Developer Network (MSDN) Resources page (http://go.microsoft.com/fwlink/?LinkId=299888) for more information.

Which, if you click the link, takes you to the page "Install SQL Server 2014"

Remember, now, that I'm dealing with a target server that has SQL Server 2012 on it, and I have 2014 tools on the machine I'm using to access it. Installing 2014 is a red herring - it's not the real issue!

The fix, for the test lab, was to install Client Tools Connectivity on the Domain Controller from the SQL Server 2012 media, and then, not surprisingly, to reboot.

Had this been a production domain, and not just a test lab, I think I would differently about the need to reboot, but there you have it!

Atlanta Bound!

I'm going to be presenting in Atlanta this weekend at SQL Saturday 521 on 21 May. I hope to see you there!

2016 RC3 Samples

SQL Server 2016 RC3 has it's own set of samples ! 

https://blogs.msdn.microsoft.com/sqlserverstorageengine/2015/10/29/samples-for-sql-server-2016-ctp3/

Baltimore Presentation

Thanks to everyone that came out to my Session on Auditing in SQL Server!

Credit and a "Thanks!" to Slava for the picture

Presenting in Baltimore on 30 April

So this weekend, I'm presenting in Baltiimore at SQL Saturday 506. If you're in town, swing over and join us!

SSMS 2016

In SQL Server 2016, SQL Server Management Studio (SSMS) has been de-coupled from the installer media. You can now find it here:

https://msdn.microsoft.com/en-us/library/mt238290.aspx

It'd stink to have an install with no SSMS, so there you go.

HammerDB under Windows 10 returns odd transaction count error

I'm running Windows 10, and am trying to run HammerDB using a 4K display as my primary monitor against SQL Developer 2014.

First thing I noticed is that the tree of choices is missing. A quick drag from the LEFT (!) made the tree of choices appear.

So I set up a quick test using Autopilot, 2 users, and logged the results. To which, HammerDB said it couldn't get the transaction counts, because SQL Server returned a non-numeric transaction count data.

Eh?