If the process was to be stopped or crash for some reason the door status will not be updated and events from Brivo will stop being received. This will also generate an email **"Failed to post event data to http://***.***.***.***:43323/orb-briv-proxy/eventscallback/"** to the error email address configured for this connection. ## Event Viewer if this was due to a crash please look in the Windows Event Viewer to events related to the crash. Share these with ORBNET Support for further assistance. `Windows Logs` > `Application` ![[z_img/72e7c2bf0dc3f7857086306d6f68d169_MD5.jpeg|350]] On the right select `Filter Current Log...` For `Event sources` select `ORBNETBriveoEventsProxy` ![[z_img/ebe326696fb7a396a00f8b830369b134_MD5.jpeg|650]] This will show events related to just this service, find `Error` or `Warning` events to find what could be causing an issue with the application. # Services Here is a way to keep the service running: In `Services` find the `ORBNET Brivo Event Proxy service`, go into `Properties` then `Recovery`, set the **First, Second, and Subsequent failures** to "**Restart the Service**". If you end the task in **Task Manager**, the service stops, and after a minute it is restarted. ![[z_img/1687959b87187f54f82435fed31735e2_MD5.jpeg|450]]