-
Notifications
You must be signed in to change notification settings - Fork 54
Falcon Orchestrator Client Service - Dying after startup #34
Comments
Hey FJ - You don't need a CS domain to join slack, just sign up through here https://falcon-orchestrator.herokuapp.com/. As for the issue being reported, please see below: This issue just surfaced this week as the UTCTimestamp field on events of type AuthActivityAuditEvent is being pushed through the API with two types of unix epoch formatted timestamps...one with milliseconds and one without. Orchestrator is expecting a certain format and is crashing because of this. I will look to provide a bug fix for this early next week. |
Thanks for the response and I was able to join slack. Please do let us know when a fix is available for the previously mentioned issue. |
Fix has been published here. Please follow implementation steps to apply it. |
So we have replaced the EXE but receive this error when trying to start the service:
I do see this line in the web.config:
Any ideas? |
Web.config is only used by the web application. Can you check the connection string is there in the client service configuration file? This is located at |
The connection string is there in the above location as well. Any other ideas? |
Resolved as per discussion on Slack. |
My team noticed we were not receiving alerts via email. Found out the Falcon Orchestrator Client service terminated unexpectedly. Event ID: 7031
Looking in:
C:\Program Files (x86)\Falcon Orchestrator\RunLog.txt
We see several of these errors:
Could you provide assistance with how to resolve this or what we can check next to provide more info?
Thanks! FJ
PS: Is slack not an option for support? Seems I need a crowdstrike email to create an account for https://falcon-orchestrator.slack.com/
The text was updated successfully, but these errors were encountered: