Moving SCCM 2012 R2 SQL 2014 Database to New Server

Greetings,
I have a SCCM 2012 R2 server with SQL 2014 installed which has been upgraded from SQL 2008 R2. My goal is to separate the SCCM and SQL servers. I am aware that SCCM only supports SQL 2014 if it has been upgraded on new installs, but after installing
SQL 2014 on a new server and importing the database I get an error from the Configuration Manager Setup stating that I must upgrade the SQL server before I can modify the SQL Server configuration.
Does this mean I need to install SQL 2008 or 2012 on the new DB server and from there upgrade to SQL 2014?

Thank you for your reply. We have been having several issues with our current server, and have had performance issues with SQL and SCCM installed on the same server mainly during OSD deployments to several machines at the same time. These servers
wouldn't necessarily need to be separated since we can allocate more resources, but the overall goal is to move our primary site server to a new server running Server 2012 R2 (current server is 2008 R2).
I have tried the site recovery option in the installer where you run the SCCM backup and restore maintenance task and I have renamed the new server to the name of the old server. If I understand correctly, this is the correct method of switching out
a site server machine? I experience the same error as my original post when trying this, but I will try the hotfix Torsten provided as this seems to be the issue I'm having.
Thank you.

Similar Messages

SCCM 2012 - Migrating SQL components to cluster including Reporting Services

Current SCCM 2012 environment:
- CAS with database on remote SQL (non-cluster) server in a named instance - SQLSRV\CASINST
- SQL Reporting Services in also installed in the SQLSRV\CASINST instance
- The SCCM Reporting Services Point role is installed on the SQLSRV\CASINST instance
- Primary server with database on the same remote SQL (non-cluster) server in a different named instance - SQLSRV\PRIINST
Now I would like to move all of the database stuff to an existing SQL 2008 R2 cluster (SQLCLUSTER) and decommission the SQLSRV server. SQLCLUSTER already exists and the default instance is already in use (for other applications) for both database engine
services and reporting services.
From my understanding:
- SQL 2008 R2 Reporting Services cannot be clustered
- Best practise is to install Reporting Services Point on a remote site server rather than a CAS server
- SSRS can be installed on nodes in SQL cluster as standalone installs - with the caviat that they don't use instance names already in use
So I plan to:
- Move CAS database to new named instance on cluster eg SQLCLUSTER\CASINST
- Move primary database to new named instance on cluster eg SQLCLUSTER\PRIINST
- Install SQL Reporting Services on one of the cluster nodes (unclustered) using a named SSRS instance eg SQLCLUSTERNODE1\SCCMREPORTING
- This article points out some interesting results of not have a default instance - http://magalhaesv.wordpress.com/2012/05/24/system-center-configuration-manager-x-sql-server-reporting-services-x-wmi-english-version/
- Move Reporting Services Point from SQLSRV\CASINST to the cluster node eg SQLCLUSTERNODE1\SCCMREPORTING
I have read on some forums (eg
http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/40ad0cb4-a464-4576-b824-957ed6e1b2e2) things like '' If you have an app like SCCM that requires a default instance of SSRS, you are out of luck if your cluster already has a default
instance of the database engine.", but I cannot find this anywhere in Microsoft documentation. From the MS documentation (http://technet.microsoft.com/en-us/library/7fd0d4f5-14e0-4ec7-b2e6-3b67487df555#BKMK_InstallReportingServicesPoint)
I understand that as long the current user has read access to WMI on the remote site server where SQL Reporting Services is installed, you should be able to use a named instance for SQL Reporting Services and successfully install the Reporting Services Point
on it.
So a 2 part question:
- Anybody see any obvious flaws in my high level plan?
- Anybody care to comment on the SCCM requiring a default instance of SSRS?
My Microsoft Core Infrastructure & Systems Management blog -
blog.danovich.com.au

Yes, I know this is an old post, I’m trying to clean them up, Did you figure this out, if so how?
http://www.enhansoft.com/
Hi Garth,
Yes we moved the DBs and RS as outlined above. As expected, we needed to have a default instance of RS because otherwise the SCCM console doesn't see the Reporting Services instance when you try to deploy the Reporting Services site role.
So the above plan worked.
My Microsoft Core Infrastructure & Systems Management blog -
blog.danovich.com.au

Trouble connecting to SQL 2014 Database using Power Query

I am trying to connect to a SQL 2014 Database using Power Query. My connection string requires that I set the "Application Intent" setting to a value of "readonly", The connection parameter is required by SQL 2014 because of
the failover cluster configuration.
I have successfully been able to connect via PowerPivot with the following connection string:
Provider=SQLNCLI11;Data Source=<Server>;Persist Security Info=False;Integrated Security=SSPI;Initial Catalog=<DB>;Application Intent=readonly
I cannot seem to find the correct syntax to connect via SQL 2014. This is the syntax that I have been attempting:
Sql.Database("<Server>", "<DB>",[Application Intent=readonly])
Is this currently supported?
Thanks, Barbara

It's not yet, I'm afraid, but it's something we're aware of and have vague plans to address :/.

MOVE REPLICATION DATABASE TO NEW SERVER

WE HAVE A PRODUCTION DATABASE THAT WORK'S AS REPLICATION FROM 9 DATABASES, WE ARE GOING TO MOVE DATABASE TO NEW SERVER.
AS DATABASE IS PRODUCTION, WE CAN NOT STOP SERVICES. WE THINK TO CREATE A NEW DATABASE ON NEW SERVER, IMPORT DATA FROM PROD. DATABASE. SIZE APROX 100GB.
QUESTION:
I NEED TO KNOW HOW I CAN STOP SERVICES SHORT TIME. TO CHANGE TO SNEW SERVER.
THANKS FOR YOUR SUGGESTIONS

Здравствуте Ivan.
Before i would do anything like this i would make sure that i have a good valid backup (just in case!).
I would check all the applications that are currently conencting to your ORacle and make sure they are all conneting 'by name' not the IP. Or and then i would check DNS server (make sure nslookup is working) to makesure that everything resolves correctly after the moving DB to another machine.
Then check that the oracle_home etc are in the same directory and check that all paths etc in the configurations are the same.
Hope this helps
Kind Regards

Migrating MySQL database to new server

I'm rebuilding a server for a client and I need to migrate the MySQL database off of the old server onto the new. I'm going from Server 10.5.4 to Server 10.5.4. I tried just taring the old database location at /var/mysql and untaring it to the new server at the same location and started the MySQL service, but it service won't start properly.
I get an error in the MySQL Admin Log file that says that the "MySQL daemon startup timed-out"
After looking at the database files, they appear to have the old server name included in their names, and there is a pid file that is specific to the server.
Is there a process for exporting/importing the MySQL databases so I can get them installed on the new server?
Thanks.

So I'll reply to my own question so the answer is documented.
I used the following command it export all the database from the old server:
mysqldump -u username -ppassword --all-databases > alldump.sql
username is the name of the admin user, usually root
password is the admin password, make sure there is no space between the -p and the password. So if the password is "twit" the option is -ptwit
And the two -- are needed in the --all-databases option
Copy the alldump.sql file to the new server and run the following command to import all the databases:
mysql -u username -ppassword < alldump.sql
Be sure to set the admin password in Server Admin and start the MySQL service before importing.
That's it.

Move Owb database to new server

Hi,
We are going to move our Owb (9.2.0.2.8) database to a new server. The nodename isn't going to change only the ip-address will change. The OS will be the same.
The steps will be:
1) install Owb on new server
2) copy database to new server
Is there some other step we'll need to take?
regards,
Ivan

Здравствуте Ivan.
Before i would do anything like this i would make sure that i have a good valid backup (just in case!).
I would check all the applications that are currently conencting to your ORacle and make sure they are all conneting 'by name' not the IP. Or and then i would check DNS server (make sure nslookup is working) to makesure that everything resolves correctly after the moving DB to another machine.
Then check that the oracle_home etc are in the same directory and check that all paths etc in the configurations are the same.
Hope this helps
Kind Regards

Migrate Mirror Database to New Server

