Exception code: 0xc06d007f

I started this post thinking the issue was with CommandManager commands. (SEE “Original Post” below)

Then I thought it might be a licensing issue (SEE “Additional Information 01” below).

Now I believe its a camera driver issue (SEE “Additional Information 02” below)

With that said, what does “Exception code: 0xc06d007f” indicate?

------------------------------

Original Post

Every now and then, I try to run a CommandManager command (such as Lock Door / Unlock Door) and the Smart Client crashes. The below error is found in the Application event viewer.

Like the DemoAccessControlPlugin sample app, I am wrapping the call to our Access Control system in a try catch, catching any error that might occur, logging the error using ACUtil.Log helper method, and then returning a new ACCommandResult(false, ex.Message);

No exception in the MIPS logs shows up even though I’m calling ACUtil.Log … BUT, there is no code outside of the try-catch in the CommandManager.ExecuteCommand method … so, there is no opportunity for an unhandled exception … at least not in that code

The only method i overrode is ExecuteCommand(string operationableInstance, string commandType) … i have not overrode the other three. Might that be the issue?

The last time it occurred, I moved the mouse to wake up the PC in the morning, the Smart Client was already running (our Access Control system is running on the same PC), I clicked on Lock Door and the issue occurred.

Does the exception code (as seen below: 0xc06d007f) help pinpoint the culprit?

----------------------------

Exception:

Faulting application name: Client.exe, version: 20.1.29.1, time stamp: 0x5e5e46ec

Faulting module name: KERNELBASE.dll, version: 10.0.18362.815, time stamp: 0xb89efff3

Exception code: 0xc06d007f

Fault offset: 0x000000000003a799

Faulting process id: 0x41c

Faulting application start time: 0x01d659f85fc03e6b

Faulting application path: [C:\Program](file:C:/Program) Files\Milestone\XProtect Smart Client\Client.exe

Faulting module path: [C:\Windows\System32\KERNELBASE.dll](file:C:/Windows/System32/KERNELBASE.dll)

Report Id: 9881c195-d8bd-4080-8743-ce25aeca3b3e

Faulting package full name:

Faulting package-relative application ID:

​[9:25 AM] BJ Ingle

Fault bucket 1621395220051433076, type 4

Event Name: APPCRASH

Response: Not available

Cab Id: 0

------------------------------

Additional Information 01

The Smart Client also crashed without me executing a CommandManager command at all with the following conditions:

I am using an Extended test license which has Access Control with a 2 doors. But my configuration has retrieved 4 doors from our Access Control system. All 4 doors show up in the Smart Client > Access tab. The last 2 have question marks next to them. When an event is received by the plugin and that event concerns one of the doors I don’t have a license for the client THEN crashes.

I do have the following message in the Milestone Event Manager Logs:

2020-07-15 11:37:34 AM UTC-05:00

Warning AccessControlSystem

Unable to handle EventOccurred event from access control system plugin. Event source not licensed. Access Point: Door 3 (49a215ae-53dd-e768-efef-4ba3d0968f63) on door: Door 3 (e30f1a08-ba83-8941-607f-550e42d22afc)

I can only image that Milestone is simply supposed to ignore the event for a door that is not licensed. Not crash the Client (if in fact that is the culprit causing the crash and not just a coincidence)

------------------------------

Additional Information 02

This must be a camera driver issue. As soon as i removed the associated camera from the doors, Smart Client stopped crashing

What version is the Smart Client? What product and version is the XProtect VMS?

Can you please enable logging and reproduce the crash and then make the logs available for us?

https://developer.milestonesys.com/s/article/Enable-XProtect-Smart-Client-logging-automatically-and-manually

Please describe how the “Lock door” command is executed; is it in the Access workspace in the Smart Client, on a Map in Smart Client, in a fly-out or something different?