The sms_executive service starts and crashes shortly after. The below message appears in the event logs. 

Faulting application name: smsexec.exe, version: 5.0.7958.1000, time stamp: 0x5230e560
Faulting module name: baseobj.dll, version: 5.0.7958.1000, time stamp: 0x5230e4fe
Exception code: 0xc0000005
Fault offset: 0x00000000000e647e
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
Faulting package full name: %14
Faulting package-relative application ID: %15

Shortly after this message appears there is a .net error as below. 

Application: smsexec.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 000000005114647E

I've also checked out the crash dump and get the following error. 

This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(10bc.22f4): Access violation - code c0000005 (first/second chance not available)
ntdll!NtWaitForSingleObject+0xa:
00007ff8`850865ba c3              ret
0:105> excr
Couldn't resolve error at 'xcr'

I'm really at a loss to explain what is going on here after hours spent searching I'm unable find any knowledge base articles that are for similar issues. Any help would be appreciated. 

Have you tried repairing the .Net Framework installation?

Have you disabled your AV?

Have you verified that a hardware failure is not the source of the issue?

Other than that, it's time to call CSS and open a support case.

Haven't tried repairing the .net framework yet, tried with a previous installation which made no difference. Having said that though I'll try that again now. 

Currently no AV installed. 

It is running on as a virtual machine on VMware doesn't appear to be any hardware problems with the hosts. 

I thinking that opening a case might be the best path forward. 

Repaired the .net framework and unfortunately this didn't seem to make a difference. 

Hi,

Have you seen this thread.

http://social.technet.microsoft.com/Forums/systemcenter/en-US/2f4a56d8-cf2a-4535-bf68-1c88aa7954ff/smsexecutive-crash-after-sccm-sp2-r2-upgrade?forum=configmgrgeneral

This great blog can help you http://blogs.technet.com/b/configurationmgr/archive/2013/01/29/troubleshooting-configuration-manager-2012-2007-and-sms-2003-unhandled-exceptions.aspx