Hi,
I need to migrate my SQL server Mirror Database to
a new server. my current setup is as below
1. server A principal (192.168.1.100)
2. server B Mirror (192.168.1.200)
now i have a new server (Server C) to replace server B as below
1. server A principal (192.168.1.100)
2. server C Mirror (192.168.1.300)
my question is how to migrate mirror db to new server without any affect or downtime on principal server, please share idea/experience for above.
note: SQL SERVER 2008R2 EE(64BIT), Win2008R2 EE 64bit.
Regard
Faisal Wahid

Thanks for your quick response.
Is it possible something like in oracle (pardon as i am oracle DBA not sql server guy),
(Oracle Steps to migrate standby(mirror) db to new server)
1. Pause replication on primary(principal)
2. Move standby(mirror) database files to new server(using copy/rman/etc).
3. Update connection information (TNS in oracle) on primary(principal) to point new server.
4. Start replication on primary(principal).
the above steps will simply migrate the standby(mirror) database to new server,
can we do something like above in sql server?

Recovering andrestoring of database in new server after current server fail

Hi,
If we have a disaster ,where the Database server has gone and we can not use it again.
1) We do not have dataguard.
2) We have rman backup file of 2 days before (Full database backup). Rman backup with nocatalogue
3) Flashback log files of 2 days back
3) Archive log till yesterday
4) Export file of morning.
Can we be able to restore and recover our database in new server
if yes then how.
Because RMAN Backup has its DBID and the new Oracle software which i install on new server will be installed with new ID.
Please help me understanding this thing (About target database)
Regards

First of all, you should install the software on the server only, you should NOT create a database.
As you can restore a database to a new host (and this is documented), you won't have any problems. That is, if you don't create a database during installation, and read up on recovery.
I wonder: why do all those anonymous users always can't be bothered to read the documentation, and ask others to paraphrase it for free?
Sybrand Bakker
Senior Oracle DBA

SCCM 2012 R2 SQL Database Upgrade Fails : Setup cannot upgrade the ConfigMgr database. Contact your SQL administrator.

Hi Friends,
We have planned to upgrade our SCCM 2012 SP1 infrastructure to SCCM 2012 R2 so we have setup test environment to test SQL database upgrade before doing same in production.
But while testing SQL database upgrade on test machine, it is getting failed with below error.
ConfigMgrSetupWizard.log
ConfigMgrSetupWizard Verbose: 1 : Scripted setup failure handling callback called. Failure: 29.
ConfigMgrSetupWizard Verbose: 1 : Received error [Setup cannot upgrade the ConfigMgr database. Contact your SQL administrator.] from native code.
ConfigMgrSetup.log
ERROR: SQL Server error: [23000][2627][Microsoft][SQL Server Native Client 11.0][SQL Server]Violation of PRIMARY KEY constraint 'ContentDistribution_PK'. Cannot insert duplicate key in object 'dbo.ContentDistribution'. The duplicate key value is (921). :
tr_ContentDistributionNotification_insert
ERROR: Failed to execute SQL Server command: ~-- ~-- Rebuild ContentDistribution tables ~-- ~IF (EXISTS(SELECT TOP 1 1 FROM dbo.SMSData WHERE SMSBuildNumber <= 7900) AND dbo.fnIsSecondary() != 1) ~BEGIN ~ exec spRebuildContentDistribution
@TruncateTables=0 ~END
Failed to create process of SetupWpf.exe.
Can anyone please help to get this resolved.
Thanks.

We found out that there were duplicate entries in the PkgStatus_G and the PkgServers_G tables in the SCCM DB. We identified them, deleted them , and then we were able to run the /TESTDBUPGRADE command and it went through fine. We performed
all of this on a COPY of the PROD DB and then moved the changes in PROD. Hope this helps someone.
- Dave

SCCm 2012 : Move SQL Database

Hi
I have root domain (domain A) and child domain (B).
I install SCCM 2012 in domain A and use SQL 2012 cluster on domain B. I have a problem with a firewall. I install a new cluster SQL 2012 in root domain (Domain A).
My SCCM use: MP, DP, SUP, WSUS, Deployment Application, Deployment packages, Deploy Hotfix.
My question: It's possible to move SQL 2012 database (SCCM and WSUS) in domain B to domain A? and reconnect SCCM 2012 to database.
Thanks

