localhost 404, default website points to the mojoportal subdirectory i.e. "c:\websites\mojopotal" directly and not to c;|intepub\wwwroot

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.
3/19/2012 2:45:17 PM
Gravatar
Total Posts 27

localhost 404, default website points to the mojoportal subdirectory i.e. "c:\websites\mojopotal" directly and not to c;|intepub\wwwroot

  • operating System 2008R2
  • IIS 7.0
  • mojoPortal 2.3.8.1 for .NET 4.0 MS SQL

I have installed MojoPotal successfully 10+ times using WEb Platform Installer 3.0. I reqally like MojoPortal and a grateful for all the wok done on it. However, this past Friday, 3/16/2012 - experienced my first failure while following the same procedures.  Unfortunately, the failed installation has left our IIS "default web site" on our productions in a malfunctioning state:

  • "http://www.serverDNS.com" points to the mojoportal subdirectory i.e. "c:\websites\mojopotal" directly and not to c;|intepub\wwwroot.
  • there is no virtual directory "mojoportal" under the Default Website" under IIS
  • the "basic settings" of the "Default Website" shows the physical path to be "C:\inetpub\wwwroot" - yet, the de facto physical path is  "c:\websites\mojopotal"
  • many of our existing virtual directories\applications under Default Website are malfunctioning
  • when running a browser on the affected web server, "localhost" returns a "404"

I assume MojoPortal makes changes in applicationHost.config file.  Is there anyway to "rollback" to before the 3/16 installation?  Or, is there another way (easier) to fix the "default web site" to point to "C:\inetpub\wwwroot"?

3/19/2012 5:10:05 PM
Gravatar
Total Posts 27

Re: localhost 404, default website points to the mojoportal subdirectory i.e. "c:\websites\mojopotal" directly and not to c;|intepub\wwwroot

an addendum --

interestingly -- many (not all) of the virtual/applications under the default website -- will respond to a https  URL and will not via an http prefaced URL. 

3/20/2012 8:32:41 AM
Gravatar
Total Posts 18439

Re: localhost 404, default website points to the mojoportal subdirectory i.e. "c:\websites\mojopotal" directly and not to c;|intepub\wwwroot

I assume MojoPortal makes changes in applicationHost.config file

No, possibly Web Platform Installer does but not mojoPortal. mojoPortal is just a web app that runs in IIS it doesn't control or configure IIS. 

"http://www.serverDNS.com" points to the mojoportal subdirectory

no dns names point to ip addresses not folders so I don't know what you mean by that

the "basic settings" of the "Default Website" shows the physical path to be "C:\inetpub\wwwroot" - yet, the de facto physical path is "c:\websites\mojopotal"

I have no idea what you mean by de-facto, an IIS web site points to whatever folder it says in Basic Settings there is nothing that changes that.

I suspect the actual problem is that you created (via platform installer) another IIS web site that is conflicting with the default web site. So in effect there are 2 default web sites and that causes both of them to break. The second web site needs a host name on its bindings to differentiate it from the default web site. The thing that makes the default web site default is that it has no host names, there can be only one IIS web site for a given ip address that has no host names in the bindings. As soon as a second site is configured that way it breaks one or both sites.

So if a new IIS site was created for mojoPortal by platform installer and it broke the default web site you either need to add a host name to the bindings of the new site or delete it completely to repair the default web site.

Hope that helps,

Joe

3/20/2012 12:18:34 PM
Gravatar
Total Posts 27

Re: localhost 404, default website points to the mojoportal subdirectory i.e. "c:\websites\mojopotal" directly and not to c;|intepub\wwwroot

Joe -- thanks for your kind and informed reply.  Your clarity regarding IIS and default sites is spot on  and instrumental in me solving this issue -- the MojoPortal site I added did share a binding with the default site -- I just didn't catch it.  This must have been due to my error and not Web Platform Installer. My understanding of the IIS default site and bindings has just deepened, thanks to you.

btw: glad to note you recently enjoyed a vacation -- well deserved. 

Peter

 

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