SQL 2012 Enterprise (Evaluation) - To Enterprise Core (Licensed) Edition Upgrade Warning on Always-On

Hi all,
I am need to do an Edition Upgrade on a SQL Server 2012 Enterprise (evaluation) to a licensed version of the Enterprise version. We do already have set-up Always on Availability Groups, however when I want to perform the Edition Upgrade I receive the following
warning:
The AlwaysOn Availability Groups feature is enabled on this instance of SQL Server and it is not supported in the edition being changed to. Before proceeding, disable AlwaysOn Availability Groups on the server instance. For more information, see SQL Server
Books Online.
I am using the correct media, as well if I need to accept the license terms I can see it's the Enterprise Core edition, so I am wondering why I receive this message. And of course I did not proceed, because I do not want to loose my availability groups.

Hi Hans,
Personally, according to the
features supported by the editions of SQL Server 2012, it is support on AlwaysOn Availability Groups feature on the Enterprise version. In theory, the AlwaysOn Availability Groups feature is supported on the Enterprise version after upgrading.
About this warning, if it is in test environment, we can do a test and check if the warning will effect AlwaysOn Availability Groups feature. Or
I recommend to submit it to the Microsoft Connect at this link
https://connect.microsoft.com/SQLServer/Feedback. So that a dedicated Support Professional can assist
you in a more efficient manner.
Thanks for your understanding.
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

Similar Messages

SQL Server Enterprise Core 2012

When trying to in stall SQL Sever Enterprise core 2012 on a Hyper-V VM running Microsoft server 2008 r2 Data Center I recieve a error 0x84B20001. First a box pops up and says "Please wait while Microsoft Server 2012 setup processes the current operation.
Then a box pops up and says SQL Server setup failure.
The action type "ExecuteWorkflowAction" is not valid for the WorkflowIdentity element. The only valid action type is ExecuteWorkflowAction.
Error Code: 0x84B20001
What do I need to do to get past this error?

Hello,
Please make sure SP1 for Windows Server 2008 R2 is installed.
Checkout the features and languages supported also:
http://msdn.microsoft.com/en-us/library/hh231669.aspx
The following guide may help:
http://www.sqlcoffee.com/SQLServer2012_0005.htm
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Unable to install SQL 2012 Enterprise on Windows 8.1 OS

I had installed SQL 2012 Enterprise on my Windows 8.1 and was running successfully. I faced some SSRS & SSIS Authentication issue. So i decided to uninstall SQL and re-install it. On doing so, i am unable to install it.
Wizard disappears from this screenshot onwards.
Tried installing from Command Prompt.
Setup.exe /q /ACTION=Repair /INSTANCENAME=instancename /IAcceptSqlserverLicenseTerms=true
Still wizard disappears.

Hello,
I guess un-installation of SQL server is not complete and there are fragments remaining.Have you made sure you have uninstalled SQL server from add remove program completely.Make sure no features related to SQL server are present there.Please remove setup
support files as well.Refer below link to remove it completely
http://technet.microsoft.com/en-us/library/hh231731.aspx
Similar issue docemented here
If you face any issue below manual method for removing SQL server will be helpful
1. Uninstall the existing SQL Server 2012 and all the components from the control panel.
    2. Backup the registry.
    3. Delete the following keys in regedit:
    --HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
    --HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
    4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and delete all the sub-keys referencing SQL Server.
    5. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and delete all the keys referencing SQL Server.
    6. Rename all the SQL Server folders in the computer.
    7. Reboot the machine.
Revert if you face any issue.
EDIT: IMP POINT installation of SQL server 2012 Enterprise edition On win 8.1 ( client OS machine) is not supported by MS.But it will not stop you from installation
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

SQL 2012 enterprise service pack 2 fails to install

Hi,
I have installed SQL 2012 sp2 x64 onto the main service manager 2012 database, but it fails on the datawarehouse SQL server. Both are going from SP1 to SP2. Servers are running windows server 2012 sp1 x64.
On the datawarehouse server it gets so far and then just displays a message of completed, with all the other fields blank.
The text file for the Summary of the installation has been copied below:
Overall summary:
Final result:                  The patch installer has failed to update the following instance: MSSQLSERVER. To determine the reason for failure, review the log files.
Exit code (Decimal):           -2068709375
Start time:                    2015-01-09 13:55:32
End time:                      2015-01-09 14:04:09
Requested action:              Patch
Instance MSSQLSERVER overall summary:
Final result:                  The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
Exit code (Decimal):           -2068709375
Exit facility code:            1202
Exit error code:               1
Exit message:                  The NT service 'MSSQLServerOLAPService' could not be stopped.
Start time:                    2015-01-09 14:00:18
End time:                      2015-01-09 14:04:01
Requested action:              Patch
Exception help link:
http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0xAC454CB1%400xF762992B%401202%401&EvtType=0xAC454CB1%400xF762992B%401202%401
Machine Properties:
Machine name:                  SCSDWM01
Machine processor count:       4
OS version:                    Future Windows Version
OS service pack:
OS region:                     United Kingdom
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 Configured
SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Database Engine Services
1033                 Enterprise Edition   11.1.3153.0     No         Yes
SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033
Enterprise Edition   11.1.3000.0     No         Yes
SQL Server 2012      MSSQLSERVER          MSAS11.MSSQLSERVER             Analysis Services
1033                 Enterprise Edition   11.1.3130.0     No         Yes
SQL Server 2012      MSSQLSERVER          MSRS11.MSSQLSERVER             Reporting Services - Native
1033                 Enterprise Edition   11.1.3153.0     No         Yes
SQL Server 2012
Management Tools - Basic                 1033                 Enterprise Edition   11.1.3153.0
No         Yes
SQL Server 2012
Management Tools - Complete              1033                 Enterprise Edition   11.1.3130.0
No         Yes
SQL Server 2012
SQL Server Data Tools - Business Intelligence for Visual Studio 2012 1033
11.1.3402.0     No         Yes
SQL Server 2012
Integration Services                     1033                 Enterprise Edition
11.1.3153.0     No         Yes
Package properties:
Description:                   Microsoft SQL Server 2012
ProductName:                   SQL Server 2012
Type:                          RTM
Version:                       11
SPLevel:                       2
KBArticle:                     KB2958429
KBArticleHyperlink:
http://support.microsoft.com/?kbid=2958429
PatchType:                     SP
AssociatedHotfixBuild:         0
Platform:                      x64
PatchLevel:                    11.2.5058.0
ProductVersion:                11.0.2100.60
GDRReservedRange:              11.0.5300.0:11.0.5499.0
PackageName:                   SQLServer2012-KB2958429-x64.exe
Installation location:         c:\ce370c3d01e3ec4095540d8578cc7e\x64\setup\
Updated product edition:
Instance             Edition
MSSQLSERVER          Enterprise
User Input Settings:
ACTION:                        Patch
ALLINSTANCES:                  false
CLUSTERPASSIVE:                false
CONFIGURATIONFILE:
ENU:                           false
HELP:                          false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS:              false
INSTANCEID:                    <empty>
INSTANCENAME:                  <empty>
QUIET:                         false
QUIETSIMPLE:                   false
SQMREPORTING:                  false
UIMODE:                        Normal
X86:                           false
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_135509\SystemConfigurationCheck_Report.htm
Any ideas on why this has happened and how to fix the error?
Thanks.
Jaz

Hello,
Open the errorlog file on the following path C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log. There
you will find a more descriptive error.
I received that error before. The workaround I used is contained on the following article:
http://www.sqlcoffee.com/Troubleshooting112.htm
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL 2012 Enterprise SP1 installation for SCCM 2012 R2

I am just starting to install SQL 2012 with SP1 Enterprise for SCCM 2012 R2.
Does anyone have a step by step guide for this install please
I am planning to install SQL 2012 with SP1 Enterprise as a physical install which I intend to geo cluster later on
Also I am thinking of installing WSUS on a separate server and get my SCCM 2012 servers (1 primary and 3 secondary) to use this server - would appreciate some help on how this can be setup as well

That doesn't make sense to me. Both versions are fully supported on virtual and physical platforms.
Also, I'm with Garth - local SQL all the way.
Here are my thoughts on the subject
http://www.gerryhampsoncm.blogspot.ie/2013/10/configmgr-sql-some-tips.html
ConfigMgr is not a real-time product like Exchange, for example. A certain amount of downtime can be tolerated. I would spend more time implementing a robust backup solution, rather than trying to implement high availability.
You should be able to recover a ConfigMgr site from SQL backup in a couple of hours.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Slient install of Sql 2012 enterprise fails 'MEDIALAYOUT' is invalid"

I'm trying to install SQL 2012 using the config file. It's failing and reporting 'MEDIALAYOUT' is invalid. The problem is that this isn't even a parmater that exists in the file. I know it's finding the file, because it I put a bogus file name there, it
complains and says "invalid file". So i think it's reading the file, doesn't like something in there, then it kicks out this erroneous error that means nothing. I've looked in the event logs, see nothing.
Has anybody seen this before? It not, is there any other log file I can look at that will tell me specifically what might be wrong?
.\setup.exe \ConfigurationFile=ConfigurationFile.ini
The specified value for setting 'MEDIALAYOUT' is invalid. The expected values are:None, Core, Advanced, Full
THX

Can you make sure that the config file is valid and comment lines are not text wrapped.
FAQ
Regards,
Ahmed Ibrahim
SQL Server Setup Team
My Blog
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click
"Mark as Answer" and "Vote as Helpful"
on posts that help you.
This can be beneficial to other community members reading the thread.

Point Imaged/Cloned Sharepoint 2010 to different/renamed SQL 2012 server - what needs to be changed/edited?

Newbie here... I am using our development VM's one has SP 2010 installed/working and configured and the other is SQL 2012 housing the DB's for the working SP sites and a third running IIS and hosting the pages. I want to use clones to copy to additional
VM's, rename the SQL and rename the SP 2010 (the IIS will stay the same just add the cloned site to it. MY question is "Is there an automated way of reconfiguring SP 2010 to point to the new SQL server? (I've already figured out how to change the SID
information and run the queries on the SQL, just need info on the SP 2010 part.)
Thanks,
Jon P.

You can't do this, don't try it. For VM purposes, SharePoint does not support:
Time Sync
Snapshotting/Checkpoints
VM Backups (e.g. SAN-based or VMDK/VHD-based backups)
You will cause problems doing what you're attempting to do, unless you isolate these VMs onto a new network that has no access to the production network -- in this case, you would also need a copy of one Domain Controller from production, as well.
Best bet is to build a new farm and restore content to it via content database/service application database restoration.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Server 2012 r2 Evaluation copy asking for license key?

So, I'm an old dog trying to learn new tricks - the newest trick being to install Server 2012 R2 Standard with Hyper-V role. After a bit of fumbling around (good story for another time) I have managed to make it to the point of installing the OS onto the
virtual machine I created. Sweet. My understanding from extensive internet research is that I should now use an ISO image of Server 2010 R2 (an ISO of the Evaluation Copy it seems being universally suggested), for installing the OS to the virtual
machine and then subsequently change the license key to my OEM license key using the
slmgr -rearm command. OK, if that is correct I can deal with it. But I have top get it installed first. I have downloaded the following ISO from Technet:
9600.16384.WINBLUE_RTM.130821-1623_X64FRE_SERVER_SOLUTION_EN-US-IRM_SSSO_X64FRE_EN-US_DV5
The setup installation starts up fine, but immediately presents a prompt screen for entering the product key. Huh? I thought evaluation copies did not require a product key to perform the installation. It will not accept my OEM product key, so I am
stumped. Do I have the wrong ISO? I did try a couple of other copies/versions, but they conk out because Windows generates errors saying something to the effect that they are not the right version for the SCSI Synthetic Adapter. So is there
maybe some other ISO's I should be trying? Or, is there some place I am supposed to request a key for the ISO eval copy I have? And, if at some point I am able to get the evaluation copy installed, is my thinking correct about using my OEM key used
to activate the physical host to change the evaluation installation into a regular installation? Or, should be burning an ISO of my OEM installation disk to install from and use my OEM key directly to activate that when doing setup to the
VM?

The eval iso will not accept a oem key, this is by design, oem versions are designed for original hardware only, the eval can be activated with a volume key or I believe a retail key, the licensing agreement is different between the OEM and other
versions.
Appreciate your response. After a lot of late night mucking around was able to get a different evaluation copy to load: This one worked (but not without a bit of a struggle):
9600.17050.WINBLUE_REFRESH.140317-1640_X64FRE_SERVER_EVAL_EN-US-IR3_SSS_X64FREE_EN-US_DV9
Initially I could not get this evaluation to load as the virtual SCSI adapter kept generating a system error to the effect: "Synthetic SCSI controller [...] Failed to Power on with Error: 'The version does not support this version of the file
format'". Only after moving the ISO file onto the physical drive holding the VHXD containing the VM and messing with security settings on the file did it finally load. This version (vs the other ISO) begins loading by first presenting a list of OS versions
(standard and datacenter variants) to load. From there on the installation pretty much proceeded as would a normal installation would. This version did not ask for an activation key and when finally installed shows a message on the desktop that it is good
for 180 days usage (as Microsoft has stated should be the case). I did encounter two additional problems though that had to be dealt with before success was attained.
1) the install crashed with an error "Windows cannot find the Microsoft Software License Terms. Make sure the installation sources are valid and restart the installation" . That was a head scratcher. After another an hour
of research I came a cross a mention in another forum post about memory issues being the culprit in a similar situation of someone trying to install Windows 8 into a VM. My VM was set to a use dynamic memory with a minimum of 512 MB, which is pretty typically
recommended in the install guides I have been consulting. Wrong. So, I bumped the minimum up to 1024 MB and the problem disappeared.
2) The installation halted when asking for the drive where I wanted the installation to be placed. Problem? No available drives were shown to pick from, i.e. the virtual drive defined in the hyper-V setup simply did not appear. Another
hour of digging online produced a suggestion that the VM install could not recognize the drivers for the raid controller in the physical server. Perplexing. But anyway I loaded a copy of the raid controller drivers onto a USB thumb drive and
manage to mount the thumb drive as a hard drive in the VM settings after which the virtual drive appeared in the list and the installation managed to successfully complete.
So, at this point I have a functional VM operating - albeit with much hair pulling an teeth gnashing along the way. Will spend a bit of time pounding on the system to what else I can break, or breaks on its own. Hopefully nothing because I don't have
much hair left or many teeth left to lose. fingers crossed because I haven't tried to activate the VM OS yet.

SQL 2012 SP1 Enterprise (SSRS in SharePoint mode): Reporting Services scale-out deployment is not supported in this edition of Reporting Services

Hello,
SSRS in SharePoint mode is driving me insane.
We are recreating a SharePoint 2013 (SP1) farm in a test environment with the following set-up:
2 SP Web FrontEnds
2 SP Application Servers
1 SQL Server
At both SP APP Servers, we installed SSRS (SQL 2012 Enterprise w/ SP1) in SP integrated mode.
We managed to start the SSRS SP service at the first SP APP Server. However when we try to start it on the second APP Server, we get the following error:
"Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot
be started on this server unless it is stopped on all other servers in the farm. "
Now I can't stress this enough: This is a SQL Server 2012 SP1 Enterprise. This is the image we got from our MSDN subscription. There is no mistake here.
Could someone please advise why SP might think this version of SSRS is not the correct one?
Thanks in advance for your help.
Regards,
P.

Hello,
I'm afraid that is not it.
After a long, frustrating and strenuous investigation and troubleshooting, we found the problem.
The problem is the current ISO for SQL Server 2012 Enterprise SP1 (x64) found at MSDN. Bear in mind that we downloaded this ISO from MSDN about a month ago.
As soon as we recreated the environment using the ISO for SQL Server 2012 Enterprise SP2 (x64) found at MSDN, everything worked as expected -- and that includes running more than one SSRS in SharePoint mode.
Also bear in mind that we tried updating the SQL SP1 install with SP2 and subsequent cumulative updates but that never fixed the problem.
There is something fundamentally wrong with that ISO with SP1 slipstreamed in it that no matter the subsequent updates installed, SSRS in SharePoint mode fails to work properly on a multi-server environment. We went as far as SP2 with CU3 and nothing seemed
to fix the problem. And yes, we also performed manual updates to the SSRS and PowerPivot SharePoint MSI add-ins.
I am shocked and distraught to find out that I lost hours of work due to a dodgy ISO image.
Regards,
P.

SQL Server Processor/Core Licensing and Windows CALs

I've scoured the internet for an answer to this question, so I'm assuming the scenario isn't as common as I think, or people are purposely looking the other way because they don't want to know the answer :)
The application in question is pretty simple - An ASP.net web application using ASP.net forms auth (no end-user Windows Authentication). Using Windows Server 2008 Web Edition, we've confirmed that no Windows CAL is required on the front-end web tier.
So then on the back-end data tier (SQL Server) it also seems pretty straight forward. As far as I can tell, the SQL Server licensing makes it pretty clear "...users who input data into, query, or view data through a web-based application... require
a CAL". So that makes it pretty obvious, you need a CAL or a per-processor/pre-core license of SQL Server.
Here's where it gets tricky... What about the licensing requirements for the Windows Server that SQL Server is running on? Do we need a
WindowsCAL for each connection from the Web Tier to the SQL Server? Note that Windows CALs and SQL Server CALs are completely separate in terms if purchasing, and nothing says a SQL Server CAL is of a higher
order than a Windows CAL (thereby covering both).
It would seem ridiculous (IMHO) to allow unlimited connections to SQL, but then dump you back to the CAL model on Windows (since there is no "unlimited" option in Windows Server). But licensing is a strange beast, and non-compliance is not
something I'm interested in.
Any insight with pointers to Microsoft documentation would be greatly appreciated!
Thanks guys,

