Outlook 2013 CRASH AND BURN - with multiple 'failed VL activation attempt's just prior...

Question

Outlook 2013 crashing frequently,  have removed, reinstalled, etc etc - to no avail
Before the "Outlook" crash, the application log always  shows multiple warnings as below:
The rules engine reported a failed VL activation attempt.
Reason:0x8007232B
AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = 771c3afa-50c5-443f-b151-ff2546d863a0
Trigger=TimerEvent
===================
"Off1ce15" - kind of a giveaway that this must be related, no??
This is "Office Home and Business 2013 32-bit" on windows 8.1u1 (32 bit)
Anybody at MS-support even remotely interested in troubleshooting this??

Answer 1

There is a 'volume licence' Outlook2010 installed on this machine, it's been switched back and forth to this a few times, as Outlook 2013 has had numerous issues. The licence key was supplied by our Exchange server provider.
I suspect that Windows simply doesn't clean up after itself! This (recent clean installation) W8.1u1 machine has gone through these versions:
Office365 outlook2013 (trial) - which eventually crashed and burned, so I removed it.
Outlook2013 'volume licence' from my Exchange Server provider - also crashed and burned, so I removed it.
Outlook2010 'volume licence' from my Exchange Server provider.
Office2013 Home and Business ( including Outlook 2013) - but the Outlook2013 crashed and burned, so I removed it, and re-installed the Outlook 2010, which was working fine. Exchange provider has supplied me a volume licence key for Outlook 2010, but
I cannot for the life of me find a place to enter it!!
Have tried clean boot of windows, it doesn't solve the issue of Outlook Crashing. All other Office2013 modules work fine, no problems whatsoever with Excel, Word, PPT, etc.
Outlook safe mode doesn't work, either.. see these log excerpts:
The program OUTLOOK.EXE version 15.0.4615.1000 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
 Process ID: f78
 Start Time: 01cfb37dc73f3a2d
 Termination Time: 55
 Application Path: C:\Program Files\Microsoft Office\Office15\OUTLOOK.EXE
 Report Id: 96150ae0-218a-11e4-afc1-002564df0634
 Faulting package full name: 
 Faulting package-relative application ID: 
Faulting application name: OUTLOOK.EXE, version: 15.0.4615.1000, time stamp: 0x534cda15
Faulting module name: OUTLOOK.EXE, version: 15.0.4615.1000, time stamp: 0x534cda15
Exception code: 0xc0000005
Fault offset: 0x00034171
Faulting process id: 0xed0
Faulting application start time: 0x01cfb5976bc8928a
Faulting application path: C:\Program Files\Microsoft Office\Office15\OUTLOOK.EXE
Faulting module path: C:\Program Files\Microsoft Office\Office15\OUTLOOK.EXE
Report Id: aa3b48e7-218a-11e4-afc1-002564df0634
Faulting package full name: 
Faulting package-relative application ID: 
The description for Event ID 2001 from source Microsoft Office 15 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local
computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: 
Microsoft Outlook
Outlook couldn't start last time. Safe mode could help you troubleshoot the problem, but some features might not be available in this mode.
Do you want to start in safe mode?
The description for Event ID 2000 from source Microsoft Office 15 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local
computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: 
Microsoft Outlook
Outlook failed to launch in safe mode. Do you want to start repair?
... and so on ...
Immediately preceding the crash, there were hourly warnings as follow:
The rules engine reported a failed VL activation attempt.
Reason:0x8007232B
AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = 771c3afa-50c5-443f-b151-ff2546d863a0
Trigger=TimerEvent
coincidence??
Will check out that OffCat tool, thanks!