Registry Key Question
-
What registry key is hiding the "Shared Feature Directory" for SQL Server?
I need to change this from the C: drive to the D: drive, but it's grayed out and has been since the first time I tried installing SQL 2012.
The annoying thing is, we haven't had this issue on any of our other servers. Just one.
-
Brandie Tarvin (6/22/2015)
What registry key is hiding the "Shared Feature Directory" for SQL Server?I need to change this from the C: drive to the D: drive, but it's grayed out and has been since the first time I tried installing SQL 2012.
The annoying thing is, we haven't had this issue on any of our other servers. Just one.
First guess would be under "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\110"
😎
-
Not sure what you mean, but
It could be at either
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\110\SharedCode
or
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\110\Tools\ClientSetup\SQLBinRoot
or
both
or
maybe somewhere else altogether.
(Both those values are set to c:\Program Files\Microsoft SQL Server\100\Shared\ on my system).
Tom
-
TomThomson (6/23/2015)
Not sure what you mean...When installing SQL Server, the Feature Selection page, near the bottom.
EDIT: I'm doing a registry search right now for the C:\Program Files\Microsoft SQL Server\. There's a lot of entries, most of which aren't even named with a user friendly name.
-
My brain just caught up with the suggestions. Per advice from this thread here, I have deleted "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server" which means, the shared directory information is not kept here.
Thoughts on where else it might be hiding?
-
Brandie Tarvin (6/24/2015)
My brain just caught up with the suggestions. Per advice from this thread here, I have deleted "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server" which means, the shared directory information is not kept here.Thoughts on where else it might be hiding?
A wild guess: somewhere under "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\software\" ?
Tom
-
This is from a "clean" installation of SQL 2012
😎
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\110\[b]SharedCode[/b] has the value of the Shared Code installation directory
[b]ErrorReportingDir[/b] the error dump folder
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\110\Tools\ClientSetup
[b]SQLBinRoot[/b] The SQL Server's binn directory
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Folders
List of installation folders
HKEY_CLASSES_ROOT\CLSID\{GUID-OF-DLL}\InprocServer32
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{GUID-OF-DLL}\InprocServer32
All registered DLLs which are part of the "Shared"
-
Eirikur Eiriksson (6/25/2015)
This is from a "clean" installation of SQL 2012😎
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\110\[b]SharedCode[/b] has the value of the Shared Code installation directory
.... ....
That's where my system has it, as I said in my first response to Brandie's question; but Brandy pointed out that having deleted HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
in her system's directory (presumably leaving a working system) meant that the system must be getting it from somewhere else; I'm inclined to say that it's a ltttle surprising if that's not a valid deduction.
Tom
-
Isn't that usually disabled when there is already some component installed in the shared directory?
Have you checked whether the specified folder already exists and has something in it? If it does, you will struggle to move it.
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);- Forum Etiquette: How to post Reporting Services problems
[/url]- Forum Etiquette: How to post data/code on a forum to get the best help - by Jeff Moden
[/url]- How to Post Performance Problems - by Gail Shaw
[/url] -
mister.magoo (6/25/2015)
Isn't that usually disabled when there is already some component installed in the shared directory?Yes, that's my problem. Someone installed client tools on the server in question. I uninstalled them. Unfortunately, the installer still wants to use that folder.
Have you checked whether the specified folder already exists and has something in it? If it does, you will struggle to move it.
I deleted the specified folder before trying the re-install. The installer still has it listed as the target for the shared directory and because it's grayed out, I cannot change it. Hence the reason I'm looking for the registry key.
-
TomThomson (6/25/2015)
Eirikur Eiriksson (6/25/2015)
This is from a "clean" installation of SQL 2012😎
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\110\[b]SharedCode[/b] has the value of the Shared Code installation directory
.... ....
That's where my system has it, as I said in my first response to Brandie's question; but Brandy pointed out that having deleted HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
in her system's directory (presumably leaving a working system) meant that the system must be getting it from somewhere else; I'm inclined to say that it's a ltttle surprising if that's not a valid deduction.
I've restored the registry backup and am going to start from scratch, deleting the services registry entries. This time instead of deleting the entire Microsoft SQL Server hive, I'll try altering it to see if that helps. But give that it still asked for that folder every single time I've tried the restore after deleting that section of the hive, I doubt that the base entry is hiding in that subsection.
I've tried changing / deleting all mentions of the C: folder, but then the installer craps out on me after getting the registration key and running the setup files. It just ... vanishes and does nothing. Doesn't even touch the bootstrap log to tell me what the problem is.
This project is an exercise in frustration, but I'm hoping I learn something from it that no one has found before.
-
Okay. So I did just learn something. Looking at another server, where I was able to change the directory to the D: drive, the folders listed under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\110 do NOT refer to the installer's "shared directory".
On the machine that properly got installed, it also has C:\Program Files\Microsoft SQL Server listed in those registry keys, and yet it properly installed shared features under the D:\Program Files\Microsoft SQL Server.
So the value that affects the installer is coming from another key somewhere else. I'm going to search the good install for the D: drive path and see if I can't locate the key that way.
-
Hi Brandie,
Have you tried using Process Monitor to log all the reg key accesses? I've found it's a real useful tool when trying to determine exactly what an application or process is doing with the registry.
Jim
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply