Setup of SQL 2008 Management Tools

We are getting the following error when trying to setup SQL 2008 Management tools on an Windows 2008 server.
CASPOL.exe - .NET Framework Initialization error
Set registry key: HKLM\software\microsoft\.NET Framework\InstallRoot
the installer won't does not go any further.
Thanks in advance

This has been very frustrating so far without success yet.
Then execute the following command line: Drive:\WINDOWS\Microsoft.NET\Framework\%version%\caspol.exe -m -ag 1 -url "file:////\computername\sharename*"
FullTrust -exclusive on --> what does this mean?
We copied the SQL 2008 dvd to the local machine. right now we are still getting the caspol.exe error.

Similar Messages

Silent Install for SQL 2008 admin tools, to be pushed out via SCCM 2012

Hi I would like to know if you have any information on Silent App installs for MS SOL fetchers only? I really need to know what MSI to use in my Application and any switched i can incorporate for deployment though SCCM 2012.
Thanks,
Manny

Hi,
do you want to install SQL 2008 admin tools? and what tools do you want to install? and what is your application? And do you want to deploy the installation script via SSCM? Please be more clear.

SQL Server Management Tools - Could not write value to key \SOFTWARE. Error code: 1406

Detailed Results:
Feature: Management Tools-Basic
Status: Failed
Component Name: Sql Server Management Studio
Component Error code: 1406
Error Description: Could not write value to key \SOFTWARE. Verify that you have sufficient access to that key, or contact your support personnel.
The first time the installer worked installing perfectly, but I needed an named instance of "SQL2008", so I removed the instances. After this re-installing is not working.
From past 3-4 days I went through most of the links which has provided solutions for error code 1406, and not having success for installing.
I have tried these options,
1) Ran the installer using "Run as Administrator"option. I am an Administrator user for the machine.
2) 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.
3) Uninstalled the Sql server product, and used Revo Uninstaller / CCleaner to clean the registry and the remaining files and folders.
4) Multiple versions of SQL installers have been tried (SQL 2008/2012/2014)
5) Logged in as local/Administrator for the machine, tried the similar steps.
6) The same installers are still working in one of the virtual machines for multiple times of installation and uninstallation without having any problems.
Please let me know, if needed further information. Please provide help for installing SQL server management studio.
Regards,
Ananth.

I have the same problem.
I can not install MSSQLManagementStudio. I suppose
that is not the fault of permissions
. I have tried to
install as an administrator
on the computer in the domain where the account has domain administrator permissions.The account is added to the local administrators.
I also have tried to install as local administrator
account after the removal of the domain.
With the same result.
Operating System Windows 8.1 Prof.
I have tried 2012, 2012with SP1 , 2012x86 , 2014. All with same result:
Product: SQL Server 2012 Management Studio -- Error 1406. Could not write value to key \SOFTWARE. System error . Verify that you have sufficient access to that key, or contact your support personnel.
Other elements installs without any problem.
sql_ssms_Cpu64_1.log show that the problem is in that point:
MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL Server\110\Tools\ClientSetup,,BinaryType=0,,)
MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegAddValue(Name=SqlToolsPath,Value=C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\,)
MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegAddValue(Name=Path,Value=C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\,)
MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegAddValue(Name=SQLPath,Value=C:\Program Files (x86)\Microsoft SQL Server\110\Tools,)
MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE,,BinaryType=0,,)
MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegAddValue(,,)
MSI (s) (1C:C0) [10:32:51:834]: Note: 1: 1406 2: 3: SOFTWARE 4: 5
MSI (s) (1C:C0) [10:33:19:949]: Product: SQL Server 2012 Management Studio -- Error 1406. Could not write value to key \SOFTWARE. System error . Verify that you have sufficient access to that key, or contact your support personnel.
Error 1406. Could not write value to key \SOFTWARE. System error . Verify that you have sufficient access to that key, or contact your support personnel.
07/30/2014 10:33:19.949 [540]: Assembly Install: Failing with hr=80070005 at RemoveDirectoryAndChildren, line 396
...... rest of the roolbaack next
As i the lines:
MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE,,BinaryType=0,,)
MSI i opening the root hive of HKLM/Softftware
and MSI (s) (1C:C0) [10:32:51:834]: Executing op: RegAddValue(,,)
and trying to Add Default Value.
What is impossible regardless of the
level of permissions.
Please provide help for installing SQL server management studin in any version
Regards,
Michael

Sql server 2008 management studio

hi sir
we want to install following version of sql 2008 management studio for our access control.
it is free version or we need to purchase license for this please tell us because access control support team said this is free version. and when we check in Microsoft site also showing free version.need just confirm it is free or paid.
Microsoft SQL Server Management Studio 10.0.1600.22
Microsoft Data Access Components (MDAC) 2000.086.3959.00

please confirm this is free version or paid
Microsoft SQL Server Management Studio 10.0.1600.22
Microsoft Data Access Components (MDAC) 2000.086.3959.00
Regarding MDAC: It' a System component and already integrated in all current Windows OS Version, no Need to install it; see
Microsoft Data Access Components (MDAC) 2.8 SP1 => System Requirements =>
Supported Operating System
Regarding SSMS: If you have a SQL Server licenses then you can install SSMS on the client machine, it's part of the license; see
http://download.microsoft.com/download/6/F/8/6F84A9FE-1E5C-44CC-87BB-C236BFCBA4DF/SQLServer2008_LicensingGuide.pdf page 47
"Additional Software That May Be Run"=> "... without the need for additional licenses
Olaf Helper
[ Blog] [ Xing] [ MVP]

Sql 2008 peer-to-peer replication and jdbc driver

Hi, sorry but i'm a sql dummy...:-)
I setup a sql 2008 p2p replication for a database.
Can i specify, on a jbdc connection string, the path of the 2nd sql server for automatic failover?
I try failoverPartner variable, but this is only for database mirroring.....
Can u help me?
Thanks in advance

Hi, sorry but i'm a sql dummy...:-)
I setup a sql 2008 p2p replication for a database.
Can i specify, on a jbdc connection string, the path of the 2nd sql server for automatic failover?
I try failoverPartner variable, but this is only for database mirroring.....
Can u help me?
Thanks in advance

SQL Azure Administration Tool

Are there any web-based admin tools to develop my Azure SQL database with? I have downloaded the SQL 2012 Express Management Tools, but cannot connect to my Azure SQL Database server with them because port 1433 is blocked.
This seems to be a common problem, but so far I have found no way to connect to my database. My 30 day trial ends in 29 days and I'm hoping to get this resolved before day #30. :-)
The SQL Azure Labs I downloaded from the Azure website talk about a tool in the Azure Portal, but I cannot find anything there. Everything just points to downloading the SQL 2012 Management Tools.
Thanks,
Brian

You can use the database management tools in the Portal to create tables and run T-SQL. Granted, it is not as convenient as SSMS but it will do the job very nicely.
Patrick Wood,
Founder, Gaining Access Technologies http://gainingaccess.net/

SQL 2008 R2 Management Tools Install Fails - The specified account already exists

