System. Web. Hosting. hostingenvironmentexception: failed to access IIS metabas

System. Web. Hosting. hostingenvironmentexception: failed to access IIS metabas:
Today is a weekend. I like it very much because it can make me forget many things. Especially for a weekend that has been raining all day, I can forget more, especially the pig head director.

When I get up, the window is raining, and Shanghai is raining every day, but every rain is different. 'The light is clear and clear, and the mountains are blank and the rain is strange. 'This is the rain of Su Shi; 'There are plenty of rain in the Ching Ming Dynasty, and there are endless people on the road. 'This is
Du Mu's rain; 'Night sleep listen to the wind and the rain, the iema glacier dream come to ', This is the rain of land travel; 'mountain river broken wind highlights, the life of the rain and the ping', this is Wen Tianxiang. I have never known what the rain is like, but I know my
Rain is definitely not a good rain season, but it happens in spring, because I was summoned to work overtime today and work overtime on weekends, resentment ......................................

Today's problem is very simple: the new server, XP + vs2005 environment, website deployment is not accessible, internal problems are excluded, only the possibility of external environment changes.

System. Web. Hosting. hostingenvironmentexception: failed to access IIS metabas. This proves that there is a problem in the IIS direction. Ask the server deployment personnel carefully,
I found that the deployment group first installed v2005 in the new XP environment, and then the IIS components installed (shame, I always thought there was no IIS component, XP could not install vs2005, ). Then deploy the website and find the problem.

The preliminary judgment is that ASP. net2.0 is not registered. After carefully reading the KB of MS, I decided to use aspnet_regiis-ga <user_name> to add permissions. The result is invalid.

Then I decided to use aspnet_regiis-I-enable to start registration. Practice has proved that all websites can be accessed normally.

In fact, this is really a small problem caused by a small installation step, but he ruined my perfect weekend. The deployment of Asp.net 2.0 websites is a very simple problem, but it is a problem.
.