Skip to content

SCMU does not set ServiceControlQueueAddress when only adding audit instances #4753

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

Open
andreasohlund opened this issue Jan 28, 2025 · 1 comment

Comments

@andreasohlund
Copy link
Member

andreasohlund commented Jan 28, 2025

When adding an additional audit instance using SCMU ServiceControl.Audit/ServiceControlQueueAddress does not get set in the config file. This results in https://docs.particular.net/servicecontrol/troubleshooting#no-destination-specified-for-message

Expected behavior

ServiceControl.Audit/ServiceControlQueueAddress set to the name of the service control error instance

Actual behavior

ServiceControl.Audit/ServiceControlQueueAddress is not set

Versions

Reproduced on 6.1.3 but likely all versions

Likely related to:

Steps to reproduce

  1. Install the latest SCMU
  2. Untick "ServiceControl"
  3. Proceed with installing the audit instance
  4. Note that the mentioned setting is not present in ServiceControl.Audit.exe.config

Checkboxes showing only audit instance is selected

Relevant log output

Additional Information

Workarounds

Install using PowerShell https://docs.particular.net/servicecontrol/audit-instances/deployment/powershell#audit-instance-cmdlets-and-aliases-deploying-an-audit-instance

Possible solutions

Additional information

@mauroservienti mauroservienti changed the title Only installing an audit instance using SCME does not set ServiceControlQueueAddress Only installing an audit instance using SCMU does not set ServiceControlQueueAddress Feb 1, 2025
@andreasohlund andreasohlund changed the title Only installing an audit instance using SCMU does not set ServiceControlQueueAddress SCMU does not set ServiceControlQueueAddress when only adding audit instances Apr 25, 2025
@andreasohlund
Copy link
Member Author

We've reviewed this bug and added it to our backlog. It is not currently prioritized, but it may be fixed along with other future work in the repository. We will update this issue when work begins.

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

No branches or pull requests

1 participant