Hyper-V guest SQL 2012 cluster live migration failure

I have two IBM HX5 nodes connected to IBM DS5300. Hyper-V 2012 cluster was built on blades. In HV cluster was made six virtual machines, connected to DS5300 via HV Virtual SAN. These VMs was formed a guest SQL Cluster. Databases' files are placed on
DS5300 storage and available through VM FibreChannel Adapters. IBM MPIO Module is installed on all hosts and VMs.
SQL Server instances work without problem. But! When I try to live migrate SQL VM to another HV node an SQL Instance fails. In SQL error log I see:
2013-06-19 10:39:44.07 spid1s      Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.07 spid1s      SQLServerLogMgr::LogWriter: Operating system error 170(The requested resource is in use.) encountered.
2013-06-19 10:39:44.07 spid1s      Write error during log flush.
2013-06-19 10:39:44.07 spid55      Error: 9001, Severity: 21, State: 4.
2013-06-19 10:39:44.07 spid55      The log for database 'Admin' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
2013-06-19 10:39:44.07 spid55      Database Admin was shutdown due to error 9001 in routine 'XdesRMFull::CommitInternal'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.
2013-06-19 10:39:44.31 spid36s     Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.31 spid36s     fcb::close-flush: Operating system error (null) encountered.
2013-06-19 10:39:44.31 spid36s     Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.31 spid36s     fcb::close-flush: Operating system error (null) encountered.
2013-06-19 10:39:44.32 spid36s     Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.32 spid36s     fcb::close-flush: Operating system error (null) encountered.
2013-06-19 10:39:44.32 spid36s     Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.32 spid36s     fcb::close-flush: Operating system error (null) encountered.
2013-06-19 10:39:44.33 spid36s     Starting up database 'Admin'.
2013-06-19 10:39:44.58 spid36s     349 transactions rolled forward in database 'Admin' (6:0). This is an informational message only. No user action is required.
2013-06-19 10:39:44.58 spid36s     SQLServerLogMgr::FixupLogTail (failure): alignBuf 0x000000001A75D000, writeSize 0x400, filePos 0x156adc00
2013-06-19 10:39:44.58 spid36s     blankSize 0x3c0000, blkOffset 0x1056e, fileSeqNo 1313, totBytesWritten 0x0
2013-06-19 10:39:44.58 spid36s     fcb status 0x42, handle 0x0000000000000BC0, size 262144 pages
2013-06-19 10:39:44.58 spid36s     Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.58 spid36s     SQLServerLogMgr::FixupLogTail: Operating system error 170(The requested resource is in use.) encountered.
2013-06-19 10:39:44.58 spid36s     Error: 5159, Severity: 24, State: 13.
2013-06-19 10:39:44.58 spid36s     Operating system error 170(The requested resource is in use.) on file "v:\MSSQL\log\Admin\Log.ldf" during FixupLogTail.
2013-06-19 10:39:44.58 spid36s     Error: 3414, Severity: 21, State: 1.
2013-06-19 10:39:44.58 spid36s     An error occurred during recovery, preventing the database 'Admin' (6:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected,
contact Technical Support.
In windows system log I see a lot of warnings like this:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider
Name="Microsoft-Windows-Ntfs" Guid="{3FF37A1C-A68D-4D6E-8C9B-F79E8B16C482}" />
<EventID>140</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000008</Keywords>
<TimeCreated
SystemTime="2013-06-19T06:39:44.314400200Z" />
<EventRecordID>25239</EventRecordID>
<Correlation
/>
<Execution
ProcessID="4620" ThreadID="4284" />
<Channel>System</Channel>
<Computer>sql-node-5.local.net</Computer>
<Security
UserID="S-1-5-21-796845957-515967899-725345543-17066" />
</System>
- <EventData>
<Data Name="VolumeId">\\?\Volume{752f0849-6201-48e9-8821-7db897a10305}</Data>
<Data Name="DeviceName">\Device\HarddiskVolume70</Data>
<Data Name="Error">0x80000011</Data>
</EventData>
</Event>
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \\?\Volume{752f0849-6201-48e9-8821-7db897a10305}, DeviceName: \Device\HarddiskVolume70.
({Device Busy}
The device is currently busy.)
There aren't any error or warning in HV hosts.

Hello,
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Regards,
Fanny Liu
If you have any feedback on our support, please click
here.
Fanny Liu
TechNet Community Support

Similar Messages

Adding existing SQL Server 2012 to a New SQL 2012 Cluster

We currently have a SQL 20012 Server setup and running on our domain. We would like to switch this to a clustered environment. Is it possible to setup the new SQL 2012 Cluster and add the existing SQL 2012 server as a node in the cluster
without losing any functionality. All servers will be built with same drive letter.

We currently have a SQL 20012 Server setup and running on our domain. We would like to switch this to a clustered environment. Is it possible to setup the new SQL 2012 Cluster and add the existing SQL 2012 server as a node in the
cluster without losing any functionality. All servers will be built with same drive letter.
No its not possible to convert standalone installation to cluster.Moreover first you need to configure Windows cluster then backup all SQL server databases logins jobs packages and install fresh instance of SQL Server in cluster aware mode
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Sql 2008 r2 cluster side by side with sql 2012 cluster on Windows 2008 R2

We have a SQL 2008R2 active/passive SQL cluster running on Windows 2008 R2 cluster.
I would like to add a SQL 2012 clustered instance to the same Winows 2008 R2 cluster.
Are there any issues involved having a SQL 2008 R2 clustered instance running side by side with a SQL 2012 instance in same Windows 2008 R2 cluster?
Are there any pitfalls/"gotchas" to watch for with SQL 2012 cluster install?
Thank you so much!

Hello,
Two instances, one SQL Server 2008 and the other SQL Server 2012, side-by-side, is fully supported.
I would like to recommend you to assign a different port (not port 1433) to the non-default instance
to avoid an IP address conflict between both instances.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

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

Hyper-v 2012 R2 Live migration issue in 2003 Domain function Level

hi Team ,
i recently build 2012 R2 Hyper-v Cluster with three node. Everrything working fine with out any issue . Cluster working also fine. Later i came across one issue when tried to Live migration virtual machine from one host to another . it failed all the time
while quick migration is working . i gone through few articles and find it is known issue with hyper-v 2012 R2 where domain functional level is set to 2003 . although they have provided Hotfix but no solution.
http://support.microsoft.com/kb/2838043
Please let me know if any one face similar issue and able to resolve by any hotfix. My host are updated .
Thanks
Ravindra
Ravi

Hi Ravi1987,
The KB2838043 is applied for Server 2012 node, Could you offer us the related cluster error event id, or you can refer the following article to check your cluster
network binding order is correct or not.
Configuring Windows Failover Cluster Networks
http://blogs.technet.com/b/askcore/archive/2014/02/20/configuring-windows-failover-cluster-networks.aspx
You can try to install recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters first, then monitor this issue again.
The KB download:
Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
http://support.microsoft.com/kb/2920151
More information:
Windows Server 2008 R2 Live Migration – “The devil may be in the networking details.”
http://blogs.technet.com/b/askcore/archive/2009/12/10/windows-server-2008-r2-live-migration-the-devil-may-be-in-the-networking-details.aspx
I’m glad to be of help to you!

Hyper-V Failover Cluster Live migration over Virtual Adapter

Hello,
Currently we have a test environment 3 HyperHost wich have 2 Nic teams. LAN team and team Live/Mngt.
In Hyper-V we created a Virtual Switch (Wich is Nic team Live/Mngt)
We want to seperate the Mngt and live with Vlans. To do this we created 2 virtual adapters. Mngt and Live, assigned ip adresses and 2 vlans(Mngt 10, Live 20)
Now here is our problem: In Failover cluster you cannot select the Virtual Adapter(live). Only the Virtual Switch wich both are on. Meaning live migration simple uses the vSwitch instead of the Virtual adapter.
Either its not possible to seperate Live migration with a Vlan this way or maybe there are Powershell commands to add Live migration to a Virtual adapter?
Greetings Selmer

It can be done in PowerShell but it's not intuitive.
In Failover Cluster Manager, right-click Networks and you'll find this:
Click Live Migration Settings and you'll find this:
Checked networks are allowed to carry traffic. Networks higher in the list are preferred.
Eric Siron
Altaro Hyper-V Blog
I am an independent blog contributor, not an Altaro employee. I am solely responsible for the content of my posts.

Hyper-V 2012 R2 - live migration dynamic memory issue

Hi..
we use a two node hyper-v cluster.
On each node running 5 vm that shared the 64GB system memory.
The vms are configured to use dynamic memory. The sum of the startup (min) memory of the 10 vms are currently 50 GB.
So now our problem:
If we try to drain roles on node A for maintenance purpose two vms are still on node A because they wasted currently each 25GB memory and so on node B is not enough free memory to host this vms.
That sounds logical
But as all vms configured to use dynamic memory they should shrink their memory to get enough space for all vms? If we shutdown all vms, move it to one node, then everything works fine.
Is it by design that live migration do not trigger the vm to shrink their memory?
Best regards, Alexander Zirbes

Hi Alexander,
Dynamic memory means that memory can increase or decrease based on the demand of the VM, not based on the load of the Hyper-V host. If the gust OS of VM dont need that much memory, memory will be released. I dont think live migration has any role shrinking
the allocated memory of a VM.
Since you are using two node cluster, you should only load 50% resourses on each host so that incase of a failure of second node, the first node can have all the VMs.
This calculation will become more effective if you have more nodes. I am having a six node cluster and I load each host upto 80% so that in case of a single node failure, the VMs can be split on other five nodes without issues.
Cheers,
Shaba
Optimism is the faith that leads to achievement. Nothing can be done without hope and confidence.
InsideVirtualization.com

Server 2012 r2 live migration fails with hardware error

Hello all, we just upgraded one of our hyper v hosts from server 2012 to server 2012 r2; previously we had live replication setup between it and another box on the network which was also running server 2012. After installing server 2012 r2 when a live migration
is attempted we get the message:
"The virtual machine cannot be moved to the destination computer. The hardware on the destination computer is not compatible with the hardware requirements of this virtual machine. Virtual machine migration failed at migration source."
The servers in question are both dell, currently we have a poweredge r910 running server 2012 and a poweredge r900 running server 2012 r2. The section under processor for "migrate to a physical computer using a different processor" is already checked
and this same vm was successfully being live replicated before the upgrade to server 2012 r2. What would have changed around hardware requirements?
We are migrating from server 2012 on the poweredge r910 to server 2012 r2 on the poweredge r900. Also When I say this was an upgrade, we did a full re install and wiped out the installation of server 2012 and installed server 2012 r2, this was not an upgrade
installation.

The only cause I’ve seen so far is virtual switches being named differently. I do remember that one of our VMs didn’t move, but we simply bypassed this problem, using one-time backup (VeeamZIP, more specifically).
If it’s one-time operation you can use the same procedure for the VMs in question -> backup and restore them at new server.
Kind regards, Leonardo.

Hyper-V replica vs Shared Nothing Live Migration

Shared Nothing Live Migration allows to transport your VM over the WAN without shutting it down (how much time it takes on io intensive vm is another story)
  Hyper-V replica does not allow to perform the DR switch without shutdown operation on primary site VM !
why can't it take the VM live to the DR ?
that's because if we use Shared Nothing across the WAN, we don't use the data that Hyper-V replica can and then it also breaks everything hyper-V replica does.
Point is: how to take the VM to DR in running state, what is the best way to do that ?
Shahid Roofi

Hi Shahid,
Hyper-V Replica is designed as a DR technology, not as a technique to move VMs. It assumes that should you require it, the source VM would probably be offline and therefore you would be powering up the passive copy from a previous point in time
as its not a true synchronous replica copy. It does give you the added benefit to be able to run a planned failover which as you say, powers of the VM first, runs a final Sync then powers the new VM up. Obviously you cant have the duplicate copy of this VM
running all the time at the remote site, otherwise you would have a split brain situation for network traffic.
Like the live migration the shared nothing live migration is a technology aimed at moving a VM, but as you know offers the ability to do this without having shared storage and only requires a network connection. When initiated moves the whole
VM, well copies the virtual drive and memory before sending machine writes to both, then only to the new VM when they both match. With regards to the speed, I assume you have the SNLM setup to compress data before sending across the wire?
If you want a true live migration between remote sites, one way would be to have a SAN array between both sites synchronously replicating data, then stretch the Hyper-V cluster across both sites. Obviously this is a very expensive solution but perhaps
the perfect scenario.
Kind Regards
Michael Coutanche
Blog:
Twitter:   LinkedIn:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Time-out issue Always on SQL 2012 Cluster

Currently I'm working on a large deployment of a SharePoint 2013 environment (stretched farm over 2 DC's). We are using a SQL 2012 alwayson multisubnet cluster (each DC has 1 SQL node). During the installation of SharePoint we encountered several connection
time-out errors from the SQL environment. (Exception calling "Open" with "0" argument(s): "Connection Timeout Expired. The timeout period elapsed during the post-login
phase. The connection could have timed out while waiting for server to complete the login process and respond;)
Steps we follow for SharePoint installation are:
Steps to configure SharePoint 2013 on an AlwaysOn Availability group:
1>Create SharePoint databases (with the PowerShell script)
Configure a SQL alias for a consistent SQL instance name.
Create farm on SQL instance/replica 1 (one of the SQL nodes), creating all databases needed (service-apps & web-apps). -->
we are connected directly to 1 SQL node and not connecting to the cluster. Installation server is in same DC as the SQL node.
Stop SharePoint so databases remain static during migration to an AlwaysOn cluster.
2>Move database to AlwaysOn high-availability group.
Restore all the DBs onto SQL replica 2 (with NORECOVERY).
Create AlwaysOn availability group, or use existing
Join the replica 2 databases to availability group.
Create listener.
3>Migrate SharePoint onto AlwaysOn on cluster
Make all SharePoint DB MultiSubnetFailover aware with PowerShell Cmdlet
Reconfigure SQL alias for new listener
àat this point the SharePoint farm is connecting to the SQL cluster (listener of AlwaysOn availability group of the SQL Instance), but we never reached this point so far.
Restart SharePoint services with updated alias.
Event errors and SQL log errors that I found:
Date,Source,Severity,Message,Category,Event,User,Computer
09/18/2014 07:34:59,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPAG_CU8000001105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:34:59,MSSQL$SPAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:34:52,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPWMAG_CU8000002105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:34:52,MSSQL$SPWMAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:34:47,Service Control Manager,Information,The WMI Performance Adapter service entered the running state.,(0),7036,,CU8000000015
09/18/2014 07:32:41,Microsoft-Windows-FailoverClustering,Error,Cluster network name resource 'SPSDAG_CU8000003105' failed registration of one or more associated DNS name(s) for the following reason:<nl/>DNS bad key.<nl/>.<nl/><nl/>Ensure
that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.,(19),1196,NT AUTHORITY\SYSTEM,CU8000000015
09/18/2014 07:32:41,MSSQL$SPSDAG,Information,The Service Broker endpoint is in disabled or stopped state.,(2),9666,,CU8000000015
09/18/2014 07:31:09,PowerShell,Information,Engine state is changed from Available to Stopped. <nl/><nl/>Details: <nl/> NewEngineState=Stopped<nl/> PreviousEngineState=Available<nl/><nl/> SequenceNumber=61464<nl/><nl/> HostName=OpsMgr
PowerShell Host<nl/> HostVersion=7.0.5000.0<nl/> HostId=32012185-8d9a-41c2-be56-91929c02f1e8<nl/> EngineVersion=4.0<nl/> RunspaceId=af176e01-185d-4574-ab9b-0fd745178d29<nl/> PipelineId=<nl/> CommandName=<nl/> CommandType=<nl/> ScriptName=<nl/> CommandPath=<nl/> CommandLine=,(4),403,,CU8000000015
We are not allow to update/write in the DNS for the multisubnet cluster IP registration, so I think that explains the "failed registration
" error. But can this explains our time-out errors during the SharePoint installation? For the installation we are connection directly to 1 SQL node and not to the SQL
cluster.
Any help is appreciated!
Ronald Bruinsma - Independent SharePoint Consultant - iDocs.info - The Netherlands -- Please don't forget to propose this post as an answer or mark it as helpful if it did help you. Thanks.

Don't just change the connection timeout on your SharePoint farm. This will just hide the real issue. From your error message, it seems that the DNS record for the Availability Group listener name is not being written. Talk to your AD administrators to validate
if dynamic DNS registration is configured for the DNS servers. If it is, AD will create the DNS entry of the virtual computer object for the Availability Group listener name. The WSFC should also have Create Computer Objects permission in the AD Organizational
Unit where your Availability Group listener name will be created.
On a side note, make sure that you configure a separate SharePoint 2013 farm for your DR environment that will use the content databases joined in the Availability Group. For a stretched farm deployments, latency should be less than 1ms one way as
per this article. And while you can add your admin content and config databases on the Availability Group, asynchronous commit is
not supported.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

SQL 2012 Cluster install - error msg

Hi
I am in the process of installing SQL server 2012 cluster, on the Instance configuration page where i gave "SQL Server Network Name" as "appsqlclsA" and the "Named Instance" as "Ins01". I am getting the below
error msg, i am not sure exactly what permissions i need.
"The SQL Server failover cluster network name "appsqlclsA" is not valid. The name must be a valid DNS and Wins name.
So what i understand is i do not have permission to create the virtual sql name account "appsqlclsA"" in the AD.
But i need help finding exactly what permission i need.
Thank you for your help

Take a look at this
TechNet article for assigning permissions in Active Directory to create the virtual computer object. Either you are granted the appropriate permissions or the virtual computer object be pre-staged prior to installation
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

SQL 2012 Cluster- How to or Steps to Move Tempdb Files from Local drive to Shared volume

Hi..
I did Installation of SQL Server 2012 Cluster. During this setup I installed Tempdb Files on Local drive. Now I want to move this tempdb files from local drive to Shared Drive . When I am trying to move I am getting below error.
Does any one can help me or provide the steps to move this tempdb files from local drive to Shared Drive ?
Msg 5184, Level 16, State 1, Line 1
Cannot use file 'Z:\Tempdb\tempdb.mdf' for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource
of the Sql Server does not have a dependency on it.
Thanks
Regards..
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

Hi,
The error message may be thrown out when you attempt to create a database on another shared cluster drive when the SQL Server resource is not dependent on that disk.
Check if you are in the scenario which mentioned in the following article:
How to create databases or change disk file locations on a shared cluster drive on which SQL Server was not originally installed
http://support.microsoft.com/kb/295732/en-nz
Here is a thread with similar issue:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/c9f80af7-5b51-4c43-a2a0-f9c7d97aa41d/sql-disk-dependency-problem-on-sql-2008-cluster-including-errors
Hope it helps.
Tracy Cai
TechNet Community Support

Sql 2012 cluster

Hi guys
We have the following scenario:
Our sql servers are in a cluster consisting of two servers. All running sql 2012. Both off the servers DNS is configured for a primary in a local AD site and a secondary DNS to a different AD site.
When we reboot the local dc in the local AD site, sql get the following error:
"Cannot generate SSPI context."
When the local DC is back online everything works fine.
My question is why dont SQL query the secondary DC? Or is this a SPN/kerberos issue? Or should we rather add a secondary dc in the local site aswell?
Thanks

This could be a DNS issue or a DC replication issue. Check the primary and alternate DNS settings of the network adapter on both nodes to make sure they are configured to connect to the correct DNS servers
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Live Migration Failure

I am attempting to migrate virtual machines from one site to another but they are failing. I have sufficient bandwidth but am concerned about the latency. Can anyone recommend the maximum latency between the two sites?

Hi Sir,
I assume it is shared nothing live migration .
I would suggest you to perform live migration inside each site to check if the configuration is OK.
If live migration run successfully within local site , you may need to check the link layer between two sites .
During live migration you also can use netmon.exe to analyse the traffic to find some useful information.
In addition , please check the evet log of hyper-v host to check if there is any clue .
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Error while trying to upgrade SQL 2008 (SP2) to SQL 2012: There was a failure to calculate the applicability of setting LICENSEPATH.

Hi,
I am trying to upgrade one of our SQL Server Enterprise (2008 (SP2)) to 2012. I am using the upgrade option but it gives me the following error:
Error Code 0x85640002: There was a failure to calculate the applicability of setting LICENSEPATH
We have downloaded the image from our Volume Licensing account. Also, the same image was used to install SQL 2012 on Windows Server 2012 R2 servers without any issues.
Below is the install summary.txt. I have tried everywhere but no go. Would really appreciate any assistance.
Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2057043966
Exit facility code:            1380
Exit error code:               2
Exit message:                  There was a failure to calculate the applicability of setting LICENSEPATH.
Start time:                    2014-02-28 10:58:49
End time:                      2014-02-28 10:58:58
Requested action:              RunRules
Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0x0BA02FC6%400x294A9FD9&EvtType=0x0BA02FC6%400x294A9FD9
Machine Properties:
Machine name:                  xxxxxxx
Machine processor count:       2
OS version:                    Windows Server 2008 R2
OS service pack:               Service Pack 1
OS region:                     U.A.E.
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  No
Package properties:
Description:                   Microsoft SQL Server 2012
ProductName:                   SQL Server 2012
Type:                          RTM
Version:                       11
SPLevel:                       0
Installation location:         D:\x64\setup\
Installation edition:
User Input Settings:
ACTION:                        RunRules
CONFIGURATIONFILE:
ENU:                           true
FEATURES:
HELP:                          false
INDICATEPROGRESS:              false
INSTANCENAME:                  <empty>
PID:                           *****
QUIET:                         true
QUIETSIMPLE:                   false
RULES:                         GlobalRules
UIMODE:                        Normal
X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140228_105848\ConfigurationFile.ini
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               The rule result report file is not available.
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingApplicabilityException
    Message:
        There was a failure to calculate the applicability of setting LICENSEPATH.
    HResult : 0x85640002
        FacilityCode : 1380 (564)
        ErrorCode : 2 (0002)
    Data:
      SettingId = LICENSEPATH
      WatsonData = Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingApplicabilityException@2
      DisableWatson = true
    Stack:
        at Microsoft.SqlServer.Chainer.Infrastructure.Setting.CalculateApplicability()
        at Microsoft.SqlServer.Configuration.BootstrapExtension.ValidateChainerSettingAction.ExecuteAction(String actionId)
        at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
    Inner exception type: Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingValueException
        Message:
                There was a failure to calculate the default value of setting LICENSEPATH.
        HResult : 0x85640001
                FacilityCode : 1380 (564)
                ErrorCode : 1 (0001)
        Data:
          SettingId = LICENSEPATH
          WatsonData = Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingValueException@1
        Stack:
                at Microsoft.SqlServer.Chainer.Infrastructure.Setting`1.CalculateValue()
                at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallQueuedSubscriberDelegates()
                at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.Publish(Publisher publisher)
                at Microsoft.SqlServer.Chainer.Infrastructure.Setting.CalculateApplicability()
        Inner exception type: System.ArgumentException
            Message:
                        Culture ID 3072 (0x0C00) is not a supported culture.
                        Parameter name: culture
            Stack:
                        at System.Globalization.CultureInfo..ctor(Int32 culture, Boolean useUserOverride)
                        at System.Globalization.CultureTable.GetCultures(CultureTypes types)
                        at Microsoft.SqlServer.Configuration.SetupExtension.LcidUtilities.GetLangPackParentFolderForLcid(String lcid)
                        at Microsoft.SqlServer.Configuration.SetupExtension.LcidUtilities.GetLcidFolder(ServiceContainer context, String baseFolderFullPath)
                        at Microsoft.SqlServer.Configuration.SetupExtension.LicensePathSetting.DefaultValue()
                        at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallFunctionWhileAutosubscribing[T](SubscriberDelegate
subscriberDelegate, Int32 priority, AutosubscribingFunctionDelegate`1 function)
                        at Microsoft.SqlServer.Chainer.Infrastructure.Setting`1.CalculateValue()
Regards,
Mohammed

Culture ID 3072 (0x0C00) is not a supported culture.
                        Parameter name: culture
This appears to be the root problem. It seems that the regional settings on this machine is messed up. 0x0C00 is an unusual LCID, they do not normally not end in two zeroes.
is there a custom culture installed on this machine?
Review the regional settings and also check the System locale. If it looks spooky, set it to Arabic - U.A.E. if this is where you are located.
Erland Sommarskog, SQL Server MVP, [email protected]

Hyper-V guest SQL 2012 cluster live migration failure

Similar Messages

Maybe you are looking for