MSDTC set up in SQL Server 2008 failover cluster

Hi Guys,
I am in the process of setting up failover cluster using SQL Server 2008 (64Bit) Enterprise on Windows Server 2008 R2 (64Bit) I have completed almost all the works but I got few questions regarding MSDTC configuration whether the MSDTC disk should
be assigned from SAN or it should be local to the disk , Separate disk for each nodes in the cluter or 1 disk to be used across all the servers for MSDTC in windows fail over cluster.
With regards, Gopinath.

Hi Gopinath,
Please review the following similar blogs to get more details about configuring MDTC and pros & cons of different options.
How to Configure Multiple Instances of Distributed Transaction Coordinator (DTC) on a Windows Server Failover Cluster 2008
http://blogs.technet.com/b/askcore/archive/2009/02/18/how-to-configure-multiple-instances-of-distributed-transaction-coordinator-dtc-on-a-windows-server-failover-cluster-2008.aspx
How to configure DTC for SQL Server in a Windows 2008 cluster
http://blogs.msdn.com/b/cindygross/archive/2009/02/22/how-to-configure-dtc-for-sql-server-in-a-windows-2008-cluster.aspx
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Similar Messages

SQL Server 2012 Failover Cluster configuration questions

Hi,
I have few questions on , SQL Server 2012 Failover cluserting pleasse provide suggestions:
1) In SQL Server 2012 is there a configuration for active / passive Failover Cluster installation? If so how is it done? if you could provide any links or articles that would help.
OR
Is this been replaced by Always ON Availability Groups?
2) Also in our environment we have done active/active installation but at a time my understanding is only node has the ownership to the shared storage versus both the nodes, is that correct? If not please provide an explanation?
Any additional information would be valuable in clearing my doubts?
Thank youy
Malini=

Hi malinisethi,
If you install SQL Server in a cluster and configure Active-Passive cluster. In the first node, select “New SQL Server Failover Cluster installation” option , when we are installing Active-Passive cluster, we have to specify one virtual/network name. (Note:
For Active-Active clustering you have specify different network names as per the number of nodes). on the other nodes is similar to installing on the first node except that we have select the Add Node to a SQL Server failover cluster option from the initial
menu. For more information, there is a similar issue about SQL Server 2008 Active-Passive/Active-Active cluster installation, you can review the following article.
http://sqldbpool.com/2009/10/07/sql-server-2008-active-passive-cluster-installation/
About Active/Active SQL Cluster, two clustered SQL Server instance are created in different nodes. Then apply Active /Active configuration of both instance. There is an example about creating an Active/Active SQL Cluster using Hyper-V. you can review the
following article.
http://blogs.msdn.com/b/momalek/archive/2012/04/11/creating-an-active-active-sql-cluster-using-hyper-v-part2-the-clustered-instances.aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Question about updating SQL Server on failover cluster

Hi all,
I would like to better understand the update process of SQL Server (2008 r2) in a failover cluster environment.
In our cluster we have 4 instances of SQL running, where two of them I am able to at anytime stop the instance and update it.
The question is... Applying the latest update, will update forcibly all instances installed on that node, or do I have the ability to choose which instance I want to update?
This way, I could "test" the update process in those two SQL Instances, as described in http://support.microsoft.com/kb/958734 and after finishing I would update the remaining instances.
Please let me know.
Thanks in advance.
Nuno Silva

Hi Nuno,
It's a failover cluster issue, I moved it to SQL Server High Availability and Disaster Recovery. So that you can get better help.
Regards,
Charlie Liao
TechNet Community Support

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

Update SQL Server 2008 R2 CLUSTER To SP1 With TFS 2010

Hi,
I have Cluster SQL Server 2008 R2 configured to store Team Foundation Server 2010 DBs
I want to Update this Cluster to SP1 to support Sharepoint DBs
So i want to see if this update can impact my TFS DBs
Thnx
vote if you think useful

Hello,
I which way is this "Database Design" related, the Topic of this forum?
You can install the SP 1 without any harm to your TFS 2010 database; we host them on SQL Server 2012 and also this work.
But instead of the old SP1 you should go with the last SP 3 for SQL Server 2008 R2.
Olaf Helper
[ Blog] [ Xing] [ MVP]
thank you for your reply
I want to test it in a lab environment
vote if you think useful

SQL Server 2012 Failover Cluster Setup

I have to set up a Lab Test environment for SQL Server 2012 with failover clustering. What are the most cost effective specifications for H\W & S\W. AFAIK Apart of Enterprise edition, Standard edition can support failover clustering for upto
2 nodes with one node in passive mode. Somewhere (Here) I got that it is possible to configure SQL Server failover clustering On SQL
Server 2012 Developer edition. Also Is it possible to use Windows 7 Platform with SQL Server 2012 Developer Edition for configuring Always on Failover Clustering. Although I have researched alot, but puzzled. Seeking for experts advise. Thanks in advance.
Pranshul Gupta

Yes you can configure and install in windows 7.. but make sure you have made all the proper updates as per the microsoft suggestion..
Software and hardware requirments for sql 2012
http://msdn.microsoft.com/en-us/library/ms143506%28SQL.110%29.aspx
http://www.yourdba.com/?p=123
http://resources.arcgis.com/en/help/system-requirements/10.2/index.html#//015100000070000000
Developer Edition..
SQL Server 2012 Developer Edition will continue to be part of the SQL Server 2012 family. The Developer edition provides the same feature set as the Enterprise edition. However, it's licensed per developer and can't be used for production work.
Clustering FAQ's
http://www.brentozar.com/archive/2012/02/introduction-sql-server-clusters/
SQL Server licensing :
http://www.microsoft.com/sqlserver/en/us/future-editions/sql2012-licensing.aspx
http://www.microsoft.com/sqlserver/en/us/get-sql-server/how-to-buy.aspx
Overview and support :
http://msdn.microsoft.com/en-us/library/cc645993.aspx
FCI Failover Cluster Instances (SQL Server)
http://technet.microsoft.com/en-us/library/ms189134.aspx
AlwaysOn Availability Groups (SQL Server) -- AG's
http://technet.microsoft.com/en-us/library/hh510230.aspx
Raju Rasagounder Sr MSSQL DBA

MS SQL Server 2008 Metro Cluster with same subnet

Hi All,
I want to setup SQL 2008 Active / Passive Cluster for OCS 2007 between two Data centers, Both DCs are same location which building 1(DC1) and building 2(DC2).
I am planning to use Hyper-V cluster between two DCs and then create SQL 2008 VMs then create another windows 2008 with SQL clusters.
For the above solution, I need to use ISCSI based EMC VNX-e storages on both DCs and do the replication.
Is there any other better solution to perform? Please help me to provide more infromation.

Hi,
Additional, we recommend that your clustered servers be member servers. If they are, you need an additional server that acts as the domain controller in the domain that contains
your failover cluster.
The related KB:
Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster
http://technet.microsoft.com/en-us/library/cc731844(v=ws.10).aspx
Windows Server 2008 Multi-Site Clustering Technical Decision-Maker White Paper
http://download.microsoft.com/download/3/B/5/3B51A025-7522-4686-AA16-8AE2E536034D/WS2008%20Multi%20Site%20Clustering.doc
Hope this helps.
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.

Windows Server 2008 failover cluster in VirtualBox

Hi,
I'm a Windows NT student and I need help with understanding how to do clustering using multiple Windows 2008 R2 Enterprise servers in VirtualBox 4.3.8. I have a Windows 7 host computer. I was wondering if someone could provide clearly detailed step-by-step
directions (ex. Click this, then click that) on what I need to do prior to clustering, as well as starting the clustering process. Please ask if you need additional information.
Thank You.

I'm sorry. I'm such a noob. Should I have 3 virtual machines, where one is the domain controller and the other 2 are nodes? Or is it ok to just have 2 virtual machines?
It's optional. You just need your both cluster nodes (VMs) belong to the same domain. It can be own domain serviced by your private VM or it can be "external" one. See:
Using Guest Clustering for High Availability
http://technet.microsoft.com/en-us/library/dn440540.aspx
Active Directory domain requirements
Failover clusters require that nodes of the same cluster are members of the same Active Directory domain. However, there is no requirement that a guest cluster belongs to the same Active Directory
domain as the physical hosts on which the virtual machines are running.
Also you'll need some shared storage. See (same URL as above):
Storage options
The following tables lists the storage types that you can use to provide shared storage for a guest cluster.
Storage Type
Description
Shared virtual hard disk
New in Windows Server 2012 R2, you can configure multiple virtual machines to connect to and use a single virtual hard disk (.vhdx) file. Each virtual machine can access the virtual hard disk
just like servers would connect to the same LUN in a storage area network (SAN). For more information, see Deploy a Guest Cluster Using a Shared Virtual
Hard Disk.
Virtual Fibre Channel
Introduced in Windows Server 2012, virtual Fibre Channel enables you to connect virtual machines to LUNs on a Fibre Channel SAN. For more information, see Hyper-V
Virtual Fibre Channel Overview.
iSCSI
The iSCSI initiator inside a virtual machine enables you to connect over the network to an iSCSI target. For more information, see iSCSI
Target Block Storage Overview and the blog post Introduction of iSCSI Target
in Windows Server 2012.
Shared VHDX is out as you don't have proper software (Windows 7 is not supported as a host and Windows 2008 R2 does not support shared VHDX as a guest), virtual Fibre Channel is out as you again don't have Windows Server 2012 R2 (and don't have any FC gear).
So iSCSI is your only choice. Either spawn dedicated Windows (or other OS if you like UNIX) VM with iSCSI stack or use third-party Windows software running on your host. Windows Server 2008 R2 does not have iSCSI target embedded so you can get it here:
MSFT iSCSI Target 3.3 Download
http://www.microsoft.com/en-us/download/details.aspx?id=19867
Good luck and happy clustering :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Applying Service Pack on multiple instance SQL Server 2008 R2 Cluster and Standalone.

Friends,
Its my first time I am applying Service pack to both Standalone and Clustered SQL 2008 R2 servers. I have multiple instances running on both stand alone and Clustered environment. I don't know how to apply pack with multiple instances. Do I need to apply
the service pack each instance one by one or I can just run the pack to each node of cluster and each box of stand alone server? Will I get any multi instance selection option during the installation process so that I can select multiple instances at once??

When installing service pack for multiple instances in a standalone machine, you just run the installer and it lists all the instances eligible for the update. You could do it one by one or do it at the same time. Doing it at the same time saves time and
energy. If you selected multiple instances then you dont have to do anything else.
In case of cluster, if you have multiple instances then you need to be little careful.
Eg: Assume you have a 2 node cluster Node 1 and Node 2. Two instances Instance 1 active on Node 1 and Instance 2 active on Node 2. What I would do in this case is to first failover any one instance to the passive node. Assume I failed over Instance 2 to
Node 1. Now Node 1 is active node for both instance 1 and instance 2 and Node 2 is passive for both instances. At this point I run the service pack on Node 2. Once patching is done, I reboot the node and then failover the instaces one by one to Node
2. At this point both instances 1 and 2 would get upgraded and will be active in Node2. Now Node 1 is passive and so run the update there. Once the service pack is installed, reboot and then fail back Instance 1 back to Node 1. Note: I would also failover
Instance 2 to Node 1 just to confirm that failover works completely after service pack update.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

An error occurred attempting to install SQL Server 2008 Express Service Pack 1

i have Setup application with complete prerequisite requirement package create from Visual Studio 2010 setup application.And yes this setup working fine in windows 7 and windows vista but not working in windows xp service pack 3.and getting error when install "An error occurred attempting to install SQL Server 2008 Express Service Pack 1"Give me solution as soon as possible.I have listed summery.txt and log.txt. please refer it.Summery.txt
===============================================================Component SQL Server 2008 Express has failed to install with the
following error message:
"An error occurred attempting to install SQL Server
2008 Express Service Pack 1."
The following components were successfully
installed:
- Microsoft .NET Framework 4 Client Profile (x86 and
x64)
The following components failed to install:
- SQL Server 2008
Express
See the setup log file located at
'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\install.log' for more
information.Install.log
==========================================================================The following properties have been set:
Property: [AdminUser]
= true {boolean}
Property: [InstallMode] = HomeSite {string}
Property:
[ProcessorArchitecture] = Intel {string}
Property: [VersionNT] = 5.1.3
{version}
Running checks for package 'Windows Installer 3.1', phase
BuildList
The following properties have been set for package 'Windows
Installer 3.1':
Running checks for command
'WindowsInstaller3_1\WindowsInstaller-KB893803-v2-x86.exe'
Result of running
operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsi' and value '3.1':
true
Result of checks for command
'WindowsInstaller3_1\WindowsInstaller-KB893803-v2-x86.exe' is
'Bypass'
'Windows Installer 3.1' RunCheck result: No Install
Needed
Running checks for package 'Microsoft .NET Framework 4 Client Profile
(x86 and x64)', phase BuildList
Reading value 'Version' of registry key
'HKLM\Software\Microsoft\NET Framework Setup\NDP\v4\Client'
Unable to read
registry value
Not setting value for property
'DotNet40Client_TargetVersion'
The following properties have been set for
package 'Microsoft .NET Framework 4 Client Profile (x86 and x64)':
Running
checks for command 'DotNetFX40Client\dotNetFx40_Client_x86_x64.exe'
Result of
running operator 'ValueEqualTo' on property 'InstallMode' and value 'HomeSite':
true
Result of checks for command
'DotNetFX40Client\dotNetFx40_Client_x86_x64.exe' is 'Bypass'
Running checks
for command 'DotNetFX40Client\dotNetFx40_Client_setup.exe'
Result of running
operator 'ValueNotEqualTo' on property 'InstallMode' and value 'HomeSite':
false
Skipping ByPassIf because Property 'DotNet40Client_TargetVersion' was
not defined
Result of running operator 'ValueEqualTo' on property 'AdminUser'
and value 'false': false
Result of running operator 'VersionLessThan' on
property 'VersionNT' and value '5.1.2': false
Result of running operator
'ValueEqualTo' on property 'ProcessorArchitecture' and value 'IA64':
false
Result of checks for command
'DotNetFX40Client\dotNetFx40_Client_setup.exe' is 'Install'
'Microsoft .NET
Framework 4 Client Profile (x86 and x64)' RunCheck result: Install
Needed
Running checks for package 'SQL Server 2008 Express', phase
BuildList
Running external check with command
'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\SqlExpress2008\SqlExpressChk.exe' and
parameters '10.0.1600 1033'
Process exited with code 2
Setting value '2
{int}' for property 'SQLExpressChk'
The following properties have been set
for package 'SQL Server 2008 Express':
Property: [SQLExpressChk] = 2
{int}
Running checks for command
'SqlExpress2008\SQLEXPR32_x86_ENU.EXE'
Result of running operator
'ValueNotExists' on property 'VersionNT': false
Result of running operator
'VersionLessThan' on property 'VersionNT' and value '5.1.2': false
Result of
running operator 'VersionEqualTo' on property 'VersionNT' and value '5.2.0':
false
Result of running operator 'VersionEqualTo' on property 'VersionNT' and
value '5.2.1': false
Result of running operator 'ValueEqualTo' on property
'AdminUser' and value 'false': false
Result of running operator
'ValueEqualTo' on property 'SQLExpressChk' and value '-1': false
Result of
running operator 'ValueEqualTo' on property 'SQLExpressChk' and value '-2':
false
Result of running operator 'ValueEqualTo' on property 'SQLExpressChk'
and value '-3': false
Result of running operator 'ValueEqualTo' on property
'SQLExpressChk' and value '-4': false
Result of running operator
'ValueLessThan' on property 'SQLExpressChk' and value '-4': false
Result of
running operator 'ValueNotEqualTo' on property 'ProcessorArchitecture' and value
'Intel': false
Result of running operator 'ValueNotEqualTo' on property
'SQLExpressChk' and value '1': true
Result of checks for command
'SqlExpress2008\SQLEXPR32_x86_ENU.EXE' is 'Bypass'
Running checks for command
'SqlExpress2008\SQLEXPR32_x86_ENU.EXE'
Result of running operator
'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'Intel':
false
Result of running operator 'ValueNotEqualTo' on property
'SQLExpressChk' and value '2': false
Result of checks for command
'SqlExpress2008\SQLEXPR32_x86_ENU.EXE' is 'Install'
Running checks for
command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE'
Result of running operator
'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'amd64':
true
Result of checks for command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE' is
'Bypass'
Running checks for command
'SqlExpress2008\SQLEXPR_x64_ENU.EXE'
Result of running operator
'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'amd64':
true
Result of checks for command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE' is
'Bypass'
'SQL Server 2008 Express' RunCheck result: Install Needed
EULA
for components 'Microsoft .NET Framework 4 Client Profile (x86 and x64)' was
accepted.
EULA for components 'SQL Server 2008 Express' was
accepted.
Copying files to temporary directory
"C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\"
Downloading files to
"C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\"
(11/15/2014 3:59:51 PM)
Downloading 'DotNetFX40Client\dotNetFx40_Client_setup.exe' from 'http://go.microsoft.com/fwlink/?linkid=182804'
to 'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\'
Download completed at
11/15/2014 3:59:53 PM
Verifying file integrity of
C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\DotNetFX40Client\dotNetFx40_Client_setup.exe
WinVerifyTrust
returned 0
File trusted
(11/15/2014 3:59:53 PM) Downloading
'SqlExpress2008\SQLEXPR32_x86_ENU.EXE' from 'http://go.microsoft.com/fwlink/?LinkID=153228&clcid=0x409'
to 'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\'
Download completed at
11/15/2014 4:00:22 PM
Verifying file integrity of
C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\SqlExpress2008\SQLEXPR32_x86_ENU.EXE
WinVerifyTrust
returned 0
File trusted
Running checks for package 'Microsoft .NET
Framework 4 Client Profile (x86 and x64)', phase BeforePackage
Reading value
'Version' of registry key 'HKLM\Software\Microsoft\NET Framework
Setup\NDP\v4\Client'
Unable to read registry value
Not setting value for
property 'DotNet40Client_TargetVersion'
The following properties have been
set for package 'Microsoft .NET Framework 4 Client Profile (x86 and
x64)':
Running checks for command
'DotNetFX40Client\dotNetFx40_Client_setup.exe'
Result of running operator
'ValueNotEqualTo' on property 'InstallMode' and value 'HomeSite':
false
Skipping ByPassIf because Property 'DotNet40Client_TargetVersion' was
not defined
Result of running operator 'ValueEqualTo' on property 'AdminUser'
and value 'false': false
Result of running operator 'VersionLessThan' on
property 'VersionNT' and value '5.1.2': false
Result of running operator
'ValueEqualTo' on property 'ProcessorArchitecture' and value 'IA64':
false
Result of checks for command
'DotNetFX40Client\dotNetFx40_Client_setup.exe' is 'Install'
'Microsoft .NET
Framework 4 Client Profile (x86 and x64)' RunCheck result: Install
Needed
Verifying file integrity of
C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\DotNetFX40Client\dotNetFx40_Client_setup.exe
WinVerifyTrust
returned 0
File trusted
Installing using command
'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\DotNetFX40Client\dotNetFx40_Client_setup.exe'
and parameters ' /q /norestart /ChainingPackage ClientX64ClickOnce /lcid
1033'
Process exited with code 0
Running checks for package 'Microsoft
.NET Framework 4 Client Profile (x86 and x64)', phase AfterPackage
Reading
value 'Version' of registry key 'HKLM\Software\Microsoft\NET Framework
Setup\NDP\v4\Client'
Read string value '4.0.30319'
Setting value
'4.0.30319 {string}' for property 'DotNet40Client_TargetVersion'
The
following properties have been set for package 'Microsoft .NET Framework 4
Client Profile (x86 and x64)':
Property: [DotNet40Client_TargetVersion] =
4.0.30319 {string}
Running checks for command
'DotNetFX40Client\dotNetFx40_Client_setup.exe'
Result of running operator
'ValueNotEqualTo' on property 'InstallMode' and value 'HomeSite':
false
Result of running operator 'VersionGreaterThanOrEqualTo' on property
'DotNet40Client_TargetVersion' and value '4.0.30129': true
Result of checks
for command 'DotNetFX40Client\dotNetFx40_Client_setup.exe' is
'Bypass'
'Microsoft .NET Framework 4 Client Profile (x86 and x64)' RunCheck
result: Install Succeeded
Running checks for package 'SQL Server 2008
Express', phase BeforePackage
Running external check with command
'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\SqlExpress2008\SqlExpressChk.exe' and
parameters '10.0.1600 1033'
Process exited with code 2
Setting value '2
{int}' for property 'SQLExpressChk'
The following properties have been set
for package 'SQL Server 2008 Express':
Property: [SQLExpressChk] = 2
{int}
Running checks for command
'SqlExpress2008\SQLEXPR32_x86_ENU.EXE'
Result of running operator
'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'Intel':
false
Result of running operator 'ValueNotEqualTo' on property
'SQLExpressChk' and value '2': false
Result of checks for command
'SqlExpress2008\SQLEXPR32_x86_ENU.EXE' is 'Install'
'SQL Server 2008 Express'
RunCheck result: Install Needed
Verifying file integrity of
C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\SqlExpress2008\SQLEXPR32_x86_ENU.EXE
WinVerifyTrust
returned 0
File trusted
Installing using command
'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\SqlExpress2008\SQLEXPR32_x86_ENU.EXE'
and parameters '/q /hideconsole /action=Upgrade /instancename=SQLEXPRESS
/skiprules=RebootRequiredCheck'
Process exited with code
-2068578302
Status of package 'Microsoft .NET Framework 4 Client Profile (x86
and x64)' after install is 'InstallSucceeded'
Status of package 'SQL Server
2008 Express' after install is 'InstallFailed'
S S Manne

Hi Manne,
As your description, you come across an error when trying to install SQL Server 2008 express Service Pack 1 on windows XP Service Pack 3 machine. From your error log, I get the error(unable to read registry value). As my analysis, the issue could be due
to that your account doesn't have access to registry. Below are the recommendations for troubleshooting the issue.
1. Make sure that you log in as an administrator of the machine.
2. Please follow the steps below to make sure that you have granted the right permission to registry.
a. Located HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server in registry.
b. Right click and go to Permission, then you could see user accounts or groups. If your user account is not in the list, you could click Add to add your account there.
c. Select your account and Click on Advance.
d. Check on both check box ('Include inheritable permissions from this object's parent'.
and 'Replace all child object permissions with inheritable permissions from this object'), click OK.
e. Click OK again.
Regards,
Michelle Li

Is ODI compatible with Microsoft SQL Server 2008??

Hi,
We are trying to set ODI for SQL Server 2008 but we are getting an error: "connection failed". I do not know if the problem is the driver or the incompatibility between ODI and SQL Server 2008.
Does someone use them together? Are compatible?
If the response is yes, where is the problem? We are using the following JDBC driver:
com.microsoft.jdbc.sqlserver.SQLServerDriver
jdbc:microsoft:sqlserver://<host>:<port>
And we have download the sqljdbc_2.0 driver.
Thank you very much,
Araitz.-

Hi Araitz,
I have ODI Connecting to a Master and Work Repository on SQL Server 2008
Couple of things:
- Have you put the JDBC driver in the drivers folder of you ODI installation?
- In terms of the connection strings, your driver name seems OK; This is the string I have for my URL - jdbc:sqlserver://localhost:1433;databaseName=odimaster; IntegratedSecurity=false
For the user name and password, put those in the connection area. By using IntegratedSecurity=false, you are forcing the password to be picked up from the connection area and not trying to use your AD credentials
Note - The connection string contains odimaster (this is for our ODI Designer login)
Hope this helps.
Best Regards,
geeo

SQL Server 2008 Express -- Process exited with code -2068643839

When installing SQL Server 2008 Express, I continue to get the following info in the install log. I notice that I only get this issue with 64-bit PC's (win 7 & win 8.1). Ideas?
Thanks.
The following components failed to install:
- SQL Server 2008 Express
See the setup log file located at 'C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\install.log' for more information.
The following properties have been set:
Property: [AdminUser] = true {boolean}
Property: [InstallMode] = SameSite {string}
Property: [ProcessorArchitecture] = AMD64 {string}
Property: [VersionNT] = 6.1.0 {version}
Running checks for package 'Windows Installer 3.1', phase BuildList
The following properties have been set for package 'Windows Installer 3.1':
Running checks for command 'WindowsInstaller3_1\WindowsInstaller-KB893803-v2-x86.exe'
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsi' and value '3.1': true
Result of checks for command 'WindowsInstaller3_1\WindowsInstaller-KB893803-v2-x86.exe' is 'Bypass'
'Windows Installer 3.1' RunCheck result: No Install Needed
Running checks for package 'SyncSDK', phase BuildList
The following properties have been set for package 'SyncSDK':
Running checks for command 'SynSDK\syncsdk-v2.1-x86-enu.msi'
Result of checks for command 'SynSDK\syncsdk-v2.1-x86-enu.msi' is 'Install'
'SyncSDK' RunCheck result: Install Needed
Running checks for package 'Windows Installer 4.5', phase BuildList
Looking up path for special folder 'WindowsFolder'
Running check with folder 'C:\Windows\System32' and file 'msi.dll'
Attempting to find file 'C:\Windows\System32\msi.dll'
File version is '5.0.7601.18637'
Setting value '5.0.7601.18637 {version}' for property 'VersionMsiDll'
The following properties have been set for package 'Windows Installer 4.5':
Property: [VersionMsiDll] = 5.0.7601.18637 {version}
Running checks for command 'WindowsInstaller4_5\WindowsXP-KB942288-v3-x86.exe'
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsi' and value '4.5': true
Result of checks for command 'WindowsInstaller4_5\WindowsXP-KB942288-v3-x86.exe' is 'Bypass'
Running checks for command 'WindowsInstaller4_5\WindowsXP-KB958655-v2-x86-ENU.exe'
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsiDll' and value '4.5.6001.22299': true
Result of checks for command 'WindowsInstaller4_5\WindowsXP-KB958655-v2-x86-ENU.exe' is 'Bypass'
Running checks for command 'WindowsInstaller4_5\WindowsServer2003-KB942288-v4-x86.exe'
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsi' and value '4.5': true
Result of checks for command 'WindowsInstaller4_5\WindowsServer2003-KB942288-v4-x86.exe' is 'Bypass'
Running checks for command 'WindowsInstaller4_5\WindowsServer2003-KB958655-v2-x86-ENU.exe'
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsiDll' and value '4.5.6001.22299': true
Result of checks for command 'WindowsInstaller4_5\WindowsServer2003-KB958655-v2-x86-ENU.exe' is 'Bypass'
Running checks for command 'WindowsInstaller4_5\WindowsServer2003-KB942288-v4-x64.exe'
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsi' and value '4.5': true
Result of checks for command 'WindowsInstaller4_5\WindowsServer2003-KB942288-v4-x64.exe' is 'Bypass'
Running checks for command 'WindowsInstaller4_5\WindowsServer2003.WindowsXP-KB958655-v2-x64-ENU.exe'
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsiDll' and value '4.5.6001.22299': true
Result of checks for command 'WindowsInstaller4_5\WindowsServer2003.WindowsXP-KB958655-v2-x64-ENU.exe' is 'Bypass'
Running checks for command 'WindowsInstaller4_5\Windows6.0-KB958655-v2-x86.MSU'
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsiDll' and value '4.5.6001.22308': true
Result of checks for command 'WindowsInstaller4_5\Windows6.0-KB958655-v2-x86.MSU' is 'Bypass'
Running checks for command 'WindowsInstaller4_5\Windows6.0-KB958655-v2-x64.MSU'
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsiDll' and value '4.5.6001.22308': true
Result of checks for command 'WindowsInstaller4_5\Windows6.0-KB958655-v2-x64.MSU' is 'Bypass'
'Windows Installer 4.5' RunCheck result: No Install Needed
Running checks for package 'Microsoft .NET Framework 4 (x86 and x64)', phase BuildList
Reading value 'Version' of registry key 'HKLM\Software\Microsoft\NET Framework Setup\NDP\v4\Full'
Read string value '4.5.50938'
Setting value '4.5.50938 {string}' for property 'DotNet40Full_TargetVersion'
The following properties have been set for package 'Microsoft .NET Framework 4 (x86 and x64)':
Property: [DotNet40Full_TargetVersion] = 4.5.50938 {string}
Running checks for command 'DotNetFX40\dotNetFx40_Full_x86_x64.exe'
Result of running operator 'ValueEqualTo' on property 'InstallMode' and value 'HomeSite': false
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'DotNet40Full_TargetVersion' and value '4.0.30129': true
Result of checks for command 'DotNetFX40\dotNetFx40_Full_x86_x64.exe' is 'Bypass'
Running checks for command 'DotNetFX40\dotNetFx40_Full_setup.exe'
Result of running operator 'ValueNotEqualTo' on property 'InstallMode' and value 'HomeSite': true
Result of checks for command 'DotNetFX40\dotNetFx40_Full_setup.exe' is 'Bypass'
'Microsoft .NET Framework 4 (x86 and x64)' RunCheck result: No Install Needed
Running checks for package 'Microsoft .NET Framework 4 Client Profile (x86 and x64)', phase BuildList
Reading value 'Version' of registry key 'HKLM\Software\Microsoft\NET Framework Setup\NDP\v4\Client'
Read string value '4.5.50938'
Setting value '4.5.50938 {string}' for property 'DotNet40Client_TargetVersion'
The following properties have been set for package 'Microsoft .NET Framework 4 Client Profile (x86 and x64)':
Property: [DotNet40Client_TargetVersion] = 4.5.50938 {string}
Running checks for command 'DotNetFX40Client\dotNetFx40_Client_x86_x64.exe'
Result of running operator 'ValueEqualTo' on property 'InstallMode' and value 'HomeSite': false
Result of running operator 'VersionGreaterThanOrEqualTo' on property 'DotNet40Client_TargetVersion' and value '4.0.30129': true
Result of checks for command 'DotNetFX40Client\dotNetFx40_Client_x86_x64.exe' is 'Bypass'
Running checks for command 'DotNetFX40Client\dotNetFx40_Client_setup.exe'
Result of running operator 'ValueNotEqualTo' on property 'InstallMode' and value 'HomeSite': true
Result of checks for command 'DotNetFX40Client\dotNetFx40_Client_setup.exe' is 'Bypass'
'Microsoft .NET Framework 4 Client Profile (x86 and x64)' RunCheck result: No Install Needed
Running checks for package 'SQL Server 2008 Express', phase BuildList
Running external check with command 'C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\SqlExpress2008\SqlExpressChk.exe' and parameters '10.0.1600 1033'
Process exited with code 1
Setting value '1 {int}' for property 'SQLExpressChk'
The following properties have been set for package 'SQL Server 2008 Express':
Property: [SQLExpressChk] = 1 {int}
Running checks for command 'SqlExpress2008\SQLEXPR32_x86_ENU.EXE'
Result of running operator 'ValueNotExists' on property 'VersionNT': false
Result of running operator 'VersionLessThan' on property 'VersionNT' and value '5.1.2': false
Result of running operator 'VersionEqualTo' on property 'VersionNT' and value '5.2.0': false
Result of running operator 'VersionEqualTo' on property 'VersionNT' and value '5.2.1': false
Result of running operator 'ValueEqualTo' on property 'AdminUser' and value 'false': false
Result of running operator 'ValueEqualTo' on property 'SQLExpressChk' and value '-1': false
Result of running operator 'ValueEqualTo' on property 'SQLExpressChk' and value '-2': false
Result of running operator 'ValueEqualTo' on property 'SQLExpressChk' and value '-3': false
Result of running operator 'ValueEqualTo' on property 'SQLExpressChk' and value '-4': false
Result of running operator 'ValueLessThan' on property 'SQLExpressChk' and value '-4': false
Result of running operator 'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'Intel': true
Result of checks for command 'SqlExpress2008\SQLEXPR32_x86_ENU.EXE' is 'Bypass'
Running checks for command 'SqlExpress2008\SQLEXPR32_x86_ENU.EXE'
Result of running operator 'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'Intel': true
Result of checks for command 'SqlExpress2008\SQLEXPR32_x86_ENU.EXE' is 'Bypass'
Running checks for command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE'
Result of running operator 'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'amd64': false
Result of running operator 'ValueNotEqualTo' on property 'SQLExpressChk' and value '1': false
Result of checks for command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE' is 'Install'
Running checks for command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE'
Result of running operator 'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'amd64': false
Result of running operator 'ValueNotEqualTo' on property 'SQLExpressChk' and value '2': true
Result of checks for command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE' is 'Bypass'
'SQL Server 2008 Express' RunCheck result: Install Needed
EULA for components 'SQL Server 2008 Express' was accepted.
Installation of components 'SyncSDK' was accepted.
Copying files to temporary directory "C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\"
Copying from 'C:\Installs\NewMBA\SynSDK\syncsdk-v2.1-x86-enu.msi' to 'C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\SynSDK\syncsdk-v2.1-x86-enu.msi'
Verifying file integrity of C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\SynSDK\syncsdk-v2.1-x86-enu.msi
WinVerifyTrust returned 0
File trusted
Copying from 'C:\Installs\NewMBA\SqlExpress2008\SQLEXPR_x64_ENU.EXE' to 'C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\SqlExpress2008\SQLEXPR_x64_ENU.EXE'
Verifying file integrity of C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\SqlExpress2008\SQLEXPR_x64_ENU.EXE
WinVerifyTrust returned 0
File trusted
Running checks for package 'SyncSDK', phase BeforePackage
The following properties have been set for package 'SyncSDK':
Running checks for command 'SynSDK\syncsdk-v2.1-x86-enu.msi'
Result of checks for command 'SynSDK\syncsdk-v2.1-x86-enu.msi' is 'Install'
'SyncSDK' RunCheck result: Install Needed
Verifying file integrity of C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\SynSDK\syncsdk-v2.1-x86-enu.msi
WinVerifyTrust returned 0
File trusted
Installing using command 'C:\Windows\SysWOW64\msiexec.exe' and parameters ' -I "C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\SynSDK\syncsdk-v2.1-x86-enu.msi" -q '
Will attempt to elevate process.
Process exited with code 0
Running checks for package 'SyncSDK', phase AfterPackage
The following properties have been set for package 'SyncSDK':
Running checks for command 'SynSDK\syncsdk-v2.1-x86-enu.msi'
Result of checks for command 'SynSDK\syncsdk-v2.1-x86-enu.msi' is 'Install'
'SyncSDK' RunCheck result: Unknown
Running checks for package 'SQL Server 2008 Express', phase BeforePackage
Running external check with command 'C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\SqlExpress2008\SqlExpressChk.exe' and parameters '10.0.1600 1033'
Process exited with code 1
Setting value '1 {int}' for property 'SQLExpressChk'
The following properties have been set for package 'SQL Server 2008 Express':
Property: [SQLExpressChk] = 1 {int}
Running checks for command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE'
Result of running operator 'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'amd64': false
Result of running operator 'ValueNotEqualTo' on property 'SQLExpressChk' and value '1': false
Result of checks for command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE' is 'Install'
'SQL Server 2008 Express' RunCheck result: Install Needed
Verifying file integrity of C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\SqlExpress2008\SQLEXPR_x64_ENU.EXE
WinVerifyTrust returned 0
File trusted
Installing using command 'C:\Users\Roy\AppData\Local\Temp\VSDE1F7.tmp\SqlExpress2008\SQLEXPR_x64_ENU.EXE' and parameters '/q /hideconsole /action=Install /features=SQL /instancename=SQLEXPRESS /enableranu=1 /sqlsvcaccount="NT Authority\Network
Service" /AddCurrentUserAsSqlAdmin /skiprules=RebootRequiredCheck'
Process exited with code -2068643839
Status of package 'SyncSDK' after install is 'InstallUnknown'
Status of package 'SQL Server 2008 Express' after install is 'InstallFailed'

The SP3 patch installed ok.
When I ran my software installer, it failed again w/ the error 1001.
Here is the summary.txt.
Overall summary:
Final result:                  Passed
Exit code (Decimal):           0
Exit message:                  Passed
Start time:                    2015-01-20 19:26:40
End time:                      2015-01-20 19:37:08
Requested action:              Patch
Instance MSSQLSERVER overall summary:
Final result:                  Passed
Exit code (Decimal):           0
Exit message:                  Passed
Start time:                    2015-01-20 19:31:48
End time:                      2015-01-20 19:34:52
Requested action:              Patch
Instance MBA overall summary:
Final result:                  Passed
Exit code (Decimal):           0
Exit message:                  Passed
Start time:                    2015-01-20 19:34:57
End time:                      2015-01-20 19:36:17
Requested action:              Patch
Instance MBANEW overall summary:
Final result:                  Passed
Exit code (Decimal):           0
Exit message:                  Passed
Start time:                    2015-01-20 19:36:21
End time:                      2015-01-20 19:37:01
Requested action:              Patch
Machine Properties:
Machine name:                  JOHN
Machine processor count:       4
OS version:                    Windows Vista
OS service pack:
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
Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             Database Engine Services
1033                 Express Edition      10.1.2531.0     No
Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             SQL Server Replication
1033                 Express Edition      10.1.2531.0     No
Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Database Engine Services
1033                 Express Edition      10.3.5500.0     No
Sql Server 2008      MBA                  MSSQL10.MBA
Database Engine Services                 1033                 Express Edition
10.3.5500.0     No
Sql Server 2008      MBANEW               MSSQL10.MBANEW                 Database
Engine Services                 1033                 Express Edition
10.3.5500.0     No
Package properties:
Description:                   SQL Server Database Services 2008
SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName:                   SQL2008
Type:                          RTM
Version:                       10
SPLevel:                       3
KBArticle:                     KB2977321
KBArticleHyperlink:
PatchType:                     GDR
AssociatedHotfixBuild:         5869
Platform:                      x64
PatchLevel:                    10.3.5520.0
ProductVersion:                10.3.5500.00
GDRReservedRange:              10.0.1000.0:10.0.1099.0;10.0.3000.0:10.0.3099.0;10.0.4010.0:10.0.4250.0;10.0.5501.0:10.0.5750.0
PackageName:                   SQLServer2008-KB2977321-x64.exe
Installation location:         c:\adcd5df38e670a98a9f2aafcc70e\x64\setup\
Updated product edition:
Instance             Edition
MSSQLSERVER          EXPRESS
MBA                  EXPRESS
MBANEW               EXPRESS
User Input Settings:
ACTION:                        Patch
ALLINSTANCES:                  False
CLUSTERPASSIVE:                False
CONFIGURATIONFILE:
HELP:                          False
INDICATEPROGRESS:              False
INSTANCENAME:                  <empty>
QUIET:                         False
QUIETSIMPLE:                   False
X86:                           False
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150120_192631\SystemConfigurationCheck_Report.htm

Sql server 2008 standard edition cluster adding 3rd node

we have a 2 node active passive sql server 2008 r2 cluster. We plan to add a third node on temp basis to the cluster. As one old nodes will be removed. As standard edition of sql support 2 nodes, can we add third node to it ??

Hi,
There is no way to add a 3rd node without doing an EDITION UPGRADE from Standard to Enterprise. It is by design.
Microsoft SQL Server 2008 R2 Standard Edition supports up to two nodes in a failover cluster.
Check out the following MSDN article for more information:
Features Supported by the Editions of SQL Server 2008 R2
http://msdn.microsoft.com/en-us/library/cc645993(v=sql.105).ASPX
Thanks.
Tracy Cai
TechNet Community Support

MS DTC not coming online on SQL Server 2008 R2 failover cluster

Dear Experts,
On a SQL Server 2008 R2 failover cluster, MS DTC cluster service is not coming online. It fails with below error message.
"The DTC cluster resource's log file path was originally configured at: E:. Attempting to change that to: M:. This indicates a change in the path of the DTC cluster resource's dependent disk resource. This is not supported. The error code
returned: 0x8000FFFF".
From the Component Services, we can see under the clustered DTCs, in the properties of the log file that it is configured for E drive. The 'Transaction list' and 'Transaction Statistics' are empty. When I try to change the log file path to
point to M drive I get this warning message.
"An MSDTC log file already exists in the selected directory. Resetting an existing MS DTC log file may cause your databases and other transactional resource managers to become inconistent. Please review the MSDTC Administrator's manual before
proceeding. Do you wish to reset the existing MS DTC log"
Could you please advise if this is safe to proceed with this warning as the 'Transaction list' and 'Transaction Statistics' are empty or would it cause any other issue.
Thanks,
MM

