Upgrade to SCCM 2012 R2
Which download do I choose in Microsoft Volume license to upgrade my SCCM 2012 SP1 to R2?
Mine looks like this:
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)
Similar Messages
-
Upgrade from SCCM 2012 SP1 CU4 to R2 Fails - Unsupported Upgrade Path
Hi everybody,
I'm currently upgrading our SCCM infrastructure to SCCM 2012 R2 after have finished with the upgrade from SCCM 2012 RTM to SP1 CU4, thus far everything works fine, but when I try to update any
of the site servers, whether CAS or Primary, I'm getting the following error message in the Prerequisites Check:
I've gone through the system requirements and prerequisites over and over again and I can assure you that every possible update, supported OS, feature set, SQL Server, check list, etc,
etc, have been followed as per the official documentation available, however I'm stuck in this point, and surely enough I haven't been able to find out a similar case.Additionally I'm adding
the ConfigMgrPrereq log (the relevant portion of it) in case someone could kindly take a look at it.
<04-25-2014 02:06:46> ******* Start Prerequisite checking. *******
<04-25-2014 02:06:47> ********************************************
<04-25-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade,
minimum supported installed build version is [7804].
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Unsupported upgrade path; Error;
Configuration Manager has detected that one or more sites in the hierarchy are installed with a version of Configuration Manager that is not supported for upgrade.
<04-25-2014 02:07:00> INFO: This rule only apply to primary site, skip checking.
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Active Replica MP; Passed
<04-25-2014 02:07:00> INFO: This rule only applies to primary or secondary site in hierarchy, skip checking.
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Parent site replication status; Passed
<04-25-2014 02:07:00> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:00> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:00> ===== INFO: Prerequisite Type & Server: SQL:INFPROSCCMCDB.usersad.everis.int
=====
<04-25-2014 02:07:00> <<<RuleCategory: Access Permissions>>>
<04-25-2014 02:07:00> <<<CategoryDesc: Checking access permissions...>>>
<04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;
SQL Server sysadmin rights; Passed
<04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int; SQL Server sysadmin rights
for reference site; Passed
<04-25-2014 02:07:00> INFO: CheckLocalSys is Admin of <INFPROSCCMCDB.usersad.everis.int>.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Site server computer account administrative rights; Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server security mode; Passed
<04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: OS version:601, ServicePack:1.
<04-25-2014 02:07:09> INFO: Target computer is a Windows server.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Unsupported site server operating system version for Setup; Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Domain membership; Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Pending system restart; Passed
<04-25-2014 02:07:09> <<<RuleCategory: Dependent Components>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: Return code:0, Major:10, Minor:50, BuildNum:4000
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server version; Passed
<04-25-2014 02:07:09> INFO: Get Sql edition:Enterprise Edition.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server Edition; Passed
<04-25-2014 02:07:09> INFO: Checking Tcp is enabled to Static port, SQL Server:INFPROSCCMCDB.usersad.everis.int,
Instance:.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server Tcp Port; Passed
<04-25-2014 02:07:09> INFO: Checking if SQL Server memory is limited.
<04-25-2014 02:07:09> INFO: SQL Server memory is limited.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Configuration for SQL Server memory usage; Passed
<04-25-2014 02:07:09> INFO: Checking if SQL Server memory is configured to reserve minimum memory.
<04-25-2014 02:07:09> INFO: Installing the central administration site or primary site, requires SQL
Server to reserve a minimum of 8 gigabytes (GB) of memory.
<04-25-2014 02:07:09> WARN: SQL Server minimum memory is 8000 MB.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int; SQL Server process memory allocation;
Warning; Configuration Manager requires SQL Server to reserve a minimum of 8 gigabytes (GB) of memory for the central administration site and primary site and a minimum of 4 gigabytes (GB) for the secondary site. This memory is reserved by
using the Minimum server memory setting under Server Memory Options and is configured by using SQL Server Management Studio. For more information about how to set a fixed amount of memory, see
http://go.microsoft.com/fwlink/p/?LinkId=233759.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Case-insensitive collation on SQL Server; Passed
<04-25-2014 02:07:09> INFO: Check Machine FQDN: <INFPROSCCMCDB.usersad.everis.int>.
<04-25-2014 02:07:09> INFO: getaddrinfo returned success.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Validate FQDN of SQL Server Computer; Passed
<04-25-2014 02:07:09> INFO:CheckSupportedFQDNFormat <INFPROSCCMCDB.usersad.everis.int>
<04-25-2014 02:07:09> INFO: NetBIOS <INFPROSCCMCDB>
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Primary FQDN; Passed
<04-25-2014 02:07:09> <<<RuleCategory: Site Upgrade Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
<04-25-2014 02:07:09> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:09> ===== INFO: Prerequisite Type & Server: SDK:INFPROSCCMCMS.usersad.everis.int
=====
<04-25-2014 02:07:09> <<<RuleCategory: Access Permissions>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking access permissions...>>>
<04-25-2014 02:07:09> INFO: The rule 'Administrative rights on site system' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: The rule 'Unsupported site server operating system version for Setup' has
been run on server 'INFPROSCCMCMS.usersad.everis.int', skipped.
<04-25-2014 02:07:09> INFO: The rule 'Domain membership' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:09> INFO: Windows Cluster not found on INFPROSCCMCMS.usersad.everis.int.
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
Windows Failover Cluster; Passed
<04-25-2014 02:07:10> INFO: The rule 'Pending system restart' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:10> <<<RuleCategory: Dependent Components>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
Windows Deployment Tools installed; Passed
<04-25-2014 02:07:10> INFO: CheckAdkWinPeInstalled on INFPROSCCMCMS.usersad.everis.int.
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int; Windows Preinstallation Environment
installed; Passed
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
SMS Provider machine has same domain as site server; Passed
<04-25-2014 02:07:10> <<<RuleCategory: Site Upgrade Requirements>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
<04-25-2014 02:07:10> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:10> ***************************************************
<04-25-2014 02:07:10> ******* Prerequisite checking is completed. *******
<04-25-2014 02:07:10> ******************************************<04-25-2014 02:07:10> INFO: Updating
Prerequisite checking result into the registry
<04-25-2014 02:07:10> INFO: Connecting to INFPROSCCMCMS.usersad.everis.int registry
<04-25-2014 02:07:10> INFO: Setting registry values
If you wonder whether it might be related to this error:
-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade, minimum supported installed build version is [7804].
I confirm that this one site is a secondary one that's attached to a primary site and this log is from the CAS server, I managed to tall it and delete it from that site, but still appears listed
on the CAS management console, any idea how to force the removal of a secondary site that's attached to a primary from the CAS site when it has been removed already from said primary?
I've already tried the
Preinst /DELSITE XXX command but it only works when the site to remove it's attached to the local site and certainly not from a CAS
Finally, the version, build number and everything is correct, no idea what could be the problem, does anybody know a way to bypass this or force the re-evaluation of this rules, I've got
the impression that it's being cached somehow.
Any help would be highly appreciated,
Thank you.
Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSEHello again everybody,
I've finally managed to fix this up, in the end I had to delete those entries manually from the database as Garry suggested. After this was done the upgrade has gone through as expected with no further ado and has finalized already, now moving on to the
primary sites.
If anybody out there is facing the same issue, what I did was to delete those "stubborn" records executing the following statements over the CAS database:
DELETE
FROMServerDataWHERESiteCode='XXX'
DELETE
FROMSC_SiteDefinitionWHERESiteCode='XXX'
And this is pretty much about it. I'd recommend to take a proper backup first though as best practice.
Thank you all anyways for your answers and comments,
Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE -
Reports no longer work after upgrading to SCCM 2012 R2
I upgraded my SCCM 2012 SP1 environment to R2 and reports no longer work. I've removed the site role, waited a day, and added it. I've also verified the account (used by the reporting site role) has access to the DB and can logon locally. The
problem still persists. Here's a copy/paste of the error:
Microsoft.Reporting.WinForms.ReportServerException
An error has occurred during report processing. (rsProcessingAborted)
Stack Trace:
at Microsoft.Reporting.WinForms.ServerReportSoapProxy.OnSoapException(SoapException e)
at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ProxyMethodInvocation.Execute[TReturn](RSExecutionConnection connection, ProxyMethod`1 initialMethod, ProxyMethod`1 retryMethod)
at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
at Microsoft.Reporting.WinForms.ServerReport.EnsureExecutionSession()
at Microsoft.Reporting.WinForms.ServerReport.SetParameters(IEnumerable`1 parameters)
at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerWindowsForms.SetParameterValues_DoWork(Object sender, DoWorkEventArgs e)
Microsoft.Reporting.WinForms.ReportServerException
Cannot read the next data row for the dataset DataSet1. (rsErrorReadingNextDataRow)
Stack Trace:
at Microsoft.Reporting.WinForms.ServerReportSoapProxy.OnSoapException(SoapException e)
at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ProxyMethodInvocation.Execute[TReturn](RSExecutionConnection connection, ProxyMethod`1 initialMethod, ProxyMethod`1 retryMethod)
at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
at Microsoft.Reporting.WinForms.ServerReport.EnsureExecutionSession()
at Microsoft.Reporting.WinForms.ServerReport.SetParameters(IEnumerable`1 parameters)
at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerWindowsForms.SetParameterValues_DoWork(Object sender, DoWorkEventArgs e)
Microsoft.Reporting.WinForms.ReportServerException
Conversion failed when converting the nvarchar value 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXscrubbed' to data type int.
Stack Trace:
at Microsoft.Reporting.WinForms.ServerReportSoapProxy.OnSoapException(SoapException e)
at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ProxyMethodInvocation.Execute[TReturn](RSExecutionConnection connection, ProxyMethod`1 initialMethod, ProxyMethod`1 retryMethod)
at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
at Microsoft.Reporting.WinForms.ServerReport.EnsureExecutionSession()
at Microsoft.Reporting.WinForms.ServerReport.SetParameters(IEnumerable`1 parameters)
at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerWindowsForms.SetParameterValues_DoWork(Object sender, DoWorkEventArgs e)
I've tried many other TechNet solutions as well with no improvement:
http://social.technet.microsoft.com/Forums/en-US/ae08aa43-054d-47e7-99fb-c4f101962478/reports-not-working-after-upgrade-to-sccm-2012-r2-?forum=configmanagergeneral
http://social.technet.microsoft.com/Forums/en-US/77bad9b6-de0e-42d3-ae9f-e7c9d26b4330/reporting-error-after-upgrading-to-sccm-2012-r2?forum=configmanagergeneral
Any other thoughts on this?So to be clear you have Done both the Mofcomp and Added the correct account to the Windows Authorization Access Group?
What is version of SQL are you using?
Is SSRS remote or local to CM12?
What service account are you using for SSRS?
Bases on the error message you are getting this within the console, Does the native SSRS report work? BTW I never recommend accessing the report via the console.
http://be.enhansoft.com/post/2013/09/10/Should-Configuration-Manager-SSRS-or-ASP-Reports-be-Accessed-from-the-Browser-or-the-Console.aspx
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ -
Reports not working after upgrade to SCCM 2012 R2 -
I am having the same issue described in this post:
http://social.technet.microsoft.com/Forums/en-US/30f185ac-c34e-44ad-87eb-7d180a0d76b8/after-2012-r2-upgrade-some-sql-queries-wont-run?forum=configmanagergeneral
When running reports after upgrading from SCCM 2012 SP1 CU2 to SCCM 2012 R2 I get the following error:
An
error has occurred during report processing. (rsProcessingAborted)
Cannot
read the next data row for the dataset DataSet1. (rsErrorReadingNextDataRow)
Conversion
failed when converting the nvarchar value
'S-1-5-21-1010966800-777871707-395339515-124623' to data type int.
I have removed the Reporting Services Point and reinstalled it with no effect. All reports I try get the error listed above.
Any suggestions?The issue has been resolved. For anyone experiencing a similar issue I will post the fix that worked for us below:
I ended up opening a PSS case and in this instance the problem was the required SQL management provider was not properly registered in WMI, which ultimately meant the reporting point upgrade/install was not able to complete successfully after the upgrade.
As a result the updated reports were not properly being redeployed to the Reporting Service Point.
To diagnose this on the Reporting Service Point look in the srsrp.log for entries indicating of an
Invalid Class, as seen in the example below:
Invalid class SMS_SRS_REPORTING_POINT 11/6/2013 5:47:12 PM 6096 (0x17D0)
Could not retrieve the reporting service name for instance 'RPSERVER' SMS_SRS_REPORTING_POINT 11/6/2013 5:47:12 PM 6096 (0x17D0)
Invalid class SMS_SRS_REPORTING_POINT 11/6/2013 5:47:12 PM 6096 (0x17D0)
Could not stop the reporting service '' SMS_SRS_REPORTING_POINT 11/6/2013 5:47:12 PM 6096 (0x17D0)
Next security configuration at [11/6/2013 5:52:12 PM] SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Root Folder exists SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Successfully checked that the SRS web service is healthy on server SERVERRP.AD.DOMAIN SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Registry change SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Waiting for changes for 1 minutes SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
SRSRP registry key change notification triggered. SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Registry change SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Waiting for changes for 1 minutes SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Timed Out... SMS_SRS_REPORTING_POINT 11/6/2013 5:48:13 PM 6096 (0x17D0)
The important part is the lines saying Invalid Class and then it timing out, so the RP installation was not completed.
As mentioned earlier the WMI class that was missing or corrupt was the SQL management Provider. To re-register the class we need to compile the MOF file that is available in SQL. In our instance the command to run was:
mofcomp "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"
Once that was done, monitoring the srsrp.log shows that it could properly detect the SSRS service, stop it and start coping the updated reports and such. After a few minutes the deploy completed, and all the broken reports started working
correctly.
Hope that helps someone else. -
Reporting Error After Upgrading to SCCM 2012 R2
After upgrading from SCCM 2012 SP1 CU2 to SCCM 2012 R2, some users receive an error whenever they open a report. This occurs in both the SCCM console and the SSRS web site. What's odd is not all users receive the error. In fact, for two
users with the exact same permissions, running the console on the same computer, 1 gets the error and the other doesn't. Anybody else see this or have any ideas to troubleshoot or fix it? I'm thinking this may relate to the fix for permissions
in reporting included in R2.
The error message from the console is:Microsoft.Reporting.WinForms.ReportServerException
The DefaultValue expression for the report parameter ‘UserSIDs’ contains an error: The user name or password is incorrect.
(rsRuntimeErrorInExpression)
Stack Trace:
at Microsoft.Reporting.WinForms.ServerReportSoapProxy.OnSoapException(SoapException e)
at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ProxyMethodInvocation.Execute[TReturn](RSExecutionConnection connection, ProxyMethod`1 initialMethod, ProxyMethod`1 retryMethod)
at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
at Microsoft.Reporting.WinForms.ServerReport.EnsureExecutionSession()
at Microsoft.Reporting.WinForms.ServerReport.SetParameters(IEnumerable`1 parameters)
at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerWindowsForms.SetParameterValues_DoWork(Object sender, DoWorkEventArgs e)
The following error is logged in the SSRS logs:
processing!ReportServer_0-1!12d0!10/31/2013-15:28:48:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Exception of type 'Microsoft.ReportingServices.ReportProcessing.ReportProcessingException' was thrown.;I just wanted to share my last upgrade experience with you, in case, someone is running into the same problem:
I've just upgraded to SCCM 2012 R2 CU4 (from CU3).
Guess what? It broke the Reporting, error message as above!
So I've put the computeraccount of my SCCM/SSRS server (SSRS service is running under local system account) into the WAA group, reboot - but it didn't help. Tried also the Pre-Win2000-Compat-group. Didn't help. A colleague was not experiencing the problem.
Hmmm. So what is different between our accounts?
The difference found: My account's userPrincipalName was set to the same as the sAMAccountName, but missing a domain. The account was obviously created by a bad script.
Solution 1: Delete the userPrincipalName attribute, or
Solution 2: Make the userPrincipalName complete by adding a valid domain, i.e. [email protected]: In the Active Directory Users and Computers mmc, User Properties, Account tab, select a domain for the "User logon name".
The problem seems to be only for user accounts, that are in a different domain than the SCCM server's account, i.e. server in example.com, user account in sub.example.com. Always multi-domain problems...
Thorsten Lau - IT-Lösungen http://blog.system-center.de -
Upgrade to SCCM 2012 R2: WinPE 5.0 and Legacy system.
Hi,
When upgrade to SCCM 2012 SP1 we get WinPE 4.0 boot images, and the PXE-boot did not working with CPU's that do not support NX/PAE/SSE2.
SCCM 2012 R2 need "ADK for Windows 8.1" with WinPE 5.0. I think it is same with WinPE 5.0 that it dont working with CPU's that do not support NX/PAE/SSE2.
Is there something else to considerations with WinPE 5.0 boot with Legacy systems?
ref:
http://blogs.technet.com/b/configmgr_geek_speak/archive/2013/03/03/winpe-4-0-boot-images-not-working-with-cpu-s-that-do-not-support-n
/SaiTechI think the link you posted is broken, but this one works:
http://blogs.technet.com/b/configmgr_geek_speak/archive/2013/03/03/winpe-4-0-boot-images-not-working-with-cpu-s-that-do-not-support-nx-pae-sse2.aspx
You can still use WinPE3.1, for those legacy computers:
http://blogs.technet.com/b/brandonlinton/archive/2013/06/21/how-to-create-and-import-a-winpe-3-1-boot-image-for-use-in-configmgr-2012-sp1-cu2.aspx
http://technet.microsoft.com/en-us/library/dn387582.aspx
http://technet.microsoft.com/en-us/library/hh397288.aspx
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!) -
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. -
Duplicate Reports after upgrading to SCCM 2012 R2 CU1
Single Primary Site with SCCM 2012 R2 CU1.
Upgraded from SCCM 2012 SP1.
Duplicate Reports after upgrading to SCCM 2012 R2 CU1
SCCM 2012 R2 CU1
SQL 2008 SP3 CU 14This is known to happen if you modified any of the default reports
I've seen that happening even in my lab (and and customers) where I am sure that I did not modify them. Just delete them (they should be prefixed with "_").
Torsten Meringer | http://www.mssccmfaq.de -
¿Is it possible to upgrade from SCCM 2012 a domain controller in Windows Server 2008 R2 TO 2012 R2?
Hi all.
I want to know if is it possible to upgrade a domain controller from Windows Server 2008 r2 to 2012 r2 installing from SCCM 2012.
Thanks.
Regards.Hi all.
I want to know if is it possible to upgrade a domain controller from Windows Server 2008 r2 to 2012 r2 installing from SCCM 2012.
Thanks.
Regards.
Anything is possible if you can script it. You could create a task sequence to do the following (with scripts):
1. Demote 2008R2 DC to member server
2. Remove 2008R2 member server from domain
3. Build new 2012R2 member server and join to domain
4. Promote 2012R2 member server to DC
You can do this. However, why would you? Just because you can doesn't mean you should. In my opinion it's more trouble and testing than it's worth. How many times would you need to do this?
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson -
SMS_Exec service crashing repeatedly after upgrade from SCCM 2012 SP1 to 2012R2
SCCM 2012R2 is running on 2008R2 in the primary site. After the upgrade to R2 we noticed that none of the stats or collection memberships were updating. We also couldn't manually run summerization on any deployments.
We started digging through logs and looking at some of the threads on there with similar issues but couldn't see any issues with inbox contents or any of the other suggested fixes. We tried repairing .NET but that didn't help.
If anyone can help guide us in the right direction it would be greatly appreciated. I've included the crash.log below.
EXCEPTION INFORMATION
Time = 12/30/2013 13:08:43.990
Service name = SMS_EXECUTIVE
Thread name = SMS_ALERT_NOTIFICATION
Executable = C:\Program Files\Microsoft Configuration Manager\bin\x64\smsexec.exe
Process ID = 3368 (0xd28)
Thread ID = 4684 (0x124c)
Instruction address = 0000000077B33290
Exception = c0000005 (EXCEPTION_ACCESS_VIOLATION)
Description = "The thread tried to read from the virtual address 0000000000BA2D28 for which it does not have the appropriate access."
Raised inside CService mutex = No
CService mutex description = ""
LOADED MODULES
Module BaseAddr Size File Version Product Version Debug Symbols Full Path To Module Full Path To Debug Symbols
===========================================================================================================================================================================
C:\Windows\WinSxS\amd64_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_044aad0bab1eb146\mfc90.dll 0000000053FD0000 004e4000 9.0.30729.6161 9.0.30729.6161 Symbols Load Failed C:\Windows\WinSxS\amd64_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_044aad0bab1eb146\mfc90.dll
C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251\MSVCR90.dll 000000006E0B0000 000a3000 9.0.30729.6161 9.0.30729.6161 DLL Exports Only C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251\MSVCR90.dll
C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251\MSVCP90.dll 000000006E7D0000 000d3000 9.0.30729.6161 9.0.30729.6161 DLL Exports Only C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251\MSVCP90.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\basesvr.dll 0000000070220000 00393000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\basesvr.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseobj.dll 00000000705C0000 001e7000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\baseobj.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll 00000000707B0000 0014a000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\mfc100.dll 0000000070900000 0055d000 10.0.40219.1 10.0.40219.1 Symbols Load Failed C:\Program Files\Microsoft Configuration Manager\bin\x64\mfc100.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\MSVCR100.dll 0000000071780000 000d2000 10.0.40219.1 10.0.40219.1 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\MSVCR100.dll
C:\Windows\system32\MSVCP100.dll 0000000072840000 00098000 10.0.40219.1 10.0.40219.1 DLL Exports Only C:\Windows\system32\MSVCP100.dll
C:\Windows\system32\security.dll 0000000072B70000 00003000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\security.dll
C:\Windows\system32\odbcint.dll 0000000073020000 00038000 6.1.7600.16385 6.1.7600.16385 Symbols Load Failed C:\Windows\system32\odbcint.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\amtproxymgr.dll 0000000073200000 00024000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\amtproxymgr.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\aikbmgr.dll 0000000073230000 00016000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\aikbmgr.dll
C:\Windows\system32\sqlncli11.dll 0000000073470000 00353000 2011.110.2100.60 11.0.2100.60 DLL Exports Only C:\Windows\system32\sqlncli11.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\SMSSVREH.DLL 0000000073A70000 0000f000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\SMSSVREH.DLL
C:\Program Files\Microsoft Configuration Manager\bin\x64\MFC100ENU.DLL 0000000074130000 0000d000 10.0.40219.1 10.0.40219.1 Symbols Load Failed C:\Program Files\Microsoft Configuration Manager\bin\x64\MFC100ENU.DLL
C:\Program Files\Microsoft Configuration Manager\bin\x64\LibRDC.dll 0000000074140000 00029000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\LibRDC.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\basesql.dll 0000000074170000 0004c000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\basesql.dll
C:\Windows\system32\1033\SQLNCLIR11.RLL 0000000074270000 00038000 2011.110.2100.60 11.0.2100.60 Symbols Load Failed C:\Windows\system32\1033\SQLNCLIR11.RLL
C:\Windows\WinSxS\amd64_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_01c9581e60cbee58\MFC90ENU.DLL 0000000074930000 0000d000 9.0.30729.6161 9.0.30729.6161 Symbols Load Failed C:\Windows\WinSxS\amd64_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_01c9581e60cbee58\MFC90ENU.DLL
C:\Windows\system32\USER32.dll 0000000077400000 000fa000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\USER32.dll
C:\Windows\system32\kernel32.dll 0000000077500000 0011f000 6.1.7601.18229 6.1.7601.18229 DLL Exports Only C:\Windows\system32\kernel32.dll
C:\Windows\SYSTEM32\ntdll.dll 0000000077AE0000 001a9000 6.1.7601.18247 6.1.7601.18247 DLL Exports Only C:\Windows\SYSTEM32\ntdll.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\smsexec.exe 000000013FDA0000 0001f000 5.0.7804.1000 5.0.7804.1000 Symbols Load Failed C:\Program Files\Microsoft Configuration Manager\bin\x64\smsexec.exe
C:\Windows\system32\dbghelp.dll 000007FEE3340000 00125000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\dbghelp.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\AmtUtil.dll 000007FEF40A0000 00174000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\AmtUtil.dll
C:\Windows\system32\comsvcs.dll 000007FEF4400000 001b0000 2001.12.8530.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\comsvcs.dll
C:\Windows\system32\MTXDM.DLL 000007FEF45B0000 0000e000 2001.12.8530.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\MTXDM.DLL
C:\Windows\system32\framedynos.dll 000007FEF5670000 0004c000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\framedynos.dll
C:\Windows\system32\ODBC32.dll 000007FEF56C0000 000b1000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\ODBC32.dll
C:\Windows\system32\CLUSAPI.DLL 000007FEF5800000 00050000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\CLUSAPI.DLL
C:\Windows\system32\RESUTILS.DLL 000007FEF5950000 00019000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\RESUTILS.DLL
C:\Windows\system32\MSIMG32.dll 000007FEF5A00000 00007000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\MSIMG32.dll
C:\Windows\system32\BROWCLI.DLL 000007FEF5FC0000 00012000 6.1.7601.17887 6.1.7601.17887 DLL Exports Only C:\Windows\system32\BROWCLI.DLL
C:\Windows\system32\webio.dll 000007FEF6090000 00064000 6.1.7601.17725 6.1.7601.17725 Symbols Load Failed C:\Windows\system32\webio.dll
C:\Windows\system32\WINHTTP.dll 000007FEF6100000 00071000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\WINHTTP.dll
C:\Windows\System32\msxml6.dll 000007FEF61B0000 001f1000 6.30.7601.17988 6.30.7601.17988 DLL Exports Only C:\Windows\System32\msxml6.dll
C:\Windows\system32\cscapi.dll 000007FEF8990000 0000f000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\cscapi.dll
C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_a4d3b9377117c3df\COMCTL32.dll 000007FEF89E0000 000a0000 5.82.7601.18201 6.1.7601.18201 DLL Exports Only C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_a4d3b9377117c3df\COMCTL32.dll
C:\Windows\system32\WSOCK32.dll 000007FEF96A0000 00009000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\WSOCK32.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\NotiCtrl.dll 000007FEF9750000 00017000 5.0.7804.1000 5.0.7804.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\NotiCtrl.dll
C:\Windows\system32\MPR.dll 000007FEF9D30000 00018000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\MPR.dll
C:\Windows\system32\adsldpc.dll 000007FEF9D70000 0003d000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\adsldpc.dll
C:\Windows\system32\ACTIVEDS.dll 000007FEF9DB0000 00046000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\ACTIVEDS.dll
C:\Windows\system32\SAMCLI.DLL 000007FEFA930000 00014000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\SAMCLI.DLL
C:\Windows\system32\ntdsapi.dll 000007FEFA9D0000 00027000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\ntdsapi.dll
C:\Windows\system32\rasadhlp.dll 000007FEFAA00000 00008000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\rasadhlp.dll
C:\Windows\system32\wkscli.dll 000007FEFADA0000 00015000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\wkscli.dll
C:\Windows\system32\NETAPI32.dll 000007FEFADC0000 00016000 6.1.7601.17887 6.1.7601.17887 DLL Exports Only C:\Windows\system32\NETAPI32.dll
C:\Windows\System32\fwpuclnt.dll 000007FEFAFF0000 00053000 6.1.7601.18283 6.1.7601.18283 DLL Exports Only C:\Windows\System32\fwpuclnt.dll
C:\Windows\system32\WINNSI.DLL 000007FEFB100000 0000b000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\WINNSI.DLL
C:\Windows\system32\IPHLPAPI.DLL 000007FEFB140000 00027000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\IPHLPAPI.DLL
C:\Program Files\Microsoft Configuration Manager\bin\x64\AmtInstFileUtil.dll 000007FEFBC30000 00031000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\AmtInstFileUtil.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\Certificate.dll 000007FEFBC70000 00015000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\Certificate.dll
C:\Windows\system32\DSROLE.DLL 000007FEFBDB0000 0000c000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\DSROLE.DLL
C:\Windows\system32\ATL.DLL 000007FEFBDD0000 00019000 3.5.2284.0 6.5.0.2284 DLL Exports Only C:\Windows\system32\ATL.DLL
C:\Windows\system32\dwmapi.dll 000007FEFC320000 00018000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\dwmapi.dll
C:\Windows\system32\UxTheme.dll 000007FEFC880000 00056000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\UxTheme.dll
C:\Windows\system32\WTSAPI32.dll 000007FEFCEB0000 00011000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\WTSAPI32.dll
C:\Windows\system32\VERSION.dll 000007FEFD080000 0000c000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\VERSION.dll
C:\Windows\System32\wshtcpip.dll 000007FEFD150000 00007000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\System32\wshtcpip.dll
C:\Windows\system32\schannel.DLL 000007FEFD360000 00057000 6.1.7601.18270 6.1.7601.18270 DLL Exports Only C:\Windows\system32\schannel.DLL
C:\Windows\system32\rsaenh.dll 000007FEFD3E0000 00047000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\rsaenh.dll
C:\Windows\system32\credssp.dll 000007FEFD430000 0000a000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\credssp.dll
C:\Windows\system32\bcryptprimitives.dll 000007FEFD480000 0004c000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\bcryptprimitives.dll
C:\Windows\system32\DNSAPI.dll 000007FEFD560000 0005b000 6.1.7601.17570 6.1.7601.17570 DLL Exports Only C:\Windows\system32\DNSAPI.dll
C:\Windows\system32\kerberos.DLL 000007FEFD670000 000b4000 6.1.7601.17926 6.1.7601.17926 DLL Exports Only C:\Windows\system32\kerberos.DLL
C:\Windows\system32\LOGONCLI.DLL 000007FEFD780000 00030000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\LOGONCLI.DLL
C:\Windows\system32\msv1_0.DLL 000007FEFD7B0000 00051000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\msv1_0.DLL
C:\Windows\system32\netutils.dll 000007FEFD850000 0000c000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\netutils.dll
C:\Windows\System32\wship6.dll 000007FEFD860000 00007000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\System32\wship6.dll
C:\Windows\system32\mswsock.dll 000007FEFD870000 00055000 6.1.7601.18254 6.1.7601.18254 DLL Exports Only C:\Windows\system32\mswsock.dll
C:\Windows\system32\bcrypt.dll 000007FEFD900000 00022000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\bcrypt.dll
C:\Windows\system32\ncrypt.dll 000007FEFD930000 0004d000 6.1.7601.18270 6.1.7601.18270 DLL Exports Only C:\Windows\system32\ncrypt.dll
C:\Windows\system32\CRYPTSP.dll 000007FEFD9C0000 00017000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\CRYPTSP.dll
C:\Windows\system32\srvcli.dll 000007FEFD9E0000 00023000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\srvcli.dll
C:\Windows\system32\cryptdll.dll 000007FEFDAF0000 00014000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\cryptdll.dll
C:\Windows\system32\secur32.dll 000007FEFDB10000 0000b000 6.1.7601.18270 6.1.7601.18270 DLL Exports Only C:\Windows\system32\secur32.dll
C:\Windows\system32\SspiCli.dll 000007FEFDDA0000 00025000 6.1.7601.18270 6.1.7601.18270 DLL Exports Only C:\Windows\system32\SspiCli.dll
C:\Windows\system32\CRYPTBASE.dll 000007FEFDE30000 0000f000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\CRYPTBASE.dll
C:\Windows\system32\RpcRtRemote.dll 000007FEFDF20000 00014000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\RpcRtRemote.dll
C:\Windows\system32\profapi.dll 000007FEFDF40000 0000f000 6.1.7600.16385 6.1.7600.16385 Symbols Load Failed C:\Windows\system32\profapi.dll
C:\Windows\system32\MSASN1.dll 000007FEFDFE0000 0000f000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\MSASN1.dll
C:\Windows\system32\KERNELBASE.dll 000007FEFE0B0000 0006b000 6.1.7601.18229 6.1.7601.18229 DLL Exports Only C:\Windows\system32\KERNELBASE.dll
C:\Windows\system32\WINTRUST.dll 000007FEFE120000 0003a000 6.1.7601.18205 6.1.7601.18205 DLL Exports Only C:\Windows\system32\WINTRUST.dll
C:\Windows\system32\CRYPT32.dll 000007FEFE160000 0016c000 6.1.7601.18277 6.1.7601.18277 DLL Exports Only C:\Windows\system32\CRYPT32.dll
C:\Windows\system32\CLBCatQ.DLL 000007FEFE310000 00099000 2001.12.8530.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\CLBCatQ.DLL
C:\Windows\system32\ole32.dll 000007FEFE430000 00203000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\ole32.dll
C:\Windows\system32\SHELL32.dll 000007FEFE640000 00d88000 6.1.7601.18222 6.1.7601.18222 DLL Exports Only C:\Windows\system32\SHELL32.dll
C:\Windows\system32\WLDAP32.dll 000007FEFF3D0000 00052000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\WLDAP32.dll
C:\Windows\system32\USP10.dll 000007FEFF430000 000c9000 1.626.7601.18009 1.626.7601.18009 DLL Exports Only C:\Windows\system32\USP10.dll
C:\Windows\system32\COMDLG32.dll 000007FEFF500000 00097000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\COMDLG32.dll
C:\Windows\system32\LPK.dll 000007FEFF780000 0000e000 6.1.7601.18177 6.1.7601.18177 DLL Exports Only C:\Windows\system32\LPK.dll
C:\Windows\system32\IMM32.DLL 000007FEFF790000 0002e000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\IMM32.DLL
C:\Windows\system32\NSI.dll 000007FEFF7C0000 00008000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\NSI.dll
C:\Windows\system32\ADVAPI32.dll 000007FEFF7D0000 000db000 6.1.7601.18247 6.1.7601.18247 DLL Exports Only C:\Windows\system32\ADVAPI32.dll
C:\Windows\system32\GDI32.dll 000007FEFF8B0000 00067000 6.1.7601.18275 6.1.7601.18275 DLL Exports Only C:\Windows\system32\GDI32.dll
C:\Windows\system32\IMAGEHLP.DLL 000007FEFF920000 00019000 6.1.7601.18288 6.1.7601.18288 DLL Exports Only C:\Windows\system32\IMAGEHLP.DLL
C:\Windows\system32\MSCTF.dll 000007FEFF940000 00109000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\MSCTF.dll
C:\Windows\system32\OLEAUT32.dll 000007FEFFA50000 000d7000 6.1.7601.17676 6.1.7601.17676 DLL Exports Only C:\Windows\system32\OLEAUT32.dll
C:\Windows\system32\RPCRT4.dll 000007FEFFB30000 0012d000 6.1.7601.18205 6.1.7601.18205 DLL Exports Only C:\Windows\system32\RPCRT4.dll
C:\Windows\system32\WS2_32.dll 000007FEFFC60000 0004d000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\WS2_32.dll
C:\Windows\SYSTEM32\sechost.dll 000007FEFFCB0000 0001f000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\SYSTEM32\sechost.dll
C:\Windows\system32\SHLWAPI.dll 000007FEFFCD0000 00071000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\SHLWAPI.dll
C:\Windows\system32\msvcrt.dll 000007FEFFD50000 0009f000 7.0.7601.17744 6.1.8638.17744 DLL Exports Only C:\Windows\system32\msvcrt.dll
STACK TRACE FOR SMS_EXECUTIVE THREAD 4516 (0x11a4) AT 12/30/2013 13:08:44.120
CS: 0033 RIP: 0000000077B0C541 EFLAGS: 00000246
SS: 002b RSP: 0000000001ABFB30 RBP: 0000000000000000
DS: 0000 ES: 0000 FS: 0000 GS: 0000
RAX: 0000000000000000 RDX: 0000000000C06BD0
RBX: 0000000000000000 RCX: 0000000000C0F960
RSI: 0000000000000000 RDI: 0000000000000000
R8: 000007FFFFFD6000 R9: 0000000000000004
R10: 0000000000000000 R11: 0000000000000043
R12: 0000000000000000 R13: 0000000000000000
R14: 0000000000000000 R15: 0000000000000000
Module Address Offset Function + Displacement # Params Possible Values Of First Four Params Decorated Function Name
================================================================================================================================================================================================================================
C:\Windows\SYSTEM32\ntdll.dll 0000000077B315FA 000515fa ZwDelayExecution() + 10 bytes Unknown 00000000 00000000 00000000 00000000 ZwDelayExecution
C:\Windows\system32\KERNELBASE.dll 000007FEFE0B1203 00001203 SleepEx() + 179 bytes Unknown 00000000 00000000 00000000 00000000 SleepEx
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll 00000000707F51A1 000451a1 CService::ProceedIfNotHandlingException() + 29 bytes Unknown 00000000 00000000 00000000 00000000 ?ProceedIfNotHandlingException@CService@@CAXXZ
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll 00000000707F3844 00043844 CService::Yield() + 44 bytes Unknown 00000000 00000000 00000000 00000000 ?Yield@CService@@SAKHK@Z
C:\Program Files\Microsoft Configuration Manager\bin\x64\smsexec.exe 000000013FDACC86 0000cc86 Unknown Unknown 00000000 00000000 00000000 00000000 Unknown
C:\Program Files\Microsoft Configuration Manager\bin\x64\smsexec.exe 000000013FDB08CA 000108ca Unknown Unknown 00000000 00000000 00000000 00000000 Unknown
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll 00000000707F40F2 000440f2 CService::_WorkerThread() + 54 bytes Unknown 00000000 00000000 00000000 00000000 ?_WorkerThread@CService@@CAKPEAX@Z
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll 00000000707F3F60 00043f60 CService::_NewThreadWrapper() + 28 bytes Unknown 00000000 00000000 00000000 00000000 ?_NewThreadWrapper@CService@@CAKPEAX@Z
C:\Windows\system32\kernel32.dll 000000007751652D 0001652d BaseThreadInitThunk() + 13 bytes Unknown 00000000 00000000 00000000 00000000 BaseThreadInitThunk
C:\Windows\SYSTEM32\ntdll.dll 0000000077B0C541 0002c541 RtlUserThreadStart() + 33 bytes Unknown 00000000 00000000 00000000 00000000 RtlUserThreadStart
WARNING: The stack could not be completely unwound. This is usually due to a
limitation in the stack unwinding algorithm, but it can also happen if the stack
itself was corrupted.
STACK TRACE FOR SMS_ALERT_NOTIFICATION THREAD 4684 (0x124c) AT 12/30/2013 13:08:43.990
CS: 0033 RIP: 0000000077B0C541 EFLAGS: 00010202
SS: 002b RSP: 0000000002F2FCC0 RBP: 0000000000000000
DS: 002b ES: 002b FS: 0053 GS: 002b
RAX: 000000125A55DA38 RDX: 00000000023123E0
RBX: 0000000000000000 RCX: 000000FFFFFFFFFF
RSI: 0000000000000000 RDI: 0000000000000000
R8: 00000000023123F0 R9: 000007BC01BA00BC
R10: 6F626E695C554946 R11: 00000000004DAB18
R12: 0000000000000000 R13: 0000000000000000
R14: 0000000000000000 R15: 0000000000000000
Module Address Offset Function + Displacement # Params Possible Values Of First Four Params Decorated Function Name
================================================================================================================================================================================================================================
C:\Windows\SYSTEM32\ntdll.dll 0000000077B33290 00053290 RtlFreeHeap() + 208 bytes Unknown 00000000 00000000 00000000 00000000 RtlFreeHeap
C:\Windows\system32\kernel32.dll 000000007752300A 0002300a HeapFree() + 10 bytes Unknown 00000000 00000000 00000000 00000000 HeapFree
C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251\MSVCR90.dll 000000006E0FCABC 0004cabc free() + 28 bytes Unknown 00000000 00000000 00000000 00000000 free
C:\Program Files\Microsoft Configuration Manager\bin\x64\NotiCtrl.dll 000007FEF97560D6 000060d6 ConnectToShare() + 4254 bytes Unknown 00000000 00000000 00000000 00000000 ConnectToShare
C:\Program Files\Microsoft Configuration Manager\bin\x64\NotiCtrl.dll 000007FEF97569FF 000069ff ConnectToShare() + 6599 bytes Unknown 00000000 00000000 00000000 00000000 ConnectToShare
C:\Program Files\Microsoft Configuration Manager\bin\x64\NotiCtrl.dll 000007FEF975AC17 0000ac17 ThreadMain() + 9579 bytes Unknown 00000000 00000000 00000000 00000000 ThreadMain
C:\Program Files\Microsoft Configuration Manager\bin\x64\NotiCtrl.dll 000007FEF975B00D 0000b00d ThreadMain() + 10593 bytes Unknown 00000000 00000000 00000000 00000000 ThreadMain
C:\Program Files\Microsoft Configuration Manager\bin\x64\NotiCtrl.dll 000007FEF97587A0 000087a0 ThreadMain() + 244 bytes Unknown 00000000 00000000 00000000 00000000 ThreadMain
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll 00000000707F3F60 00043f60 CService::_NewThreadWrapper() + 28 bytes Unknown 00000000 00000000 00000000 00000000 ?_NewThreadWrapper@CService@@CAKPEAX@Z
C:\Windows\system32\kernel32.dll 000000007751652D 0001652d BaseThreadInitThunk() + 13 bytes Unknown 00000000 00000000 00000000 00000000 BaseThreadInitThunk
C:\Windows\SYSTEM32\ntdll.dll 0000000077B0C541 0002c541 RtlUserThreadStart() + 33 bytes Unknown 00000000 00000000 00000000 00000000 RtlUserThreadStart
WARNING: The stack could not be completely unwound. This is usually due to a
limitation in the stack unwinding algorithm, but it can also happen if the stack
itself was corrupted.
STACK TRACE FOR SMS_AMT_PROXY_COMPONENT THREAD 7724 (0x1e2c) AT 12/30/2013 13:08:44.150
CS: 0033 RIP: 0000000077B0C541 EFLAGS: 00000246
SS: 002b RSP: 00000000030BFC00 RBP: 0000000000000000
DS: 0000 ES: 0000 FS: 0000 GS: 0000
RAX: 0000000000C3CE30 RDX: 000000000000008C
RBX: 0000000000000000 RCX: 0000000000120000
RSI: 0000000000000000 RDI: 0000000000000000
R8: 0000000000C3CE20 R9: 0000000000C3CE30
R10: 0000000000000002 R11: 0000000000C3CE78
R12: 0000000000000000 R13: 0000000000000000
R14: 0000000000000000 R15: 0000000000000000
Module Address Offset Function + Displacement # Params Possible Values Of First Four Params Decorated Function Name
================================================================================================================================================================================================================================
C:\Windows\SYSTEM32\ntdll.dll 0000000077B3168A 0005168a NtQueryAttributesFile() + 10 bytes Unknown 00000000 00000000 00000000 00000000 NtQueryAttributesFile
C:\Windows\system32\KERNELBASE.dll 000007FEFE0B32C8 000032c8 GetFileAttributesW() + 120 bytes Unknown 00000000 00000000 00000000 00000000 GetFileAttributesW
C:\Windows\system32\KERNELBASE.dll 000007FEFE0B9784 00009784 GetFileAttributesA() + 68 bytes Unknown 00000000 00000000 00000000 00000000 GetFileAttributesA
C:\Program Files\Microsoft Configuration Manager\bin\x64\AmtUtil.dll 000007FEF40F152C 0005152c CAMTInboxManager::InitializeSiteComponentInbox() + 436 bytes Unknown 00000000 00000000 00000000 00000000 ?InitializeSiteComponentInbox@CAMTInboxManager@@QEAAJPEBD0@Z
C:\Program Files\Microsoft Configuration Manager\bin\x64\amtproxymgr.dll 000000007321107F 0001107f ThreadMain() + 9075 bytes Unknown 00000000 00000000 00000000 00000000 ThreadMain
C:\Program Files\Microsoft Configuration Manager\bin\x64\amtproxymgr.dll 0000000073213379 00013379 ThreadMain() + 18029 bytes Unknown 00000000 00000000 00000000 00000000 ThreadMain
C:\Program Files\Microsoft Configuration Manager\bin\x64\amtproxymgr.dll 000000007320DF0C 0000df0c CCertificateHashList::operator=() + 15580 bytes Unknown 00000000 00000000 00000000 00000000 ??4CCertificateHashList@@QEAAAEAV0@AEBV0@@Z
C:\Program Files\Microsoft Configuration Manager\bin\x64\amtproxymgr.dll 000000007320ECB5 0000ecb5 CAMTInboxManager::operator=() + 137 bytes Unknown 00000000 00000000 00000000 00000000 ??4CAMTInboxManager@@QEAAAEAV0@AEBV0@@Z
C:\Program Files\Microsoft Configuration Manager\bin\x64\amtproxymgr.dll 000000007320ED15 0000ed15 ThreadMain() + 9 bytes Unknown 00000000 00000000 00000000 00000000 ThreadMain
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll 00000000707F3F60 00043f60 CService::_NewThreadWrapper() + 28 bytes Unknown 00000000 00000000 00000000 00000000 ?_NewThreadWrapper@CService@@CAKPEAX@Z
C:\Windows\system32\kernel32.dll 000000007751652D 0001652d BaseThreadInitThunk() + 13 bytes Unknown 00000000 00000000 00000000 00000000 BaseThreadInitThunk
C:\Windows\SYSTEM32\ntdll.dll 0000000077B0C541 0002c541 RtlUserThreadStart() + 33 bytes Unknown 00000000 00000000 00000000 00000000 RtlUserThreadStart
WARNING: The stack could not be completely unwound. This is usually due to a
limitation in the stack unwinding algorithm, but it can also happen if the stack
itself was corrupted.
STACK TRACE FOR SMS_AI_KB_MANAGER THREAD 2468 (0x9a4) AT 12/30/2013 13:08:44.166
CS: 0033 RIP: 0000000077B0C541 EFLAGS: 00000246
SS: 002b RSP: 0000000001E4FC90 RBP: 0000000000000000
DS: 0000 ES: 0000 FS: 0000 GS: 0000
RAX: 0000000000000000 RDX: 0000000000000080
RBX: 0000000000000000 RCX: 0000000001E4F8A0
RSI: 0000000000000000 RDI: 0000000000000000
R8: 0000000070228A40 R9: 0000000001E4F878
R10: 0000000000000001 R11: 0000000001E4F790
R12: 0000000000000000 R13: 0000000000000000
R14: 0000000000000000 R15: 0000000000000000
Module Address Offset Function + Displacement # Params Possible Values Of First Four Params Decorated Function Name
================================================================================================================================================================================================================================
C:\Windows\SYSTEM32\ntdll.dll 0000000077B3186A 0005186a NtWaitForMultipleObjects() + 10 bytes Unknown 00000000 00000000 00000000 00000000 NtWaitForMultipleObjects
C:\Windows\system32\KERNELBASE.dll 000007FEFE0B1430 00001430 GetCurrentProcess() + 64 bytes Unknown 00000000 00000000 00000000 00000000 GetCurrentProcess
C:\Windows\system32\kernel32.dll 0000000077511220 00011220 WaitForMultipleObjects() + 176 bytes Unknown 00000000 00000000 00000000 00000000 WaitForMultipleObjects
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll 00000000707F4997 00044997 CService::YieldAndWait() + 1047 bytes Unknown 00000000 00000000 00000000 00000000 ?YieldAndWait@CService@@CAKKPEBQEAXHKKHHK@Z
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll 00000000707F3B36 00043b36 CService::YieldAndWaitForMultipleObjects() + 186 bytes Unknown 00000000 00000000 00000000 00000000 ?YieldAndWaitForMultipleObjects@CService@@SAKKPEBQEAXHKHK@Z
C:\Program Files\Microsoft Configuration Manager\bin\x64\basesvr.dll 00000000703A8A88 00188a88 CSMSObjectManager::WaitForEvents() + 464 bytes Unknown 00000000 00000000 00000000 00000000 ?WaitForEvents@CSMSObjectManager@@QEAAKHPEAPEAXK@Z
C:\Program Files\Microsoft Configuration Manager\bin\x64\aikbmgr.dll 0000000073234CF7 00004cf7 Unknown Unknown 00000000 00000000 00000000 00000000 Unknown
C:\Program Files\Microsoft Configuration Manager\bin\x64\aikbmgr.dll 0000000073235BFD 00005bfd ThreadMain() + 289 bytes Unknown 00000000 00000000 00000000 00000000 ThreadMain
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll 00000000707F3F60 00043f60 CService::_NewThreadWrapper() + 28 bytes Unknown 00000000 00000000 00000000 00000000 ?_NewThreadWrapper@CService@@CAKPEAX@Z
C:\Windows\system32\kernel32.dll 000000007751652D 0001652d BaseThreadInitThunk() + 13 bytes Unknown 00000000 00000000 00000000 00000000 BaseThreadInitThunk
C:\Windows\SYSTEM32\ntdll.dll 0000000077B0C541 0002c541 RtlUserThreadStart() + 33 bytes Unknown 00000000 00000000 00000000 00000000 RtlUserThreadStart
WARNING: The stack could not be completely unwound. This is usually due to a
limitation in the stack unwinding algorithm, but it can also happen if the stack
itself was corrupted.
ATTEMPTING TO WRITE OUT A MINIDUMP...
- Successfully wrote out a minidump.Hi,
I agree with Jason.
You'd better contact product support so that they can track the crash to see if there is a common theme
around it, thus the need for a hotfix. Or maybe there is already a hotfix for this that has not been made public yet.
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. -
Upgrade to SCCM 2012 R2 Fails by ADD SQL ACCOUNT
Hello,
im Testing Today the Upgrade to R2.
in Step to Upgrade the Database I become an Error xxx\Compuertname not found to add SQL Account
My Server name is xxx.de\computername an not xxx\computername (netbiosname with dot and same with DNS Name) .
Have anywhere an Idea as Workaround for me ?Microsoft support were no help...
I found a couple work arounds:
Move the database to the site server, do the upgrade, move the database back to the database server
Hack the DB:
create a login with a valid user account on the master DB on the SQL server
stop the sql server
Start SQL in single server mode
From an elevated cmd (Run as administrator), access the right folder where sqlservr.exe executable is located and execute below commands. Normally you will find it at “C:\Program Files\Microsoft SQL Server\MSSQL[InstanceName]\MSSQL\Binn”
C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn>sqlservr.exe -m
start SSMS in DAC mode: start SSMS, cancel the connection to the server,click on the
Database Engine Query icon (to the right of the new query button),and put admin: in front of the server name
run the following:
select @@servername
GO
use master
GO
sp_configure 'allow updates', 1
GO
reconfigure with override
GO
then do this:
update
master.sys.server_principals
set master.sys.server_principals.name
= 'domain\servername$'
where master.sys.server_principals.name
= 'domain.com\dummyaccount'
restart the sql server
upgrade SCCM
keep in mind i am currently testing this solution to make sure it doesn't cause issues -
SCCM 2012 RTM to SP1 Upgrade - Windows ADK 8.1
Hello,
I am after some advice. We have two physical locations containing a single SCCM 2012 primary site server in one location and distribution point server in the other location.
Both servers are also configured as DHCP Servers and DHCP scope options have been configured correctly to allow both DHCP and Windows Deployment Services to co-exist.
OSD was working fine, until I upgraded the primary site server to SCCM 2012 SP1. During the upgrade process, I installed Windows ADK 8.1 which would appear is not supported however no errors were reported during the upgrade process.
Issues I have encountered;
- I can no longer PXE boot with the following error 'PXE-E55: ProxyDHCP service did not reply to request on port 4011'
- The x:\remoteInstall\Boot\Fonts directory is empty suggesting the boots images were not finalised.
- When updating the distribution points with the boot images i get the following error via the wizard;
• The SMS Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
• Description = "Failed to insert OSD binaries into the WIM file";
• ErrorCode = 2152205056;
• File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
• Line = 4566;
• ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
• Operation = "ExecMethod";
• ParameterInfo = "SMS_BootImagePackage.PackageID=\"UKS0003B\"";
• ProviderName = "WinMgmt";
• StatusCode = 2147749889
SMSPXE.log contains the following errors;
Failed to copy X:\RemoteInstall\SMSTempBootFiles\XXX00014\WINDOWS\Boot\PXE\wdsmgfw.efi to X:\RemoteInstall\SMSBoot\x86\wdsmgfw.efi
InstallBootFilesForImage failed. 0x80070002
Warning: Failed to copy the needed boot binaries from the boot image X:\RemoteInstall\SMSImages\XXX00014\WinPE.XXX00014.wim.
The operation completed successfully. (Error: 00000000; Source: Windows)
Failed adding image X:\RemoteInstall\SMSImages\XXX00014\WinPE.XXX00014.wim. Will Retry..
The system cannot find the file specified. (Error: 80070002; Source: Windows)
Failed to read ADK installation root registry value
I am looking for some advice on the best way to rectify this issue. Options I am considering are as follows, however I am unsure of the outcome should I attempt these;
1 - Upgrade to SCCM 2012 R2 which supports ADK 8.1
2 - Uninstall Windows ADK 8.1, install 8.0
3 - Attempt to restore back to SCCM 2012 RTM using file system backups and SCCM backups.
Any help or suggestions would be much appreciated.Thank you both for your replies and advice
The configMgr 2012 environment is primarily used for OSD, and software updates for Servers only.
I have followed Peter’ advice, and uninstalled WADK 8.1 and installed 8.0 and I am currently investigating errors within the SMSPXE.log, and I have seen other posts elsewhere within these forums
with the same issue with suggested solutions which I shall investigate.
With regards to DHCP on the ConfigMgr site servers – I could not agree with you more.
Unfortunately, my company use a third party DHCP solution which was incapable of supporting PXE-boot for OSD.
We were therefore required to have a separate Microsoft DHCP solution on the site servers to by-pass this issue.
The intention is to upgrade to Configmgr 2012 R2.
My understanding is that there is no direct upgrade process from SCCM 2012 RTM to R2, therefore I have upgraded to SP1 and would prefer all features are working correctly before progressing to R2.
Many thanks again,
Regards,
JohnRox -
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 -
Reports are not opening after SCCM 2012 R2 Upgrade
Hi,
I have upgraded my SCCM 2012 SP1 to R2, After that I am unable to run a report and getting below error
System.Web.Services.Protocols.SoapException: The DefaultValue expression for the report parameter ‘UserTokenSIDs’ contains an error: Logon failure: unknown user name or bad password.
Seems it is a known issue after R2 upgrade,To resolve this issue we need to change the registry value for "EnableRbacReporting" to "0" under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SRSRP.
It was fine for some time,Later its value reverted back to "1" on its own and again reports stopped working.
Is there any other way to resolve this issue in order to make sure my reports are always available
Please help me.Thanks
srkrHi Paul,
We recently upgraded our SCCM 2012 R2 servers to OS 2012 R2, Now i could not able to see the path you mention in your blog.
mofcomp.exe “C:\Program
Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof”
Bear in mind that the above command is for SQL Server 2008 and it assumes that SQL is installed in its default location.
The command for SQL Server 2012 is:
mofcomp.exe “C:\Program
Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof”
I can only see D:\Program Files (x86)\Microsoft SQL Server\100\<Below
folders>
DTS
SDK
Tools
srkr -
SCCM 2012 R2 upgrade & broken reports
After upgrading to R2, everything went off w/o a hitch until we tried to run reports (see below for error)
Weird part is *some* of the admins can run reports just fine (for instance, two separate AD groups that are a part of the Full Administrators within SCCM, one can run, while the others cannot). We can also do this solution: http://www.netdavidic.com/2013/11/how-to-fix-sccm-2012-r2-reporting.html .
While this works, it is not a viable solution moving forward.
Our setup is pretty simple; single site server w/ all services, 2-3 DP's etc. Server 2012, SQL 2012 SP1. We upgraded from SCCM 2012 SP1.
The DefaultValue expression for the report parameter ‘UserTokenSIDs’ contains an error: The user name or password is incorrect.
(rsRuntimeErrorInExpression)
Microsoft.Reporting.WinForms.ReportServerException
The DefaultValue expression for the report parameter ‘UserTokenSIDs’ contains an error: The user name or password is incorrect.
(rsRuntimeErrorInExpression)
Stack Trace:
at Microsoft.Reporting.WinForms.ServerReportSoapProxy.OnSoapException(SoapException e)
at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ProxyMethodInvocation.Execute[TReturn](RSExecutionConnection connection, ProxyMethod`1 initialMethod, ProxyMethod`1 retryMethod)
at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
at Microsoft.Reporting.WinForms.ServerReport.EnsureExecutionSession()
at Microsoft.Reporting.WinForms.ServerReport.SetParameters(IEnumerable`1 parameters)
at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerWindowsForms.SetParameterValues_DoWork(Object sender, DoWorkEventArgs e)
-------------------------------Update:
TL;DR If you're running SQL services under a different context other than Local Service, you'll have problems.
The ultimate solution was this: http://social.technet.microsoft.com/Forums/en-US/77bad9b6-de0e-42d3-ae9f-e7c9d26b4330/reporting-error-after-upgrading-to-sccm-2012-r2?forum=configmanagergeneral
However, I'll provide a bit more detail in case anyone else runs into this.
In our environment, we run all SQL services as a separate account, say domain\CMSQLSERVICE account (so if you looked at the services, you'd see SQL Server, SQL Server Agent & SQL Server Reporting Services all running as CMSQLSERVICE). We also run
reporting as another account, say domain\CMSQLREPORTING account (SCCM console, Admin, Site Config, Servers & Sites, Reporting services point). Placing CMSQLREPORTING account into the Windows Authorization Access Group did not resolve the issue as
I had thought. We then placed CMSQLSERVICE account in there & everything worked as intended.
You'll be able to easily see the errors by looking on the reporting point / server with the SQL database for C:\Users\ACCOUNTRUNNINGSQLSERVICE\AppData\Local\Temp .
It took procmon to lead me to that location for the ultimate solution.
Maybe you are looking for
-
I am running a MacBook Pro (late 2012) with the most recent version of Yosemite (version 10.10.2). Whenever I have the search dialog box open in one PDF and I attempt to open another PDF, Reader crashes. Supposedly this bug was fixed with the 11.0.10
-
New to JDeveloper, having problems with EJB tutorial.
Hi, I'm new to the world of JDeveloper, I'm trying to follow this tutorial http://st-curriculum.oracle.com/obe/jdev/obe11jdev/ps1/ejb/ejb.html Firstly when I create an entity from a table I get the following error; Starting Offline Database Synchroni
-
I want to install Lightroom 5, but I get this message an error occurred of the installation of assembly component (5C21D397-1DA5-3749-8C1F-165F21DE9E3E) HRESULT: 0x8007054F. I have Windows 7.
-
BSP - Client with Account Group
Hi all, we just finished upgrading our Support Package to level 10 (SAPKU40010) and we get now a new problem with BSP application. Everytime the BP is created via BSP application, the screen stays in "Change" mode and furthermore there is a Bdoc erro
-
Adobe authorization is not working, what does Sha-1 implementation not found (error code 2004) mean?