im tring to insatll sql server 2014 management studio in windows 8 . but it shows error message that system does not support . How will i install it in my windows 8 or should i go for any other version of sql??
You must tell what edition of SSMS you are trying to install. As per Microsoft Hardware and Software requirement for SQL Server 2014 Enterprise and BI edition is not supported on Client OS(Windows 8) but it wont block the installation it will allow you to install. Have yu read the requiremnts ?
Can you please add error message and edition information in your question I would be able to help you better. I strongly suggest you to read How to use SQL Server on Windows 8
Edit:
Could not write value to /Softwre
Please add complete details about problem in Question. How do you suggest we can help you with little piece of information. Have a look at This Stackexchange thread and also at this support article
What you can do
1.Click Start, click Run, type control userpasswords, and then click OK.
2.Create a new computer administrator account.
3.Click Start, click Run, type regedit, and then click OK.
4.In Registry Editor, right-click HKEY_CURRENT_USER\Software, and then click Permissions.
5.Click Add, type Everyone, and then click OK.
6.Under Group or user names, click Everyone.
7.Under Permissions, click to select Full Control in the Allow column, and then click OK.
8.Locate the following subkeys:
HKEY_LOCAL_MACHINE\Software
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Current Version\Setup
9.Unregister and then reregister the Microsoft Windows Installer service. To do this, follow these steps:a.Click Start, click Run, type msiexec /unregister, and then click OK.
b.Click Start, click Run, type msiexec /regserver, and then click OK.
This can also be caused if any malware or addon is running on your system which can block access to the registry. Please clean your system and make sure any unwanted software is removed. If possible format the OS and try installing again
Related
Running SSMS 18.6 causes the program to launch, hang, and then crash. There is no error message given, the program simply terminates before any action is taken and nothing is connected.
I've uninstalled and deleted all files for SSMS, Visual Studio, and SQL Complete.
I tried the 18.6 and 18.5.1 versions of SSMS to no avail.
From https://dba.stackexchange.com/questions/237086/sql-server-management-studio-18-wont-open-only-splash-screen-pops-up/237087#237087 :
I have tried copying the Interop.8.0.dll file from privateassemblies into public. No effect. The line in the config file mentioned here is already commented out in the recent release of SSMS.
From Sql Server Management Studio closes immediately after startup :
I have tried renaming or deleting the package file listed here and removed the relevant registry key. This causes SSMS not to open at all and Windows to issue an alert sound. No other effect.
From https://social.msdn.microsoft.com/Forums/silverlight/en-US/9d0e2459-eb74-46e8-a983-05ae2ba18977/ssms-crashes-on-startup?forum=sqltools :
I tried to repair .NET framework. No effect.
I was only able to install and successfully connect on SSMS version 17.9.1
I can provide Event Viewer details if anyone is willing to help me troubleshoot. I have a .NET Runtime error and two application errors- one is event name CLR20r3 and the other is APPCRASH. Happy to provide more information if needed.
While I can't speak to the exact reason it happened, I found a solution. Whatever the issue was, I discovered it was user specific and limited to my machine. Other users were able to access SSMS as normal on my machine as was I on theirs.
I happened to remember that the AppData folder exists and is just hidden, so I used an administrator account to copy that from a working user and rewrite the files in both of mine that were not used in some background process. This allowed me to once again access SSMS both as my regular user and with my elevated administrator account.
I had this same issue (it happened all of a sudden perhaps due to a windows update). I also tried all the other solutions listed above, but the only thing that worked for me was to uninstall and then reinstall version 7.9.1 like the original poster recommended.
In my case I only have 1 user on the computer, so the other user accounts being able to access was not applicable.
I created SSIS packages and used the Integration Services Deployment Wizard to deploy it out to the server. I'm manually going to the Integration Services Catalog access through SQL Server 2012 and right-clicking and executing my package.
However, the package keeps failing and I'm getting the following errors when I check the execution report's messages.
They appear to be failing on data tasks where I have script components.
Assign :Error: CS2001 - Source file 'C:\Windows\TEMP.NETFramework,Version=v4.0.AssemblyAttributes.cs' could not be found, CSC, 0, 0
Assign :Error: Failed to compiled scripts contained in the package. Open the package in SSIS Designer and resolve the compilation errors.
This answer is a more detailed version of UberDoodles answer.
In Windows Explorer.
Navigate to C:\Windows\Temp\
Right click the folder and select properties
Go to tab Security, choose Advanced
On the default tab Permissions, choose Change Permissions
For the relevant Permission entry, choose edit.
By default, I had 'allow' checked for Traverse folder / execute file, Create files / write data and Create folders / append data.
Also check 'allow' for List folder / read data and Take ownership.
Press OK, the window closes
Press Apply and confirm anything you need.
Additionally, the logged in user had already Full control, but when I changed this for the entry 'Users', it worked for me.
(based on microsoft file/folder permissions).
I had the same problem today, just on SQL 2016.
For me it helped to change the target server version in Visual Studio project properties from SQL Server 2012 to SQL Server 2016.
I was investigating the same issue, and I came across a solution here :
https://social.msdn.microsoft.com/Forums/vstudio/en-US/73e67f3a-c575-4c73-a71d-ed7a2aeabb50/csc-error-cs2001-source-file-cwindowstempnetframeworkversionv40assemblyattributescs?forum=msbuild
Basically, the account which the package runs under needs to have full permissions to the C:\Windows\Temp\ folder, so that it can create temporary classes.
It worked for me :)
I had the same problem. I first used Eric G. response and added the List and Read permission to the c:\windows\temp. After I got everything working I went back and removed that permission. I then redeployed my solution from Visual Studio, this time designating the deployment target as SQL Server 2014 (which was the environment I was using) using Martin's solution. I then reran the process, and it worked with the List and Read removed.
I kept it using Martin's solution, as I don't like to have special permissions granted if I don't need them.
Good Luck
[Visual Studio 2017 15.9.16]
I just restarted Visual Studio as Administrator and the issue disappeared, which confirms the permissions idea of the answers above but spared me all work.
It's not a quirk though, as per this question and its answer you need that kind of permission for several tasks, like profiling and debugging under certain conditions.
For the sake of completeness, this blog says you might incur in some security contraindication if run VS as administrator when opening third-party solutions.
I have the following error when installing SQL Server 2014:
Could not write value to key \SOFTWARE. Verify that you have sufficient access to that key, or contact your support personnel.
It happens when it tries to install the SSMS and my machine has Windows 7 running. I have done the following things in order to make it work:
• Run the set up as an admin
• Reinstall the machine
I found this on a Microsoft link and doesn’t work either
• Click Start, click Run, type control userpasswords, and then click OK.
• Create a new computer administrator account.
• Click Start, click Run, type regedit, and then click OK.
• In Registry Editor, right-click HKEY_CURRENT_USER\Software, and then click Permissions.
• Click Add, type Everyone, and then click OK.
• Under Group or user names, click Everyone.
• Under Permissions, click to select Full Control in the Allow column, and then click OK.
• Locate the following subkeys:
HKEY_LOCAL_MACHINE\Software
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Current Version\Setup
• For each subkey, follow these steps:
Click the subkey.
Delete the InstanceComponentSet.# string value in the right panel. Notice that # is a number, and the value of this key is {66563AD8-637B-407F-BCA7-0233A16891AB}.
• Unregister and then reregister the Microsoft Windows Installer service. To do this, follow these steps:
Click Start, click Run, type msiexec /unregister, and then click OK.
Click Start, click Run, type msiexec /regserver, and then click OK.
Thanks
Allan
I have installed an addware program "adwcleaner" and run it. It has cleaned and remove the malware viruses from my system and then i try to reinstall SQL Server Management tool and it's installed without any error. Thank God.
Here is the website for the "adwcleaner" software.
http://www.bleepingcomputer.com/download/adwcleaner/
I know this is old thread but I guess I know the answer so posting if this can be helpful to someone.
Yes this is not related to account issue but this issue is not related to SQL Server as well believe me. What is happening is some registry scanner software, some addware, some Malware is stopping SQL Server installation from writing information to Reg Key /Software that is why this message is coming.
You need to uninstall any such third party software you have installed on your system. Go to add remove program in windows machine and uninstall all such dubious softwares.
I have seen lots of such issue on MSDN forum and an OP finally told the solution and that solution has been helping lot of people so I though of posting here. See answer provided by Michpol In this thread
As per him
The solution is as simple as possible.
Win32/Toolbar.SearchSuite.C marked as " potentially undesirable adware" was the reason.
Simple online scanner and no problem.
There is some kind of virus/adware/addone that blocked access to the registry.
The solution was simple: remove that virus from your system with the scanner on line.
Hope this helps
Try running the installation from an administrator command prompt (and not from Explorer):
* Right-click `Command Prompt` and select `Run as administrator`
* cd %HOMEPATH%\Downloads
* INSTALLER.exe (or .msi or whatever)
This may not work for all installations, but worked for me with Meld v3.20.3 (Meld-3.20.3-mingw.msi) on Windows 10, where running the .msi as "Administrator" did not allow the registry key to be created.
Just provisioned a new server running IIS and Server 2012 and SQL Server 2012. I also installed SQL Server Management Studio tool so I can quickly inspect databases without the need to open a remote connection.
When I browse an ASP.NET sites remotely, I get a Just-in-time debgugger exception dialog when an error is encountered in addition to the yellow screen. The dialog stays up on the server and piles up unless I RDP and manually close all the dialog boxes.
The only way to disable this is by removing Visual Studio Shell 2010 (integrated) using the control panel. The side effect is that I can no longer use SSMS.
Most of the available solutions are outdated or don't work. The registry settings are no longer applicable and most articles concerning this issue are old. Microsoft's official documentation is a rat's nest of broken links. Moreover, many users are confusing IE's script debugging dialog with this issue. Although they are related and similar, this specific issue is tied to Visual Studio's runtime environment.
Any ideas?
ASIDE: I can't believe Microsoft has this "feature" on a product that is installed on a production server. I am just floored by the incompetence of a multi-billion dollar corporation. I've seen my question asked since at least since 2005 with no official solution that works. I just have to ask one last time for sanity checking. I want to make sure I'm not the one who is "thick" in the head here.
To disable Just-In-Time debugging by editing the registry
In the Start menu, click Run.
In the Run dialog box, type regedit, then click OK.
In the Registry Editor window, locate and delete the follow registry keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger
If your computer is running a 64-bit operating system, delete the following registry keys also:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\WindowsNT\CurrentVersion\AeDebug\Debugger
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\DbgManagedDebugger
Take care not to accidentally delete or change any other registry keys.
Instead of deleting it, you can also just (temporarily) rename the AeDebug key for the bitness of your choice to something else, e.g. AeDebug-disable!
For server 2012, IIS, and SSMS 2014 we tried all three registry three deletions and those did not work.
What did work was old school renaming the JIT Debug executable.
Renamed these files.
C:\WINDOWS\system32\vsjitdebugger.exe
C:\Windows\SysWOW64\vsjitdebugger.exe
Renamed this folder
C:\Program Files\Common Files\Microsoft Shared\VS7Debug
As a follow-up to nfox's answer, I've created a registry file that you can simple use instead of searching manually through regedit.exe.
1.) Copy this script to your clipboard:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug]
"Debugger"=-
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework]
"DbgManagedDebugger"=-
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug]
"Debugger"=-
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework]
"DbgManagedDebugger"=-
2.) Save it to a file with the .reg extension:
E.g. to a file named
C:\Users\<user name>\Desktop\DisableJit.reg
3.) Double click the file
After confirming the appearing message box, the keys are getting deleted.
5.) Alternatively: Download file
If this is too much effort, you can download the registry file from here:
disable-the-just-in-time-debugger-windows-64-bit.reg
disable-the-just-in-time-debugger-windows-64-bit.zip (As a ZIP)
Download and then double-click it.
This tip was simply taken from the MSDN article "Just-In-Time Debugging in Visual Studio".
The syntax on how to delete registry keys via a .reg file was taken from the MSDN KB article "How to add, modify, or delete registry subkeys and values by using a .reg file".
You should be able to disable Jist-In-Time debugging using the Debug options dialog inside Visual Studio. The registry keys are also well documented here.
See:
http://msdn.microsoft.com/en-us/library/5hs4b7a6.aspx
Aside: I think it's not a wise thing to install a management studio on a production server. This is what management workstations are for. Remote connections from a management station can be pre-configured and stored so that it doesn't take much effort. That way you can keep your production environment clean.
Sometimes I miss the 1 or the F2 in my computer keyboard when using SQL Server Maganement Studio, that causes my SQL MS to hang and the I have to close it with the Task Manager, but many time I loss a lot from the queries I was working on, so I would like to fix this problem,
Maybe someone here has the same problem.
Microsoft Document Explorer
The Application Data folder for Microsoft Document Explorer could not be created
Right click on the SSMS program (in the start menu / desktop) and select "run as administrator". Do whatever you do to cause SSMS to hang, quit and re-run as normal user. This should remove that warning.
After many intents to solve this problem, I received this message:
External help is not available because Microsoft Document Explorer is
not installed. To view help, change your Help preferences to use the
Integrated Help Viewer or Install Microsoft Document Explorer
I tried to do it at Tools->Options->Help->General->
Show Help usaing: Integrated Help Viewer
Search Result per page: 20
Show Topic abstracts: checked
Reuse Topic window: checked
Highlight search termn: checked
I had to tried many times until SSMS wanted let me to do it.
Now the problem has been partially solved, when I press F1 the SSMS does not hang, but when I still try to change something in the help options, then chunks..