When you open SQL Server 2008 configuration manager you do not see the following options :
Scenario 1 (64 bit options):
1) SQL Native Client 10.0 configuration
2) SQL Server Network configuration
Scenario 2 (32 bit options):
1) SQL Native Client 10.0 configuration(32 bit)
2) SQL Server Network configuration (32 bit)
SQL Server configuration manager pulls the details with the help of SQLMGMPROVIDER.DLL.
This DLL has got two versions - one is 64 bit and the other is 32 bit :
The location 64 bit DLL is: C:\Program Files\Microsoft SQL Server\100\Shared\sqlmgmprovider.dll and the location 32 bit DLL is: C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmprovider.dll
If this DLL is corrupted then you will see this issue. In this case when I checked the property of the 64 bit DLL it was blank.
If you are not able to see the 64 bit options, replace “C:\Program Files\Microsoft SQL Server\100\Shared\sqlmgmprovider.dll” with SQLMGMPROVIDER.dll copied from another working machine.
For the 32 bit options, replace “C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmprovider.dll” with the 32 bit SQL SQLMGMPROVIDER.dll” copied from another working machine.
Amit Khandelwal SE, Microsoft SQL Server
Amit Banerjee TL, Microsoft SQL Server
Did not work for me, but I can see both (1) and (2) I just can't see the SQL services other than Integration Services under SQL Services. (32 bit version)
This not work for me
does not work for me as well.
Me neither. I think this solution is for a specific issue (i.e. corrupted dll). I have a 2-node SQL Cluster and the 64-bit options are missing on one of the servers, but there on the 2nd.
Just had this problem with SQL Server 2012 and the above steps were the solution but that was not all that was needed. Basically the c:\program files\microsoft sql server\110\shared folder was locked down because of DISA STIGs and it was preventing the mofcomp from accessing the files appropriately. In order to fix I had to revert permissions from the parent temporarily, run the mofcomp command and then lock down the directory again.
Didn't work in my case too.
Because the sqlmgmprovider.dll wasn't the only file needed. I copied from another SQL-Server the hole shared folder and it worked. I didn't examine which files are needed, just happy it works that way.
In my case Server 2008R2 SP1 with SQL 2008
We encountered an alike issue where ntfs privileges were modified (for security hardiening)on the folder containing these dll's.