Tauseef
Did you tried using wmi....win32_share
$path = "location where to create the folder"
$share = $Shares=[WMICLASS]'WIN32_Share' # class in wmi for share
$Sharename = 'Sharename'
New-Item -type directory -Path $Path
$Shares.Create($Path,$Sharename,0,255,$Sharename)
$Acl = Get-Acl $Path # cmdlet for getting access control list
$Access = New-Object system.security.accesscontrol.filesystemaccessrule("Username","FullControl","ContainerInherit, ObjectInherit", "None", "Allow")
$Acl.AddAccessRule($Access)
Set-Acl $Path $Acl
Thanks Azam When you see answers please Mark as Answer if Helpful..vote as helpful.

Error on setup failover cluster with Windows 2008 R2 enterprise and SQL Server 2008 R2 (also with SP1)

Hi!
The setup process fails with this error:
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
I have found some hints by google, but nothing really helpfull.
Has anyone had a simular problem when installing SQL server 2008 R2?
All posts I found are about sql server 2008 (no R2!).
The cluster itself is working (storage, network, msdtc, quorum...).
Any hints?
Andreas
Here is the complete log:
Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2067791871
Exit facility code:            1216
Exit error code:               1
Exit message:                  Failed: see details below
Start time:                    2012-04-06 11:23:57
End time:                      2012-04-06 12:01:21
Requested action:              InstallFailoverCluster
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.2500.0%26EvtType%3d0x625969A3%400x294A9FD9
Cluster properties:
Machine name: OC-SQLCL02ND01
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Machine name: OC-SQLCL02ND02
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Machine Properties:
Machine name:                  OC-SQLCL02ND01
Machine processor count:       32
OS version:                    Windows Server 2008 R2
OS service pack:               Service Pack 1
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  Yes
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:\x64\setup\
Installation edition:          STANDARD
Slipstream:                    True
SP Level                       1
User Input Settings:
ACTION:                        InstallFailoverCluster
AGTDOMAINGROUP:                <empty>
AGTSVCACCOUNT:                 MANAGEMENT\sqladmin
AGTSVCPASSWORD:                *****
ASBACKUPDIR:                   S:\OLAP\Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   S:\OLAP\Config
ASDATADIR:                     S:\OLAP\Data
ASDOMAINGROUP:                 <empty>
ASLOGDIR:                      S:\OLAP\Log
ASPROVIDERMSOLAP:              1
ASSVCACCOUNT:                  MANAGEMENT\sqladmin
ASSVCPASSWORD:                 *****
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            MANAGEMENT\administrator
ASTEMPDIR:                     S:\OLAP\Temp
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\ConfigurationFile.ini
CUSOURCE:
ENU:                           True
ERRORREPORTING:                False
FAILOVERCLUSTERDISKS:          Cluster Disk 3,Cluster Disk 4,Cluster Disk 5
FAILOVERCLUSTERGROUP:          SQL Server (MSSQLSERVER)
FAILOVERCLUSTERIPADDRESSES:    IPv4;172.29.2.122;Cluster Network 2;255.255.255.0,IPv4;172.29.3.122;Cluster Network 3;255.255.255.0
FAILOVERCLUSTERNETWORKNAME:    CLUSTER02
FARMACCOUNT:                   <empty>
FARMADMINPORT:                 0
FARMPASSWORD:                  *****
FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SSMS,ADV_SSMS
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD:                 *****
HELP:                          False
INDICATEPROGRESS:              False
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR:             S:\
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    MSSQLSERVER
INSTANCENAME:                  MSSQLSERVER
ISSVCACCOUNT:                  NT AUTHORITY\SYSTEM
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
PASSPHRASE:                    *****
PCUSOURCE:                     d:\install\mssql\sp1
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
RSINSTALLMODE:                 FilesOnlyMode
RSSVCACCOUNT:                  MANAGEMENT\sqladmin
RSSVCPASSWORD:                 *****
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  SQL
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLDOMAINGROUP:                <empty>
SQLSVCACCOUNT:                 MANAGEMENT\sqladmin
SQLSVCPASSWORD:                *****
SQLSYSADMINACCOUNTS:           MANAGEMENT\administrator
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               L:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
SQLUSERDBDIR:                  T:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
SQLUSERDBLOGDIR:               L:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
SQMREPORTING:                  False
UIMODE:                        Normal
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Feature:                       Full-Text Search
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Feature:                       Analysis Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Reporting Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Integration Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Connectivity
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Complete
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Backwards Compatibility
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Business Intelligence Development Studio
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\SystemConfigurationCheck_Report.htm

Hi Andreas Plachy,
Please make sure that the Virtual Server Name ‘CLUSTER02’ is unique on the network. In addition, are there any resources named ‘SQL Server’ on the Windows cluster? If that is the case, you may need to rename the related resources to avoid conflicting with
SQL Server, and try again.
Stephanie Lv
TechNet Community Support

MSDTC set up in SQL Server 2008 failover cluster

Similar Messages

Maybe you are looking for