For those of you who would like an answer on this without calling licensing support, here's the answer :)
Windows Server 2012 does NOT have a CAL limitation for "public" web traffic. I specifically asked about ASP.net Forms Authenticated users, and the licensing specialist said any website that uses anonymous authentication which then passes
auth onto some other back-end process (e.g. ASP.net forms auth) you do not need a Windows CAL. You DO need a Windows CAL if your application is somehow tied to services on the Windows box where the website user actually enters credentials which are authenticated
against the local account store or domain controller. So to me, that's a pretty simple answer -
anonymous auth = No CALs
integrated auth = CAL required
Ok, onto SQL Server... As quoted from my original post, SQL licensing makes it very clear that ANY connection to the database requires a CAL, even if it's multiplexed through IIS or some other middle-tier. Bottom line? Simple answer here as well:
public website with a SQL back-end = per-socket or core-licensing (since you can't count "CALs" on a public site)
Finally, the most illusive question (for me anyway). What about the copy of Windows running your SQL Server? the answer here was - No CALs required if it's purely a SQL Server connection. Meaning, if all your Windows server is doing
is running SQL Server and fielding query requests from your front-end IIS ASP.net app, you're do NOT need any Windows Server CALs. You obviously do need SQL CALs or socket/core licenses, which I covered above. You will however need Windows CALs
on your SQL Server box for any Support specialists or Deployment folks who remote into the machine using TS or using UNC file shares and such to work with the server.
Hopefully that helps someone else looking for a quick answer. And as the moderator noted, if that doesn't make sense you should definitely call the licensing specialist. They are very helpful and surprising quick to answer questions (without
any sales pressure).
Thanks for posting this, I am in the same boat. I will have a public facing web server and a backend SQL server. The web site requires all users to login so they can see the content. We use forms authentication as well (no Windows or Active Directory authentication).
The application does all the authentication itself using the backend database (credentials are stored in a database table).
I just called the licensing pre-sales number and spoke to a rep who said the web server would require CALs (or an External Connector in this case), because I am requiring people to login to view the content. He said it did not matter what the authentication
method was. I clearly explained the web application handles all the authentication, but he still said we would need CALs in this case because users must authenticate to access the content. He likened it to a museum. If you need to buy a ticket to get in to
see the content (in this case login to the web site), you need CALs he said.
He also said I would need Windows Server CALs/EC for the Windows server that hosts the database. I will be using SQL Core licensing, so no additional SQL CALs will be needed.
Just thought I would share what I learned.
Sorry to dredge up an old thread, but I have been doing a lot of reading on CALs lately in anticipation of launching a public website. Reading the license agreement, I don't think you need CALs on the front end Windows Server 2012 just because people
are authenticating. The Windows Server 2012 license agreement makes no mention of this that I can find. It only says you need CALs for employees or your affiliates' employees. A non-employee visitor does not fall under the definition an affiliate.
The SQL Server licensing is tricky, and not written for public website access. Is every user with an account to your online store need a CAL? The only other option is SQL Server Enterprise licensed by CPU cores.

SQL 2012 FCI Failure Help Troubleshoot Cause

Starting since the upgrade to SQL 2012 Enterprise in May of 2013, in a highly transactional OLTP environment, We experience periodic cluster failures.
When I generate the Cluster.log for this cluster we receive the following, (We've increased the timeout already and that doesn't seem to help)
00001724.00004920::2014/11/25-04:01:18.130 WARN [RES] SQL Server <SQL Server>: [sqsrvres] Failed to retrieve data column. Return code -1
00000f14.00002988::2014/11/25-04:01:21.235 DBG Sending control 4950882
00000f14.000020c8::2014/11/25-04:01:21.235 DBG Sending control 4950883
00000f14.000020c8::2014/11/25-04:01:21.250 DBG Sending control 4950884
00000f14.000020c8::2014/11/25-04:01:21.250 DBG Sending control 4950885
00000f14.000020c8::2014/11/25-04:01:21.250 DBG Sending control 4950886
00000f14.000020c8::2014/11/25-04:01:21.250 DBG Sending control 4950887
00000f14.000020c8::2014/11/25-04:01:21.250 DBG Sending control 4950888
00000f14.000020c8::2014/11/25-04:01:21.250 DBG Sending control 4950889
00000f14.000020c8::2014/11/25-04:01:21.250 DBG Sending control 4950890
00000f14.000020c8::2014/11/25-04:01:21.250 DBG Sending control 4950891
00000f14.000020c8::2014/11/25-04:01:21.250 DBG Sending control 4950892
00000f14.000020c8::2014/11/25-04:01:21.250 DBG Sending control 4950893
00000f14.000020c8::2014/11/25-04:01:21.250 DBG Sending control 4950894
00000f14.000020c8::2014/11/25-04:01:21.250 DBG Sending control 4950895
00000f14.000020c8::2014/11/25-04:01:21.266 DBG Sending control 4950930
00000f14.000020c8::2014/11/25-04:01:21.266 DBG Sending control 4950931
00000f14.000020c8::2014/11/25-04:01:21.282 DBG Sending control 4950932
00000f14.000020c8::2014/11/25-04:01:21.282 DBG Sending control 4950933
00000f14.000020c8::2014/11/25-04:01:21.282 DBG Sending control 4950934
00000f14.000020c8::2014/11/25-04:01:21.282 DBG Sending control 4950935
00000f14.000020c8::2014/11/25-04:01:21.282 DBG Sending control 4950936
00000f14.000020c8::2014/11/25-04:01:21.282 DBG Sending control 4950937
00000f14.000020c8::2014/11/25-04:01:21.282 DBG Sending control 4950938
00000f14.000020c8::2014/11/25-04:01:21.282 DBG Sending control 4950939
00000f14.000020c8::2014/11/25-04:01:21.282 DBG Sending control 4950940
00000f14.000020c8::2014/11/25-04:01:21.282 DBG Sending control 4950941
00000f14.000020c8::2014/11/25-04:01:21.282 DBG Sending control 4950942
00000f14.000020c8::2014/11/25-04:01:21.282 DBG Sending control 4950943
00000f14.000020c8::2014/11/25-04:01:21.297 DBG Sending control 4950944
00000f14.000020c8::2014/11/25-04:01:21.297 DBG Sending control 4950945
00000f14.000020c8::2014/11/25-04:01:21.297 DBG Sending control 4950946
00001724.0000305c::2014/11/25-04:01:21.344 ERR [RES] SQL Server <SQL Server>: [sqsrvres] Failure detected, diagnostics heartbeat is lost
00001724.0000305c::2014/11/25-04:01:21.344 INFO [RES] SQL Server <SQL Server>: [sqsrvres] IsAlive returns FALSE
00001724.0000305c::2014/11/25-04:01:21.344 WARN [RHS] Resource SQL Server IsAlive has indicated failure.
00000f14.00002988::2014/11/25-04:01:21.344 INFO [RCM] HandleMonitorReply: FAILURENOTIFICATION for 'SQL Server', gen(2) result 1.
00000f14.00002988::2014/11/25-04:01:21.344 INFO [RCM] TransitionToState(SQL Server) Online-->ProcessingFailure.
What can we do to find the cause of this as it causes the SQL Resource to Fail, and then restart on the same node, a node failure does not occur on the SQL Server 2012 FCI.
Thanks in advance for all responses,
Tyler
Tyler Krusenstjerna | Database Administrator

