Failed to access IIS metabase.

Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

Post here for help with installation of mojoPortal pre-compiled release packages

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.

You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

This thread is closed to new posts. You must sign in to post in the forums.
11/24/2009 11:23:27 AM
Gravatar
Total Posts 18439

Re: Failed to access IIS metabase.

Hi,

Sorry, but I'm not sure I could solve the problem at all much less quickly enough that $25 would be a motivator for me to try it. I've seen cases where things are so messed up it would take re-paving to solve it, not saying this is for sure one of those cases but I have no way of knowing. This is really not a mojoPortal issue at all, its an issue of setting up an XP machine for ASP.NET.

I also would not want to install any software to be able to access your machine. If it was a server on the internet and I could just use the windows remote desktop client I'd be more inclined to take a look and try to help, but trying to fix a developer xp desktop remotely is a different situation.

Best,

Joe

11/24/2009 12:30:28 PM
Gravatar
Total Posts 13

Re: Failed to access IIS metabase.

Joe,

re: I've seen cases where things are so messed up it would take re-paving to solve it

I've installed and run Visual Studio 2003, 2005, and 2008. All worked just fine on my box.

Also, I installed ASP.NET framework 2.0, 3.0, 3.5 and probably most Service Packs and I'm able to create and run web applications just fine.

So I'm not sure what the problem is. Just frustrating when I hear about a good CMS and I want to try it out and I hit a roadblock in step 1 of the process. Even worse, is when I try many of the recommended solutions and none of them work :(.

re: This is really not a mojoPortal issue at all, its an issue of setting up an XP machine for ASP.NET.

I understand. As I said I create and run ASP.NET apps on my box all the time so seems that ASP.NET is setup OK for those situations.

re: I also would not want to install any software to be able to access your machine.

I've used the Crossloop tool a number of times with other consultants, bookkeepers and it seems to work great.

Well, I'll do more research and hopefully I can find a solution. I may try installing it under my web site VPS and see what happens.

Thanks for your help.

Ed

11/24/2009 12:40:49 PM
Gravatar
Total Posts 18439

Re: Failed to access IIS metabase.

So do you have other .NET 3.5 apps working on the box?

Do you see an ASP.NET tab in IIS settings? If so make sure you choose 2.0 (there won't be an option for 3.5 because it's really a superset of 2.0). If not it means something did not go right with aspnet_regiis, make sure you run it from the Framework 2.0 folder nested down under the windows directory, otherwise you may be just reconfiguring 1.1 .NET.

Also make sure you are not using the same application pool for any 1.1 .NET apps, a 2.0 app cannot use the same app pool with 1.1 apps.

You might also try chopping out some of the IIS 7 specific stuff from Web.config though it should be able to ignore it. I would try remove the entire system.webServer section as well as the system.ServiceModel section and possibly also the system.web.extensions section, the system.codedom and runtime sections and see if any of that makes a difference.

Hope it helps,

Joe

You must sign in to post in the forums. This thread is closed to new posts.