Config builder fails on production but works on dev

Question

Config builder fails on production but works on dev

James 0

Hello I have an angular site and I am trying to store my connection strings in the azure key vault and retrieve them in my web.config file. With my current set up it works locally. It also works when I deploy to our dev web app. When I deploy to the production web app it does not work and I get a yellow screen with the following output. I think it is an azure issue, but I am unsure how to fix it.

[AmbiguousMatchException: Multiple custom attributes of the same type found.]
   System.Attribute.GetCustomAttribute(Assembly element, Type attributeType, Boolean inherit) +109
   System.Runtime.InteropServices.RuntimeInformation.get_FrameworkDescription() +87
   Azure.Core.TelemetryDetails.GenerateUserAgentString(Assembly clientAssembly, String applicationId) +166
   Azure.Core.TelemetryDetails..ctor(Assembly assembly, String applicationId) +66
   Azure.Core.Pipeline.HttpPipelineBuilder.CreateTelemetryPolicy(ClientOptions options) +56
   Azure.Core.Pipeline.HttpPipelineBuilder.BuildInternal(ClientOptions options, HttpPipelinePolicy[] perCallPolicies, HttpPipelinePolicy[] perRetryPolicies, HttpPipelineTransportOptions defaultTransportOptions, ResponseClassifier responseClassifier) +285
   Azure.Identity.CredentialPipeline..ctor(TokenCredentialOptions options) +125
   Azure.Identity.<>c.<.cctor>b__19_0() +79
   System.Lazy`1.CreateValue() +413
   System.Lazy`1.LazyInitValue() +372
   System.Lazy`1.get_Value() +133
   Azure.Identity.CredentialPipeline.GetInstance(TokenCredentialOptions options) +51
   Azure.Identity.DefaultAzureCredential..ctor(DefaultAzureCredentialOptions options) +37
   Microsoft.Configuration.ConfigurationBuilders.AzureKeyVaultConfigBuilder.LazyInitialize(String name, NameValueCollection config) +523
   Microsoft.Configuration.ConfigurationBuilders.KeyValueConfigBuilder.EnsureInitialized() +92
   Microsoft.Configuration.ConfigurationBuilders.KeyValueConfigBuilder.GetValueInternal(String key) +77

[Exception: Error in Configuration Builder 'AzureKeyVault'::GetValue(aspnet:PortableCompilationOutput)]
   Microsoft.Configuration.ConfigurationBuilders.KeyValueConfigBuilder.GetValueInternal(String key) +429
   Microsoft.Configuration.ConfigurationBuilders.KeyValueConfigBuilder.ProcessConfigurationSection(ConfigurationSection configSection) +207
   System.Configuration.Internal.InternalConfigHost.System.Configuration.Internal.IInternalConfigurationBuilderHost.ProcessConfigurationSection(ConfigurationSection configSection, ConfigurationBuilder builder) +22
   System.Configuration.Internal.DelegatingConfigHost.ProcessConfigurationSection(ConfigurationSection configSection, ConfigurationBuilder builder) +20
   System.Configuration.BaseConfigurationRecord.CallHostProcessConfigurationSection(ConfigurationSection configSection, ConfigurationBuilder configBuilder) +50

Shweta Mathur 15,066 Reputation points Microsoft Employee

2023-05-11T08:07:00.4766667+00:00

Hi @James ,

Thanks for reaching out.

This error requires deep troubleshooting.

Generally, this error comes in the context of custom attributes when there are multiple custom attributes of the same type found, causing ambiguity.

Based on the stackTrace ,it appears that the exception is thrown while trying to retrieve a custom attribute using the System.Attribute.GetCustomAttribute method. This method is called with an Assembly object and a Type representing the attribute type. However, since there are multiple custom attributes of the same type, the method cannot determine which one to return, resulting in the exception.

You can try to resolve this error by ensuring that only one version of the assembly is loaded in the application domain. You can also try to update the assembly to the latest version to see if that resolves the issue.

In case the above does not work for you, please send us an email on azcommunity [at] microsoft [dot] com referencing this issue with a subject line "ATTN:shweta" and we will help you with alternative support options on this.

Thanks,

Shweta

Shweta Mathur 15,066 Reputation points Microsoft Employee

2023-05-11T08:07:00.4766667+00:00

Hi @James ,

Thanks for reaching out.

This error requires deep troubleshooting.

Generally, this error comes in the context of custom attributes when there are multiple custom attributes of the same type found, causing ambiguity.

Based on the stackTrace ,it appears that the exception is thrown while trying to retrieve a custom attribute using the System.Attribute.GetCustomAttribute method. This method is called with an Assembly object and a Type representing the attribute type. However, since there are multiple custom attributes of the same type, the method cannot determine which one to return, resulting in the exception.

You can try to resolve this error by ensuring that only one version of the assembly is loaded in the application domain. You can also try to update the assembly to the latest version to see if that resolves the issue.

In case the above does not work for you, please send us an email on azcommunity [at] microsoft [dot] com referencing this issue with a subject line "ATTN:shweta" and we will help you with alternative support options on this.

Thanks,

Shweta

Config builder fails on production but works on dev

Activity