Here is what runs right before the failure is detected in the cluster.log I show >
00000f14.00002988::2014/11/25-04:01:07.460 DBG Sending control 4950846
00000f14.00002988::2014/11/25-04:01:07.460 DBG Sending control 4950847
00000f14.00001928::2014/11/25-04:01:10.814 DBG [CM] mscs::RegCheckpoint::SaveCheckpointTimerCallback(SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQLServer)
00000f14.00001928::2014/11/25-04:01:10.814 DBG [CM] mscs::RegCheckpoint::SaveCheckpointTimerCallback: Before: Checkpoint state for key SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQLServer.
00000f14.00001928::2014/11/25-04:01:10.814 DBG [CM] mscs::RegCheckpoint::SaveCheckpointInternal(SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQLServer)
00000f14.00001928::2014/11/25-04:01:10.814 DBG [CM] mscs::RegCheckpoint::SaveCheckpointInternal: Before: Checkpoint state for key SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQLServer.
00000f14.00001928::2014/11/25-04:01:10.939 DBG [CM] mscs::RegCheckpoint::SaveCheckpoint: Stored registry checkpoint SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQLServer for resource SQL Network Name (XXXXXXXXXXX).
00000f14.00001928::2014/11/25-04:01:10.939 DBG [GUM] Node 1: gum.SendRequest(/dm/update) Started
00000f14.00001928::2014/11/25-04:01:10.939 DBG [GUM] Node 1: skipping lock aquisition
00000f14.00001928::2014/11/25-04:01:10.939 DBG [GUM] Node 1: sending request
00000f14.00001928::2014/11/25-04:01:10.939 DBG [MRR] Node 1: insert request record for RID 28422
00000f14.00001928::2014/11/25-04:01:10.939 DBG [MRR] SendRequest(<message action='gum/do-update' GemId='0' target='GUMA' sender='1'mrr='28422'/>)
00000f14.00001928::2014/11/25-04:01:10.939 DBG [GEM] Node 1: message added to send queue
00000f14.00001928::2014/11/25-04:01:10.939 DBG [GEM] Node 1: SendNextMessageSerially
00000f14.00001928::2014/11/25-04:01:10.939 DBG [GEM] Node 1: delivering message 1:28579
00000f14.00001928::2014/11/25-04:01:10.939 DBG [GUM] Node 1: DoUpdate(/dm/update, gumid: 28477)
00000f14.00001928::2014/11/25-04:01:10.939 DBG [GEM] Node 1: ProcessAck from node 1 (already acked (1))
00000f14.00001110::2014/11/25-04:01:10.939 DBG [NODE] Node 1: just about to send a message of size 0 to 3
00000f14.00000f88::2014/11/25-04:01:10.939 DBG [DM] Beginning transaction
00000f14.00001114::2014/11/25-04:01:10.939 DBG [NODE] Node 1: just about to send a message of size 16932 to 2
00000f14.00000f88::2014/11/25-04:01:10.939 DBG [DM] Beginning transaction
00000f14.00001110::2014/11/25-04:01:10.939 DBG [NODE] Node 1: message to node 3 sent
00000f14.00001110::2014/11/25-04:01:10.939 DBG [NODE] Node 1: just about to send a message of size 16932 to 3
00000f14.00001114::2014/11/25-04:01:10.939 DBG [NODE] Node 1: message to node 2 sent
00000f14.00001110::2014/11/25-04:01:10.939 DBG [NODE] Node 1: message to node 3 sent
00000f14.00002080::2014/11/25-04:01:10.939 DBG [GEM] Node 1: ProcessAck from node 2 (already acked (1))
00000f14.00000f94::2014/11/25-04:01:10.939 DBG [GEM] Node 1: ProcessAck from node 3 (already acked (1 2))
00000f14.00000f94::2014/11/25-04:01:10.939 DBG [GEM] Node 1: SendNextMessageSerially
00000f14.00000f94::2014/11/25-04:01:10.939 DBG [GEM] Node 1: No more messages in queue
00000f14.00000f94::2014/11/25-04:01:10.954 DBG [MRR] Node 1: processing reply <message action='mrr/reply' GemId='0' target='MRRA' sender='3'mrr='28422'/>
00000f14.00000f94::2014/11/25-04:01:10.954 DBG [MRR] Node 1: Waiting for RID 28422 stragglers (1 2)
00000f14.00002080::2014/11/25-04:01:11.079 DBG [MRR] Node 1: processing reply <message action='mrr/reply' GemId='0' target='MRRA' sender='2'mrr='28422'/>
00000f14.00002080::2014/11/25-04:01:11.079 DBG [MRR] Node 1: Waiting for RID 28422 stragglers (1)
00000f14.00000f88::2014/11/25-04:01:11.110 DBG [DM] Successfully flushed the log and rewound it
00000f14.00000f88::2014/11/25-04:01:11.110 DBG [DM] Committed transaction 128:128:1101525
00000f14.00000f88::2014/11/25-04:01:11.110 DBG [DM] Flushing hive with timeout of 300 seconds
00000f14.00000f88::2014/11/25-04:01:11.157 DBG [TAA] Timed action completed in time
00000f14.00000f88::2014/11/25-04:01:11.157 DBG [DM] Successfully flushed the log and rewound it
00000f14.00000f88::2014/11/25-04:01:11.157 DBG [DM] Committed transaction 128:128:1101525
00000f14.00000f88::2014/11/25-04:01:11.157 DBG [CORE] Node 1: sending mrr/reply to MRRA at DBSPRD1F
00000f14.00001118::2014/11/25-04:01:11.157 DBG [NODE] Node 1: just about to send a message of size 0 to 1
00000f14.00001118::2014/11/25-04:01:11.157 DBG [NODE] Node 1: message to node 1 sent
00000f14.00001118::2014/11/25-04:01:11.157 DBG [NODE] Node 1: just about to send a message of size 232 to 1
00000f14.00001118::2014/11/25-04:01:11.157 DBG [NODE] Node 1: message to node 1 sent
00000f14.00000f90::2014/11/25-04:01:11.157 DBG [MRR] Node 1: processing reply <message action='mrr/reply' GemId='0' target='MRRA' sender='1'mrr='28422'/>
00000f14.00000f90::2014/11/25-04:01:11.157 DBG [MRR] Node 1: Request RID 28422 is completed
00000f14.00001928::2014/11/25-04:01:11.157 DBG [GUM] Node 1: gum.SendRequest(/dm/update) Completed
00000f14.00001928::2014/11/25-04:01:11.157 DBG [CM] mscs::RegCheckpoint::SaveCheckpointInternal: After: Checkpoint state for key SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQLServer.
00000f14.00001928::2014/11/25-04:01:11.157 DBG [CM] mscs::RegCheckpoint::SaveCheckpointTimerCallback: After: Checkpoint state for key SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQLServer.
00001724.00004920::2014/11/25-04:01:18.130 WARN [RES] SQL Server <SQL Server>: [sqsrvres] Failed to retrieve data column. Return code -1
Tyler Krusenstjerna | Database Administrator

