Azure Service Fabric
An Azure service that is used to develop microservices and orchestrate containers on Windows and Linux.
252 questions
Getting error while deploying Rest Web Api in Service Fabric on local VDI machine
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(307.2, 81%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKS%3C/text%3E%3C/svg%3E)
KUMAR Sushil
0
Reputation points
'System.RA' reported Warning for property 'ReplicaOpenStatus'.
Replica had multiple failures during open on _Node_0. API call: IStatelessServiceInstance.Open(); Error = Microsoft.Azure.KeyVault.Models.KeyVaultErrorException (-2146233088)
Operation returned an invalid status code 'NotFound'
at Microsoft.Azure.KeyVault.KeyVaultClient.GetSecretWithHttpMessagesAsync(String vaultBaseUrl, String secretName, String secretVersion, Dictionary2 customHeaders, CancellationToken cancellationToken) at Microsoft.Azure.KeyVault.KeyVaultClientExtensions.GetSecretAsync(IKeyVaultClient operations, String vaultBaseUrl, String secretName, CancellationToken cancellationToken) at Axa.Insurance.Configuration.Development.CredentialConfigurationExtensions.GetCurrentSecret(KeyVaultClient keyVaultClient, String certificateKeyName) at Axa.Insurance.Configuration.Development.CredentialConfigurationExtensions.<>c__DisplayClass3_0.<<AddDevelopmentCredentials>b__0>d.MoveNext() --- End of stack trace from previous location --- at Axa.Insurance.Configuration.Development.CredentialConfigurationExtensions.AddDevelopmentCredentials(IConfigurationBuilder config, ConfigurationSection applicationConfig) at Axa.Insurance.ServiceFabric.Hosting.WebHost.ServiceContextWebHostBuilderFactory.<>c__DisplayClass0_01.<CreateWebHost>b__3(WebHostBuilderContext context, IConfigurationBuilder cfg)
at Microsoft.AspNetCore.Hosting.WebHostBuilder.BuildCommonServices(AggregateException& hostingStartupErrors)
at Microsoft.AspNetCore.Hosting.WebHostBuilder.Build()
at Axa.Insurance.ServiceFabric.Hosting.WebHost.WebHostStatelessService`1.<>c__DisplayClass6_0.<CreateServiceInstanceListeners>b__1(String url, AspNetCoreCommunicationListener listener)
at Microsoft.ServiceFabric.Services.Communication.AspNetCore.AspNetCoreCommunicationListener.OpenAsync(CancellationToken cancellationToken)
at Microsoft.ServiceFabric.Services.Runtime.StatelessServiceInstanceAdapter.OpenCommunicationListenersAsync(CancellationToken cancellationToken)
at Microsoft.ServiceFabric.Services.Runtime.StatelessServiceInstanceAdapter.System.Fabric.IStatelessServiceInstance.OpenAsync(IStatelessServicePartition partition, CancellationToken cancellationToken)
For more information see: <a href='https://aka.ms/sfhealth' target='_blank'>https://aka.ms/sfhealth</a>
Azure Service Fabric
.NET
.NET
Microsoft Technologies based on the .NET software framework.
3,391 questions
{count} votes
-
deherman-MSFT 33,471 Reputation points Microsoft Employee2024-01-23T19:25:34.9733333+00:00 @KUMAR Sushil
The KeyVaultErrorException with a status code of NotFound indicates that the web server is trying to access a secret from Azure Key Vault, but the secret is either missing or inaccessible. Here are some possible causes and solutions for this error:Incorrect or outdated secret name: The web server may be using a wrong or outdated secret name to access the Key Vault. Check the configuration file or the code that specifies the secret name and make sure it matches the actual secret name in the Key Vault. Verify that the secret has not been deleted or expired.
Insufficient permissions or authentication: The web server may not have the proper permissions or authentication to access the Key Vault or the secret. Check the access policies and the identity of the web server and make sure they have the required permissions to read the secret. Also ensure that the web server has a valid token or certificate to authenticate with the Key Vault.
Network or service issues: The web server may not be able to reach the Key Vault due to network or service issues. Check the network connectivity and the availability of the Key Vault service and make sure there are no interruptions or outages. Check the firewall and proxy settings and make sure they are not blocking the communication between the web server and the Key Vault.
Sign in to comment