|
Home > Archive > Microsoft Content Management Server > November 2007 > MCMS Internal Server Error 500
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
MCMS Internal Server Error 500
|
|
|
| Hi,
in our development environment we have MCMS installed and our web
application is located in a virtual directory under default web site
in IIS. Everything works fine.
However, in production, MCMS seems not to be intercepting the requests
since all MCMS pages can not be found when browsing the web site and
when we try to import templates and channels via Site Manager we get
an internal server error 500. We didn't find any clues of what could
cause the error.
In our production environment MCMS has been installed the same way so
it's located under the default web site in IIS. The problem is that we
have our default web site in IIS pointing directly to the root of our
web application instead of being located under a virtual directory in
this environment. According to the company that is hosting the site,
this is the only configuration permitted (we don't know why...). So
instead of having the MCMS virtual directory in the same level of our
web application, it is a virtual directory UNDER the web application.
Could this configuration lead to the error mentioned above? If so, is
there anything we can do to workaround the problem without changing
this configuration of virtual directories and default web site?
Thanks in advance.
| |
| Stefan Goßner [MSFT] 2007-11-30, 1:20 pm |
| Hi Lowko,
please check here for common reasons and troubleshooting steps:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#DD159085-1AFB-4244-AE6D-D0A1C0E9E274
Cheers,
Stefan
"Lowko" <israellow@gmail.com> wrote in message
news:fed28010-f9fd-4e3e-a9e4-b02e1afbe48d@o6g2000hsd.googlegroups.com...
> Hi,
>
> in our development environment we have MCMS installed and our web
> application is located in a virtual directory under default web site
> in IIS. Everything works fine.
>
> However, in production, MCMS seems not to be intercepting the requests
> since all MCMS pages can not be found when browsing the web site and
> when we try to import templates and channels via Site Manager we get
> an internal server error 500. We didn't find any clues of what could
> cause the error.
>
> In our production environment MCMS has been installed the same way so
> it's located under the default web site in IIS. The problem is that we
> have our default web site in IIS pointing directly to the root of our
> web application instead of being located under a virtual directory in
> this environment. According to the company that is hosting the site,
> this is the only configuration permitted (we don't know why...). So
> instead of having the MCMS virtual directory in the same level of our
> web application, it is a virtual directory UNDER the web application.
>
> Could this configuration lead to the error mentioned above? If so, is
> there anything we can do to workaround the problem without changing
> this configuration of virtual directories and default web site?
>
> Thanks in advance.
|
|
|
|
|