12

Module IIS Web Core
Notification Unknown
Handler Not yet determined
Error Code 0x8007000d
Config Error Failed to decrypt attribute 'password'
Config File Unavailable (Config Isolation)

When i run my app im getting this error and i couldn't find any solution please help?

WeyCell
  • 273
  • 1
  • 2
  • 12
  • See this as it resolved my issue http://serverfault.com/questions/230934/iis-7-5-encryption-keys-and-hresult-0x80090005 –  May 22 '15 at 22:42

5 Answers5

13

I resolved the issue. The problem was C:\Windows\System32\inetsrv\config\applicationHost.config file. In the config file, I deleted username and password definitions for applications and it worked well.

spottedmahn
  • 14,823
  • 13
  • 108
  • 178
WeyCell
  • 273
  • 1
  • 2
  • 12
  • 5
    Awesome!!! I had the same problem--looked at the applicationHost.config file (which BTW is located in Windows 2012 at C:\Windows\System32\inetsrv\config) and found which application used a password. I didn't change the config file, but went back into IIS and re-entered the credentials for that app and bingo that updated the config file and it worked. (BTW, this problem causes ALL apps for a server to fail with this error. What is a bit confusing is the error appears to be a application pool failure, but the password is for the application not the pool--triggered when the pool wakes up.) – Jeff Feb 11 '14 at 03:41
  • 2
    Yes had the same issue and had to re-enter the physical path credentials for each web application. In my case it was to do with Keepass encrypting the password but the hash being wrong for the machine as everything had been copied over from another machine – Jaycee Jul 25 '14 at 14:11
6

I had the same issue after clone a Web Server.

Solution:

Source Server:

aspnet_regiis -px "iisConfigurationKey" "C:\temp\iisConfigurationKey.xml" -pri 
aspnet_regiis -px "iisWasKey" "C:\temp\iisWasKey.xml" -pri

Destination Server:

aspnet_regiis -pi "iisConfigurationKey" "C:\temp\iisConfigurationKey.xml" 
aspnet_regiis -pi "iisWasKey" "C:\temp\iisWasKey.xml"

And, at the final, copy applicationhost.config from the source server to destination server.

pableiros
  • 14,932
  • 12
  • 99
  • 105
Alexandre Smialoski
  • 61
  • 1
  • 1
  • 2
    This worked great on my cloned VM. aspnet_regiis had to be called from C:\Windows\Microsoft.NET\Framework\v4.0.30319 on my configuration. applicationhost.config was located in C:\Windows\System32\inetsrv\config – ryatkins Sep 27 '18 at 21:03
  • You sir, are a genius! Note to anyone getting a "rsa key container not found" error, you have to run this as an administrator (in my case this was also due to a cloned Web Server). – Alberto Rechy Apr 23 '19 at 09:01
  • Worked for me too. It didn't seem to at first (maybe I didn't test right), but after a restart of the cloned VM all went well. So, much thanks (and +1). – Fred vdP May 19 '21 at 14:18
2

This is one of those mystery errors. For me, the issue occurred when we cloned a development server. When I went to reconfigure some the sites in IIS on the cloned server, one of the sites threw this error. You need to delete all the sites that shared the same app pool in IIS and recreate them.

PhillyNJ
  • 3,859
  • 4
  • 38
  • 64
1

I fixed this by disabling Anonymous Access in the application, then re-enabling it immediately. No IIS restart necessary.

Rots
  • 5,506
  • 3
  • 43
  • 51
0

I had the same problem and I changed the Physical Path under the website's advanced settings to a dummy path then changed it back, then it started working.

BurnWithLife
  • 364
  • 4
  • 11