Internal Server Error with Site Manager
Evert
After solving my last problem (Thanks to Stefan for helping me out!) I
bumped into another one. When I try to connect to the server with the site
manager the error "Could not connect to the Microsoft Content Management
Server <servername>. Either the web services is not running, or there are
network problems that are keeping you from connecting to the server, or the
server is not accessible through MCMS Site Manager"
When I try to connect to the site which the Site Manager is connecting to I
get an Internal Server Error. Unfortunatly no messages turn up in the Event
Viewer so I can't determine what the problem is.
Could anyone give me some hints or has even solved a similar error?
Thanks in advance,
Evert
Stefan [MSFT]
check out the following article:
--------------
Question: "Could not connect to the Microsoft Content Management Server
localhost:80"
I get the following error message when I try to connect to my Microsoft®
Content Management Server (MCMS) webserver using Site Manager:
Could not connect to the Microsoft Content Management Server localhost:80.
Either the web service is not running, or there are network problems that
are keeping you from connecting to the server, or the server is not
accessible through MCMS Site Manager.
Answer
1.. Check if your MCMS entry is really configured to port 80. If not you
need to adjust the port number in the parameter string of your SiteManager
Shortcut.
2.. Check if there is a global.asa in the root of your Web site. This
global.asa contain errors or settings which interact with MCMS as MCMS does
not ship with it's own global.asa.
3.. Try to access http://localhost:80/NR/System/ClientUI/login.asp from
Microsoft Internet Explorer and see if you get an error from Microsoft
Internet Information Server (IIS). If so, put a testing (very simple one;
e.g. just say "hello world") regular ASP page in
\Server\IIS_NR\System\ClientUI\ and try to access it from Microsoft Internet
Explorer. If that testing ASP page gives the same error, work on the issue
as a regular IIS access problem until you get the testing ASP page works.
Then try to open Site Manager again.
--------------
Cheers,
Stefan.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Evert" <eve...@nospam.etx.nl> wrote in message
news:uyYbNjB...@TK2MSFTNGP11.phx.gbl...
Stefan [MSFT]
Question: How to troubleshoot 500 server error
I receive 500 server errors. What's wrong?
Answer
500 server errors are internal processing error. There are many reasons for
this.
1.. As a quick check: ensure that there is no web.config or global.asax
file in the root of your website as this can cause such troubles.
Which .NET framework version do you use? If it is 1.1 ensure that
<pages smartNavigation="false" validateRequest="false" />is included in
your web.config. If you receive the error using one of your template check
the web.config in your template project. If you receive the error using
SiteManager or Authoring Connector check the web.config in the /MCMS
directory.
If it is .NET framework 1.0 ensure that the above entry is NOT in the
web.config!
2.. check if there is a global.asax or a web.config in the root of your
website. If one of these files exist, remove or rename them and test if the
problem is gone. An error in one of these files can cause these kind of
problems.
3.. If this does not help, do the request from a machine which is not the
CMS server machine and ensure that
<customErrors mode="Off" />is set in your web.config. See above about
how to determine which web.config to use. Then take a Network Monitor trace
to to see the complete error response sent by MCMS.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Evert" <eve...@nospam.etx.nl> wrote in message
news:uyYbNjB...@TK2MSFTNGP11.phx.gbl...
Evert
Thank you for replying so quickly.
Problem is solved. We have our website in a virtual directory and the MCMS
dirs reside in this directory.
Site manager cannot handle that (?). I 've made a new virtual directory
entry of the 'NR' folder in the root of the website which solves the
problem.
Thanks again for your input!
Cheers,
Evert
"Stefan [MSFT]" <ste...@online.microsoft.com> wrote in message
news:uceDd1Bi...@TK2MSFTNGP12.phx.gbl...