Sander's space

Just another WordPress.com site

CcmExec.exe Crashing

Posted by Sander on December 30, 2011

On my SCCM 2007 SP2 R3 Central Site Server I have been experiencing the following errors on the Application log:

Problem Description:

 

Error 1:

Level: Error

Source: Application Error

EventID: 100

Task Category: 100

 

Faulting application name: CcmExec.exe, version: 4.0.6487.2000, time stamp: 0x4ab33e4d

Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba58

Exception code: 0xc0000005

Fault offset: 0x0009ce04

Faulting process id: 0xfefc

Faulting application start time: 0x01ccc62e7266ed78

Faulting application path: C:\Windows\SysWOW64\CCM\CcmExec.exe

Faulting module path: C:\Windows\SysWOW64\ntdll.dll

Report Id: 1c2a5ad0-322a-11e1-afc7-005056b22f84

 

Error 2:

Level: Error

Source: SMS Server

EventID: 5436

Task Category: SMS_MP_CONTROL_MANAGER

 

On 12/29/11 15:34:25, component SMS_MP_CONTROL_MANAGER on computer %Servername% reported: MP Control Manager detected management point is not responding to HTTP requests. The HTTP status code and text is 500, Internal Server Error.

Possible cause: Management point encountered an error when connecting to SQL Server.
Solution: Verify that the SQL server is properly configured to allow Management Point access. Verify that management point computer account or the Management Point Database Connection Account is a member of SMS Management Point Role (msdbrole_MP) in the SQL Server database.

Possible cause: The SQL Server Service Principal Names (SPNs) are not registered correctly in Active Directory
Solution: Ensure SQL server SPNs are correctly registered. Review Q829868.

Possible cause: Internet Information Services (IIS) isn’t configured to listen on the ports over which SMS is configured to communicate.
Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use.

Possible cause: The designated Web Site is disabled in IIS.
Solution: Verify that the designated Web Site is enabled, and functioning properly.

Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges.
Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy.

For more information, refer to Microsoft Knowledge Base article 838891.

 

Troubleshooting Steps

 

Verified was able to access MP URL

http://%ServerName%/SMS_MP/.sms_aut?MPcert

http://%ServerName%/SMS_MP/.sms_aut?MPlist

Checked MPControl.log

Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error SMS_MP_CONTROL_MANAGER 12/29/2011 2:29:25 PM 7148 (0x1BEC)

Http test request failed, status code is 500, ‘Internal Server Error’. SMS_MP_CONTROL_MANAGER 12/29/2011 2:29:25 PM 7148 (0x1BEC)

STATMSG: ID=5436 SEV=E LEV=M SOURCE=”SMS Server” COMP=”SMS_MP_CONTROL_MANAGER” SYS=%ServerName% SITE=%SiteCode% PID=9608 TID=7148 GMTDATE=Thu Dec 29 13:29:25.065 2011 ISTR0=”500″ ISTR1=”Internal Server Error” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0 SMS_MP_CONTROL_MANAGER 12/29/2011 2:29:25 PM 7148 (0x1BEC)

Checked the IIS Logs (Seems like fine)

2011-12-29 13:59:25 ::1 GET /SMS_MP/.sms_aut MPLIST 80 – ::1 SMS_MP_CONTROL_MANAGER 200 0 0 15

We checked the Status Message and found 5436 is happening every 65 mins

Severity Type Site code Date / Time System Component Message ID Description

Error Milestone %SiteCode% 12/29/2011 2:29:25 PM %ServerName% SMS_MP_CONTROL_MANAGER 5436 MP Control Manager detected management point is not responding to HTTP requests. The HTTP status code and text is 500, Internal Server Error.

Possible cause: Management point encountered an error when connecting to SQL Server.
Solution: Verify that the SQL server is properly configured to allow Management Point access. Verify that management point computer account or the Management Point Database Connection Account is a member of SMS Management Point Role (msdbrole_MP) in the SQL Server database.

Possible cause: The SQL Server Service Principal Names (SPNs) are not registered correctly in Active Directory
Solution: Ensure SQL server SPNs are correctly registered. Review Q829868.

Possible cause: Internet Information Services (IIS) isn’t configured to listen on the ports over which SMS is configured to communicate.
Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use.

Possible cause: The designated Web Site is disabled in IIS.
Solution: Verify that the designated Web Site is enabled, and functioning properly.

Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges.
Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base article 838891.

Severity Type Site code Date / Time System Component Message ID Description

Error Milestone %SiteCode% 12/29/2011 10:12:39 AM %ServerName% SMS_MP_CONTROL_MANAGER 5420 SMS management point encountered an error when connecting to the database SMS_%SiteCode% on SQL Server %SQL Server Instance%. The OLEDB error code was 0x80004005.

Possible cause: The computer running SQL Server is turned off, not connected to the network, or not functioning properly.
Solution: Verify that the computer running SQL Server site system is turned on, connected to the network, and functioning properly.

Possible cause: Management point does not have sufficient access rights to the SQL server site system.
Solution: Verify that management point computer account or the Management Point Database Connection Account is a member of SMS Management Point Role (msdbrole_MP) in the SQL Server database.

Possible cause: Network problems are preventing the management point from properly accessing the SQL Server.
Solution: Investigate and correct any problems with your network.

Possible cause: The management point having problems is at a secondary site, and SQL access account being used was recently reset by the parent site.
Solution: This can automatically repair itself after one hour , as long as the account in use is not locked out. Check that the account in use is not locked out. Instead of waiting an hour, you can stop and start the SMS_SITE_COMPONENT_MANAGER service to immediately apply the new configuration.

Possible cause: The SQL server Service Principal Names (SPNs) are not registered correctly in Active Directory
Solution: Ensure SQL server SPNs are correctly registered. Review Q829868.

Created a Test.UDL file and was able to connect to the SQL Server instance under user context
Opened a CMD.exe under System Context (PSExec) and verified connectivity to SQL Server Instance under System Context

 

This is a known bug with CCM_caltrack.dll

Ran Logman query –ets > c:\logman.txt

Data Collector Set                      Type                          Status

——————————————————————————-

Eventlog-Security                       Trace                         Running

Audio                                   Trace                         Running

DiagLog                                 Trace                         Running

EventLog-Application                    Trace                         Running

EventLog-System                         Trace                         Running

NtfsLog                                 Trace                         Running

UBPM                                    Trace                         Running

WdiContextLog                           Trace                         Running

TracingGuidsBID                         Trace                         Running

TracingGuidsConfigService               Trace                         Running

TracingGuidsNative                      Trace                         Running

TracingGuidsScript                      Trace                         Running

TracingGuidsUI                          Trace                         Running

MSDTC_TRACE_SESSION                     Trace                         Running

WDC.BE95A9B1-DE15-4B78-B923-A12AB70BE951 Trace                         Running

 

The command completed successfully.

We stopped the ETW Tracing for WDC.BE95A9B1-DE15-4B78-B923-A12AB70BE951
  1. Start the Server Manager on the target server, “diagnosis” – “Performance” – “Data Collector Sets” in the left pane and select.
  2. “Event Trace Sessions” and select the right pane “WDC.BE95A9B1-DE15-4B78-B923-A12AB70BE951” look for the named session. For the session “Stop”
  3. Go to Startup event trace session, select “WDC.BE95A9B1-DE15-4B78-B923-A12AB70BE951” and properties \ Trace Session\ uncheck “enabled”.

Problem fixed.

 

Advertisements

One Response to “CcmExec.exe Crashing”

  1. Wouter Sonneveldt said

    Thanks, I had the exact same error and your solution fixed the problem!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: