Does a Hyper-V VM running SQL 2014 Standard Edition support Hot Add Memory?

According to this article: http://support.microsoft.com/kb/956893
This was the case with SQL 2012 Standard Edition when running in a Hyper-V VM:
Q7: Is Hyper-V Dynamic Memory supported for SQL Server?
A7: Hyper-V Dynamic Memory is fully supported with SQL Server. Only SQL Server versions and editions that support Hot Add Memory (Enterprise and Datacenter) can see memory that is added by using Hyper-V Dynamic Memory. SQL Server 2012 Standard
edition also recognizes Hot Add memory when running in a virtual enviroment. SQL Server versions that do not support Hot Add Memory are still supported. But these versions will detect only the memory that is present in the operating system when SQL Server
starts.
I setup SQL 2014 Standard Edition in a VM and set it to Dynamic Memory, and just realized that Standard Edition does not support Hot Add Memory. However, this support article contradicts that, but only mentions SQL 2012.
Is anyone aware of the real answer to this question? I just need to know how to configure the memory for my VM to make it run optimally.

> just realized that Standard Edition does not support Hot Add Memory. However, this support article contradicts that, but only mentions SQL 2012.
It would not have been removed in SQL 2014. So proceed accordingly.
David
David http://blogs.msdn.com/b/dbrowne/

Similar Messages

SCOM 2012 R2 HA design but using SQL 2014 Standard edition

Hi All,
I want to deploy SCOM 2012r2 with a HA design (but have constraints!)
Plan is two management servers with all roles to each (fresh deployment so 2012r2 RU5)
SQL servers need to be 2014 standard edition due to licensing and cost constraints.
Design is to be split between two datacentres that are fibre connected and sub 3ms latency
Plan was to have a Management Server and a SQL server at each location.
Each location has a dedicated SAN but SAN replication is not an option.
What are my SQL options for the DB??
AlwaysOn FCI is not preferable as it gives a single point of failure due to shared storage requirement.
I read Database mirroring is not a supported config but this isn't Microsoft direct info just blog post, is this correct.
Which leaves me with log shipping, is this supported and the best option??
Would be great to get advice on what works well in the field with a contraint of having to use SQL Standard edition!
Thanks
James

Hi,
No additional licenses are needed for management servers or SQL Server technology.
System Center 2012 R2 licensing
http://www.microsoft.com/en-us/Licensing/product-licensing/system-center-2012-r2.aspx#tab=2
Reference:
SCOM 2012 R2 HA options with Server 2012 and SQL 2012
https://gallery.technet.microsoft.com/SCOM-2012-R2-HA-options-540beb95
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]

Downgrade to SQL 2014 Standard edition after "accidental" install of Enterprise?

Hi,
After installing the umpteenth SQL server on autopilot, i realized that i installed a standard edition with an enterprise ISO.... stupid me, and i got my fair share of laughs from my colleagues (and then some) :)
But i was wondering.... since i have not installed or used any Enterprise features, a downgrade should be possible right?
Being a lazy bastard or time efficient nerd (take your pick), i fired up setup again, and i got to this screen.... and i was stumped.... the downgrade path is valid, the rule passed, so why can't i downgrade?
I know i can re-install to get it to work, but why can't i downgrade?
A downgrade also comes in handy sometimes when customers want to downsize a server from Enterprise OLTP to Standard OLTP, or when some stupid yahoo like me installed Enterprise for OLTP DEV / TEST, where Standard is more than enough.
Any ideas anyone?
Theo Ekelmans
The Netherlands

The codebase for the engine is the same; there are no Std or Ent specific service packs.
So why not make it possible....?
This question you should ask to Micrsoft team( I am not aware why they made restriction) . It would be premature for you to comment that 'code base for Stand and Ent are same'. Its not an open source whoes code you can see and can make changes( Like Unix
and Linux )
I am sure if you ask this question to MS they wont give any Geeky reply to you they woudl just say its how we work and have designed.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers
My TechNet Wiki Articles

SQL Server Standard Edition with Sharepoint 2013 Enterprise

Hi there,
I need some help figuring out what will be the ideal SQL Server Standard Edition that can run all features for SharePoint 2013 Enterprise Edition. I ordered CAL licenses for a Sharepoint 2013 Enterprise Server (Supports 500 users). Now I need to find out
if it is worth upgrading SQL server to the following:
Upgrade to SQL Server Standard R2 2012 or upgrade to SQL Server Standard 2014? Basically, I am looking for the pros and cons?
-Esteban
Microsoft manager to programmer: You start coding. I'll go find out what they want ...

Hello,
PowerPivot for SharePoint is a feature available only if SQL Server Enterprise Edition and Business Intelligence Edition is used. Reporting Services of SQL Server Standard has also some limitations that will impact SharePoint 2013.
Additionally, SQL Server Standard Edition do not offer AlwaysON, database snapshots and online index rebuild.
To me, the biggest difference between SQL Server 2012 Standard Edition and SQL Server 2014 Standard Edition is that SQL 2014 Standard now supports 128 GB of RAM. SQL Server 2012 Standard is limited to 64 GB.
https://msdn.microsoft.com/en-us/library/cc645993.aspx#CrossBoxScale
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Can you replicate databases from SQL Server 2014 Enterprise Edition to SQL Server 2014 Standard edition?

Hello,
Can you replicate databases from SQL Server 2014 Enterprise Edition to SQL Server 2014 Standard edition?
Thanks.

Yes, you can replicate from Enterprise edition to Standard edition. The only caveat is Peer-to-Peer Replication requires all nodes to be Enterprise Edition.
Brandon Williams (blog |
linkedin)

Downgrade SQL Server 2008 Enterprise to SQL Server2008 Standard Edition

I would like to know from fourm users, what are the necessary steps I would take care for above mentioned activity and also please let me know best suitable option for Production.
SNS

You can't do in-place downgrade. You need to go with backup -> uninstall ent -> install std -> bring it to same patch -> restore databases approach.
You need to make sure that there is not enterprise only feature used else you can't restore database on standard.
Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
Balmukund's answer above is the Microsoft supported route for doing a downgrade of an instance of SQL Server. However, before you do this, you need to query the sys.dm_db_persisted_sku_fearures DMV in each of your user databases to make certain that
you don't have any Enterprise features in use that would block your ability to restore a database onto Standard Edition.
No matter what you are going to have to do an uninstall and reinstall of the SQL Server instance to downgrade the SKU. However, you can save yourself some time and the headache of trying to restore the system databases if you are careful about what
you do. I have done a couple of SKU downgrades in the past and the easiest way to do it, and I am not saying this is the Microsoft supported way but that it works if done correctly, is to:
Take a good backup of all of your databases (system and user).
Run SELECT @@VERSION and note the specific build number of SQL Server that you are currently on.
Shut down your existing instance of SQL Server.
Copy the master, model, and msdb database files (both mdf and ldf), don't move them copy them, from the current location to a new folder that you mark as readonly.
Uninstall SQL Server from the system.
Reboot the server.
Install SQL Server Standard Edition.
Apply the necessary Service Pack and/or Cumulative Updates to bring the instance up to your previous build number.
Shutdown SQL Server.
Copy the master, model, and msdb database files (both mdf and ldf) from the folder you saved them in to the correct location for the new install and remove the readonly flag from the files, and change the file ACL's so that the SQL Service account has Full
Control over the files.
Startup SQL Server and if you did it correctly it will startup and be exactly where you were before you made any changes, with all of your user databaes online and you should be ready to let applications connect and resume operations.
If you screw something up in the above, you still have your backups and you can run setup to rebuild the system databases and then go about following the Microsoft supported path for restoring the system databases and then user databases into the system
to bring it online. Essentially the file copy is no different that what would occur through attach/detach you are just doing it with system databases which is not supported, but it does work. The key is to have your backups from before you do anything
so you have the supported route available if you encounter an issue. The only issue I have ever had doing this set of steps is that I didn't set the file ACL's correctly and the database engine threw Access Denied errors and failed to start until I fixed
the ACL's correctly. This can save you many hours of frustration and downtime trying to restore everything since the database files are already there and it is just some small copy operations to put them where you need them to be.
Balmukund, feel free to beat me over the head for suggesting a non-supported path. :-)
Jonathan Kehayias | Senior Consultant,
SQLSkills.com
SQL Server MVP | Microsoft Certified Master: SQL Server 2008
Feel free to contact me through
My Blog or
Twitter. Become a
SQLskills Insider!
Please click the Mark as Answer button if a post solves your problem!

Using BizTalk Enterprise Edition 2009/2013 with SQL Server Standard Edition vs Enterprise Edition

Hi All,
I would like to know what are the Drawbacks of using BizTalk Server Enterprise Edition 2009/2013 with SQL Server Standard Edition vs Enterprise Edition.
We are currently using Enterprise Edition.
1) Are there any adverse performance constraints? Microsoft mentions to use SQL Server Enterprise Edition for "Optimal Performance" but does not expand on the topic.
2) Any features missing?
2) Is there a supported way to downgrade SQL Enterprise to Standard for an exisiting BTS Environment?
Thanks!

1) SQL Standard is limited to 4 CPU's and 64GB of memory while Enterprise is 8 CPU and 2TB or memory.
2) The only BizTalk feature dependency on a SQL Enterprise feature is BAM Real-Time Aggrigations which requires Analysis Services RTA.
3) Yes, but it's not a SQL downgrade really, you would move the BizTalk databases:
http://msdn.microsoft.com/en-us/library/aa559835.aspx

Can we use SSRS in sharepoint 2013 standard and sql server standard edition

can we use SSRS in sharepoint 2013 standard and sql server standard edition
MCTS Sharepoint 2010, MCAD dotnet, MCPDEA, SharePoint Lead

Yes you can. You do lose some features:
http://msdn.microsoft.com/en-us/library/cc645993.aspx#Reporting
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.

Sql 2005 standard edition for sql and AS databases with bpc 7.0 sp3 ?

hello
Install guide tells that we must use SQL 2005 Enterprise Edition with BPC except for Reporting Services.
Customer asks wether he could use SQL 2005 Standard Edition for SQL database and Analysis Services ?
Thanks.

Hello Sorin. Two more questions, please:
1) what do you mean by "Also into Application server you need EE because only in this version you have control flow." ?
Is "control flow" "business process flow" new functionality ?
2) On the other hand, I don't think that BPC admin task is able to handle lite or full optimize without an Enterprise Edition Client.
But customer asks wether it is possible to install on application server
- SSIS standard edition for SSIS service
- SSRS standard edition for Reporting Services
- SQL client Enterprise Edition to let BPC admin task handle lite and full optimize properly.
Why all this ? Because Enterprise Edition costs ten times more than Standard Edition and in a multi-server configuration, customer has to buy several SQL Server licenses, one per server running at least one SQL server service. (For example, with SQL,SSIS and OLAP on one server, and SSIS and SSRS running on the application server, customer has to buy two SQL servers licenses).
Thanks. R.

SQL Server Setup Failure 0x84B10001 (SQL 2012 SP2 and SQL 2014 Standard)

I'm having a problem with SQL Server Setup. I had SQL Server 2012 R2 SP1 installed, and the SP2 installer would fail.
I decided to just get SQL Server 2014. The setup (and system configuration checker) for that fails with the same error.
SQL Server Setup failure
SQL Server Setup has encountered the following error:
'.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
Error code 0x84B10001
I found this and other posts about similar problems that point at MSDE being the cause.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/bc9f4949-1b45-427c-aa2b-d2222488a13e/problems-installing-sql-server-2012error-code-0x84b10001?forum=sqlexpress
I definitely had MSDE installed, but I went through the steps to manually remove it and rebooted with no luck.
/* Don Reynolds */

(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserStopServicePrivateConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserStopServicePrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserStopServicePrivateConfig.xsd' loaded
into datastore path '/Datastore/ProductSettings/SqlBrowserStopService/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPublicConfigObject.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPublicConfigObjectDefault.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPublicConfigObjectDefault.xml' validated with schema 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPublicConfigObject.xsd' loaded into datastore path '/Datastore/ProductSettings/Sku/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPrivateConfigObject.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPrivateConfigObjectDefault.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPrivateConfigObjectDefault.xml' validated with schema 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPrivateConfigObject.xsd' loaded into datastore path '/Datastore/ProductSettings/Sku/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPrivateSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPrivateDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPrivateSettings.xsd' loaded into datastore path
'/Datastore/ProductSettings/Repl/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPublicDefaultSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPublicDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPublicDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPublicDefaultSettings.xsd' loaded into datastore
path '/Datastore/ProductSettings/SqlRSSHP/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPrivateDefaultSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPrivateDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPrivateDefaultSettings.xsd' loaded into
datastore path '/Datastore/ProductSettings/SqlRSSHP/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPublicDefaultSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPublicDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPublicDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPublicDefaultSettings.xsd' loaded into datastore path
'/Datastore/ProductSettings/SqlRS/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPrivateDefaultSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPrivateDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPrivateDefaultSettings.xsd' loaded into datastore path
'/Datastore/ProductSettings/SqlRS/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSDBConfigPrivateDefaultSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSDBConfigPrivateDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSDBConfigPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSDBConfigPrivateDefaultSettings.xsd' loaded into datastore
path '/Datastore/ProductSettings/SqlRS/DBPrivate'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPublicSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPublicDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPublicDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPublicSettings.xsd'
loaded into datastore path '/Datastore/ProductSettings/ManagementTools/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPrivateSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPrivateDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPrivateSettings.xsd'
loaded into datastore path '/Datastore/ProductSettings/ManagementTools/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPublicSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPublicDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPublicDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPublicSettings.xsd'
loaded into datastore path '/Datastore/ProductSettings/ManagementToolsAdvanced/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPrivateSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPrivateDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPrivateSettings.xsd'
loaded into datastore path '/Datastore/ProductSettings/ManagementToolsAdvanced/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ControllerPrivateSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ControllerPrivateDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ControllerPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ControllerPrivateSettings.xsd' loaded
into datastore path '/Datastore/ProductSettings/DReplayController/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ClientPrivateSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ClientPrivateDefaultSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ClientPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ClientPrivateSettings.xsd' loaded into
datastore path '/Datastore/ProductSettings/DReplayClient/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPrivateConfig.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPrivateConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPrivateConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterDisk/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPublicConfig.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPublicConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPublicConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterDisk/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPrivateConfig.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPrivateConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPrivateConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterGroup/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPublicConfig.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPublicConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPublicConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterGroup/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPrivateConfig.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPrivateConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPrivateConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterIPAddresses/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicConfig.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterIPAddresses/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePrivateConfig.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePrivateConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePrivateConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/FailOverClusterName/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePublicConfig.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePublicConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePublicConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/FailoverClusterName/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePrivateConfig.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePrivateConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePrivateConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterNode/Private'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterNode/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xsd' loaded into datastore path '/Datastore/ProductSettings/SQLServerSCP/Private'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodesStatusPublicConfig.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodesStatusPublicConfig.xml' loaded into datastore path '/Datastore/ProductSettings/ClusterNodesStatus/Public'
(01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettings.xsd'
(01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettingsDefaults.xml'
(01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettingsDefaults.xml' validated with schema 'Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettings.xsd' loaded into datastore path '/Datastore/ProductSettings/ASSIP/Public'
(01) 2014-07-02 10:52:57 Slp: Completed Action: LoadPackageDatastoreObjects, returned True
(01) 2014-07-02 10:52:57 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:57 Slp: Running Action: InitializeInputSettingStore
(01) 2014-07-02 10:52:57 Slp: Completed Action: InitializeInputSettingStore, returned True
(01) 2014-07-02 10:52:57 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:57 Slp: Running Action: InitializeRoleService
(01) 2014-07-02 10:52:57 Slp: Loading role: SPI_AS_NewFarm
(01) 2014-07-02 10:52:58 Slp: Loading role: SPI_AS_ExistingFarm
(01) 2014-07-02 10:52:58 Slp: Loading role: AllFeatures_WithDefaults
(01) 2014-07-02 10:52:58 Slp: Completed Action: InitializeRoleService, returned True
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:58 Slp: Running Action: ProcessChainerCommandLineArguments
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Setting: WORKFLOW
(01) 2014-07-02 10:52:58 Slp: Value specified: RUNRULES
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: NotSpecified
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Setting: TIMESTAMP
(01) 2014-07-02 10:52:58 Slp: Value specified: 20140702_105236
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Setting: LOGMARKER
(01) 2014-07-02 10:52:58 Slp: Value specified:
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Setting: MEDIASOURCE
(01) 2014-07-02 10:52:58 Slp: Value specified: R:\
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: NotSpecified
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Setting: INSTALLMEDIAPATH
(01) 2014-07-02 10:52:58 Slp: Value specified: R:\x64\setup\
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: NotSpecified
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Setting: ENU
(01) 2014-07-02 10:52:58 Slp: Value specified: True
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Setting: MEDIALAYOUT
(01) 2014-07-02 10:52:58 Slp: Value specified: Full
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Setting: ACTION
(01) 2014-07-02 10:52:58 Slp: Value specified: RUNRULES
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: NotSpecified
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Setting: RULES
(01) 2014-07-02 10:52:58 Slp: Value specified: SCCCheckRules
(01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Completed Action: ProcessChainerCommandLineArguments, returned True
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:58 Slp: Running Action: ProcessMediaChainerConfigFileArguments
(01) 2014-07-02 10:52:58 Slp: Procssing media configuration file R:\x64\setup\..\DefaultSetup.ini.
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Setting: PID
(01) 2014-07-02 10:52:58 Slp: New setting source: ConfigFile; previous setting source: NotSpecified
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------
(01) 2014-07-02 10:52:58 Slp: Completed Action: ProcessMediaChainerConfigFileArguments, returned True
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:58 Slp: Running Action: ProcessChainerConfigFileArguments
(01) 2014-07-02 10:52:58 Slp: Completed Action: ProcessChainerConfigFileArguments, returned True
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:58 Slp: Running Action: ProcessSlipstreamParameters
(01) 2014-07-02 10:52:58 Slp: Completed Action: ProcessSlipstreamParameters, returned True
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:58 Slp: Skipping Action: SetRoleAndUIModeForExpressMedia
(01) 2014-07-02 10:52:58 Slp: Action is being skipped due to the following restrictions:
(01) 2014-07-02 10:52:58 Slp: Condition "IsMediaExpress" did not pass as it returned false and true was expected.
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:58 Slp: Running Action: InitializeRetryHandler
(01) 2014-07-02 10:52:58 Slp: Completed Action: InitializeRetryHandler, returned True
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:58 Slp: Running Action: ExecuteBootstrapProcessInputSettings
(01) 2014-07-02 10:52:58 Slp: Workflow to execute: 'BOOTSTRAPPROCESSINPUTSETTINGS'
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:58 Slp: Running Action: StartSqmSession
(01) 2014-07-02 10:52:58 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2014-07-02 10:52:58 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\120
(01) 2014-07-02 10:52:58 Slp: Sco: Attempting to get registry value CustomerFeedback
(01) 2014-07-02 10:52:58 Slp: SQM Service: Sqm does not have active session.
(01) 2014-07-02 10:52:58 Slp: SQM is opted-out by command line parameter /SQMREPORTING or registry key setting, SQM session is closed
(01) 2014-07-02 10:52:58 Slp: Completed Action: StartSqmSession, returned True
(01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:58 Slp: Running Action: ValidateChainerSetting
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Compute new PID
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Read lcid 1033 from CultureInfo
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: Completed Action: ValidateChainerSetting, returned True
(01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:59 Slp: Running Action: ProcessFeatureCommandLineArguments
(01) 2014-07-02 10:52:59 Slp: ----------------------------------------
(01) 2014-07-02 10:52:59 Slp: Completed Action: ProcessFeatureCommandLineArguments, returned True
(01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:59 Slp: Running Action: ProcessMediaFeatureConfigFileArguments
(01) 2014-07-02 10:52:59 Slp: Procssing media configuration file R:\x64\setup\..\DefaultSetup.ini.
(01) 2014-07-02 10:52:59 Slp: ----------------------------------------
(01) 2014-07-02 10:52:59 Slp: Completed Action: ProcessMediaFeatureConfigFileArguments, returned True
(01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:59 Slp: Running Action: ProcessFeatureConfigFileArguments
(01) 2014-07-02 10:52:59 Slp: Completed Action: ProcessFeatureConfigFileArguments, returned True
(01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:59 Slp: Running Action: ValidateSettingsAgainstScenario
(01) 2014-07-02 10:52:59 Slp: Scenario: RunRules
(01) 2014-07-02 10:52:59 Slp: Completed Action: ValidateSettingsAgainstScenario, returned True
(01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:59 Slp: Running Action: FinalCalculateSettings
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
(01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
(01) 2014-07-02 10:52:59 Slp: Completed Action: FinalCalculateSettings, returned True
(01) 2014-07-02 10:52:59 Slp: Completed Action: ExecuteBootstrapProcessInputSettings, returned True
(01) 2014-07-02 10:52:59 Slp: Completed Action: ExecuteBootstrapAfterExtensionsLoaded, returned True
(01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:52:59 Slp: Running Action: RunRemoteDiscoveryAction
(01) 2014-07-02 10:52:59 Slp: Running discovery on local machine
(01) 2014-07-02 10:53:03 Slp: Error: Action "Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction" threw an exception during execution.
(01) 2014-07-02 10:53:03 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747. ---> Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException:
'.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747. ---> System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
(01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.Throw(Exception e)
(01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Int32 pos, Char invChar)
(01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, Boolean expand, BufferBuilder internalSubsetBuilder, Int32& charCount, EntityType& entityType)
(01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ParseNumericCharRef(Boolean expand, BufferBuilder internalSubsetBuilder, EntityType& entityType)
(01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.HandleEntityReference(Boolean isInAttributeValue, EntityExpandType expandType, Int32& charRefEndPos)
(01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr)
(01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ParseAttributes()
(01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ParseElement()
(01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ParseElementContent()
(01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
(01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
(01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlDocument.Load(XmlReader reader)
(01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
(01) 2014-07-02 10:53:03 Slp:    --- End of inner exception stack trace ---
(01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
(01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(XmlDocument doc, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
(01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
(01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String actionId)
(01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2014-07-02 10:53:03 Slp:    --- End of inner exception stack trace ---
(01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2014-07-02 10:53:03 Slp: Received request to add the following file to Watson reporting: c:\temp\tmpFEEB.tmp
(01) 2014-07-02 10:53:03 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2014-07-02 10:53:03 Slp: Inner exceptions are being indented
(01) 2014-07-02 10:53:03 Slp:
(01) 2014-07-02 10:53:03 Slp: Exception type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException
(01) 2014-07-02 10:53:03 Slp:     Message:
(01) 2014-07-02 10:53:03 Slp:         '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
(01) 2014-07-02 10:53:03 Slp:     HResult : 0x84b10001
(01) 2014-07-02 10:53:03 Slp:         FacilityCode : 1201 (4b1)
(01) 2014-07-02 10:53:03 Slp:         ErrorCode : 1 (0001)
(01) 2014-07-02 10:53:03 Slp:     Stack:
(01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
(01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(XmlDocument doc, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
(01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
(01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String actionId)
(01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2014-07-02 10:53:03 Slp:     Inner exception type: System.Xml.XmlException
(01) 2014-07-02 10:53:03 Slp:         Message:
(01) 2014-07-02 10:53:03 Slp:                 '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
(01) 2014-07-02 10:53:03 Slp:         HResult : 0x80131940
(01) 2014-07-02 10:53:03 Slp:         Stack:
(01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.Throw(Exception e)
(01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Int32 pos, Char invChar)
(01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, Boolean expand, BufferBuilder internalSubsetBuilder, Int32&
charCount, EntityType& entityType)
(01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ParseNumericCharRef(Boolean expand, BufferBuilder internalSubsetBuilder, EntityType& entityType)
(01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.HandleEntityReference(Boolean isInAttributeValue, EntityExpandType expandType, Int32& charRefEndPos)
(01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr)
(01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ParseAttributes()
(01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ParseElement()
(01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ParseElementContent()
(01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
(01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
(01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlDocument.Load(XmlReader reader)
(01) 2014-07-02 10:53:03 Slp:                 at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix,
String namespaceUri, String rootPath)
(01) 2014-07-02 10:53:08 Slp: Watson Bucket 2
Original Parameter Values
(01) 2014-07-02 10:53:08 Slp: Parameter 0 : SQL Server
2014@RTM@
(01) 2014-07-02 10:53:08 Slp: Parameter 1 : Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument
(01) 2014-07-02 10:53:08 Slp: Parameter 2 : System.Xml.XmlTextReaderImpl.Throw
(01) 2014-07-02 10:53:08 Slp: Parameter 3 :
Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException@1201@1
(01) 2014-07-02 10:53:08 Slp: Parameter 4 :
System.Xml.XmlException@-2146232000
(01) 2014-07-02 10:53:08 Slp: Parameter 5 : RunRemoteDiscoveryAction
(01) 2014-07-02 10:53:08 Slp:
Final Parameter Values
(01) 2014-07-02 10:53:08 Slp: Parameter 0 : SQL Server
2014@RTM@
(01) 2014-07-02 10:53:08 Slp: Parameter 1 : 0xDBE3EAAC
(01) 2014-07-02 10:53:08 Slp: Parameter 2 : 0x066FCAFD
(01) 2014-07-02 10:53:08 Slp: Parameter 3 :
0xDF039760@1201@1
(01) 2014-07-02 10:53:08 Slp: Parameter 4 : 0x5539C151
(01) 2014-07-02 10:53:08 Slp: Parameter 5 : RunRemoteDiscoveryAction
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
(01) 2014-07-02 10:53:10 Slp: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
(01) 2014-07-02 10:53:10 Slp: Watson bucket for exception based failure has been created
(01) 2014-07-02 10:53:10 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2014-07-02 10:53:10 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\120
(01) 2014-07-02 10:53:10 Slp: Sco: Attempting to get registry value EnableErrorReporting
(01) 2014-07-02 10:53:10 Slp: WER: Successfully read app consent from registry Software\Microsoft\Microsoft SQL Server\120\EnableErrorReporting=.
(01) 2014-07-02 10:53:10 Slp: WER: Application level consent value '' was mapped to consent status 'WerConsentNotAsked'
(01) 2014-07-02 10:53:12 Slp: WER: Result of the submission:: 'WerReportCancelled'
(01) 2014-07-02 10:53:12 Slp: WER: Submitted 1 of 1 failures to the Watson data repository
(01) 2014-07-02 10:53:12 Slp:
(01) 2014-07-02 10:53:12 Slp: ----------------------------------------------------------------------
(01) 2014-07-02 10:53:12 Slp:
(01) 2014-07-02 10:53:12 Slp: Error result: -2068774911
(01) 2014-07-02 10:53:12 Slp: Result facility code: 1201
(01) 2014-07-02 10:53:12 Slp: Result error code: 1
(01) 2014-07-02 10:53:12 Slp: SQM Service: Sqm does not have active session.
/* Don Reynolds */

Limitations for upgrading SQL server database engin from SQL 2008 R2 enterprise edition to SQL 2014 enterprise edition

Dear All,
we are planning to upgrade SQL Server 2008 R2 Enterprise edition to SQL Server 2014 Enterprise edition.
please suggest the limitations for the up gradation.
Thanks in Advance
Vineet Srivastava
NIIT Technology Ltd.
New Delhi , India

Hello,
Please note that we have 2 Enterprise Editions now:
(1) Enterprise Edition with Server + Client Access License (CAL) and (2) the Enterprise Edition licensed by core. “Enterprise Edition with Server + Client Access License (CAL) based licensing (not available
for new agreements) is limited to a maximum of 20 cores per SQL Server instance. There are no limits under the Core-based Server Licensing model”. Source:
https://msdn.microsoft.com/en-us/library/ms143760(v=sql.120).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Backup Encryption in SQL Server Standard Edition

Hello,
I need experts advice on Backup encryption options available in SQL Server 2008 R2 Standard Edition. I know TDE is available, but only in Sql Server 2008 R2 Enterprise edition. But we are using Standard Edition.
Thanks

Password protect is not the same thing as encryption - the data is still clear text. This is what Books Online for SQL Server 2008 say about the password option:
"The protection provided by this password is weak. It is intended to prevent an incorrect restore using SQL Server tools by authorized or unauthorized users. It does not prevent the reading of the backup data by another method or the replacement of the password.
This feature will be removed in the next version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature. "
And in 2012 this option is indeed removed from the backup command.
Tibor Karaszi, SQL Server MVP |
web | blog

Contribute attempting to run SQL code in edit mode

On some PHP sites that using PHP includes and make MySQL
calls, we have seen the following:
When a user edits a page, they see a PHP error saying that
the connection to the MySQL database couldn't be made.
Why in the world is Contribute executing PHP code in an
include? To get around this, we've had to add code around the SQL
connection which simply echoes (with PHP) "unable to connect" if a
connection can not be made.
But, on other sites, we've used echo to see if PHP is indeed
executing in edit mode of Contribute, but it doesn't echo.

On some PHP sites that using PHP includes and make MySQL
calls, we have seen the following:
When a user edits a page, they see a PHP error saying that
the connection to the MySQL database couldn't be made.
Why in the world is Contribute executing PHP code in an
include? To get around this, we've had to add code around the SQL
connection which simply echoes (with PHP) "unable to connect" if a
connection can not be made.
But, on other sites, we've used echo to see if PHP is indeed
executing in edit mode of Contribute, but it doesn't echo.

SQL 2014 Always On Availability Groups

It appears to be working. I've attached a picture of the role that was created when I was finished configuring WSFC. Is there something that would I can check that would give me a definitive answer?

I am testing SQL 2014 availability groups and I have run into a snag. I setup a win2k8 r2 DC and two windows 2012 R2 servers running SQL 2014 standard. I setup failover clustering for the two SQL servers. In SQL Management Studios I have setup the availability group and everything seems to have been successful. except when the wizard completes I get an error Creating availability group listener resulted in an error.....Error 41009.The AG seems to be working I can connect to the AG in SSMS using the listener name. But in the Availability Group Listener section there is no listener setup. Also the databases also seem to be read only if I connect thru the listener name. The AD computer account seems to be setup correctly. I am just unable to create the listener in SQL. Is there a security permission in SQL that I could have missed. Any...
This topic first appeared in the Spiceworks Community

Issue of Text Qualiffier after upgrading to SQL Server 2014 Standard

Hi,
I'm facing an issue of Text Qualifier after I upgrading my system to SQL Server 2014 Standard Edition (Microsoft SQL Server 2014 - 12.0.2000.8 (X64)
   Feb 20 2014 20:04:26
   Copyright (c) Microsoft Corporation
   Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
I have a csv file with format: Text Qualifier is double pipes ||, Vertical Bar (|) as Column Delimiter and Row Delimiter is CRLF.
For example file:
||Col1|||||Col2||
||ABC|||||XYZ||
This file is working OK in SQL Server 2008 R2 (SP2) but it does not work in SQL Server 2014. It raised error message while running.
Error: An error occurred while skipping data rows.
[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on MediaAgencyGroup returned error code 0xC0202091. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure
code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
Any suggestion here?
Thanks,

Yes
There's a difference in the way text qualifiers are parsed from 2012 onwards
see
http://www.proactivespeaks.com/2012/06/22/my-5-favorite-sql-2012-ssis-features-so-far/
http://blog.concentra.co.uk/2013/06/24/ssis-2012-flat-files-now-greatly-improved-but-are-they-good-enough-yet/
ANyways my preferred way to do this is as below
http://visakhm.blogspot.in/2014/06/ssis-tips-handling-embedded-text.html
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Does a Hyper-V VM running SQL 2014 Standard Edition support Hot Add Memory?

Similar Messages

Maybe you are looking for