As long as the computer account is a local admin of the SQL server (of every node as you're talking about a cluster) it should move just fine, especially considering you are moving OUT of the trusted domain and into the same domain.
Simply move the database then re-run SCCM setup. When you do one of the first options you'll get is if you're installing into a new site or "perform site maintenance". Within in that category should be an option to connect SCCM to a
new database, which will do all the work for you.
Quick warning: in the past when using that option I've seen cases where roles have re-installed after I changed the site database, usually the MPs (I'm guessing because they need to reconnect?). So hop into monitoring and watch your logs after
doing this to make sure everything "Settles down".

Reports not Generated after moving SCCM 2012 SP1 DB on SQL 2012 SP1 cluster

Hi all,
i have moved my SCCM 2012 SP1 DB on SQL 2012 SP1 Failover Cluster,this cluster is a two node cluster.the DB was moved fine and the DB configuration in SCCM Site maintenance was also done successfully.After the migration process,SCCM was working fine created
few collections & packages, then checked the DB on cluster & they were updated successfully.
but when i tried to install report server on my SCCM machine,again there was no instance displayed after entering the cluster name.
I searched this & come across this post :-
http://social.technet.microsoft.com/Forums/en-US/configmanagergeneral/thread/4479e73e-8a19-4c7e-9418-b36770656b9b/
which says to install report server on the cluster node machine which is currently running the Reporting Service.I tried to install the report server & the instance was detected this time.it was installed successfully.
But when i tried to generate reports I got this error :-
Permissions are fine as i have added SCCMadmin & sccm machine in the local admin of both the nodes.
Please Help.
Thanks,
Pranay.

Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
If you look at your second screenshot the Remote errors is not enabled. Use this blog to enable them.
http://www.enhansoft.com/blog/enabling-remote-errors-in-sql
If changing the data source on the report fixed it for a single report. It means that your shared Datasource is having problems. Reset the username and password within CM12 console and this should fix it for every report.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCCM 2012 and SQL 2008 R2 Sync problems

Hi
I installed 2 servers for SCCM 2012:
-1 with SCCM 2012, FEP, WSUS console admin
-1 with SQL Server 2008 R2 complete install, WSUS complete install
When I made or the system mades the synchronization, it shows this error in SMS_WSUS_SYNC_MANAGER:
Error 6703:
WSUS Synchronization failed.
Message: Failed to sync some of the updates.
Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates.
And in the wsyncmgr.log appears:
sync: SMS synchronizing updates, processed 3336 out of 3368 items (99%), ETA in 00:00:06 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:14:11.663+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3360 out of 3392 items (99%), ETA in 00:00:06 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:15:11.669+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3383 out of 3415 items (99%), ETA in 00:00:07 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:16:13.206+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3412 out of 3444 items (99%), ETA in 00:00:07 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:17:14.152+300><thread=4640 (0x1220)>
Synchronized update 3a572bd0-5976-4abc-b2d8-955008c5466f - Definition Update for Microsoft Security Essentials - KB972696 (Definition 1.131.558.0). $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:17:18.227+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3446 out of 3463 items (99%), ETA in 00:00:04 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:18:14.400+300><thread=4640 (0x1220)>
Synchronized update 3eeb75c2-81aa-4cc0-9b7a-237a6a0bf737 - Definition Update for Microsoft Security Essentials - KB2310138 (Definition 1.131.574.0). $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:18:47.964+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3482 out of 3484 items (99%), ETA in 00:00:00 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:19:15.587+300><thread=4640 (0x1220)>
Synchronized update 74e86346-9384-4304-9625-2c865738c552 - Definition Update for Microsoft Endpoint Protection - KB2461484 (Definition 1.131.574.0). $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.659+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3508 out of 3508 items (100%) $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.662+300><thread=4640 (0x1220)>
Sync failures summary: $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.664+300><thread=4640 (0x1220)>
Failed to sync update 1ba2d28f-75fe-49d7-9cb4-cd39b8706f48. Error: Failed to get SQL connection. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.RemoveUpdate $$<SMS_WSUS_SYNC_MANAGER><07-24-2012
09:20:05.666+300><thread=4640 (0x1220)>
Failed to sync update 8a042978-e6d7-4ae6-b3ab-687d8f9bcd9c. Error: Failed to get SQL connection. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.RemoveUpdate $$<SMS_WSUS_SYNC_MANAGER><07-24-2012
09:20:05.669+300><thread=4640 (0x1220)>
Failed to sync update a3aff37b-ad3b-4dde-9464-767a516c76e5. Error: Failed to get SQL connection. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.RemoveUpdate $$<SMS_WSUS_SYNC_MANAGER><07-24-2012
09:20:05.671+300><thread=4640 (0x1220)>
Sync failed: Failed to sync some of the updates. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.421+300><thread=3536 (0xDD0)>
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=GDVSCCM1.gdar.local SITE=CRP PID=1908 TID=3536 GMTDATE=mar jul 24 14:20:06.423 2012 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates"
ISTR1="Failed to sync some of the updates" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.425+300><thread=3536 (0xDD0)>
Sync failed. Will retry in 60 minutes $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.501+300><thread=3536 (0xDD0)>
Setting sync alert to active state on site CRP $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.503+300><thread=3536 (0xDD0)>
Updated 173 items in SMS database, new update source content version is 36 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.526+300><thread=3536 (0xDD0)>
Set content version of update source {6A4B4446-1B80-4CF4-838D-405D3847A8E3} for site CRP to 36 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.572+300><thread=3536 (0xDD0)>
Sync time: 0d00h19m46s $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.575+300><thread=3536 (0xDD0)>
Wakeup by SCF change $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 10:00:06.651+300><thread=3536 (0xDD0)>
Next scheduled sync is a retry sync at 24/07/2012 10:20:06 a.m. $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 10:00:11.940+300><thread=3536 (0xDD0)>
Why is this behavior?
Thanks
Doc MX

Hi
Today I think I discovered what was the problem:
I used an user in the domain for deploying the role of SUP, but I forgot to put that user in the group of SQL Admins of the SQL Server.
I done that and after reseting the servers, the error for sync with SQL didn't appear again, al least from this morning until now, before this change every hour showed the error 6703.
Thanks to all for your comments.
Doc MX

SCCM 2012 R2 SQL Errors

I am getting following errors in SCCM 2012 R2 console since today!!!
Any ideas:
Microsoft SQL Server reported SQL message 266, severity 16: [25000][266][Microsoft][SQL Server Native Client 11.0][SQL Server]Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 1, current count
= 0. : sp_addrolemember
Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information.

Parvinder,
Check the link in that thread. The resolution being the following:
'Hi guys,
I have just fixed this issue in our environment a few minutes ago. I had exactly the same issue. The problem relates
to the computer record as you described. The line:
<10-27-2009 12:20:45> ***SqlError: [42000][15410][Microsoft][ODBC SQL Server Driver][SQL Server]User or role 'DOMAIN\SERVER1$'
does not exist in this database. : sp_addrolemember
is the give away.
I went in to the SQL Management Studio, opend the SCCM database and removed the 'DOMAIN\SERVER1$' record. In my case
the problem was becasue a Branch DP server had been renamed but the DB login still hadt he old server name. Removing the OLD server login record from the databse and the main SQL security database and readding it using the NEW name resolved the problem.
When you re-add the server name make sure that you give the login the correct database rights, e.g. if it is a PXE Service
Point it will need that database right again. It is best to check the user rights for the computer and note the rights down before you remove and re-add it.
After this I re-ran the SETUP.EXe for SP2 and it went through perfectly.
Hope this helps.
Nathan
NSutton'
Cheers
Paul | sccmentor.wordpress.com

XML errors when running specific reports in SCCM 2012, using SQL Server 2008 R2 Reporting Services

I've posted this to the SCCM 2012 forum and only received one response so far that states that this is a known issue that has been discussed before and isn't easy to fix; I was not given any actual solution either. Since this involves SSRS I
thought I would try my luck here as well.
I'm having almost exactly the same problem as is referenced in this article: http://social.msdn.microsoft.com/Forums/uk/sqlreportingservices/thread/587a3319-bc54-4d30-bb3f-bb90a0c6ec50.  When
I try to run either of these reports (Computers with specific software registered in Add Remove Programs; Count of instances of specific software registered with Add or Remove Programs) I receive the XML error shown in the attached screenshot. I'm fairly
sure the problem is the same as the other admin was experiencing and I just need to remove the unprintable characters (of the application name) from the dbo.v_Add_Remove_Program column.
The error references 0xFFFF but I could not find what that exactly translates too, other than it appears to be at the end of the spectrum for Unicode characters. I used the following sql query to search for the 0xFFFF entry, but no results were found:
use CM_UV2
Select distinct
CHARINDEX(cast(0xFFFF as varchar(1)),DisplayName0),
DisplayName0
from
dbo.v_Add_Remove_Programs
Where
CHARINDEX(cast(0xFFFF as varchar(1)),DisplayName0) > 0
When I used the original hex value of 0x28 I get plenty of results returned with "(" in them so the query seems sound. One of the articles I was searching mentioned running the query manually using the Management Studio and looking for strange characters
there but I'm not sure how to do that.
Basically I just need help finding the offending character and removing it. I also need to be able to replicate this for other strings as this looks like an error that will reoccur whenever any new software appears that has weird encoding in the title.
Thank you in advance for any help given.
Über Random

Hi Uber,
This is a known issue that error occurs when running report "Count of instances of specific software registered with Add or Remove Programs" due to non-printable characters for XML. Based on internal research, the hotfix for this issue will be
included in the System Center 2012 Configuration Manager Service Pack 1.
As a workaround, you can remove the nonprintable character populated into the report parameter by referring to the following KB article:
http://support.microsoft.com/KB/914159
Hope this helps.
Regards,
Mike Yin
Mike Yin
TechNet Community Support

Question on Quorum : Windows Server 2012 R2 + SQL 2014 AlwaysOn AG

OS on all nodes : Windows Server 2012 R2
SQL on all nodes : SQL Server 2014 CU2
2 cluster nodes in primary data center and AlwaysOn AG doing Sync Transfer between these nodes with auto failover.
2 cluster nodes in DR data center(Different subnet) and AlwaysON AG doing an Async Transfer between primary replica and these nodes with manual failover.
As this is a multi sub-net cluster we are giving DR nodes 0 vote. 2 nodes on primary DC has votes and a file share on the primary DC has a vote.
If the primary DC is gone,then should we re-assign node votes to the 2 nodes in DR site and again manually configure a file share witness and give it a vote?
Whats the best strategy here? Any recommendation is highly appreciated.
Thank you,

Anup,
Think if we have network issues between Primary DC and DR DC. DR node might think…Hey, I’m the only one running now. I can take all the resources. We do not want nodes in the secondary site to contribute to a decision to take the cluster offline
when there is nothing wrong with the primary site. Do you mean to say Dynamic Quorum is smart enough to handle this situation?
Is it smart enough on it's own? No. That's why someone has to determine which site they want to stay up.
If you're using dynamic quorum, a new property was introduced called "LowerQuorumPriorityNodeID" which is set at the cluster level. Give it the node of one and only one of the secondary site servers. Set a fileshare witness (if possible) as the
odd vote and make sure both sites can see it equally well. Set this property on the cluster for a node on the secondary site.
http://technet.microsoft.com/en-us/library/dn265972.aspx#BKMK_TieBreak
Assume that the fileshare goes down and you have 2 nodes at the local site and 2 nodes at the DR site. Suddenly, communicates between the two are severed. If you have dynamic quorum set and the property I mentioned above, the secondary site will shut down
and the local site will stay up as the secondary site is set for a lower precedence.
Please note, the only reason I brought this up was because you're on Windows Server 2012R2 as this is when it was first introduced.
-Sean
Sean Gallardy | Blog | Microsoft Certified Master

Moving SCCM 2012 R2 SQL 2014 Database to New Server

Similar Messages

Maybe you are looking for