SQL 2012 HADR failover instance
Greetings all.
Currently here is the setup we have built out. All are Server 2012 R2 OS
2 node FCI shared storage SQL 2012 servers in production site. Failover works flawlessly between them. WSFC setup between them
1 node in DR, member of the WSFC with the 2 servers above but not FCI, seperate storage infrastructure but same disk drive letter setups
Availability Groups setup between the 2 that are fully synchronized
We are going to have a planned primary outage in the primary DC. Nerves are getting the better of me in regard to the setup. I know the data is there and it can be accessed. My question is that once i perform the failure of the two nodes
in the FCI how are my applications going to know how to reach the HADR server as it is on a seperate instance? Does SQL aliasing need to be setup in the configuration to make it work properly or am i being overly paranoid at this point?
The listener name is similar to a cluster client access point. When you create a listener name, it will create a virtual computer object in Active Directory and, with AD-integrated DNS, will create the corresponding DNS entries. Depending on how you configure
your cluster, the listener name should have 2 virtual IP addresses - one for the production network and another for the DR network - and will be written to the DNS. That being said, your listener name has to be unique so that the network traffic can be properly
routed to the instance running the Availability Group. You also need to configure the appropriate TTL value for the listener name or use the latest SQL Server client APIs to take advantage of the MultiSubnetFailover parameter in the application connection
string
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course
Similar Messages
-
SQL 2012 Cluster Multi Instances !
Hello,
For SQL 2012 Cluster Multi Instances setup, Does the Storage Space should be different for each instance or can be the same?
Kindly help me in this.
Regards !Hello,
The reason is that's what Microsoft decided to do. It's also that way because disks are a clustered resource and belong to a single resource group. Each SQL Server install will have its own resource group. If a disk could belong to more than one resource
group, and a group fails - then all of the instances with the same disk would fail. That's not what you'd want from an HA solution. Microsoft clustering is a shared nothing model to which this is part of.
Before installing:
http://technet.microsoft.com/en-us/library/ms189910.aspx
◦The base drive, the one with the drive letter, cannot be shared among failover cluster instances.
Creating a new SQL Server Cluster:
http://technet.microsoft.com/en-us/library/ms179530.aspx
-Sean
Sean Gallardy | Blog |
Twitter -
Install SQL 2012 sp1 Named Instance on SQL 2008 r2 Cluster
I am attempting to add a 2012 instance to my 2008r2 cluster, but at 'cluster node configuration' step, the drop down for sql server instance name is empty
Hi,
Seems you have worked it out. You can mark the answers accordingly. It will be nice to let thread stay there so other
community members
can benefit from it.
Please let us know if you would like further assistance.
Thanks.
Tracy Cai
TechNet Community Support -
Reports not Generated after moving SCCM 2012 SP1 DB on SQL 2012 SP1 cluster
Hi all,
i have moved my SCCM 2012 SP1 DB on SQL 2012 SP1 Failover Cluster,this cluster is a two node cluster.the DB was moved fine and the DB configuration in SCCM Site maintenance was also done successfully.After the migration process,SCCM was working fine created
few collections & packages, then checked the DB on cluster & they were updated successfully.
but when i tried to install report server on my SCCM machine,again there was no instance displayed after entering the cluster name.
I searched this & come across this post :-
http://social.technet.microsoft.com/Forums/en-US/configmanagergeneral/thread/4479e73e-8a19-4c7e-9418-b36770656b9b/
which says to install report server on the cluster node machine which is currently running the Reporting Service.I tried to install the report server & the instance was detected this time.it was installed successfully.
But when i tried to generate reports I got this error :-
Permissions are fine as i have added SCCMadmin & sccm machine in the local admin of both the nodes.
Please Help.
Thanks,
Pranay.Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
If you look at your second screenshot the Remote errors is not enabled. Use this blog to enable them.
http://www.enhansoft.com/blog/enabling-remote-errors-in-sql
If changing the data source on the report fixed it for a single report. It means that your shared Datasource is having problems. Reset the username and password within CM12 console and this should fix it for every report.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ -
TF255186: The following SQL Server Reporting Services Instance could not be found
Hi,
I'm trying to install TFS 2013 on a remote SQL RS instance.
Using the TFS 2103 U4 installation
SQL 2012 RS, name instance, Server: SQLProdA, Instance Name COMRS
When I enabled tracing using debugView I see the following output:
[4160] [Error @11:07:10.978] Exception Message: TF255186: The following SQL Server Reporting Services Instance could not be found: COMRS. The server name is: SQLProdA. (type TfsAdminException)
Any ideas what the issue is?
Thanks,
reuvyHi Charles,
Thanks for the help. I already saw those links, and am already trying with the format. As I wrote above:
Server: SQLProdA, Instance Name COMRS
So I wrote in the box "SQLProdA\COMRS" (without quotes of course) and I still keep getting that error.
I don't know if it matters, but although this is indeed a named instance, nonetheless, the path to the report server uses the default url (ie.
http://servername/reports) as opposed to the name instance version (ie.
http://servername_instance/reports) as mentioned by your link and this post:
https://msdn.microsoft.com/en-us/library/bb552341.aspx
But, I checked with Fiddler on the server and didn't see it trying to even access the link so I don't think it is related. I saw with Process Monitor that it is indeed trying to access via the network resources on SQLProdA, so I know it's trying.
I have noticed something in the past, and wondered if this could be the issue, that for example if I have Management Studio 2014 installed, I cannot connect to a Reporting Services instance which is 2012. Only when Management Studio 2012 is installed
and being used can I connect. I wondered if this possibly could be related, that maybe the API or something else which the installer is using is missing some component to connect to the RS instance.
Just in case, I already installed both the SQL 2012 and 2014 Client Tools Connectivity (although I first installed 2014, and then 2012).
Do you think this could be the issue? If not, do you possibly have any other leads?
Thanks,
Reuvy -
Install Guide - SQL Server 2014, Failover Cluster, Windows 2012 R2 Server Core
I am looking for anyone who has a guide with notes about an installation of a two node, multi subnet failover cluster for SQL Server 2014 on Server Core edition
Hi KamarasJaranger,
According to your description, you want configure a SQL Server 2014 Multi-Subnet failover Cluster on Windows Server 2012 R2. Below are the whole steps for the configuration. For the detailed steps about the configuration, please download
and refer to the
PDF file.
1.Add Required Windows Features (.NET Framework 3.5 Features, Failover Clustering and Multipath I/O).
2.Discover target portals.
3.Connect targets and configuring Multipathing.
4.Initialize and format the Disks.
5.Verify the Storage Replication Process.
6.Run the Failover Cluster Validation Wizard.
7.Create the Windows Server 2012 R2 Multi-Subnet Cluster.
8.Tune Cluster Heartbeat Settings.
9.Install SQL Server 2014 on a Multi-Subnet Failover Cluster.
10.Add a Node on a SQL Server 2014 Multi-Subnet Cluster.
11.Tune the SQL Server 2014 Failover Clustered Instance DNS Settings.
12.Test application connectivity.
Regards,
Michelle Li -
Failover Cluster in SQL 2012 in not auto switch when stop service SQL
Good Morning to all,
I'm Mr.Tuyen from VietNam. I have a big problem with AlwaysOn High Availabity in SQL 2012.
I setup 3 server and join Availabilty Group. Ex: Server A (Primary), Server B (Secondary), Cluster Qourum is only node. I have test:
1. Stop service SQL server A, immediately server B is Primary
Start servicel SQL server A, Server A is secondary
2. Stop service SQL server B, server is not Primary and "status is Resloving" and role cluster failed with error as belows
[i]Clustered role 'XXX' has exceeded its failover threshold. It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state. No additional attempts will be made to bring the role
online or fail it over to another node in the cluster. Please check the events associated with the failure. After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it online again after
the restart delay period.[/i]
or
The Cluster service failed to bring clustered role 'XXX' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role.
Do you have same error?http://blogs.msdn.com/b/sqlserverfaq/archive/2012/03/15/inf-alwayson-the-secondary-database-doesn-t-come-automatically-when-the-primary-instance-of-sql-server-goes-down.aspx
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle -
SQL 2012 Database Availability Group - Force Automatic Failover
Hi All,
I'd appreciate some help in understanding the following scenario in my test environment.
I have created a DAG with 2 replica servers (both of which are HyperV VM's running W2012 Std).
From a client PC in my test lab, I can connect to the virtual listener of my DAG and confirm via the "select @@servername" command that I am connecting to the primary replica server.
Using the Failover Wizard, I can easily move to primary instance between my 2 nodes and the command above confirms that the primary replica server has changed. So far so good.
What I wanted to test, was what would happen to my DAG in the event of a complete loss of power to the server that was acting as the primary replica server. At first, I thought I would stop the SQL Server service on the primary server, but this did not result
in my DAG failing over to the secondary replica. I have found out that the only way I can do this is by effectively shutting down the primary server in a controlled manner.
Is there any reason why either stopping the SQL Server service on the primary replica, or indeed forcing a power off of the primary replica does not result in the DAG failing over to the secondary replica?
Thanks,
BobHi,
I would verify if Database Availability Group means AlwaysOn Availability Group.
How did you set the FailureConditionLevel?
Whether the diagnostic data and health information returned by sp_server_diagnostics warrants an automatic failover depends on the failure-condition level of the availability group. The failure-condition level specifies what failure conditions
trigger an automatic failover. There are five failure-condition levels, which range from the least restrictive (level one) to the most restrictive (level five). For details about failure-conditions level, see:
http://msdn.microsoft.com/en-us/library/hh710061.aspx#FClevel
There are two useful articles may be helpful:
SQL 2012 AlwaysOn Availability groups Automatic Failover doesn’t occur or does it – A look at the logs
http://blogs.msdn.com/b/sql_pfe_blog/archive/2013/04/08/sql-2012-alwayson-availability-groups-automatic-failover-doesn-t-occur-or-does-it-a-look-at-the-logs.aspx
SQL Server 2012 AlwaysOn – Part 7 – Details behind an AlwaysOn Availability Group
http://blogs.msdn.com/b/saponsqlserver/archive/2012/04/24/sql-server-2012-alwayson-part-7-details-behind-an-alwayson-availability-group.aspx
Thanks.
Tracy Cai
TechNet Community Support
Hi,
Thanks for the reply.
It's an AlwaysOn Availability Group.
In my test lab, I have changed the quorum configuration to a file share witness and that has allowed an automatic failover when I turn the primary replica server off (rather than power it off).
I'll take a look at the links you provided.
Regards,
Bob -
Hi, My name is Leonard and I am studying SQL. I have downloaded the newest MS SQL 2012 and also MS 2012 Hyper-V. I have set a MS 2012 Hyper-V on a laptop with AMD Turion 64 X2 and 3G of RAM (Planing
to add more to max at 8G).
Following the instructions in the free online
Administering Microsoft SQL Server 2012 Databases” Training Kit, I have set 6 virtual machines as instructed in the Training Kit. While the installation of the MS Server Core 2008 R2 SP1 completed with no
problem, the same cannot be said for the SQL Server 2012 installation. I have encountered an error that I have not seen anyone address in any of the SQL web forums.
After running the unattended setup instruction (Setup.exe /qs /ACTION=Install /FEATURES=SQLEngine /INSTANCENAME=MSSQLSERVER
/SQLSVCACCOUNT="Njowa\Pa$$worD>" /SQLSVCPASSWORD=" Pa$$worD” /SQLSYSADMINACCOUNTS="Njowa\lenny#4!@" /AGTSVCACCOUNT="NT AUTHORITY\Network Service"
/IACCEPTSQLSERVERLICENSETERMS) this is what I get after a series SQL setup
initiation windows popups then disappears.
The following error occurred:
Object reference not set to an instance of an object.
Error result: -2147467261
Result facility Code: 0
Result error Code: 16387
Please review the summary.txt log for further details
My question is: What instance of an object is not properly initialize in the Setup instructionsHello,
Please note that SQL Server requires at least 1 GB of RAM. The operating system (Windows Server) requires 2 GB of RAM (recommended) or 512 MB (minimum). This means any virtual machine that will receive the installation of a SQL Server instance requires 1.5
or 2 GB at least.
The behavior of SQL Server setup tells me that the virtual machine does not have enough memory assigned or .NET Framework 3.5 was not enable on Control Panel->Program
and Features before trying to install SQL Server.
The following thread is about another possible cause of this error:
http://social.msdn.microsoft.com/Forums/mr-IN/sqlsetupandupgrade/thread/575d3025-69f5-4152-a473-44496b008811
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Error while installing the named instance SQL 2012 Sp1
Hi,
I am getting below error while installing the named instance with features Data base engine. on same server box 2 named instance already installed and working...please suggest. i have done a lot of troubleshooting..(configure local system for Db engines
during installation, tried to install after another domain ID., repair and uninstalled existing and retried.) .. please s if i need to do anything else to resolve the issue.. installation account is domain admin account...
Can i rename the installation domain account profile from sql server that used for 2 named instance and for 3 rd named instance i am trying... is any impact after profile rename from the local sql server on any instance already configured...
Shailendra Devthanks alberto.
here is
2015-03-24 19:48:49.42 Server Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64)
Oct 19 2012 13:38:57
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
2015-03-24 19:48:49.42 Server (c) Microsoft Corporation.
2015-03-24 19:48:49.42 Server All rights reserved.
2015-03-24 19:48:49.42 Server Server process ID is 3460.
2015-03-24 19:48:49.42 Server System Manufacturer: 'Xen', System Model: 'HVM domU'.
2015-03-24 19:48:49.42 Server Authentication mode is WINDOWS-ONLY.
2015-03-24 19:48:49.42 Server Logging SQL Server messages in file 'D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\Log\ERRORLOG'.
2015-03-24 19:48:49.42 Server The service account is 'AIRWORKS\scadmin'. This is an informational message; no user action is required.
2015-03-24 19:48:49.42 Server Registry startup parameters:
-d D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\DATA\master.mdf
-e D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\Log\ERRORLOG
-l D:\Program Files\Microsoft SQL Server\MSSQL11.SCSMDB\MSSQL\DATA\mastlog.ldf
2015-03-24 19:48:49.42 Server Command Line Startup Parameters:
-s "SCSMDB"
-m "SqlSetup"
-T 4022
-T 4010
-T 1905
-T 3701
-T 8015
2015-03-24 19:48:49.69 Server SQL Server detected 1 sockets with 1 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2015-03-24 19:48:49.69 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-03-24 19:48:49.69 Server Detected 15624 MB of RAM. This is an informational message; no user action is required.
2015-03-24 19:48:49.69 Server Using conventional memory in the memory manager.
2015-03-24 19:48:49.98 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2015-03-24 19:48:50.01 Server This instance of SQL Server last reported using a process ID of 5124 at 3/24/2015 7:48:48 PM (local) 3/24/2015 2:18:48 PM (UTC). This is an informational message only; no user action is required.
2015-03-24 19:48:50.03 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2015-03-24 19:48:50.07 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2015-03-24 19:48:50.30 Server Database Mirroring Transport is disabled in the endpoint configuration.
2015-03-24 19:48:50.58 spid5s Warning ******************
2015-03-24 19:48:50.65 spid5s SQL Server started in single-user mode. This an informational message only. No user action is required.
2015-03-24 19:48:50.66 spid5s Starting up database 'master'.
2015-03-24 19:48:50.90 spid5s 9 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2015-03-24 19:48:51.04 Server CLR version v4.0.30319 loaded.
2015-03-24 19:48:51.17 spid5s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2015-03-24 19:48:51.17 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2015-03-24 19:48:51.39 Server Software Usage Metrics is enabled.
2015-03-24 19:48:51.81 spid5s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-03-24 19:48:51.83 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-03-24 19:48:51.86 spid5s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-03-24 19:48:52.02 spid5s SQL Trace ID 1 was started by login "sa".
2015-03-24 19:48:52.16 spid5s Server name is 'AWISCDB\SCSMDB'. This is an informational message only. No user action is required.
2015-03-24 19:48:52.35 spid12s The certificate [Cert Hash(sha1) "151C8B90A9A8AF12F5EFAE3439F691E2C01A7355"] was successfully loaded for encryption.
2015-03-24 19:48:52.35 spid12s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SCSMDB ].
2015-03-24 19:48:52.40 spid12s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806.
This is an informational message only. No user action is required.
2015-03-24 19:48:52.43 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Windows return code: 0x490, state: 16. Failure to register a SPN might cause integrated
authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2015-03-24 19:48:52.45 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational
message. No user action is required.
2015-03-24 19:48:54.03 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/AWISCDB.AIRWORKS.IN:SCSMDB ] for the SQL Server service.
2015-03-24 19:48:54.03 spid14s A new instance of the full-text filter daemon host process has been successfully started.
2015-03-24 19:48:54.86 spid6s Starting up database 'mssqlsystemresource'.
2015-03-24 19:48:54.86 spid5s Starting up database 'msdb'.
2015-03-24 19:48:54.87 spid6s The resource database build version is 11.00.3000. This is an informational message only. No user action is required.
2015-03-24 19:48:55.21 spid5s 12 transactions rolled forward in database 'msdb' (4:0). This is an informational message only. No user action is required.
2015-03-24 19:48:55.32 spid5s 0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
2015-03-24 19:48:55.32 spid6s Starting up database 'model'.
2015-03-24 19:48:55.32 spid5s Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
2015-03-24 19:48:55.72 spid6s Clearing tempdb database.
2015-03-24 19:48:57.22 spid6s Starting up database 'tempdb'.
2015-03-24 19:48:59.04 spid5s Database 'master' is upgrading script 'msdb110_upgrade.sql' from level 184551476 to level 184552376.
2015-03-24 19:48:59.04 spid5s ----------------------------------
2015-03-24 19:48:59.04 spid5s Starting execution of PRE_MSDB.SQL
2015-03-24 19:48:59.04 spid5s ----------------------------------
2015-03-24 19:49:00.23 spid5s Setting database option COMPATIBILITY_LEVEL to 100 for database 'msdb'.
2015-03-24 19:49:00.57 spid5s -----------------------------------------
2015-03-24 19:49:00.57 spid5s Starting execution of PRE_SQLAGENT100.SQL
2015-03-24 19:49:00.57 spid5s -----------------------------------------
2015-03-24 19:49:00.61 spid5s Setting database option COMPATIBILITY_LEVEL to 110 for database 'msdb'.
2015-03-24 19:49:00.73 spid5s Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install.
2015-03-24 19:49:00.73 spid5s Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install.
2015-03-24 19:49:01.78 spid5s Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2015-03-24 19:49:01.79 spid5s Using 'xpstar.dll' version '2011.110.3000' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2015-03-24 19:49:01.80 spid5s DBCC TRACEOFF 1717, server process ID (SPID) 5. This is an informational message only; no user action is required.
2015-03-24 19:49:01.80 spid5s DBCC execution completed. If DBCC printed error messages, contact your system administrator.
2015-03-24 19:49:01.81 spid5s
2015-03-24 19:49:01.81 spid5s Creating table temp_sysjobschedules
2015-03-24 19:49:01.91 spid5s
2015-03-24 19:49:01.91 spid5s Alter table sysdownloadlist...
2015-03-24 19:49:01.92 spid5s
2015-03-24 19:49:01.92 spid5s Alter table sysjobhistory...
2015-03-24 19:49:01.92 spid5s
2015-03-24 19:49:01.92 spid5s Alter table systargetservers...
2015-03-24 19:49:01.92 spid5s
2015-03-24 19:49:01.92 spid5s Alter table sysjobsteps...
2015-03-24 19:49:01.99 spid5s Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
2015-03-24 19:49:01.99 spid5s Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
2015-03-24 19:49:01.99 spid5s
2015-03-24 19:49:01.99 spid5s -----------------------------------------
2015-03-24 19:49:01.99 spid5s Execution of PRE_SQLAGENT100.SQL complete
2015-03-24 19:49:01.99 spid5s -----------------------------------------
2015-03-24 19:49:02.01 spid5s DMF pre-upgrade steps...
2015-03-24 19:49:02.13 spid5s DC pre-upgrade steps...
2015-03-24 19:49:02.13 spid5s Check if Data collector config table exists...
2015-03-24 19:49:02.13 spid5s Data Collector state before upgrade: 0
2015-03-24 19:49:02.13 spid5s pre_dc100::Check if syscollector_collection_sets_internal table exists...
2015-03-24 19:49:02.13 spid5s pre_dc100::Capturing Collection set status in temp table...
2015-03-24 19:49:02.19 spid5s Deleting cached auto-generated T-SQL Data Collection packages from msdb...
2015-03-24 19:49:02.19 spid5s End of DC pre-upgrade steps.
2015-03-24 19:49:02.19 spid5s DAC pre-upgrade steps...
2015-03-24 19:49:02.19 spid5s Starting DAC pre-upgrade steps ...
2015-03-24 19:49:02.19 spid5s End of DAC pre-upgrade steps.
2015-03-24 19:49:02.19 spid5s ----------------------------------
2015-03-24 19:49:02.19 spid5s Starting execution of MSDB.SQL
2015-03-24 19:49:02.19 spid5s ----------------------------------
2015-03-24 19:49:02.23 spid5s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-03-24 19:49:02.23 spid5s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-03-24 19:49:02.27 spid5s Checking the size of MSDB...
2015-03-24 19:49:02.53 spid5s
2015-03-24 19:49:02.53 spid5s Setting database option TRUSTWORTHY to ON for database 'msdb'.
2015-03-24 19:49:02.53 spid5s Setting database option RECOVERY to SIMPLE for database 'msdb'.
2015-03-24 19:49:02.64 spid5s ----------------------------------
2015-03-24 19:49:02.64 spid5s Finished execution of MSDB.SQL
2015-03-24 19:49:02.64 spid5s ----------------------------------
2015-03-24 19:49:02.64 spid5s -----------------------------------------
2015-03-24 19:49:02.64 spid5s Starting execution of MSDB_VERSIONING.SQL
2015-03-24 19:49:02.64 spid5s -----------------------------------------
2015-03-24 19:49:02.64 spid5s -----------------------------------------
2015-03-24 19:49:02.64 spid5s Finished execution of MSDB_VERSIONING.SQL
2015-03-24 19:49:02.64 spid5s -----------------------------------------
2015-03-24 19:49:02.64 spid5s Dropping view MSdatatype_mappings...
2015-03-24 19:49:02.65 spid5s Dropping view sysdatatypemappings...
2015-03-24 19:49:02.65 spid5s Dropping table MSdbms_datatype_mapping...
2015-03-24 19:49:02.66 spid5s Dropping table MSdbms_map...
2015-03-24 19:49:02.67 spid5s Dropping table MSdbms_datatype...
2015-03-24 19:49:02.67 spid5s Dropping table MSdbms...
2015-03-24 19:49:02.73 spid5s Creating table MSdbms
2015-03-24 19:49:02.75 spid5s Creating table MSdbms_datatype
2015-03-24 19:49:03.01 spid5s Creating table MSdbms_map
2015-03-24 19:49:03.02 spid5s Creating table MSdbms_datatype_mapping
2015-03-24 19:49:03.03 spid5s Definining default datatype mappings
2015-03-24 19:49:03.04 spid5s Creating datatype mappings for MSSQLSERVER to ORACLE8
2015-03-24 19:49:03.21 spid5s Creating datatype mappings for MSSQLSERVER to ORACLE9
2015-03-24 19:49:03.29 spid5s Creating datatype mappings for MSSQLSERVER to ORACLE10
2015-03-24 19:49:03.37 spid5s Creating datatype mappings for MSSQLSERVER to ORACLE11
2015-03-24 19:49:03.46 spid5s Creating datatype mappings for MSSQLSERVER to DB2
2015-03-24 19:49:03.54 spid5s Creating datatype mappings for MSSQLSERVER to SYBASE
2015-03-24 19:49:03.62 spid5s Creating datatype mappings for ORACLE8 to MSSQLSERVER
2015-03-24 19:49:03.71 spid5s Creating datatype mappings for ORACLE9 to MSSQLSERVER
2015-03-24 19:49:03.83 spid5s Creating datatype mappings for ORACLE10 to MSSQLServer
2015-03-24 19:49:03.95 spid5s Creating datatype mappings for ORACLE11 to MSSQLServer
2015-03-24 19:49:04.08 spid5s Creating view MSdatatype_mappings
2015-03-24 19:49:04.08 spid5s Creating view sysdatatypemappings
2015-03-24 19:49:05.08 spid5s
2015-03-24 19:49:05.08 spid5s Creating table syssubsystems...
2015-03-24 19:49:05.09 spid5s
2015-03-24 19:49:05.09 spid5s Creating view sysproxyloginsubsystem_view...
2015-03-24 19:49:05.11 spid5s
2015-03-24 19:49:05.11 spid5s Creating trigger trig_sysoriginatingservers_delete...
2015-03-24 19:49:05.11 spid5s
2015-03-24 19:49:05.11 spid5s Creating view sysoriginatingservers_view...
2015-03-24 19:49:05.12 spid5s
2015-03-24 19:49:05.12 spid5s Creating trigger trig_sysjobs_insert_update...
2015-03-24 19:49:05.13 spid5s
2015-03-24 19:49:05.13 spid5s Creating view sysjobs_view...
2015-03-24 19:49:05.15 spid5s
2015-03-24 19:49:05.15 spid5s Creating trigger trig_sysschedules_insert_update...
2015-03-24 19:49:05.16 spid5s
2015-03-24 19:49:05.16 spid5s Creating view sysschedules_localserver_view...
2015-03-24 19:49:05.21 spid5s
2015-03-24 19:49:05.21 spid5s Creating view systargetservers_view...
2015-03-24 19:49:05.23 spid5s
2015-03-24 19:49:05.23 spid5s Creating view sysalerts_performance_counters_view...
2015-03-24 19:49:05.25 spid5s
2015-03-24 19:49:05.25 spid5s Creating function SQLAGENT_SUSER_SNAME ...
2015-03-24 19:49:05.25 spid5s
2015-03-24 19:49:05.25 spid5s Creating function SQLAGENT_SUSER_SID ...
2015-03-24 19:49:05.26 spid5s
2015-03-24 19:49:05.26 spid5s Creating procedure SP_SQLAGENT_IS_SRVROLEMEMBER...
2015-03-24 19:49:05.27 spid5s
2015-03-24 19:49:05.27 spid5s Creating procedure sp_verify_category_identifiers...
2015-03-24 19:49:05.27 spid5s
2015-03-24 19:49:05.27 spid5s Creating function agent_datetime...
2015-03-24 19:49:05.27 spid5s
2015-03-24 19:49:05.27 spid5s Creating procedure sp_verify_proxy_identifiers...
2015-03-24 19:49:05.28 spid5s
2015-03-24 19:49:05.28 spid5s Creating procedure sp_verify_credential_identifiers...
2015-03-24 19:49:05.29 spid5s
2015-03-24 19:49:05.29 spid5s Creating procedure sp_verify_subsystems...
2015-03-24 19:49:05.30 spid5s
2015-03-24 19:49:05.30 spid5s Creating procedure sp_verify_subsystem_identifiers...
2015-03-24 19:49:05.30 spid5s
2015-03-24 19:49:05.30 spid5s Creating procedure sp_verify_login_identifiers...
2015-03-24 19:49:05.31 spid5s
2015-03-24 19:49:05.31 spid5s Creating procedure sp_verify_proxy...
2015-03-24 19:49:05.31 spid5s
2015-03-24 19:49:05.31 spid5s Creating procedure sp_add_proxy...
2015-03-24 19:49:05.32 spid5s
2015-03-24 19:49:05.32 spid5s Creating procedure sp_delete_proxy...
2015-03-24 19:49:05.32 spid5s
2015-03-24 19:49:05.32 spid5s Creating procedure sp_update_proxy...
2015-03-24 19:49:05.33 spid5s
2015-03-24 19:49:05.33 spid5s Creating procedure sp_sqlagent_is_member...
2015-03-24 19:49:05.33 spid5s
2015-03-24 19:49:05.33 spid5s Creating procedure sp_verify_proxy_permissions...
2015-03-24 19:49:05.34 spid5s
2015-03-24 19:49:05.34 spid5s Creating procedure sp_help_proxy...
2015-03-24 19:49:05.35 spid5s
2015-03-24 19:49:05.35 spid5s Creating procedure sp_get_proxy_properties...
2015-03-24 19:49:05.36 spid5s
2015-03-24 19:49:05.36 spid5s Creating procedure sp_grant_proxy_to_subsystem...
2015-03-24 19:49:05.36 spid5s
2015-03-24 19:49:05.36 spid5s Creating procedure sp_grant_login_to_proxy...
2015-03-24 19:49:05.37 spid5s
2015-03-24 19:49:05.37 spid5s Creating procedure sp_revoke_login_from_proxy...
2015-03-24 19:49:05.37 spid5s
2015-03-24 19:49:05.37 spid5s Creating procedure sp_revoke_proxy_from_subsystem...
2015-03-24 19:49:05.38 spid5s
2015-03-24 19:49:05.38 spid5s Creating procedure sp_enum_proxy_for_subsystem...
2015-03-24 19:49:05.38 spid5s
2015-03-24 19:49:05.38 spid5s Creating procedure sp_enum_login_for_proxy...
2015-03-24 19:49:05.39 spid5s
2015-03-24 19:49:05.39 spid5s Creating procedure sp_reassign_proxy...
2015-03-24 19:49:05.40 spid5s
2015-03-24 19:49:05.40 spid5s Creating procedure sp_sqlagent_get_startup_info...
2015-03-24 19:49:05.41 spid5s
2015-03-24 19:49:05.41 spid5s Creating procedure sp_sqlagent_update_agent_xps...
2015-03-24 19:49:05.42 spid5s
2015-03-24 19:49:05.42 spid5s Creating procedure sp_sqlagent_has_server_access...
2015-03-24 19:49:05.45 spid5s
2015-03-24 19:49:05.45 spid5s Creating procedure sp_sqlagent_get_perf_counters...
2015-03-24 19:49:05.46 spid5s
2015-03-24 19:49:05.46 spid5s Creating procedure sp_sqlagent_notify...
2015-03-24 19:49:05.47 spid5s
2015-03-24 19:49:05.47 spid5s Creating procedure sp_is_sqlagent_starting...
2015-03-24 19:49:05.47 spid5s
2015-03-24 19:49:05.47 spid5s Creating procedure sp_verify_job_identifiers...
2015-03-24 19:49:05.48 spid5s
2015-03-24 19:49:05.48 spid5s Creating procedure sp_verify_schedule_identifiers...
2015-03-24 19:49:05.49 spid5s
2015-03-24 19:49:05.49 spid5s Creating procedure sp_verify_jobproc_caller...
2015-03-24 19:49:05.50 spid5s
2015-03-24 19:49:05.50 spid5s Creating procedure sp_downloaded_row_limiter...
2015-03-24 19:49:05.51 spid5s
2015-03-24 19:49:05.51 spid5s Creating procedure sp_post_msx_operation...
2015-03-24 19:49:05.54 spid5s
2015-03-24 19:49:05.54 spid5s Creating procedure sp_verify_performance_condition...
2015-03-24 19:49:05.58 spid5s
2015-03-24 19:49:05.58 spid5s Creating procedure sp_verify_job_date...
2015-03-24 19:49:05.59 spid5s
2015-03-24 19:49:05.59 spid5s Creating procedure sp_verify_job_time...
2015-03-24 19:49:05.61 spid5s
2015-03-24 19:49:05.61 spid5s Creating procedure sp_verify_alert...
2015-03-24 19:49:05.62 spid5s
2015-03-24 19:49:05.62 spid5s Creating procedure sp_update_alert...
2015-03-24 19:49:05.63 spid5s
2015-03-24 19:49:05.63 spid5s Creating procedure sp_delete_job_references...
2015-03-24 19:49:05.65 spid5s
2015-03-24 19:49:05.65 spid5s Creating procedure sp_delete_all_msx_jobs...
2015-03-24 19:49:05.66 spid5s
2015-03-24 19:49:05.66 spid5s Creating procedure sp_generate_target_server_job_assignment_sql...
2015-03-24 19:49:05.66 spid5s
2015-03-24 19:49:05.66 spid5s Creating procedure sp_generate_server_description...
2015-03-24 19:49:05.67 spid5s
2015-03-24 19:49:05.67 spid5s Creating procedure sp_msx_set_account...
2015-03-24 19:49:05.68 spid5s
2015-03-24 19:49:05.68 spid5s Creating procedure sp_msx_get_account...
2015-03-24 19:49:05.69 spid5s
2015-03-24 19:49:05.69 spid5s Creating procedure sp_delete_operator...
2015-03-24 19:49:05.70 spid5s
2015-03-24 19:49:05.70 spid5s Creating procedure sp_msx_defect...
2015-03-24 19:49:05.71 spid5s
2015-03-24 19:49:05.71 spid5s Creating procedure sp_msx_enlist...
2015-03-24 19:49:05.72 spid5s
2015-03-24 19:49:05.72 spid5s Creating procedure sp_delete_targetserver...
2015-03-24 19:49:05.73 spid5s
2015-03-24 19:49:05.73 spid5s Creating procedure sp_enlist_tsx
2015-03-24 19:49:05.74 spid5s
2015-03-24 19:49:05.74 spid5s Creating procedure sp_get_sqlagent_properties...
2015-03-24 19:49:05.76 spid5s
2015-03-24 19:49:05.76 spid5s Create procedure sp_set_sqlagent_properties...
2015-03-24 19:49:05.76 spid5s
2015-03-24 19:49:05.76 spid5s Creating procedure sp_add_targetservergroup...
2015-03-24 19:49:05.77 spid5s
2015-03-24 19:49:05.77 spid5s Creating procedure sp_update_targetservergroup...
2015-03-24 19:49:05.78 spid5s
2015-03-24 19:49:05.78 spid5s Creating procedure sp_delete_targetservergroup...
2015-03-24 19:49:05.78 spid5s
2015-03-24 19:49:05.78 spid5s Creating procedure sp_help_targetservergroup...
2015-03-24 19:49:05.79 spid5s
2015-03-24 19:49:05.79 spid5s Creating procedure sp_add_targetsvgrp_member...
2015-03-24 19:49:05.80 spid5s
2015-03-24 19:49:05.80 spid5s Creating procedure sp_delete_targetsvrgrp_member...
2015-03-24 19:49:05.81 spid5s
2015-03-24 19:49:05.81 spid5s Creating procedure sp_verify_category...
2015-03-24 19:49:05.81 spid5s
2015-03-24 19:49:05.81 spid5s Creating procedure sp_add_category...
2015-03-24 19:49:05.82 spid5s
2015-03-24 19:49:05.82 spid5s Creating procedure sp_update_category...
2015-03-24 19:49:05.83 spid5s
2015-03-24 19:49:05.83 spid5s Creating procedure sp_delete_category...
2015-03-24 19:49:05.83 spid5s
2015-03-24 19:49:05.84 spid5s Creating procedure sp_help_category...
2015-03-24 19:49:05.84 spid5s
2015-03-24 19:49:05.84 spid5s Creating procedure sp_help_targetserver...
2015-03-24 19:49:05.85 spid5s
2015-03-24 19:49:05.85 spid5s Creating procedure sp_resync_targetserver...
2015-03-24 19:49:06.06 spid5s
2015-03-24 19:49:06.06 spid5s Creating procedure sp_purge_jobhistory...
2015-03-24 19:49:06.09 spid5s
2015-03-24 19:49:06.09 spid5s Creating procedure sp_help_jobhistory...
2015-03-24 19:49:06.10 spid5s
2015-03-24 19:49:06.10 spid5s Creating procedure sp_add_jobserver...
2015-03-24 19:49:06.11 spid5s
2015-03-24 19:49:06.11 spid5s Creating procedure sp_delete_jobserver...
2015-03-24 19:49:06.11 spid5s Error: 10011, Severity: 16, State: 1.
2015-03-24 19:49:06.11 spid5s Access denied.
2015-03-24 19:49:06.11 spid5s Error: 917, Severity: 15, State: 1.
2015-03-24 19:49:06.11 spid5s An upgrade script batch failed to execute for database 'master' due to compilation error. Check the previous error message for the line which caused compilation to fail.
2015-03-24 19:49:06.11 spid5s Error: 912, Severity: 21, State: 2.
2015-03-24 19:49:06.11 spid5s Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 917, state 1, severity 15. This is a serious error condition which might interfere with regular
operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective
actions and re-start the database so that the script upgrade steps run to completion.
2015-03-24 19:49:06.11 spid5s Error: 3417, Severity: 21, State: 3.
2015-03-24 19:49:06.11 spid5s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books
Online.
2015-03-24 19:49:06.12 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2015-03-24 19:49:06.50 spid12s The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/AWISCDB.AIRWORKS.IN:SCSMDB ] for the SQL Server service.
Shailendra Dev -
<p>Hi,</p><p>I'm trying to install SQL Server 2012 SP1 on the first node of a Windows Server 2012 R2 failover cluster.</p><p>The install hangs whilst displaying the "Please wait while Microsoft SQL Server 2012 Servce
Pack 1 Setup processes the current operation." message.</p><p>The detail.txt log file shows as follows:</p><p>(01) 2014-07-17 15:36:35 Slp: -- PidInfoProvider : Use cached PID<br />(01) 2014-07-17 15:36:35 Slp: -- PidInfoProvider
: NormalizePid is normalizing input pid<br />(01) 2014-07-17 15:36:35 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid<br />(01) 2014-07-17 15:36:35 Slp: -- PidInfoProvider : Use cached
PID<br />(01) 2014-07-17 15:36:35 Slp: Completed Action: FinalCalculateSettings, returned True<br />(01) 2014-07-17 15:36:35 Slp: Completed Action: ExecuteBootstrapAfterExtensionsLoaded, returned True<br />(01) 2014-07-17 15:36:35 Slp: ----------------------------------------------------------------------<br
/>(01) 2014-07-17 15:36:35 Slp: Running Action: RunRemoteDiscoveryAction<br />(01) 2014-07-17 15:36:36 Slp: Running discovery on local machine<br />(01) 2014-07-17 15:36:36 Slp: Discovery on local machine is complete<br />(01) 2014-07-17
15:36:36 Slp: Running discovery on remote machine: XXX-XXX-01</p><p>After about 4 hours and 10 minutes, the step seems to time out and move on, however it doesn't seem to have discovered what it needs to and the setup subsuently fails</p><p></p>Hi,
Sorry Information you provided did not helped can you post content of both summary file and details,txt file on shared location for analysis.
Can you download Service pack again and try once more
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles -
Reporting Services install on SQL 2012 SP1 instance blank
Sorry for the duplicate . . . didn't think the first on posted due to VDI locking up.
I have looked at all the links and tried the suggestions and I am still having the problem:
SCCM 2012 R2 SQL 2012 SP1 SSRS installed and configured (separate boxes)
When I try to add the reporting services role, it finds the SCCM database and verifies connectivity to it, the SSRS instance drop down is blank.
Using a domain service accout with local admin rights on both machines and sa rights in SQL.
There is a firewall between the Primary Server and the SQL Server and ports 80, 135, 443, 445, 1433 and the high RPC range.
Does anyone know how it is determining the instance? I have read it is via WMI but I am not sure if it is a query or executing a method. I have verified the svc acct has the correct DCOM privs.Hi,
How are things going? Please let us know if there is any progress.
Regards.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Instance failure, in System.Data in sql 2012
On Win Server 2012 Standard I have a C# app that runs fine with sql 2008 express. When I installed sql 2012 express I get "instance Failure" source: System.data. when the following LYNQ query executes:
//MessageBox.Show("Starting GetInitialPortStatus.");
db =new
DataClasses1DataContext(); //establish
dataconnection to CALMasterSQL
// 2. Query creation.
var PortsQuery =from
portrecord in db.Channels
select portrecord;
// 3. Query execution.
int count = 0;
// MessageBox.Show("Starting >portrecord in PortsQuery<.");
foreach (var
portrecord in PortsQuery)
// add rows to the grid for each record in the database Ports table
Otherwise the app works fine. The closet fix in the forum I could find was to run
exec sp_configure 'user instances enabled',
1.
Go
Reconfigure
Which I did but no change.
How can this be corrected. It seems like it is a known issue but no fix for sql 2012?
Thanks
Morris
Thank you MorrisThanks for your reply.
The connection string is:
<add name="CMMainWindow.Properties.Settings.CALLMASTERConnectionString"
connectionString="Data Source=HLA2012\\SQL2012EXP;Initial Catalog=CALLMasterSQL;Integrated Security=True;Connect Timeout=5"
providerName="System.Data.SqlClient" />
The SQl instance is call "SQL2012EXP". There is also SQL 2008 Express on the same machine called SQLExpress.
Both engines work fine in every other way.
Thanks
Morris
Thank you Morris
Hi MoCoder,
According to your description, if it contains a double-slash between the server name and the database instance name in your connection string, it should be localhost\SQLEXPRESS. There is a similar issue about instance failure when connecting to SQL Server
Express in C# application. You can review the following article.
http://www.hanselman.com/blog/FixingInstanceFailureWhenConnectingToSQLServer2005Express.aspx
In addition, Make sure your SQL Server instance(MSSQLSERVER) is running via the services management console.
Thanks,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support -
The following code
var comp = new Microsoft.SqlServer.Management.Smo.Wmi.ManagedComputer();
var bob = comp.Services;
Only returns the 2008R2 instances on my machine not the sql 2012 instances.
Oddly the ServerInstances includes all the instances.
This means I can't get the StartupParameters for the instance.
I've checked and its definitely using the sql 2012 version of SMO. All services are using the same user account (Network Service)
Can anyone think why this would be.
@simon_sabin -
SQL Know How - SQL Server Consultancy and Real world training - SQLBits - Largest SQL Server Conference in Europe and its free2014-09-08T20:23:33.1175952+02:00 *** Test of the default constructor of ManagedComputer
Name of the ManagedComputer : USER-PC
- 3 ClientProtocols
- 0 ServerAliases
- 3 ServerInstances
- Instance : EXPRESS_ADV_2014
- Instance : EXPRESSADV2014
- Instance : SQLEXPRESS
- 12 Services
List of the available services :
- Service : MSSQL$EXPRESS_ADV_2014
- DisplayName : SQL Server (EXPRESS_ADV_2014)
- ErrorControl : Normal
- PathName : "F:\Install_SQLServerExpress2014\MSSQL12.EXPRESS_ADV_2014\MSSQL\Binn\sqlservr.exe" -sEXPRESS_ADV_2014
- ProcessId : 1972
- ServiceState : Running
- Type : SqlServer
- StartMode : Auto
- Service : MSSQL$EXPRESSADV2014
- DisplayName : SQL Server (EXPRESSADV2014)
- ErrorControl : Normal
- PathName : "C:\Program Files\Microsoft SQL Server\MSSQL12.EXPRESSADV2014\MSSQL\Binn\sqlservr.exe" -sEXPRESSADV2014
- ProcessId : 0
- ServiceState : Stopped
- Type : SqlServer
- StartMode : Disabled
- Service : MSSQL$SQLEXPRESS
- DisplayName : SQL Server (SQLEXPRESS)
- ErrorControl : Normal
- PathName : "C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS_ADV\MSSQL\Binn\sqlservr.exe" -sSQLEXPRESS
- ProcessId : 356
- ServiceState : Running
- Type : SqlServer
- StartMode : Auto
- Service : MSSQLFDLauncher$EXPRESS_ADV_2014
- DisplayName : SQL Full-text Filter Daemon Launcher (EXPRESS_ADV_2014)
- ErrorControl : Normal
- PathName : "F:\Install_SQLServerExpress2014\MSSQL12.EXPRESS_ADV_2014\MSSQL\Binn\fdlauncher.exe" -s MSSQL12.EXPRESS_ADV_2014
- ProcessId : 1708
- ServiceState : Running
- Type : 9
- StartMode : Manual
- Service : MSSQLFDLauncher$EXPRESSADV2014
- DisplayName : SQL Full-text Filter Daemon Launcher (EXPRESSADV2014)
- ErrorControl : Normal
- PathName : "C:\Program Files\Microsoft SQL Server\MSSQL12.EXPRESSADV2014\MSSQL\Binn\fdlauncher.exe" -s MSSQL12.EXPRESSADV2014
- ProcessId : 0
- ServiceState : Stopped
- Type : 9
- StartMode : Manual
- Service : MSSQLFDLauncher$SQLEXPRESS
- DisplayName : SQL Full-text Filter Daemon Launcher (SQLEXPRESS)
- ErrorControl : Normal
- PathName : "C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS_ADV\MSSQL\Binn\fdlauncher.exe" -s MSSQL11.SQLEXPRESS_ADV
- ProcessId : 3980
- ServiceState : Running
- Type : 9
- StartMode : Manual
- Service : ReportServer$EXPRESSADV2014
- DisplayName : SQL Server Reporting Services (EXPRESSADV2014)
- ErrorControl : Normal
- PathName : "C:\Program Files\Microsoft SQL Server\MSRS12.EXPRESSADV2014\Reporting Services\ReportServer\bin\ReportingServicesService.exe"
- ProcessId : 0
- ServiceState : Stopped
- Type : ReportServer
- StartMode : Auto
- Service : ReportServer$SQLEXPRESS
- DisplayName : SQL Server Reporting Services (SQLEXPRESS)
- ErrorControl : Normal
- PathName : "C:\Program Files\Microsoft SQL Server\MSRS11.SQLEXPRESS_ADV\Reporting Services\ReportServer\bin\ReportingServicesService.exe"
- ProcessId : 2516
- ServiceState : Running
- Type : ReportServer
- StartMode : Auto
- Service : SQLAgent$EXPRESS_ADV_2014
- DisplayName : SQL Server Agent (EXPRESS_ADV_2014)
- ErrorControl : Normal
- PathName : "F:\Install_SQLServerExpress2014\MSSQL12.EXPRESS_ADV_2014\MSSQL\Binn\SQLAGENT.EXE" -i EXPRESS_ADV_2014
- ProcessId : 0
- ServiceState : Stopped
- Type : SqlAgent
- StartMode : Disabled
- Service : SQLAgent$EXPRESSADV2014
- DisplayName : SQL Server Agent (EXPRESSADV2014)
- ErrorControl : Normal
- PathName : "C:\Program Files\Microsoft SQL Server\MSSQL12.EXPRESSADV2014\MSSQL\Binn\SQLAGENT.EXE" -i EXPRESSADV2014
- ProcessId : 0
- ServiceState : Stopped
- Type : SqlAgent
- StartMode : Disabled
- Service : SQLAgent$SQLEXPRESS
- DisplayName : SQL Server Agent (SQLEXPRESS)
- ErrorControl : Normal
- PathName : "C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS_ADV\MSSQL\Binn\SQLAGENT.EXE" -i SQLEXPRESS
- ProcessId : 0
- ServiceState : Stopped
- Type : SqlAgent
- StartMode : Disabled
- Service : SQLBrowser
- DisplayName : SQL Server Browser
- ErrorControl : Normal
- PathName : "C:\Program Files (x86)\Microsoft SQL Server\90\Shared\sqlbrowser.exe"
- ProcessId : 2628
- ServiceState : Running
- Type : SqlBrowser
- StartMode : Auto
Hello Simon ,
For SMO assemblies : the version is 11 for SQL Server 2012 , and 10 for SQL Server 2008 R2 ( and not 10.5 , so when you have SQL Server 2008 and 2008 R2 , the SMO assemblies for 2008 are replaced by the SMO assemblies for 2008 R2 ). I faced this
problem when I installed SQL Server 2008 R2 aside a left 2008 install.
On my current computer , I have only 2012 and 2014 instances and I have no problem.
To check the version of the assemblies ( Microsoft.Smo.SqlWmiManagement mainly ) in your Visual Studio , click on the name of this assembly and look at the Version : it should be 11.0.0 ( for SQL Server 2012 ).
Yesterday , I have written a little application to view the instances and services on my computer.
using System.Collections.Specialized;
using System.Data;
using System.Linq;
using System.Management;
using System.Text;
using System.Threading.Tasks;
using System.Windows.Forms;
using Microsoft.SqlServer.Management.Common;
using Microsoft.SqlServer.Management.Dmf;
using Microsoft.SqlServer.Management.Facets;
using Microsoft.SqlServer.Management.Sdk.Sfc;
using Microsoft.SqlServer.Management.Smo;
using Microsoft.SqlServer.Management.Smo.SqlEnum;
using Microsoft.SqlServer.Management.Smo.Wmi;
namespace Test_ManagedComputer_SMO2014_VCS2014
/// <summary>
/// Class for fields/properties/methods used in the Main method
/// </summary>
class Program
private static ManagedComputer m_mc = null;
public static ManagedComputer Mc
get
return m_mc;
private set
m_mc = value;
static void Main( string[] args )
String _s = "";
if ( !CommonCls.AppInit("en-US" , true ) )
return;
_s = "Test of the default constructor of ManagedComputer";
Console.WriteLine(_s);
CommonCls.AppWriteLog(true , _s);
m_mc = new ManagedComputer();
_s = String.Format("Name of the ManagedComputer : {0}" , m_mc.Name );
Console.WriteLine(_s);
CommonCls.AppWriteLog(false , _s);
_s = String.Format(" - {0} ClientProtocols" , CommonCls.Int32ToString( m_mc.ClientProtocols.Count , 5 ));
Console.WriteLine(_s);
CommonCls.AppWriteLog(false , _s );
_s = String.Format(" - {0} ServerAliases" , CommonCls.Int32ToString( m_mc.ServerAliases.Count , 5 ) );
Console.WriteLine(_s);
CommonCls.AppWriteLog(false , _s);
_s = String.Format( " - {0} ServerInstances" , CommonCls.Int32ToString( m_mc.ServerInstances.Count , 5 ) );
Console.WriteLine(_s);
CommonCls.AppWriteLog(false,_s);
foreach ( ServerInstance _serverinstance in Mc.ServerInstances )
_s = String.Format(" - Instance : {0}" , _serverinstance.Name );
Console.WriteLine(_s);
CommonCls.AppWriteLog(false,_s);
_s = String.Format( " - {0} Services" , CommonCls.Int32ToString( m_mc.Services.Count , 5 ) );
Console.WriteLine(_s);
CommonCls.AppWriteLog(false,_s);
_s = "List of the available services : ";
Console.WriteLine(_s);
CommonCls.AppWriteLog(false,_s);
foreach ( Service _service in Mc.Services )
_s = " - Service : " + _service.Name;
Console.WriteLine(_s);
CommonCls.AppWriteLog(false,_s);
_s = " - DisplayName : " + _service.DisplayName;
Console.WriteLine(_s);
CommonCls.AppWriteLog(false,_s);
_s = " - ErrorControl : " + _service.ErrorControl.ToString();
Console.WriteLine(_s);
CommonCls.AppWriteLog(false,_s);
_s = " - PathName : " + _service.PathName;
Console.WriteLine(_s);
CommonCls.AppWriteLog(false,_s);
_s = " - ProcessId : " + _service.ProcessId.ToString();
Console.WriteLine(_s);
CommonCls.AppWriteLog(false,_s);
_s = " - ServiceAccount : " + _service.ServiceAccount;
Console.WriteLine(_s);
CommonCls.AppWriteLog(false ,_s);
_s = " - ServiceState : " + _service.ServiceState.ToString();
Console.WriteLine(_s);
CommonCls.AppWriteLog(false,_s);
_s = " - Type : " + _service.Type.ToString();
Console.WriteLine(_s);
CommonCls.AppWriteLog(false,_s);
_s = " - StartMode : " + _service.StartMode.ToString();
Console.WriteLine(_s);
CommonCls.AppWriteLog(false,_s);
EndOfProgram :
CommonCls.AppClose();
I am getting the following results
2014-09-08T20:23:33.1175952+02:00 *** Test of the default constructor of ManagedComputer
Name of the ManagedComputer : USER-PC
- 3 ClientProtocols
- 0 ServerAliases
- 3 ServerInstances
- Instance : EXPRESS_ADV_2014
- Instance : EXPRESSADV2014
- Instance : SQLEXPRESS
- 12 Services
List of the available services :
- Service : MSSQL$EXPRESS_ADV_2014
- DisplayName : SQL Server (EXPRESS_ADV_2014)
- ErrorControl : Normal
- PathName : "F:\Install_SQLServerExpress2014\MSSQL12.EXPRESS_ADV_2014\MSSQL\Binn\sqlservr.exe" -sEXPRESS_ADV_2014
- ProcessId : 1972
- ServiceState : Running
- Type : SqlServer
- StartMode : Auto
- Service : MSSQL$EXPRESSADV2014
- DisplayName : SQL Server (EXPRESSADV2014)
- ErrorControl : Normal
- PathName : "C:\Program Files\Microsoft SQL Server\MSSQL12.EXPRESSADV2014\MSSQL\Binn\sqlservr.exe" -sEXPRESSADV2014
- ProcessId : 0
- ServiceState : Stopped
- Type : SqlServer
- StartMode : Disabled
- Service : MSSQL$SQLEXPRESS
- DisplayName : SQL Server (SQLEXPRESS)
- ErrorControl : Normal
- PathName : "C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS_ADV\MSSQL\Binn\sqlservr.exe" -sSQLEXPRESS
- ProcessId : 356
- ServiceState : Running
- Type : SqlServer
- StartMode : Auto
- Service : MSSQLFDLauncher$EXPRESS_ADV_2014
- DisplayName : SQL Full-text Filter Daemon Launcher (EXPRESS_ADV_2014)
- ErrorControl : Normal
- PathName : "F:\Install_SQLServerExpress2014\MSSQL12.EXPRESS_ADV_2014\MSSQL\Binn\fdlauncher.exe" -s MSSQL12.EXPRESS_ADV_2014
- ProcessId : 1708
- ServiceState : Running
- Type : 9
- StartMode : Manual
- Service : MSSQLFDLauncher$EXPRESSADV2014
- DisplayName : SQL Full-text Filter Daemon Launcher (EXPRESSADV2014)
- ErrorControl : Normal
- PathName : "C:\Program Files\Microsoft SQL Server\MSSQL12.EXPRESSADV2014\MSSQL\Binn\fdlauncher.exe" -s MSSQL12.EXPRESSADV2014
- ProcessId : 0
- ServiceState : Stopped
- Type : 9
- StartMode : Manual
- Service : MSSQLFDLauncher$SQLEXPRESS
- DisplayName : SQL Full-text Filter Daemon Launcher (SQLEXPRESS)
- ErrorControl : Normal
- PathName : "C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS_ADV\MSSQL\Binn\fdlauncher.exe" -s MSSQL11.SQLEXPRESS_ADV
- ProcessId : 3980
- ServiceState : Running
- Type : 9
- StartMode : Manual
- Service : ReportServer$EXPRESSADV2014
- DisplayName : SQL Server Reporting Services (EXPRESSADV2014)
- ErrorControl : Normal
- PathName : "C:\Program Files\Microsoft SQL Server\MSRS12.EXPRESSADV2014\Reporting Services\ReportServer\bin\ReportingServicesService.exe"
- ProcessId : 0
- ServiceState : Stopped
- Type : ReportServer
- StartMode : Auto
- Service : ReportServer$SQLEXPRESS
- DisplayName : SQL Server Reporting Services (SQLEXPRESS)
- ErrorControl : Normal
- PathName : "C:\Program Files\Microsoft SQL Server\MSRS11.SQLEXPRESS_ADV\Reporting Services\ReportServer\bin\ReportingServicesService.exe"
- ProcessId : 2516
- ServiceState : Running
- Type : ReportServer
- StartMode : Auto
- Service : SQLAgent$EXPRESS_ADV_2014
- DisplayName : SQL Server Agent (EXPRESS_ADV_2014)
- ErrorControl : Normal
- PathName : "F:\Install_SQLServerExpress2014\MSSQL12.EXPRESS_ADV_2014\MSSQL\Binn\SQLAGENT.EXE" -i EXPRESS_ADV_2014
- ProcessId : 0
- ServiceState : Stopped
- Type : SqlAgent
- StartMode : Disabled
- Service : SQLAgent$EXPRESSADV2014
- DisplayName : SQL Server Agent (EXPRESSADV2014)
- ErrorControl : Normal
- PathName : "C:\Program Files\Microsoft SQL Server\MSSQL12.EXPRESSADV2014\MSSQL\Binn\SQLAGENT.EXE" -i EXPRESSADV2014
- ProcessId : 0
- ServiceState : Stopped
- Type : SqlAgent
- StartMode : Disabled
- Service : SQLAgent$SQLEXPRESS
- DisplayName : SQL Server Agent (SQLEXPRESS)
- ErrorControl : Normal
- PathName : "C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS_ADV\MSSQL\Binn\SQLAGENT.EXE" -i SQLEXPRESS
- ProcessId : 0
- ServiceState : Stopped
- Type : SqlAgent
- StartMode : Disabled
- Service : SQLBrowser
- DisplayName : SQL Server Browser
- ErrorControl : Normal
- PathName : "C:\Program Files (x86)\Microsoft SQL Server\90\Shared\sqlbrowser.exe"
- ProcessId : 2628
- ServiceState : Running
- Type : SqlBrowser
- StartMode : Auto
CommonCls.AppWriteLog is only a method which has 2 parameters , the 2nd one is the string to write in a application log , the 1st if true , the current datetime is written before the content of the 1st parameter. It is useful to simulate a hardcopy of the screen
, especially when the application is a console one.
I have not tested to write the startup parameters but it was working in a previous application
As you can see , I have 3 instances , 1 SQL Server 2012 and 2 SQL Server 2014 ( but one is "ill" it's why the startup of the SQL Server service is disabled , it will be repaired when I will reinstall W7 or install W8 )
I don't see any reason why you are not seen the 2012 instances except if the version of your assembly is 10 instead 11 ( a little tip :when you are adding a reference , in the box after a browse , you are sorting the names of the
assemblies in the selection box , as the assemblies 2008/2008 R2 are appearing before the assemblies 2012 , it' minimizing the risk of confusion of assemblies and try to increase the visibility of the full path by double-clicking the title of the Path
column , if you don't do that , you should not see the version number included in the path name ).
Don't hesitate to post again for more help or explanations.
Have a nice day
Patrick
Mark Post as helpful if it provides any help.Otherwise,leave it as it is. -
SQL 2012 Failover Cluster to 2014
Hi,
we have recently purchased SQL 2014 std edition with SA (VLSC), one of our guy downloaded SQL 2012 instead of 2014 by mistake and installed as failover cluster. I wanted to ask whether should I upgrade to SQL 2014 or uninstall SQL 2012 and install 2014 fresh.
In 2014, secondary server used for failover support does not need to be separately licensed for sql server as long as it is truly passive and primary SQL server is covered with active SA.
We have installed 2012 in other fashion, 4 cores on primary and 4 cores on secondary, now we just want to assign 8 cores to primary and 8 to secondary to get 2014 benefit. Is it possible using upgrade or a fresh install is required.
I Appreciate inputs from experts.Hello,
You can upgrade the cluster using the instructions provided on the following article.
https://msdn.microsoft.com/en-us/library/ms191295.aspx
I cannot provide you answers about questions related to licensing. For licensing questions, please call Microsoft Licensing at 1-800-426-9400, Monday through Friday,
6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. You can also visit the following site for more information and support on licensing issues:
http://www.microsoft.com/licensing/mla/default.aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Maybe you are looking for
-
Just finished my first Java application. What's next?
Thanks to the kind help from everyone on this forum and some intensive labor for the last couple of months, I've finally given birth to my first Java application. I used Netbeans as my IDE of choice. During the development stages I would run my proje
-
Is it worth it to fix my iBook G4 or Macbook?
I have an iBook G4 that I bought used 3 years ago for 300.00. Recently it started with the "kernal panic" stuff and I took it to a guy who fixes Macs. He determined the cause to be the logic board and quote is 250.00. Then my son gave me his non-w
-
WebLogic Server 10 MP1 Netuix warning
I am using WLS10.1. when i tried to login to admin console getting following messages in stdout. how to avoid these warnings. do i need to add any libraries to avoid these messages? *<May 5, 2009 2:38:38 PM GMT> <Warning> <netuix> <BEA-423420> <Redir
-
HT201472 How to findout lost Iphone.
Hello There... Some one has stolen my Iphone 5 .. Now the number is switched off.. is there any way we could track the mobile with IMEI number... Please note : I don't have Find my Iphone activated. Thanks, Madhu
-
How to Split Capacity Requirement
Dear PP Guru's, We are in discrete manufacturing, there are several operations having capacity requirements say 24 hours . But in actual we do not perform such operations at a go. We carry out operation in partial lots of operation qty. say each lot