CODEWITHSUNDEEP
c#angularazureazure-devopspublish
Andre
Andre

Reputation: 11

AzureDevops - ##[error]Process 'appcmd.exe' exited with code '-2146893802'

When I release a pipeline, this error appears:

ERROR ( hresult:80090016, message:Failed to commit configuration changes.
Keyset does not exist ) ##[error]Process 'appcmd.exe' exited with code '-2146893802'.

Screenshot: screenshot of error message

I do not know what else to do. I've followed some tutorials, but still nothing.

The idea is to publish the system in the approval and production environments. I use VPN to access the folder environment.
The worst thing is that I did several tests and it was working normally, but after 1 month it started giving this error and I haven't been able to solve it yet.

I tried to include LocalService in the permissions, as per the tutorial:
https://learn.microsoft.com/en-US/troubleshoot/developer/webapps/iis/www-authentication-authorization/0x80090016-change-application-pool-identity

but still nothing.

Upvotes: 0

Views: 1733

Answers (2)

user29690995
user29690995

Reputation: 1

  1. Open C:\ProgramData\Microsoft\Crypto\RSA
  2. Right click on MachineKeys, open properties and select Security
  3. In Security Add & give all the rights to everyone, IIS_IURS, Administrators it is worked in my case

Upvotes: 0

SiddheshDesai
SiddheshDesai

Reputation: 8195

I agree with @Ziyang Liu-MSFT. This issue might occur due to the corrupted machine key.

One way to resolve this issue is to regenerate new Machine key and add it in your Web.config by referring this blog

Or to generate the machine key use the command below in your local Web app hosted in IIS:-

aspnet_regiis.exe -pef "system.web/machineKey" C:\path\path\WebApplication16

Output:-

enter image description here

Now, Update your web app > web.config with the generated keys above:-

<system.web>
  <machineKey validationKey="ValidationKey" decryptionKey="DecryptionKey" validation="SHA1" />
</system.web>

Make sure Application Pool Identity has necessary permissions on the machine key and web app configurations.

enter image description here

After you update your machine key and configuration, Restart your IIS Web server and then run the Release pipeline again:-

iisreset
iisreset /restart

If none of the above steps resolves the issue, Raise an Azure support request or a query in this Forum.

Upvotes: 0

Related Questions