search

Particular / ServiceControl

Backend for ServiceInsight and ServicePulse
https://docs.particular.net/servicecontrol/
Other
51 stars 47 forks source link

A instance which is upgraded isn't run via Windows Service Control Manager which does not enforce any windows service dependencies to be started #1162

Open ramonsmits opened 6 years ago

ramonsmits commented 6 years ago

When a SC instance is updated the executable is invoked via the ServiceControl Management Utility (SCMU) process identity, and not via the Windows Service Control Manager.

Dependancies

If the instance windows service was STOPPED, but is dependent to windows services currently stopped then during the upgrade these dependencies will not be started.

Permissions

The SC process is started via the SCMU process. This could be a different user account compared to the configured account for the windows services and can result in a different permission set. This can lead to all kind of permission issues on modified system resources like folders and files but also to resources like transports if they support windows integrated security.

SzymonPobiega commented 6 years ago

I think this is intentional i.e. the account that is configured to run the SC service might not have the permissions to create queues. The SCMU account (admin) has to.

Regarding the dependencies: SC does not have any dependencies by default. Can you give some examples here?

ramonsmits commented 6 years ago

@SzymonPobiega image

I manually defined that dependency to not get any errors during boot.