Missing SQL Server management Studio

I have installed SQL Server 2012 Evaluation Edition on my laptop which is Windows 7 Professional. Due to some issues, I had to uninstall the SQL Server for some time. After few days, I reinstalled the SQL Server 2012 Evaluation Edition using the same setup media which I used before to install on the same laptop. Installation completed successfully and I can see the SQL Server services from the services console, but the problem I was facing was that I could not see SQL Server Management Studio.

– I have looked at Start -> All Programs -> SQL Server 2012 -> Could not see SQL Server Management Studio


SQL Server Management Studio Missing

– Tried to install the SQL Server Management Studio again using the Setup, but the setup wizard shows that SSMS Basic and Advanced are already installed.

– Searched for SQL Server Management Studio on the file system, but could not find it.
– Verified the configuration state from the registry(Start -> run -> regedit)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\110\ConfigurationState

Updated the “SQL_SSMS_Adv” key value from 3 to 1

– Started the repair of the SQL Server instance and Shared features which finished successfully, but still could not find the SSMS
– I ran SQL Server 2012 Setup Discovery Report which shows me that the Management Tools – Basic and Management Tools – Complete are present.
– Restarted my laptop.
– Started the installation of Shared features which completed successfully.

Now I was able to see SQL Server Management Studio and I could open and use it without any issues.

Happy Reading,
SQLServerF1 Team


Could Not Open SQL Server Errorlog File Errors in Event Viewer of Passive Node

You may sometimes notice errors like below on Passive cluster node.

initerrlog: Could not open error log file 'F:\MSSQL10_50.SQLInst\MSSQL\Log\ERRORLOG'. Operating system error = 3(failed to retrieve text for this error. Reason: 15100).

All SQL Server, IP Address, Network Name, Disk resources will be owned by the Active node, so if you try to start the SQL Services on passive node, it would result in this error.

At times, although no one tries to start the SQL Services on passive cluster node, still you may see this error in the Application Eventlog. This could be result of possibly some application is attempting to start the SQL Server service on passive node.

By running a process monitor(procmon) you should be able to see which process is trying to start the SQL instance on passive node. Some application which may do this are some Virus, Monitoring or Audit software. On one of the occasion we noticed SCCM application which has a service similar to “SMS_SITE_SQL_BACKUP_SCCMXXX” was trying to start the SQL instance on passive node.

Disabling this service on the passive node stopped these errors in our case.


Starting SQL Server using -T902 Trace Flag to skip the Script Upgrade

Whenever we install a patch(Service Pack or Cumulative Update) to SQL Server or if we upgrade SQL Server from one version to another version(Ex: SQL Server 2008 to SQL Server 2012), at the end of the up-gradation process some scripts are applied to Master and MSDB databases. Sometimes, there are possibilities that the script upgrade may fail due to various reasons like below.

Script level upgrade for database ‘master’ failed after Applying SQL 2008 R2 SP2 due to Error “The database principal owns a schema in the database, and cannot be dropped”

Script Upgrade Failure to Apply msdb110_upgrade Sript

At that time we would have to start SQL Server instance using -T902 to skip SQL Server from attempting to apply the scripts, so that we can take corrective actions to fix the problem causing failure of the scripts and finally remove Trace Flag -T902 and start SQL Server normally which will then successfully apply the upgrade scripts.

Below are the steps to perform to start SQL Server to skip the script upgrade using Trace Flag -T902

1. Start -> All Programs -> Microsoft SQL Server 2008 R2 or the highest version installed -> Configuration Tools -> SQL Server Configuration Manager

2. In SQL Server Configuration Manager, click SQL Server Services.

3. In the right pane, right-click SQL Server (), and then click Properties.

4. On the Startup Parameters tab, in the Specify a startup parameter box, type the parameter (in this case the trace flag -T902), and then click Add. You will now see the parameters similar to below

SQL Server Istance Startup Parameters

SQL Server Istance Startup Parameters

5. Click OK.
6. Restart the Database Engine.
7. Connect to SQL Server instance from SQL Server Management Studio and take corrective actions to resolve the errors causing script upgrade to fail.
8. Now finally remove the -T902 trace flag from SQL Server Configuration manager
9. Restart SQL Server Instance
10. Verify Errorlog to make sure script upgrade finished successfully

1 2