Tuesday, January 29, 2013

Troubleshooting Configuration Manager 2012/2007 and SMS 2003 unhandled exceptions (Crash Dump)


I have experienced most of the time when SMS Executive stop and when I see in logs folder, crash folder, and I found SMS Executive service again crashed. This is happening due to unhandled exception.
What is an unhandled exception?
In almost every Configuration Manger crash there is an exception involved. An exception occurs when an instruction is attempted but fails for some reason (e.g. an Access Violation), so when an exception occurs we need information about that exception or what was in memory when the exception occurred.
Most applications have their own exception handling code and Configuration Manager is no different. Configuration Manager has its own exception handler that is designed to collect certain predefined data such as thread stack information and other data when the exception has occurred. Note that it is also sometimes necessary to do live debugging or post mortem debugging when an application/OS crashes using the Windows debugging tools.
Components that could cause unhandled exception
SMS Executive: SMSEXEC.EXE is the main service that calls many threads. Any running thread will terminate SMS_EXECUTIVE service if an exception occurs in the thread, and the Configuration Manager site server exception handler will collect the required data.
Data collected when Configuration Manger site server encounters an exception
- A log file (CRASH.LOG) that details the thread stacks and very basic information.
- All current .LOG files from the \LOGS folder. These are saved in the \LOGS\CRASHDUMPS\YYYYMMDD_000XX folder where YYYYMMDD is the date when the crash occurred and XX represents the number of crashes in that day.
- An individual thread log for every component at the time of the failure. These files have no extension but can be viewed in any text editor or SMS Trace or CM Trace.
Depending on the nature of crash and current memory conditions, not all of the above information will be captured. Here’s an example:
With this in mind, here are some steps you can do if you experience one of these crashes:
1. Check the LOGS\CRASHDUMPS\CRASH.LOG file and make a note of the failing component and thread ID.

2. Locate the <component>_thread_<thread number> in \Logs and open in a text editor such as Notepad.
3. Look at the bottom of the log to identify the last thing the component was doing when the crash occurred.
4. Take corrective action based on what was occurring. Often there will be a reference in the log to a specific file or object that is causing the crash.
NOTE If nothing useful is found in the log file, a memory dump could be used to analyze the issue deeper.
In our example, examining the CRASH.LOG shows the following:
EXCEPTION INFORMATION
Time = 08/29/2012 17:28:47.406
Service name = SMS_EXECUTIVE
Thread name = SMS_AD_SYSTEM_DISCOVERY_AGENT
Executable = D: \Microsoft Configuration Manager\bin\i386\smsexec.exe
Process ID = 11789 (0x2E0D)
Thread ID = 13565 (0x33FD)
Instruction address = 77bd8efa
Exception = c0000005 (EXCEPTION_ACCESS_VIOLATION)
Description = "The thread tried to read from the virtual address 00000000 for which it does not have the appropriate access."
Raised inside CService mutex = No
Examining the corresponding <component>_thread_<thread number> we can see the following:
Starting the data discovery. SMS_AD_SYSTEM_DISCOVERY_AGENT
INFO: Processing search path: 'LDAP://OU=xxx ,OU=xx,DC=GLOBAL,DC=xx,DC=xx'. SMS_AD_SYSTEM_DISCOVERY_AGENT
INFO: Full synchronization requested SMS_AD_SYSTEM_DISCOVERY_AGENT
INFO: DC DNS name = 'FQDN' SMS_AD_SYSTEM_DISCOVERY_AGENT
So by looking at this it becomes apparent that the Active Directory System Discovery method is causing the exception to occur. From this point you could continue troubleshooting the cause of the issue with Active Directory System Discovery, or perhaps if this is a secondary site you could disable the Active Directory System Discovery if you do not need it.

Friday, January 25, 2013

System Center 2012 SP1 is Generally Available, but contains a lot of bugs. Here's a list of ConfigMgr issues known

We have obseved, after installaing CM12 SP1, we have known lots of error and issues,

I am giving all those errors/bugs and those resolutions..

1-Active Replica Error after the SP1 upgrade for ConfigMgr 2012
2-Server 2012 OSD Issues in ConfigMgr 2012 SP1
3-System Center 2012 Configuration Manager Application Catalog does not refresh on F5 in Windows 8 or Windows Internet Explorer 10
4-ConfigMgr 2012 SP1 client installation error with MicrosoftPolicyPlatformSetup.msi -    Hotfix Available!
5-Changes to built-in collections are overwritten when you upgrade to System Center 2012 Configuration Manager SP1 http://support.microsoft.com/kb/2739984
6-Antimalware Policies issue, a workaround, and a forgotten Beta message with ConfigMgr 2012 SP1 http://myitforum.com/myitforumwp/2013/01/09/antimalware-policies-issue-a-workaround-and-a-forgotten-beta-message-with-configmgr-2012-sp1/
7-Service Pack 1 for MS ConfigMgr 2012 Resets the SUP Port to 80 and Why does WSUS not sync anymore in ConfigMgr 2012 SP1? http://myitforum.com/myitforumwp/2013/01/08/service-pack-1-for-ms-configmgr-2012-resets-the-sup-port-to-80/
8-Application Catalog link breaks if you change the regional settings decimal separator in Software Center in System Center 2012 Configuration Manager http://support.microsoft.com/kb/2801822
10-The 8dot3name settings are disabled on the volumes upon partitioning and formatting of the local disk http://scug.be/sccm/2013/01/15/configmgr-2012-sp1-the-8dot3name-settings-are-disabled-on-the-volumes-upon-partitioning-and-formatting-of-the-local-disk/
11-Antivirus can cause corruption and/or incomplete installations
12-Missing PCM icon even after a successful installation - Workaround available
13-Application evaluation fails in System Center 2012 Configuration Manager running on Windows XP http://support.microsoft.com/kb/2798545
14-Unhandled exception when launching the System Center 2012 Configuration Manager SP1 Console (Microsoft.ConfigurationManagement.exe) http://support.microsoft.com/kb/2800707
17-Virtual Application Fails to Install with Event ID 1008 in the Windows Applications and Services Logs  
18-A Migrated Configuration Manager 2007 Configuration Baseline Fails to Evaluate on Client Computers
19-Error Microsoft.Reporting.WinForms.ReportServerException when you run the Roaming User Profiles Health Report http://myitforum.com/myitforumwp/docs/system-center-2012-sp1-woes-gotchas-and-workarounds/

Tuesday, January 8, 2013

Service Pack 1 for MS ConfigMgr 2012 Resets the SUP Port to 80

When you apply Service Pack 1 to Microsoft System Center Configuration Manager (ConfigMgr) 2012, ConfigMgr improperly resets the port value in the software update point (SUP) configuration options to port 80. This breaks the update publishing functionality in ConfigMgr if the SUP server was previously configured to use an alternative port. For example, if the SUP is a WSUS v6 server (included with Windows Server 2012) using the default WSUS configuration, the port needs to be 8530.

How to resolve this issue-

You will have to follow following steps:-

  1. In the left pane of the ConfigMgr 2012 console, click the Administration heading.
  2. In the center pane on the Administration page, select the SUP server in the top pane.
  3. In the Site System Rules pane (center-bottom), select Software update point.
  4. In the ribbon, click Properties.
  5. In the Software update point Properties window, configure the Port Numberand SSL Port Number as appropriate.
  6. Click Ok