Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Seq Windows service does not always start automatically upon reboot (Windows Server 2016) #901

Closed
nblumhardt opened this issue Nov 4, 2019 · 0 comments

Comments

@nblumhardt
Copy link
Member

@nblumhardt nblumhardt commented Nov 4, 2019

I've noticed that recently, the Seq service on one of our Windows Server 2016 Datacenter test machines does not reliably start upon reboot. I suspect it is another dependency issue, exhibiting very similar behavior to the previous issue in #606.

Going to try a few new dependencies, e.g. Tcpip and CryptSvc, which seem like obvious candidates given our use of TCPIP, SSL, and (perhaps) DPAPI early in start-up. If those fail I'll dig deeper - would be great to have any corroborating reports if others are hitting this.

@nblumhardt nblumhardt added this to the 6.0-pre milestone Nov 5, 2019
@nblumhardt nblumhardt closed this Nov 5, 2019
@nblumhardt nblumhardt modified the milestones: 6.0-pre, 5.1-patch6 Jan 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.