SCCM 2012 R2 Uprade - Database Concerns

I recently completed the R2 upgrade process on my production environment. Everything appeared to complete successfully. No errors, warnings, or issues aside from this RBAC mishap -
SCCM 2012 R2 Reporting error
After some further usage I'm finding some inconsistencies in my reporting data. Here's an example:
A software deployment went out last week to my users. This was a simple application upgrade, moving from 1 version to the next.
On multiple computers I can see the deployment was received and installed successfully. If I open Programs and Features I can see the software version has been updated.
From there I open the ConfigMgr console and fire up resource explorer. On multiple computers I can see a recent software scan has picked up the new software and it is reflected in resource explorer.
Now comes the DB issue - I run a manual DB query using the ADD_REMOVE_PROGRAMS table and it consistently shows me the outdated software version. This table is giving me incorrect data. Here's an example of the query I'm using:
SELECT dbo.v_R_System.Name0, dbo.v_R_System.User_Name0, dbo.v_GS_ADD_REMOVE_PROGRAMS.DisplayName0,
dbo.v_GS_ADD_REMOVE_PROGRAMS.Version0
FROM dbo.v_R_System INNER JOIN
dbo.v_GS_ADD_REMOVE_PROGRAMS ON dbo.v_R_System.ResourceID = dbo.v_GS_ADD_REMOVE_PROGRAMS.ResourceID
WHERE (dbo.v_GS_ADD_REMOVE_PROGRAMS.DisplayName0 LIKE N'%Symantec Enterprise Vault%') AND (dbo.v_R_System.Name0 LIKE N'%testcomputer')
Is there something I'm missing? Why would resource explorer have accurate data and the database be returning outdated info? Appreciate any insight. Thanks!

@Idan
Great point! I checked my last hardware inventory and it was back in December! Yikes! I pulled up my workstation policy and got hit with an ugly error as reported in
this thread. At the moment I'm rebuilding my workstation policy and will see if that resolves hardware inventory.
@ Garth
The application I'm reporting on is 32-bit. This is primarily why I didn't expand to include 64-bit programs.

Similar Messages

  • 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 moving site Database server from SQL 2008 R2 cluster to 2012 cluster

    Hello,<o:p></o:p>
    Using the SCCM 2012 setup, I get
    the following errors and then it eventually fails……I’ve been uninstalled and
    installed SQL native client .....still unable to move SQL database,i get this error:<o:p></o:p>
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS. Configuration Manager Setup 25/02/2015 21:01:03 8624 (0x21B0)
    INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure Configuration Manager Setup 25/02/2015 21:01:03 8624 (0x21B0)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted. Configuration Manager Setup 25/02/2015 21:01:07 8624 (0x21B0)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection Configuration Manager Setup 25/02/2015 21:01:07 8624 (0x21B0)
    I know that the problem is related to a certificat issue but i didn't arrived to resolve it.

    Have a look at this post (pay special attention to the comments):
    http://blogs.technet.com/b/configurationmgr/archive/2013/04/02/how-to-move-the-configmgr-2012-site-database-to-a-new-sql-server.aspx
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • SCCM 2012 Moving the Database to Another Drive

    Due to space constraints I need to move my SCCM 2012 R2 database to another drive on the same system(server). I will run preinst/stopsite command to stop all sccm services, but wanted to know if I could copy and move the DB and Log files to their
    new drive location, instead of performing a SQL backup and restore? We are currently running SCCM 2012 R2 with SQL 2012 SP1 CU4 as our backend database.
    Thanks,
    -Bern
    

    you may have already seen these posts... worth a quick look:
    http://social.technet.microsoft.com/Forums/systemcenter/en-US/3462715c-d1b7-4f1b-b5f2-1f35235e4179/move-sccm-database-to-another-drive?forum=configmgradminconsole
    http://support.microsoft.com/kb/2709082
    http://damatisystemcenter.com/2013/05/23/moving-sccm-2012-sp1-database-to-new-folder/

  • 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".

  • SCCM 2012 MP - Site Database Server Without Valid Certificate fail

    When we just imported the 2012 Management Pack we cant get this monitor back to green state:
    Site Database Server Without Valid Certificate (Database Certificate Validity Monitor)
    But we have a valid Certificate, so i dont know what this monitor reacts on.
    This info is gathered from Alert Context on the Alert:
    < DataItem type =" MOM.RegistryData " time =" 2013-05-29T15:15:55.0774480+02:00 " sourceHealthServiceId =" 79B707F7-327F-214F-02FD-8523D5BB9141 " >
    < Values >
    < Severity VariantType =" 19 " > 3 <Severity>
    < State> VariantType =" 19 " > 3332 </State>
    </ Values>
    </ DataItem>
    Now what?
    /Maekee

    Hi,
    Regarding the alert, please refer to the following page to check it:
    Database Certificate Validity Monitor Monitor
    http://mpwiki.viacode.com/default.aspx?g=posts&t=145897
    Thanks.
    Nicholas Li
    TechNet Community Support

  • SCCM 2012 monitoring

    Hi!
    We deploy SCCM 2012 SP1 with database on the SQL Server cluster. We monitore SQL Server by SCOM 2012 SP1 so, both node FQDN are displayed in SCOM console.
    SCCM display virtual SQL cluster name as FQDN and both SQL cluster nodes as NetBIOS names in its console.
    When we import SCCM management pack into SCOM, it adds 2 SQL Server cluster node as 2 NetBIOS names, so we have 4 objects for SQL cluster nodes in SCOM console:
    1. 2 "old" objects with FQDN names which have status "Available"
    2. 2 "new" objects with short NetBIOS names which have status "Not monitored" and are classified in SCCM views as "ConfigMgr Site Database Server"
    Can I "merge" these 4 objects into 2 "old" monitored objects and can SCOM display all SCCM roles (including database servers) as monitored?

    I have this same problem, except with SCCM 2012 R2 / SCOM 2012 R2. It's quite annoying, as it prevents proper monitoring of the site database.

  • SCCM 2012 SQL DB Migration

    Hi
    Can someone advice me if I can move my SCCM 2012 R2 SQL Databases (1 CAS and 2 Primary Site Server DB's) having version SQL 2008 R2 to SQL 2012?
    As per this blog, looks like we can....Do I need to take any additional checks?
    http://blogs.technet.com/b/configurationmgr/archive/2013/04/02/how-to-move-the-configmgr-2012-site-database-to-a-new-sql-server.aspx
    Thanks and regards
    Guru
    Gururaj Pai

    It can be done.  I'd try it in a lab first though. 
    Torsten Meringer | http://www.mssccmfaq.de

  • SCCM 2012 and WSUS

    I know this horse has been beat, and is probably just dust now but I am still having a problem. I am not sure what to do next. I see others have had this problem but their resolutions have not worked.
    Site Config:
    OS - Windows Server 2012 Datacenter
    SQL - SQL Server 2012 Enterprise SP1
    SCCM - SCCM 2012 SP1
    WSUS : Database and WSUS Services
    I have done the setup in the Server Manager window and can open the console. Below are the errors I am getting.
    From SMS_WSUS_SYNC_MANAGER
    WSUS Synchronization failed.
    Message: WSUS update source not found on site CM1. Please refer to WCM.log for configuration error details..
    From SMS_WSUS_CONFIGURATION_MANAGER
    WSUS Configuration Manager failed to subscribe to update categories and classifications on WSUS Server "SERVER".
    Error in WCM.log
    Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error
    Error in wsyncmgr.log
    Sync failed: WSUS update source not found on site CM1. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SERVER SITE=CM1 PID=1548 TID=1740 GMTDATE=Fri Sep 13 19:08:50.063 2013 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on
    site CM1. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    Sync failed. Will retry in 60 minutes

    Re-set the WSUS and SUP roles according to your doco, which is nice by the way, but I am still getting errors in WCM.
    Assembly WSUSMSP loaded in .NET runtime v4.0.30319.17929 SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:12 PM 5108 (0x13F4)
    Attempting connection to WSUS server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:12 PM 5108 (0x13F4)
    Successfully connected to server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:14 PM 5108 (0x13F4)
    Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:14 PM 5108 (0x13F4)
    Successfully configured WSUS Server settings and Upstream Server to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
    WSUS Server configuration has been updated. Updating Group Info. SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
    Updating Group Info for WSUS. SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
    Set DBServerName property in SCF to 'VRC1SCCMPRIP01' on this site for <SERVER.DOMAIN>. SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
    user(NT AUTHORITY\SYSTEM) runing application(SMS_WSUS_CONFIGURATION_MANAGER) from machine (<SERVER.DOMAIN>) is submitting SDK changes from site(CM1) SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:16 PM 5108 (0x13F4)
    Attempting connection to WSUS server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Successfully connected to server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:041e4f9f-3a3d-4f58-8b2f-5e6fe95c4591 (Office 2007) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:18e5ea77-e3d1-43b6-a0a8-fa3dbcd42e93 (Windows 8.1 Dynamic Update) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:2ee2ad83-828c-4405-9479-544d767993fc (Windows 8) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:3e5cc385-f312-4fff-bd5e-b88dcf29b476 (Windows 8 Language Interface Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:5312e4f1-6372-442d-aeb2-15f2132c9bd7 (Windows Internet Explorer 8 Dynamic Installer) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:6407468e-edc7-4ecd-8c32-521f64cee65e (Windows 8.1) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:6d76a2a5-81fe-4829-b268-6eb307e40ef3 (Windows 7 Language Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:704a0a4a-518f-4d69-9e03-10ba44198bd5 (Office 2013) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:84f5f325-30d7-41c4-81d1-87a0e6535b66 (Office 2010) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:97c4cee8-b2ae-4c43-a5ee-08367dab8796 (Windows 8 Language Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:a38c835c-2950-4e87-86cc-6911a52c34a3 (Forefront Endpoint Protection 2010) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:bfe5b177-a086-47a0-b102-097e4fa1f807 (Windows 7) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category Product:f4b9c883-f4db-4fb5-b204-3343c11fa021 (Windows Embedded Standard 7) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Category ProductFamily:fe729f7e-3945-11dc-8e0c-cd1356d89593 (Silverlight) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
    Starting WSUS category sync from upstream... SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:36:22 PM 5108 (0x13F4)
      WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:37:22 PM 5108 (0x13F4)
      WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:38:22 PM 5108 (0x13F4)
      WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:39:22 PM 5108 (0x13F4)
      WSUS sync running SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:22 PM 5108 (0x13F4)
    Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:37 PM 5108 (0x13F4)
    Attempting connection to WSUS server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:37 PM 5108 (0x13F4)
    Successfully connected to server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:37 PM 5108 (0x13F4)
    Successfully refreshed categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
    Attempting connection to WSUS server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
    Successfully connected to server: <SERVER.DOMAIN>, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
    Category Product:6d76a2a5-81fe-4829-b268-6eb307e40ef3 (Windows 7 Language Packs) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
    Subscription contains categories unknown to WSUS. SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
    Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error SMS_WSUS_CONFIGURATION_MANAGER 9/17/2013 1:40:45 PM 5108 (0x13F4)
    From SUPSetup.log
    <09/17/13 13:36:13> ====================================================================
    <09/17/13 13:36:13> SMSWSUS Setup Started....
    <09/17/13 13:36:13> Parameters: I:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:<SERVER.DOMAIN> SMSWSUS 0
    <09/17/13 13:36:13> Installing Pre Reqs for SMSWSUS
    <09/17/13 13:36:13>         ======== Installing Pre Reqs for Role SMSWSUS ========
    <09/17/13 13:36:13> Found 1 Pre Reqs for Role SMSWSUS
    <09/17/13 13:36:13> Pre Req SqlNativeClient found.
    <09/17/13 13:36:13> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
    <09/17/13 13:36:13> Pre Req SqlNativeClient is already installed. Skipping it.
    <09/17/13 13:36:13>         ======== Completed Installation of Pre Reqs for Role SMSWSUS ========
    <09/17/13 13:36:13> Installing the SMSWSUS
    <09/17/13 13:36:13> Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
    <09/17/13 13:36:13> Checking runtime v2.0.50727...
    <09/17/13 13:36:13> Did not find supported version of assembly Microsoft.UpdateServices.Administration.
    <09/17/13 13:36:13> Checking runtime v4.0.30319...
    <09/17/13 13:36:13> Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384
    <09/17/13 13:36:13> Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.16384
    <09/17/13 13:36:13> Supported WSUS version found
    <09/17/13 13:36:13> Supported WSUS Server version (6.2.9200.16384) is installed.
    <09/17/13 13:36:13> CTool::RegisterManagedBinary: run command line: "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\RegAsm.exe" "I:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll"
    <09/17/13 13:36:13> CTool::RegisterManagedBinary: Registered I:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll successfully
    <09/17/13 13:36:13> Registered DLL I:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll
    <09/17/13 13:36:13> Installation was successful.
    <09/17/13 13:36:13> ~RoleSetup().
    Second to last line shows completion.

  • SCCM 2012 SQL database error while installation.

    Hi,
    I'm trying to install SCCM 2012 R2 in a test Lab. While completing installation I'm getting an error message "setup has encountered fatal errors during database initialization. check the log for details. click the view log button for more information"
    and installation finishes successfully. I'm using SQL server 2008 R2 with CU6 installed. SCCM Prerequisite checker shows only SQL memory and WSUS package warnings. Still I'm able to finish installation but not able connect SCCM. I'm installing Primary site.
    My system is running on Win 2k8 R2 SP1.
    Please help.
    Regards,
    Dhananjay

    In my experience you can get strange problems if you extract the ISO to a folder and run the setup from there (that seems to be what you have done).
    Try mounting the ISO directly and I believe you will have better success. You are using W2008R2 so you will need a 3rd party app (Virtual CloneDrive is a good one).
    (Obviously if this is a VM you can just add the ISO to the DVD drive)
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • 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.

  • SCCM 2012 database issue /question

    Hi All
    We have 2 recurring errors on our Primary Server (SQL locally installed so a local database).
    We have recently updated SCCM 2012 RTM -> SCCM 2012 SP1 (no CU), and we have upgraded SQL 2008 R2 (CU6) to SQL 2008 R2 SP2.
     We have exactly the same issue in our TST environment.
    Both errors are related to SQL  
    We checked the SQL server log,
    The fist error:
    Warning: Failure to calculate super-latch promotion threshold.
    I don’t now where to search for this error also google did not provide me with some useful help, I hope someone here can help me with this one.
    The second error:
    This one has something to do with the stored procedure DRSMsgBuilderActivation
    The activated proc '[dbo].[spDRSMsgBuilderActivation]' running on queue 'CM_XXX.dbo.ConfigMgrDRSMsgBuilderQueue' output the following: 
    'ERROR: Sync of type Configuration Data failed, see previous messages for details.'
    And the previous message is the following :
    The activated proc '[dbo].[spDRSMsgBuilderActivation]' running on queue 'CM_XXX.dbo.ConfigMgrDRSMsgBuilderQueue' output the following: 
    'ERROR 3961, Level 16, State 1, Procedure spDRSSendChangesForGroup, Line 1, Message: Snapshot isolation transaction failed in database 'CM_XXX' because the object accessed by the statement has been modified by a DDL statement in another concurrent transaction
    since the start of this transaction.  It is disallowed because the metadata is not versioned. A concurrent update to metadata can lead to inconsistency if mixed with snapshot isolation.'
    I did some checking and there is no problem with the tempdb
    Also with this error I hope that someone can help me
    Perhaps someone has had the same error
    Regards and thx in advance
    Johan

    hi, one thing I did not understand is, what is the effect on the non technical side of this error?
    On the technical side you can find some information in error logs. This it's what I understood.
    Is your sccm server working? Or is it not even possible to finish the sccm installation?

  • Upgrade to SCCM 2012 R2 Failed - Can I Simply Move SCCM Database to Replacement SCCM 2012 R2 System?

    I started with SCCM 2012 RTM and attempted an upgrade to SCCM 2012 R2.  The upgrade failed and left the the system unusable.  I was able to recover the entire system (single server) from backup.  
    Rather than risk another failed upgrade can I simply build a new server and move the existing SCCM database to a new SCCM 2012 R2 system?

    Hi,
    Here is an official article talks about Upgrade for your reference.
    Planning to Upgrade System Center 2012 Configuration Manager
    http://technet.microsoft.com/en-us/library/jj822981.aspx
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Enable Re-Indexing Maintenance Task for SCCM 2012 R2 Database?

    If I use the
    MaintenanceSolution.sql script provided by Ola Hallengren here: 
    http://ola.hallengren.com/sql-server-index-and-statistics-maintenance.html
    and then use this SQL script weekly to rebuild the SCCM 2012 R2 indexes:
    EXECUTE dbo.IndexOptimize
    @Databases = 'USER_DATABASES',
    @FragmentationLow = NULL,
    @FragmentationMedium = 'INDEX_REORGANIZE,INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE',
    @FragmentationHigh = 'INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE',
    @FragmentationLevel1 = 5,
    @FragmentationLevel2 = 30,
    @UpdateStatistics = 'ALL',
    @OnlyModifiedStatistics = 'Y'
    Then do I still need to enable the built-in database re-indexing maintenance task in the SCCM 2012 R2 console?
    Thanks 

    In the Channel9 video, the statement is made that the  built in Rebuild Indexes "maintenance task does not always work and that it is kind of broken, but it works sometimes and not always." Can anyone provide further
    details regarding the state of the Rebuild Indexes
    maintenance task? Why does it only sometimes work? Should it be used at all? Has it been fixed with a CU since the video came out? Are there plans to fix it? 
    I need to defrag my database, and  I am trying to determine the best approach.
    Thanks!
    -Tony

  • Database instance for SCCM 2012 and WSUS on a single primary site server

    I am going to install SCCM 2012 and its SQL database on a single physical server. This is going to be a single primary site server. The default SQL instance will be dedicated to SCCM 2012 with no other named instances to be added on the SQL server down
    the road.
    During the WSUS server role installation, there is the Database Options page asking for using (1) Windows Internal Database, (2) existing db server on this computer, or (3) an external db server.
    Since SCCM 2012 doesn't share db instance with others, how should I handle the WSUS db that's going to be hosted on the same SCCM/SQL physical server? Do I really need to create a separate SQL instance just for the WSUS db?
    Thanks and regards. 

    Even though you can do it, it is the best practice to have SCCM 2012 and WSUS installed on separate instances.
    http://technet.microsoft.com/en-us/library/hh692394
    When the Configuration Manager and WSUS databases use the same SQL Server and share the same instance of SQL Server, you cannot easily determine the resource usage between the two applications. When you use a different SQL Server instance
    for Configuration Manager and WSUS, it is easier to troubleshoot and diagnose resource usage issues that might occur for each application.

Maybe you are looking for