Installing SQL 2012 Ent (MSDN Ver) with Sysprep

Hi folks,
I've been trying to create template VMs on Windows Server 2008 R2 with SQL 2008 R2 Enterprise and SQL 2012 Enterprise available on them (Sysprepped installs of SQL). So, I'm creating one template for 2008 and another for 2012; not both on the same
template. I was able to create the 2008 R2 template with little issue. However, after completing the advanced install of SQL 2012 and rebooting, I was unable to complete the install process because the serial number is defaulting to all zeros (normally
this copy of SQL 2012 would embed the license key, as it did for the 2008 R2 install). Here's a link to the process that I followed for 2012 - ( could not embed link, please refer to TechNet article titled 'Install SQL Server 2012 Using SysPrep').
All software / hardware is 64 bit for sake of this question. Does anyone have any thoughts or ideas around this conundrum?
Thanks,
Sean Donovan

Hi,
According to the description, I understand that during Complete Image step, the product key is empty rather than the embed the key. You followed
http://technet.microsoft.com/en-us/library/ee210664.aspx.
I suggest you try starting the ‘complete image’ from the installation media instead of starting it from the shortcut being created in the ‘prepare image’ step and see if it resolves the issue.
Thanks.
Tracy Cai
TechNet Community Support

SQL 2012 support for ADFS 2.0

We recently upgraded to SQL 2012 Enterprise from SQL 2008. Since that happened we are now seeing errors when trying to create Relying Party Trusts in our ADFS 2.0 environment.
The error is as follows:
An error occurred during an attempt to access the AD FS configuration database. Error message: Exception of type 'Microsoft.IdentityServer.PolicyModel.Client.StorageOperationException' was thrown.
That brings 3 specific questions:
1. Does ADFS 2.0 support SQL 2012 as a backend?
2. Can we move the AD FS configuration database back to WID?
3. If the answer to question 2 is yes, how do I do it?
Thanks in advance for any help or suggestions.
Just a Network Administrator in a Developers World

Hi Boomer,
There is no official document published about incompatibilities between AD FS 2.0 and SQL 2012. Though many people have issues about this combination, please see this thread below:
ADFS 2.0 + SQL 2012
http://social.msdn.microsoft.com/Forums/vstudio/en-US/6842274e-dca6-423d-9ddb-f5949fa83076/adfs-20-sql-2012?forum=Geneva
In the meantime, SQL Server 2012 is supported with AD FS 2.1 for sure, you can try to upgrade AD FS 2.0 to AD FS 2.1 if the issue persists.
In addition, I couldn’t find any resource about migrating AD FS configuration database from SQL to WID, only the other way around.
More information for you:
Federation Server Farm Using SQL Server
http://technet.microsoft.com/en-us/library/gg982487.aspx
FAQ on ADFS - Part 1
http://blogs.technet.com/b/askpfeplat/archive/2013/07/22/faq-on-adfs-part-1.aspx
Best Regards,
Amy

SQL 2012 Database Mirroring Issue is stalling

hi All,
I have a SQL 2012 Enterprise Primary and DR SQL Clusters.
I have a 500 GB TDE Enabled Using HSM SQL DB which I have mirrored across to DR.
I am noticing that my Logs are shipping to DR, but the Unrestored Log size is huge and My restore rate is about 0 - 80KB/Sec. This is Causing the unrestored
Log to grow on the DR side.
I also notice at times my Unsent Log is also getting big after any DB Maintenance activities (such as rebuild of indexes).
I have a dedicated connection between my datacenters and the traffic thruput is quite reasonable and I am able to copy out a 2GB File across within a few
minutes. I see no packet drops within my links.
How do I ensure that my unsent logs are copied out and also increase my restore rate in DR side.
Any help / Suggestions will be much appreciated.
Regards
Aravin.

You need to limit the amount of reindexing you do on your primary/principal as it generates a lot of logs which slows down mirroring and log shipping.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

Down grade SQL 2014 to SQL 2012 server

Hi,
I have purchased SQL 2014 paper license but I want to use SQL 2012 server can we use same licensing for SQL 2012. Can we downgrade the SQL 2014 to 2012.
Thanks & Regards

Hello,
yes, you can downgarde you r SQL Server 2014 to 2012 Version. for Customers who have licensed software through a Microsoft Volume Licensing program are eligible to use prior versions of the software edition that they have licensed. This is known as
a downgrade right.
In general, the
Volume Licensing Service Center (VLSC) provides download access only to the current (N) and the last (N-1) version of products(2014, 2012). however, as of December 2012, a limited set of N-2 and N-3 prior product versions remain available for download through
the VLSC. for SQL Server you can also downgrade to 2012, 2008 R2 and 2008.
Note: In addition to VLSC download software access, Volume Licensing customers can order physical media (CD/DVD) copies of their licensed software through the VLSC.
if you purchase your SQL Server as FPP(BOX) product, you can also downgrade it to 2012 but you Need to have the media + key product of 2012 Version.
thanks
diramoh

SQL 2012 Enterprise (Evaluation) - To Enterprise Core (Licensed) Edition Upgrade Warning on Always-On

Similar Messages

Maybe you are looking for