Service Control Exception : An item with the same key has already been added

, ,
1

Hi All,

i am running into the following issue, while configuring service control,

  • we use custom naming,
  • using managed identity and the identity has a “owner” permission
  • service control is configured properly
  • only the Audit is throwing this error
  • i only see the service control windows service i dont see the audit windows instance

Question

  • what am i doing wrong here ?
  • Can i disable queue creation if i am configuring service control via the ServiceControl Monitoring instances using SCMU ?

ISSUES ADDING INSTANCE:
Could not add new instance because of the following errors:
ServiceControl.Audit.exe returned a non-zero exit code: -532462766. This typically indicates a configuration error. The error output was:
Unhandled exception. System.ArgumentException: An item with the same key has already been added. Key: queue-d-domain-servicecontrol.Audit
at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
at NServiceBus.AzureServiceBusTransport.DetermineQueuesToCreate(ReceiveSettings[] receivers, String[] sendingAddresses) in /_/src/Transport/AzureServiceBusTransport.cs:line 208
at NServiceBus.AzureServiceBusTransport.Initialize(HostSettings hostSettings, ReceiveSettings[] receivers, String[] sendingAddresses, CancellationToken cancellat…
Please verify the details or contact support.

image
image822×367 12 KB

image
image782×192 4.63 KB

image
image812×216 5.51 KB

2

Hi @Nen_Zax,

Can you please let us know what version of SCMU you are using? It doesn’t appear that you’re using the latest version (6.19.3), can you please try again with the latest?
There are other queue name settings in SCMU, e.g. “Error Queue Name” and “Audit Queue Name”. What are you setting these fields to?

  • Can i disable queue creation if i am configuring service control via the ServiceControl Monitoring instances using SCMU ?

Monitoring instance is separate from error instance and audit instance. The queue names need to be unique for each instance. The error you’re seeing isn’t affected by existing queues, it’s happening when the transport is attempting to determine which queues it requires, before checking if those queues exist.