Hello,
The installation SQL 2008 R2 Management Tools on a Windows 7 workstation fails with the error, The specified account already exists.
Below is the Summary Log.
Thanks.
Paul
Overall summary:
Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Exit code (Decimal):           -2068052700
Exit facility code:            1212
Exit error code:               1316
Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Start time:                    2014-10-20 09:02:16
End time:                      2014-10-20 09:05:57
Requested action:              Install
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141020_085102\sqlncli_Cpu64_1.log
Exception help link:
http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1
Machine Properties:
Machine name:                  WS287
Machine processor count:       4
OS version:                    Windows 7
OS service pack:               Service Pack 1
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  No
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Package properties:
Description:                   SQL Server Database Services 2008 R2
ProductName:                   SQL Server 2008 R2
Type:                          RTM
Version:                       10
SPLevel:                       0
Installation location:
\\SRVDIA18\MSSQL2008R2Install\x64\setup\
Installation edition:          STANDARD
User Input Settings:
ACTION:                        Install
ADDCURRENTUSERASSQLADMIN:      False
AGTSVCACCOUNT:                 <empty>
AGTSVCPASSWORD:                *****
AGTSVCSTARTUPTYPE:             Manual
ASBACKUPDIR:                   Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   Config
ASDATADIR:                     Data
ASDOMAINGROUP:                 <empty>
ASLOGDIR:                      Log
ASPROVIDERMSOLAP:              1
ASSVCACCOUNT:                  <empty>
ASSVCPASSWORD:                 *****
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            <empty>
ASTEMPDIR:                     Temp
BROWSERSVCSTARTUPTYPE:         Disabled
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141020_085102\ConfigurationFile.ini
CUSOURCE:
ENABLERANU:                    False
ENU:                           True
ERRORREPORTING:                False
FARMACCOUNT:                   <empty>
FARMADMINPORT:                 0
FARMPASSWORD:                  *****
FEATURES:                      SSMS,ADV_SSMS
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  <empty>
FTSVCPASSWORD:                 *****
HELP:                          False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS:              False
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR:             <empty>
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    <empty>
INSTANCENAME:                  <empty>
ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
NPENABLED:                     0
PASSPHRASE:                    *****
PCUSOURCE:
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
ROLE:                          <empty>
RSINSTALLMODE:                 FilesOnlyMode
RSSVCACCOUNT:                  <empty>
RSSVCPASSWORD:                 *****
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  <empty>
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT:                 <empty>
SQLSVCPASSWORD:                *****
SQLSVCSTARTUPTYPE:             Automatic
SQLSYSADMINACCOUNTS:           <empty>
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  False
TCPENABLED:                    0
UIMODE:                        Normal
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141020_085102\ConfigurationFile.ini
Detailed results:
Feature:                       Management Tools - Complete
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141020_085102\SystemConfigurationCheck_Report.htm
The specified account already exists

There is definitely more amusing endeavours in this world, than trying to understand why an SQL Server install failed. The log files are verbose - but somehow the real information about what went wrong seems to be hiding. Never have proverb about not being
able to see the forest for all the trees felt more appropriate.
Nevertheless, this is where things go sour:
MSI (s) (F4:EC) [09:04:15:744]: Resolving source.
MSI (s) (F4:EC) [09:04:15:744]: Resolving source to launched-from source.
MSI (s) (F4:EC) [09:04:15:744]: Setting launched-from source as last-used.
MSI (s) (F4:EC) [09:04:15:744]: PROPERTY CHANGE: Adding SourceDir property. Its value is '\\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\'.
MSI (s) (F4:EC) [09:04:15:744]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is '\\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\'.
MSI (s) (F4:EC) [09:04:15:744]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{2180B33F-3225-423E-BBC1-7798CFD3CD1F}'.
MSI (s) (F4:EC) [09:04:15:744]: SOURCEDIR ==> \\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\
MSI (s) (F4:EC) [09:04:15:744]: SOURCEDIR product ==> {2180B33F-3225-423E-BBC1-7798CFD3CD1F}
MSI (s) (F4:EC) [09:04:15:744]: SECREPAIR: CryptAcquireContext succeeded
MSI (s) (F4:EC) [09:04:15:744]: Determining source type
MSI (s) (F4:EC) [09:04:15:744]: Note: 1: 2203 2: \\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\SQL ODBC Native Client 10 - 64bit.msi 3: -2147287038
MSI (s) (F4:EC) [09:04:15:744]: Note: 1: 1316 2: \\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\SQL ODBC Native Client 10 - 64bit.msi
MSI (s) (F4:EC) [09:04:15:744]: SECREPAIR: Error determining package source type
MSI (s) (F4:EC) [09:04:15:744]: SECUREREPAIR: SecureRepair Failed. Error code: 524F91D34B8
MSI (s) (F4:EC) [09:04:40:775]: Product: Microsoft SQL Server 2008 R2 Native Client -- Error 1316. The specified account already exists.
What account? I supposed you have already asked yourself that and just shaken your head.
But there is another error code 2203, NET HELPMSG 2203 says "The password parameter is invalid." And I note that the source is apparently on a share.
So where is my guess: the MSI installer - which runs as a service, somehow does not have permissions to read the installation from the share. Or is trying to log on to the share with your username/password? No, I don't know, I am just speculating widely.
But my advice would be to copy the installation directory from the share to a local disk.
Maybe that CryptAcquireContext is significant as well - I don't know.
Oh, wait, here is something just before the section above in the log:
MSI (s) (F4:EC) [09:04:15:729]: Note: 1: 2205 2: 3: Environment
MSI (s) (F4:EC) [09:04:15:729]: Note: 1: 2228 2: 3: Environment 4: SELECT `Name`,`Value` FROM `Environment`,`Component` WHERE `Component_`=`Component` AND (`Component`.`Action` = 1 OR `Component`.`Action` = 2)
Action start 9:04:15: WriteEnvironmentStrings.
2205 is "The logon processor did not add the message alias." I see that in a successful log that I have, so that is probably benign. But 2228 seems to be
"There are too many names in the user accounts database."
Exactly what that means, I have no clue, but it could be a Windows problem.
Erland Sommarskog, SQL Server MVP, [email protected]

SQL Server 2008 R2 Management Studio (express) install fails (Management Tools Basic Failed) - Error 1316. The Specific account already exists.

Hi,
I try to install, the SQL Express 2008 R2 with Advanced
The installation has only one error (Error 1316. The Specific account already exists.) and the Management Tools Basic setup is failed.
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the
reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server
Setup.
Exit code (Decimal): -2068052700
Exit facility code: 1212
Exit error code: 1316
Exit message: SQL Server installation failed. To continue, investigate the
reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server
Setup.
Start time: 2015-01-02 16:17:17
End time: 2015-01-02 16:24:01
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap
\Log\20150102_161500\SSCRuntime_Cpu32_1.log
Exception help link: http://go.microsoft.com/fwlink?
LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.4000.0
Machine Properties:
Machine name: KHPNHSI_BNANG
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
Installation location: g:\41bee43707e62fab54ec\x64\setup\
Installation edition: EXPRESS_ADVANCED
Slipstream: True
SP Level 2
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: True
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE:
CUSOURCE:
ENABLERANU: True
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,REPLICATION,SSMS,SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SQLExpress
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE: g:\41bee43707e62fab54ec\PCUSOURCE
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: PSI\ssamnang
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
UIMODE: AutoAdvance
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap
\Log\20150102_161500\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap
\Log\20150102_161500\SystemConfigurationCheck_Report.htm
Please help!
Samnang.

Hi SSamnang,
According to your description, you come across the error that the specific account already exists. Please help to share the complete error log in C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150102_161500\SSCRuntime_Cpu32_1.log. You could
use google drive to upload the error log following the steps in the article:
https://support.google.com/drive/answer/2424368?hl=en
From the exception help link, we notice that, the issue could be due to that an attempt fails to install SQL Server Native Client on a computer where SQL Server Native Client is already installed.
I recommend you to check if there is already an existing SQL Server Native Client on your computer. If there is an existing one, you could uninstall it and install SQL Server again.
In addition, there is a similar thread for reference:
https://social.technet.microsoft.com/Forums/en-US/dc31bffd-c9e2-4630-b5d7-9252b03c24fe/sql-2008-r2-management-tools-install-fails-the-specified-account-already-exists?forum=sqltools.
Regards,
Michelle Li

Managed sql server installer has stopped working sql 2008 r2

I tried to installed sql 2008 r2 on my windows 7 but unfortunately I got message "managed sql server installer has stopped working"
1. I tried to program feature on and off feature
2. I checked setup file is corrupted or not setup file is well in condition
3. I turn on firewall too.
then again I tried to installed again same problem I faced.
please any different way to overcome from this problem!
regard Bishnu Khaling!

Hi Bishnu,
As Shanky’s post, you can post the SQL Server setup log files for analysis.
According to the error message, it is usually a problem with the installation of .NET Framework on the machine. However, from your description, you try to turn on the Microsoft .NET Framework 3.5 feature and still fail to install SQL Server 2008 R2.
Do you reboot your computer after enabling .NET Framework 3.5?
To further troubleshoot this issue, I recommend you perform the following steps.
1. Run the below tool to verify the state of one or more versions of the .NET Framework on the computer .
http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx
2. If .Net Frameworks 3.5 cannot be verified in step1, please use the
.NET Framework Repair Tool to repair it.
3. If there’s no problem with .Net Frameworks 3.5, and you also have .NET Framework 4.0 or 4.5 installed on the computer, please uninstall .NET Framework 4.0 or 4.5 completely. Then reinstall SQL Server and check if it is successful.
4. In addition, please make sure that the Windows 7 system is not damaged.
For more details about the error, you can also review the following blog.
Fix: Managed SQL Server installer has stopped working on Windows 7 | 8:
http://www.thewindowsclub.com/managed-sql-server-installer-has-stopped-working
Thanks,
Lydia Zhang

SQL Server Management Studio 2008 R2 not showing Maintenance Plan

I do not have the Maintenance Plan listed under the Object Explorer. I am running SQL Server 2008 R2 (that is listed in Control Panel/Programs). When I tried to run the install to check that the management tool is configured I received the
"instance id" error (SQLManagementStudio_X64_ENU.EXE). After doing some reading online I found where some people used the SQLEXPADV_X64_ENU.exe install. This allowed me to see that the Management Tools were installed. I am not an
SQL expert and need to schedule a nightly backup of the database.

You need to have your permissions checked to ensure that you have appropriate permissions to see these. This link gives you the permissions required to see these and maintain them
http://msdn.microsoft.com/en-us/library/ms187658(v=SQL.105).aspx
Warwick Rudd MCT MCITP SQL Server 2008 Admin

How to clear the existing names in USER NAME drop down list in Sql Server Management Studion in Sql Server 2008 R2`.

Hi,
We have Sql Server 2008R2 clustered instance running in 2 nodes with Windows 2008R2 SP1 operating system. I would like to know how I could clear the existing names in the USER NAME drop down list in the Sql Server Management studio.
Thanking in you advance,
Binny Mathew,

SQL Server Management Studio 2008 delete the file:
C:\Users\%username%\AppData\Roaming\Microsoft\Microsoft SQL Server\100\Tools\Shell\SqlStudio.bin
http://dynamicsgpland.blogspot.in/2012/04/clearing-remembered-default-login-for.html

Moving Service Manager Database From SQL 2008 R2 SP2 to SQL 2012 SP1

Hi Guys,
Just looking for some clarification about moving our Service Manager 2012 R2 database to a new SQL Server.
Our Service Manager database is currently on a remote SQL server, shared with other databases, running SQL 2008 R2 SP2. It was originally setup this way as we only deployed Change Management but we are now wanting to deploy everything, fully
utilising SCSM/Orchestrator and Cireson's suite. Due to the limited resources available on that SQL server we are seeing performance issues before even getting it all up and running.
I want to move the Service Manager database to a new dedicated SQL server running SQL 2012 SP1. I am aware of the official DB move procedure but it does not specifically mention moving up SQL versions. I have seen some comments around here that
it is fine to do but some feedback would be good, it is not something I have done before.
All servers in this are fully patched Windows 2008 R2. Also, we do not currently have a Data Warehouse so do not need to worry about that. It was dropped and uninstalled before upgrading to Service Manager 2012 R2 and will be reinstalled after this DB move
using a separate dedicated SQL server.
Thanks, Chris.

As long as your collations and permissions are the same as before it
should not be a problem. That sad i could not find any other documentation saying it's not supported.
I have moved SCSM databases between different SQL-versions before and it has worked fine if the collations etc are correct.
Cheers,
Thomas Strömberg
System Center Specialist
Blog:
Twitter: LinkedIn:
Please remember to 'Propose as answer' if you find a reply helpful

While installing the sql server 2008 management studio I am getting the below error.So what do I do?

Hi,
While installing the sql server 2008 management studio I am getting the below error.
unhandled exception has occured in your application.if you click continue,the application will ignore this error and attempt to continue.if you click quit,the aplication will close immediatly.
An error occured creating the configuration section handler for userSettings/Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings:Could not load file or
assembly 'system.version=4.0.0.0. culture=neutral, publickey token=b77a5c561934e089' or one of its dependencies.the system cannot find the file supplied.
(C:\users\harsha\appdata\local\microsoft_corporation\landingpage.exe_strongname_ryspccglaxmt4nhllj5z3thycltsvyyx\10.0.0.0\user.config
and finally it is giving the options like continue and quit the installation.
So what do I do?
regards,
harsha.

Hello,
Please try deleting the following sub folder to see if this will work:
C:\users\(my profile)\AppData\Local\Microsoft_Corporation
If you can't see AppData folder, you could use following steps to show hidden files:
1. Open an explorer window, hit "ALT-T" choose Folder Options then go to the view tab.
2. Turn on Show hidden files, folders or drives and
disable Hide protected Operating System files (recommended).
SQL Server 2008 setup fails with a Microsoft .NET Framework exception:
http://blogs.msdn.com/b/vsnetsetup/archive/2009/10/29/sql-server-2008-setup-fails-with-a-microsoft-net-framework-exception.aspx.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Error installing sql server 2008 management studio express

Hello,
I need to install sql server 2008 management studio express on a sql server 2k8 R2 instance.
First of all, I've downloaded this one from this link: http://www.microsoft.com/en-us/download/details.aspx?id=7593 (for 32 bits).
Once I've the downloaded file I run this file and choose the first option (New sql server stand-alone...) in the installation part. Finally, in the installation type I choose the option 'Add features to an existing instance of SQL Server 2008' with the instance
selected. I push Next and then I get the following error: 'The instance ID is required but it is missing'.
Can anybody help me?
Thanks a lot.
Regards.

Hello,
What’s the edition of the SQL Server 2008 R2? If you had installed SQL Server 2008 R2 Developer edition, you should install “SQL Server 2008 Express with Tools” edition or “SQL Server 2008 Express with Advanced Services” edition.
Please refer to the following article for more information:
http://www.benlittler.com/2009/06/how-to-install-sql-management-studio-express-2008/
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

SQL Server Data Tools for SQL 2014 setup

Hello,
I have been using SQL server 2008 with Visual Studio 2008 to perform the ETL processes.
I have recently got SQL 2014 and realized that Business Intelligence Development Studio does not come with it so I have to download SQL Server Data Tools for Visual Basics 2012 or 2013 from:
https://msdn.microsoft.com/en-us/data/hh297027
Can someone advise what exactly I have to do if I want to start using SQL 2014 with SSDT? I still have VB 2008 installed and all my packages were created with that version.
Do I need to download VB 2012 or 2013 plus SSDT and then SSDT? Do I also uninstall VB2008?
Thanks in advnce

Hello,
If you want to keep developing packages for SQL Server 2008 then you need to use BIDS 2008, you cannot use SSDT.
If you want to upgrade BIDS projects to SSDT, then you can use Integration Services Project Conversion Wizard from Visual
Studio or SSIS Package Upgrade Wizard from SQL Server Management Studio (SSMS).
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Setup of SQL 2008 Management Tools

Similar Messages

Maybe you are looking for