Failed To Access IIS Metabase [modified]
-
I'm working on a website on a machine running Vista, and using VS2005. Even though IIS7 is installed, I am NOT running this site under IIS - I am running it from within VS2005. When I run the site, it goes through some code to load a connection string the root web.config file. There is only one web.config file associated with the site, so there's no conflicts with trying to load an overriding file that may/may not exist. When it tries to load the web.config file, I get an exception stating the following:
Failed to access IIS metabase. I have a co-worker that is also running Vista that doesn't have this problem. I have other co-workers that are running XP that do not have this problem. Despite the fact that I'm not running under IIS, I've tried usingaspnet_regiis -i, and even with the-uato unregister asp.net, and then**-i**to re-register asp.net. I'm going to go now and completely uninstall .net 2.0, and then reinstall it, but I'm not optimistic in a positive outcome. If this doesn't work, it's looking like I'll have to do a complete reinstall of this crapware they call Vista/.net, and then all my apps, etc, etc... I'm not a happy camper. If .Net can be knocked over so easily, it still remains categorized as "crap" in my book. Does anyone have any super-secret advice? -- modified at 11:15 Wednesday 24th October, 2007 It seems as if you can't uninstall .net 2.0 from Vista, so that avenue is pointless. The more I use Vista, the more pissed off I get. I've googled this problem to freakin death, and I haven't been able to find ANYTHING that will resolve this problem for me. -- modified at 14:33 Wednesday 24th October, 2007 I just got done completely uninstalling VS2005, and then reinstalling it, and I still get the exception. -- modified at 15:44 Wednesday 24th October, 2007 I'm running VS2005 as administrator."Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
I'm working on a website on a machine running Vista, and using VS2005. Even though IIS7 is installed, I am NOT running this site under IIS - I am running it from within VS2005. When I run the site, it goes through some code to load a connection string the root web.config file. There is only one web.config file associated with the site, so there's no conflicts with trying to load an overriding file that may/may not exist. When it tries to load the web.config file, I get an exception stating the following:
Failed to access IIS metabase. I have a co-worker that is also running Vista that doesn't have this problem. I have other co-workers that are running XP that do not have this problem. Despite the fact that I'm not running under IIS, I've tried usingaspnet_regiis -i, and even with the-uato unregister asp.net, and then**-i**to re-register asp.net. I'm going to go now and completely uninstall .net 2.0, and then reinstall it, but I'm not optimistic in a positive outcome. If this doesn't work, it's looking like I'll have to do a complete reinstall of this crapware they call Vista/.net, and then all my apps, etc, etc... I'm not a happy camper. If .Net can be knocked over so easily, it still remains categorized as "crap" in my book. Does anyone have any super-secret advice? -- modified at 11:15 Wednesday 24th October, 2007 It seems as if you can't uninstall .net 2.0 from Vista, so that avenue is pointless. The more I use Vista, the more pissed off I get. I've googled this problem to freakin death, and I haven't been able to find ANYTHING that will resolve this problem for me. -- modified at 14:33 Wednesday 24th October, 2007 I just got done completely uninstalling VS2005, and then reinstalling it, and I still get the exception. -- modified at 15:44 Wednesday 24th October, 2007 I'm running VS2005 as administrator."Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001If you arent already try running VS as administrator, can be done by right clicking on the link or shortcut and selecting run as administrator. I know this solved most of the problems i had running the 2005 version of VS under Vista. You could always upgrade to 2008 - Even though its only in beta i have found it to be much more reliable than the existing version of VS - and have had no compatibility issues when converting fairly complex solutions over.
-
If you arent already try running VS as administrator, can be done by right clicking on the link or shortcut and selecting run as administrator. I know this solved most of the problems i had running the 2005 version of VS under Vista. You could always upgrade to 2008 - Even though its only in beta i have found it to be much more reliable than the existing version of VS - and have had no compatibility issues when converting fairly complex solutions over.
SHatchard wrote:
f you arent already try running VS as administrator
I'm running as administrator.
SHatchard wrote:
You could always upgrade to 2008
No, I can't. Doing dev work with beta tools is (IMHO) the next best thing to "stupid". Besides, I learned from other people's experiences with installing VS2005 beta that it causes nothing but heartburn later on down the road. Microsoft's release code is dicey enough, and I really don't want to add to the "excitement" by using beta code as well.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
I'm working on a website on a machine running Vista, and using VS2005. Even though IIS7 is installed, I am NOT running this site under IIS - I am running it from within VS2005. When I run the site, it goes through some code to load a connection string the root web.config file. There is only one web.config file associated with the site, so there's no conflicts with trying to load an overriding file that may/may not exist. When it tries to load the web.config file, I get an exception stating the following:
Failed to access IIS metabase. I have a co-worker that is also running Vista that doesn't have this problem. I have other co-workers that are running XP that do not have this problem. Despite the fact that I'm not running under IIS, I've tried usingaspnet_regiis -i, and even with the-uato unregister asp.net, and then**-i**to re-register asp.net. I'm going to go now and completely uninstall .net 2.0, and then reinstall it, but I'm not optimistic in a positive outcome. If this doesn't work, it's looking like I'll have to do a complete reinstall of this crapware they call Vista/.net, and then all my apps, etc, etc... I'm not a happy camper. If .Net can be knocked over so easily, it still remains categorized as "crap" in my book. Does anyone have any super-secret advice? -- modified at 11:15 Wednesday 24th October, 2007 It seems as if you can't uninstall .net 2.0 from Vista, so that avenue is pointless. The more I use Vista, the more pissed off I get. I've googled this problem to freakin death, and I haven't been able to find ANYTHING that will resolve this problem for me. -- modified at 14:33 Wednesday 24th October, 2007 I just got done completely uninstalling VS2005, and then reinstalling it, and I still get the exception. -- modified at 15:44 Wednesday 24th October, 2007 I'm running VS2005 as administrator."Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001I know this may sound dumb, but have you tried creating a virtual directory and running the solution from IIS? I'll second your opinion that Vista is still in a crappy state and that's why it might just be some bug with the local VS web server.
Cheers, Mircea "Pay people peanuts and you get monkeys" - David Ogilvy
-
I'm working on a website on a machine running Vista, and using VS2005. Even though IIS7 is installed, I am NOT running this site under IIS - I am running it from within VS2005. When I run the site, it goes through some code to load a connection string the root web.config file. There is only one web.config file associated with the site, so there's no conflicts with trying to load an overriding file that may/may not exist. When it tries to load the web.config file, I get an exception stating the following:
Failed to access IIS metabase. I have a co-worker that is also running Vista that doesn't have this problem. I have other co-workers that are running XP that do not have this problem. Despite the fact that I'm not running under IIS, I've tried usingaspnet_regiis -i, and even with the-uato unregister asp.net, and then**-i**to re-register asp.net. I'm going to go now and completely uninstall .net 2.0, and then reinstall it, but I'm not optimistic in a positive outcome. If this doesn't work, it's looking like I'll have to do a complete reinstall of this crapware they call Vista/.net, and then all my apps, etc, etc... I'm not a happy camper. If .Net can be knocked over so easily, it still remains categorized as "crap" in my book. Does anyone have any super-secret advice? -- modified at 11:15 Wednesday 24th October, 2007 It seems as if you can't uninstall .net 2.0 from Vista, so that avenue is pointless. The more I use Vista, the more pissed off I get. I've googled this problem to freakin death, and I haven't been able to find ANYTHING that will resolve this problem for me. -- modified at 14:33 Wednesday 24th October, 2007 I just got done completely uninstalling VS2005, and then reinstalling it, and I still get the exception. -- modified at 15:44 Wednesday 24th October, 2007 I'm running VS2005 as administrator."Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001I never run anything from the built in web server ( is it called Cassini ? ), because I've found it's really only good for the most basic of sites. I set up IIS, browse to my site, and attach the debugger if I want to set breakpoints. And yes, I also hate vista. My latest peeve is that the file browse dialog has a drop arrow next to the file path, if I push it, it shows me a bunch of URLs. How retarded is that ?
Christian Graus - Microsoft MVP - C++ "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
-
I'm working on a website on a machine running Vista, and using VS2005. Even though IIS7 is installed, I am NOT running this site under IIS - I am running it from within VS2005. When I run the site, it goes through some code to load a connection string the root web.config file. There is only one web.config file associated with the site, so there's no conflicts with trying to load an overriding file that may/may not exist. When it tries to load the web.config file, I get an exception stating the following:
Failed to access IIS metabase. I have a co-worker that is also running Vista that doesn't have this problem. I have other co-workers that are running XP that do not have this problem. Despite the fact that I'm not running under IIS, I've tried usingaspnet_regiis -i, and even with the-uato unregister asp.net, and then**-i**to re-register asp.net. I'm going to go now and completely uninstall .net 2.0, and then reinstall it, but I'm not optimistic in a positive outcome. If this doesn't work, it's looking like I'll have to do a complete reinstall of this crapware they call Vista/.net, and then all my apps, etc, etc... I'm not a happy camper. If .Net can be knocked over so easily, it still remains categorized as "crap" in my book. Does anyone have any super-secret advice? -- modified at 11:15 Wednesday 24th October, 2007 It seems as if you can't uninstall .net 2.0 from Vista, so that avenue is pointless. The more I use Vista, the more pissed off I get. I've googled this problem to freakin death, and I haven't been able to find ANYTHING that will resolve this problem for me. -- modified at 14:33 Wednesday 24th October, 2007 I just got done completely uninstalling VS2005, and then reinstalling it, and I still get the exception. -- modified at 15:44 Wednesday 24th October, 2007 I'm running VS2005 as administrator."Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001John - are you running this as an administrator, or have you run Visual Studio as the Administrator? They are two slightly different things. This failure is normally associated with VS DEV running in normal mode even though you are running as an administrator. To fix this, right click on Visual Studio and select Run as administrator from the context menu.
Deja View - the feeling that you've seen this post before.
-
I'm working on a website on a machine running Vista, and using VS2005. Even though IIS7 is installed, I am NOT running this site under IIS - I am running it from within VS2005. When I run the site, it goes through some code to load a connection string the root web.config file. There is only one web.config file associated with the site, so there's no conflicts with trying to load an overriding file that may/may not exist. When it tries to load the web.config file, I get an exception stating the following:
Failed to access IIS metabase. I have a co-worker that is also running Vista that doesn't have this problem. I have other co-workers that are running XP that do not have this problem. Despite the fact that I'm not running under IIS, I've tried usingaspnet_regiis -i, and even with the-uato unregister asp.net, and then**-i**to re-register asp.net. I'm going to go now and completely uninstall .net 2.0, and then reinstall it, but I'm not optimistic in a positive outcome. If this doesn't work, it's looking like I'll have to do a complete reinstall of this crapware they call Vista/.net, and then all my apps, etc, etc... I'm not a happy camper. If .Net can be knocked over so easily, it still remains categorized as "crap" in my book. Does anyone have any super-secret advice? -- modified at 11:15 Wednesday 24th October, 2007 It seems as if you can't uninstall .net 2.0 from Vista, so that avenue is pointless. The more I use Vista, the more pissed off I get. I've googled this problem to freakin death, and I haven't been able to find ANYTHING that will resolve this problem for me. -- modified at 14:33 Wednesday 24th October, 2007 I just got done completely uninstalling VS2005, and then reinstalling it, and I still get the exception. -- modified at 15:44 Wednesday 24th October, 2007 I'm running VS2005 as administrator."Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
