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.

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-MCSE

Hello 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

Problems after upgrade from SCVMM 2012 Sp1 to SCVMM 2012 R2

I did a in-place (uninstall VMM2012 Sp1, retain the database, and install VMM2012 R2 point to old database) upgrade. All the steps work fine.
The only problem (so far) is that when I create a new VM using a custom template (for example, Windows 2008 R2), the deploy fail with the following error:
Error (2912)
An internal error has occurred trying to contact the vm-scvmm2012.domain.com server: NO_PARAM: NO_PARAM.
WinRM: URL: [http://vm-scvmm2012.domain.com:5985], Verb: [INVOKE], Method: [GetError], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/microsoft/bits/BitsClientJob?JobId={56B8E488-5DB9-4CC1-BEFA-AFF76E1E4D2D}]
Unknown error (0x80072f0d)
Recommended Action
Check that WS-Management service is installed and running on server vm-scvmm2012.domain.com. For more information use the command "winrm helpmsg hresult". If vm-scvmm2012.domain.com is a host/library/update server or a PXE server role then ensure
that VMM agent is installed and running. Refer to http://support.microsoft.com/kb/2742275 for more details.
Information (26278)
VMM could not offload transfer the file \\vm-scvmm2012.domain.com\MSSCVMMLibrary\VHDs\Template_Windows_2008_R2_SP1.vhdx to C:\ClusterStorage\Volume1\VM-NEWVM\Template_Windows_2008_R2_SP1.vhdx.
Any ideas?

I have a similar problem when migrating VMs from Windows 2008 R2 (Non Clustered) Hyper-V to Windows 2012 Hyper Cluster. I had previously migrated about 100 VMs like this with no problem. It appears since upgrading from VMM SP1 Rollup 4 to Rollup 5 this problem
is happening. All Agents are up to date.
I can migrate VMs in the cluster no problem.
I removed the Windows 2008 R2 Hyper-V host and added it back which allowed the job to at least start but when it gets to the final steps of importing the VM it fails with the same error and references the VMM server.
Others suggest this is a VMM Certificate problem and you can remove the Cluster node and add it back again but I can't do that in a production Cluster with hundreds of VMs. That is not an acceptable solution.
How can we fix this?

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

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 14

This 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

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

Missing Event Viewer VM Manager Log after ugrade from SCVMM 2012 SP1 to R2

We recently upgraded from SCVMM 2012 SP1 to SCVMM 2012 R2. After the upgrade, I noticed that the VM Manager log, in the Event Viewer, is missing. I've tried to peruse all of the logs to see if it has been moved/renamed, with no luck. I highly doubt an important
log would be removed without a replacement being available, so I'm curious if it was something that had to be enabled (isn't turned on by default).
I had scripts which relied on the log for VM status changes, Event ID 821 (shut down/running/etc), to keep a last-used database for all of the VMs on our cloud.
Has anyone run in to this problem, or have any idea how I can get get the information that was available in the VM Manager log?
Thank you.

I have a similar problem when migrating VMs from Windows 2008 R2 (Non Clustered) Hyper-V to Windows 2012 Hyper Cluster. I had previously migrated about 100 VMs like this with no problem. It appears since upgrading from VMM SP1 Rollup 4 to Rollup 5 this problem
is happening. All Agents are up to date.
I can migrate VMs in the cluster no problem.
I removed the Windows 2008 R2 Hyper-V host and added it back which allowed the job to at least start but when it gets to the final steps of importing the VM it fails with the same error and references the VMM server.
Others suggest this is a VMM Certificate problem and you can remove the Cluster node and add it back again but I can't do that in a production Cluster with hundreds of VMs. That is not an acceptable solution.
How can we fix this?

Uninstall utorrent 3.3 version Silently from SCCM 2012 Sp1

Hi All,
i am trying to uninstall utorrent application in my environment having 2000+ users from SCCM 2012 Sp1. The application will become available on client side but uninstallation not happening silently.
Please suggest something on this..
Thanks Rahul$

Hi,
I created one batch file & create the package with no program for the same & deployed. It's successfully uninstall uTorrent application from client machines:
@echo off
REM Uninstall existing uTorrent Version
if exist "%Program Files%\uTorrent\uTorrent.exe" "%Program Files%\uTorrent\uTorrent.exe" /UNINSTALL /S
if exist "%Program Files (x86)%\uTorrent\\uTorrent.exe" "Program Files (x86)%\uTorrent\uTorrent.exe" /UNINSTALL /S
if exist "%USERPROFILE%\AppData\Roaming\uTorrent\uTorrent.exe" "%USERPROFILE%\AppData\Roaming\uTorrent\uTorrent.exe /UNINSTALL /S
SET ERRORCODE=0
Thanks Rahul$

Upgrading from SCOM 2012 SP1 to SCOM 2012 R2 what CU do i install? CU5?

Hi,
I just upgraded from SCOM 2012 SP1 to SCOM 2012 R2. What CU version should I install? CU5?
Thanks
K

The most current CU version os SCOM 2012R2 is CU4
You can download it from
https://support.microsoft.com/kb/2906925?wa=wsignin1.0
For detail description of SCOM 2012 R2 CU4, you may refer to
http://support.microsoft.com/kb/2992020
and
http://syscentercldman.blogspot.hk/2014/12/update-of-scom-2012-r2-ur4.html
Roger

¿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

Problem upgrading from SCOM 2012 SP1 to R2 (near impossible to uninstall SCOM agent from Management Server)

I'm trying to upgrade our SCOM 2012 SP1 environment to R2, but I have a heck of a problem getting there.
We currently have an test installation with SCOM 2012 SP1 with Management Server and Console on a single 2012 Standard server. The database are located on a remote server. The R2 setup stopped mid way through the setup, because the SCOM 2012 SP1 agent is
installed. And I could NOT remove it my any normal means. I've tried "misexec.exe /x productcode", the setup, powershell uninstall and so on. Nothing works, because the management server installation is blocking the uninstall. The uninstall says
I have to remove the management installation first. And that's not gonna happen.
I had to follow this guide to finally getting through the setup: http://www.opsman.co.za/forcibly-removing-a-scom-agent-that-cannot-be-uninstalled-by-normal-means/
In addition to searching for the agent msi install key in registry, and deleting everything. After I did this, the setup is working, and the SCOM management server, console and DB are up to date. However, the Microsoft Monitoring Agent are STILL there in
Control Panel. And this can NOT be the most healthy way of getting through the setup.
I'm about to upgrade to R2 in our production environment with 3 management servers, and I would hate to go through this sketchy process there as well. Just for the record, I have no idea why the agents are installed on our management servers.
Any of you have tips as to how I can get rid of the agents more gracefully?

Hi
Thanks for the replay guys!
None of those links touch my problem I'm afraid. I have followed the Upgrade guides you pointed to, step by step. But the setup does not Complete. There's problems during the actual software Upgrade of the management servers (3'rd step in the Upgrade page).
I've dived into the Application logs and installation logs, and as far as I can tell, it stops because it has trouble upgrading while the server has the 2012 SP1 Agent installed. I do not remember the actual error text right now, but I can get it in a few
days.
Anyhow, the setup DID move on once I removed most of the registry information of the agent installation. So. that leaves me to the conclusion that the agent IS in fact stopping the setup. Either the agent are malfunctioning, or the setup do not expect the
agent to be present on the management servers. I suspect the latter to be the the most plausible. At least until Yan Li told me this was normal.
So, I'm not sure what to think. I'm pretty much forced to remove this agents, as this is the only thing allowing me to continue the setup. At least untill I'm told otherwise. But I hate to do it this way. It's so dirty. The registry is pretty much cleaned,
but there's still Application files present, and the agent is still in the Control panel and can be started. It's not something I would like to do in our prodution environment.

Windows Updates are not getting download after installation of SCCM 2012 SP1

I have installed SCCM 2012 SP1 step by step as per microsoft documents, Now I am getting error while downloading windows updates from microsoft site.
Error by WCM.log : System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport
connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
Error By wsyncmgr: DB Server not detected for SUP XYZ.com from SCF File. skipping.
Sync failed: WSUS update source not found on site KSL. 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=KSL-MUM-SCCM01.KSEC.KotakGroup.com SITE=KSL PID=3688 TID=4752 GMTDATE=Tue May 21 10:59:06.745 2013 ISTR0="getSiteUpdateSource" ISTR1="WSUS
update source not found on site KSL. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
I have reinstall my SUP on site server, i have my WSUS & site server is on same server. I have kept my sup setting as per requirment (8530 & 8531)
Kindly suggest is any other settings need to be done on server side.

Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
From your log snip-it, it looks like the firewall is causing your problem. Temporary turn off the firewall and see if that solves your problem.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Messages crashes repeatedly after upgrade to Mavericks

After upgrading to Mavericks, Messages crashes repeatedly.
Macbook Pro 17", circa 2011 I think, OS X 10.9.2.
Immediately after upgrading to Mavericks it would just crash when I scrolled down through my conversation history, but if I just searched for conversations it was generally functional.
Following some Apple Support Communities advice I renamed several directories, hoping that if I clear out the message history and start from "scratch" I would have better luck. I mv'd all the directories in:
~/Library/Containers/com.apple.ichat/Data/Library/Messages
~/Library/Messages
After rebooting my laptop the conversation history cleared out like I had hoped, and as messages started coming in the chat.db, Archive, etc. folders were generated in the above directories like I expected. It was generally functional for a couple hours.
Now it crashes immediately on open. Here is first bit of the "Problem Details and System Configuration"
Process:         Messages [4886]
Path:            /Applications/Messages.app/Contents/MacOS/Messages
Identifier:      com.apple.iChat
Version:         8.0 (4226)
Build Info:      iChat-4226000000000000~3
Code Type:       X86-64 (Native)
Parent Process: launchd [231]
Responsible:     Messages [4886]
User ID:         505
Date/Time:       2014-04-11 08:31:59.572 -0400
OS Version:      Mac OS X 10.9.2 (13C64)
Report Version: 11
Anonymous UUID:
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
[4886] stack overflow
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib                  0x00007fff949cb866 __pthread_kill + 10
1   libsystem_pthread.dylib                 0x00007fff8a9f235c pthread_kill + 92
2   libsystem_c.dylib                       0x00007fff8ab5bbba __abort + 145
3   libsystem_c.dylib                       0x00007fff8ab5c46d __stack_chk_fail + 196
4   com.apple.ImageIO.framework             0x00007fff88232e10 initImageJPEG + 7028
5   ???                                     0xffff9fffffd43cdf 0 + 18446638520590417119
6   ???                                     0x0000058f00000311 0 + 6111738462993
Any ideas?
Thanks!

Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Step 1
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the name of the crashed application or process in the Filter text field. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.
Step 2
In the Console window, look under User Diagnostic Reports (not "Diagnostic and Usage Messages") for crash reports related to the crashed process. The report name starts with the name of the process, and ends with ".crash". Select the most recent report and post the entire contents—again, the text, not a screenshot. I know the report is long. Please post all of it anyway.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

Search Service Application problems after upgrading from Foundation to Enterprise edition of SharePoint 2013

Hi all. I have been searching for days for a solution to a problem I am having with SP2013 Enterprise edition.
We recently upgraded from SP2013 Foundation to SP2013 Enterprise. After the upgrade, the search services are no longer working and we are receiving many application log entries indicating the following:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (ea2019ef-bb9e-4efe-85ee-5d2307406f31).
Reason: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Technical Support Details:
System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
as well as:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (ea2019ef-bb9e-4efe-85ee-5d2307406f31).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
I have tried to remove the search service application and recreate it, and even though the SharePoint Central Administration states that it was created successfully, I am still getting the same errors in the log. If I go to the Search Service Application
Search Administration page, the "System Status" shows the following message:
The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '0359af35-0982-4ede-8838-b1d390e915bf' in search application 'Search Service Application' is in a good state and
try again
Additionally, under the "Search Application Topology" section, it states "Unable to retrieve topology component health states. This may be because the admin component is not up and running" which I assume is normal if the admin is not
running.
Does anyone know how I can resolve this problem?
Thanks!

Hi Joaquin,
According to your description, the error occurred when you re-created the Search Service Application.
Based on the error message, I recommend to verify the things below:
   1. Check if the association between the Search Service Application proxy and the web application is configured.
Please go to Central Administration > Application Management > Configured service application associations > Click Default to see if the Search Service application is checked.
   2. Change the app pool for the Search Service Application to SharePoint Web Services Default in the properties of the Search Service Application.
Please go to Central Administration > Application Management > Manage service applications > Highlight the Search Service Application > Click Properties in the ribbon > Change
the two app pool to SharePoint Web Services Default: App Pool For Search Admin Web Service and Application Pool for Search Query and Site Settings Web Service.
    3. Run PS command to check if the search admin timer job is enabled: Get-SPTimerJob
job-application-server-admin-service | fl. If it is not enabled, use PS command to enabled it and then reset Internet Information Services: Enable-SPTimerJob job-application-server-admin-service.
Best regards.
Thanks
Victoria Xia
TechNet Community Support

SMS_Exec service crashing repeatedly after upgrade from SCCM 2012 SP1 to 2012R2

Similar Messages

Maybe you are looking for