Skip to content
This repository has been archived by the owner on Jan 17, 2024. It is now read-only.

Falcon Orchestrator Client Service - Dying after startup #34

Closed
cloudjumper2000 opened this issue Jun 2, 2017 · 7 comments
Closed

Falcon Orchestrator Client Service - Dying after startup #34

cloudjumper2000 opened this issue Jun 2, 2017 · 7 comments
Assignees

Comments

@cloudjumper2000
Copy link

cloudjumper2000 commented Jun 2, 2017

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:

2017-06-02 10:51:22,331 FATAL FalconOrchestrator.Client.EventModel - [21145] Error occured while trying to save authentication activity audit event to database
System.ArgumentOutOfRangeException: Value to add was out of range.
Parameter name: value
   at System.DateTime.Add(Double value, Int32 scale)
   at FalconOrchestrator.Client.AuditEvent.get_FormattedTimestamp()
   at FalconOrchestrator.Client.AuthActivityAuditModel.Save()

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/

@mr-burnse
Copy link
Contributor

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.

@mr-burnse mr-burnse self-assigned this Jun 2, 2017
@cloudjumper2000
Copy link
Author

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.

@mr-burnse
Copy link
Contributor

Fix has been published here. Please follow implementation steps to apply it.

@cloudjumper2000
Copy link
Author

So we have replaced the EXE but receive this error when trying to start the service:

Service cannot be started. System.InvalidOperationException: No connection string named '**FalconOrchestratorDB**' could be found in the application config file.
   at System.Data.Entity.Internal.LazyInternalConnection.Initialize()
   at System.Data.Entity.Internal.LazyInternalConnection.get_Connection()
   at System.Data.Entity.Internal.LazyInternalContext.get_Connection()
   at FalconOrchestrator.DAL.DatabaseHelpers.TestConnection()
   at FalconOrchestrator.Client.FalconOrchestratorService.OnStart(String[] args)
   at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

I do see this line in the web.config:

<connectionStrings>
    <add name="**FalconOrchestratorDB**" connectionString="metadata=res://*/FalconOrchestratorDB.csdl|res://*/FalconOrchestratorDB.ssdl|res://*/FalconOrchestratorDB.msl;provider=System.Data.SqlClient;provider connection string=&quot;data source=*********;initial catalog=FalconOrchestrator;user id=********;password=********;MultipleActiveResultSets=True;App=EntityFramework&quot;" providerName="System.Data.EntityClient"/>
  </connectionStrings>

Any ideas?

@mr-burnse
Copy link
Contributor

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 C:\Program Files (x86)\Falcon Orchestrator\FalconOrchestrator.Client.exe.config.

@mr-burnse mr-burnse reopened this Jun 12, 2017
@cloudjumper2000
Copy link
Author

The connection string is there in the above location as well. Any other ideas?

@mr-burnse
Copy link
Contributor

Resolved as per discussion on Slack.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants