Microsoft Content Management Server - Can't browse site after install SharePoint Services 2.0

Author

Can't browse site after install SharePoint Services 2.0

djoledjole

2005-05-26, 5:55 pm

On my MCMS server(Win2003) after I install Microsoft Windows SharePoint
Services 2.0 I can't browse my previously created site.
I wonder why?

Stefan [MSFT]

2005-05-26, 5:55 pm

Hi,

SharePoint is an ugly system.
It takes over a website completly denying access to anything not SharePoint
related.
You need to add an exclude rule in sharepoint for all MCMS URLs.

Cheers,
Stefan

--
This posting is provided "AS IS" with no warranties, and confers no rights

New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------

"djoledjole" <djdjokic@protected> wrote in message
news:e6dd21edd632cd73687bf02717d428a4@lo
calhost.talkaboutsoftware.com...
> On my MCMS server(Win2003) after I install Microsoft Windows SharePoint
> Services 2.0 I can't browse my previously created site.
> I wonder why?
>

Djole

2005-05-26, 5:55 pm

Yes I just figured that out,butt I done that and now I receive error

Server Error in '/SitoSajt' Application.
--------------------------------------------------------------------------------

Debugging is not supported under current trust level settings.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.

Exception Details: System.Web.HttpException: Debugging is not supported
under current trust level settings.

Source Error:

An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.

Stack Trace:

[HttpException (0x80004005): Debugging is not supported under current trust
level settings.]
System.Web.UI.TemplateParser.HandlePostParse() +183
System.Web.UI.TemplateParser.Parse() +200
System.Web.UI.TemplateParser.GetParserCacheItemThroughCompilation() +74
System.Web.UI.TemplateParser.GetParserCacheItemInternal(Boolean
fCreateIfNotFound) +219
System.Web.UI.TemplateParser.GetParserCacheItemWithNewConfigPath() +125
System.Web.UI.TemplateParser.GetParserCacheItem() +98
System.Web.UI.ApplicationFileParser.GetCompiledApplicationType(String
inputFile, HttpContext context, ApplicationFileParser& parser) +171
System.Web.HttpApplicationFactory.CompileApplication(HttpContext context)
+43
System.Web.HttpApplicationFactory.Init(HttpContext context) +485
System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext
context) +170
System.Web.HttpRuntime. ProcessRequestInternal(HttpWorkerRequest
wr) +414

"Stefan [MSFT]" wrote:

> Hi,
>
> SharePoint is an ugly system.
> It takes over a website completly denying access to anything not SharePoint
> related.
> You need to add an exclude rule in sharepoint for all MCMS URLs.
>
> Cheers,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
> New to MCMS?
> Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
> ----------------------
>
>
> "djoledjole" <djdjokic@protected> wrote in message
> news:e6dd21edd632cd73687bf02717d428a4@lo
calhost.talkaboutsoftware.com...
>
>
>

Angus Logan [MVP]

2005-05-26, 5:55 pm

Hi,

See http://support.microsoft.com/?id=835248

Regards
--
________________________________________

Angus Logan (MCAD/MCDBA/MCP/MVP for MCMS)
Product Specialist
Microsoft Application Solutions
Data#3 Limited
E angus_logan@data3.com.au
BLOG www.anguslogan.com
________________________________________

"Djole" <Djole@discussions.microsoft.com> wrote in message
news:76559346-C0F7-4F56-87D9-4F6FCDC9DB7D@microsoft.com...[vbcol=seagreen]
> Yes I just figured that out,butt I done that and now I receive error
>
> Server Error in '/SitoSajt' Application.
> --------------------------------------------------------------------------------
>
> Debugging is not supported under current trust level settings.
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about
> the error and where it originated in the code.
>
> Exception Details: System.Web.HttpException: Debugging is not supported
> under current trust level settings.
>
> Source Error:
>
> An unhandled exception was generated during the execution of the current
> web
> request. Information regarding the origin and location of the exception
> can
> be identified using the exception stack trace below.
>
> Stack Trace:
>
>
> [HttpException (0x80004005): Debugging is not supported under current
> trust
> level settings.]
> System.Web.UI.TemplateParser.HandlePostParse() +183
> System.Web.UI.TemplateParser.Parse() +200
> System.Web.UI.TemplateParser.GetParserCacheItemThroughCompilation() +74
> System.Web.UI.TemplateParser.GetParserCacheItemInternal(Boolean
> fCreateIfNotFound) +219
> System.Web.UI.TemplateParser.GetParserCacheItemWithNewConfigPath() +125
> System.Web.UI.TemplateParser.GetParserCacheItem() +98
> System.Web.UI.ApplicationFileParser.GetCompiledApplicationType(String
> inputFile, HttpContext context, ApplicationFileParser& parser) +171
> System.Web.HttpApplicationFactory.CompileApplication(HttpContext
> context)
> +43
> System.Web.HttpApplicationFactory.Init(HttpContext context) +485
> System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext
> context) +170
> System.Web.HttpRuntime. ProcessRequestInternal(HttpWorkerRequest
wr) +414
>
>
>
> "Stefan [MSFT]" wrote:
>

Stefan [MSFT]

2005-05-26, 5:55 pm

Hi Djole,

you need to change your web.config settings to ensure that the MCMS
application is running as full trusted:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#B8567D1A-AE8E-4578-B8C3-B70ACEB8A16A

Cheers,
Stefan

--
This posting is provided "AS IS" with no warranties, and confers no rights

New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------

"Djole" <Djole@discussions.microsoft.com> wrote in message
news:76559346-C0F7-4F56-87D9-4F6FCDC9DB7D@microsoft.com...[vbcol=seagreen]
> Yes I just figured that out,butt I done that and now I receive error
>
> Server Error in '/SitoSajt' Application.
> --------------------------------------------------------------------------------
>
> Debugging is not supported under current trust level settings.
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about
> the error and where it originated in the code.
>
> Exception Details: System.Web.HttpException: Debugging is not supported
> under current trust level settings.
>
> Source Error:
>
> An unhandled exception was generated during the execution of the current
> web
> request. Information regarding the origin and location of the exception
> can
> be identified using the exception stack trace below.
>
> Stack Trace:
>
>
> [HttpException (0x80004005): Debugging is not supported under current
> trust
> level settings.]
> System.Web.UI.TemplateParser.HandlePostParse() +183
> System.Web.UI.TemplateParser.Parse() +200
> System.Web.UI.TemplateParser.GetParserCacheItemThroughCompilation() +74
> System.Web.UI.TemplateParser.GetParserCacheItemInternal(Boolean
> fCreateIfNotFound) +219
> System.Web.UI.TemplateParser.GetParserCacheItemWithNewConfigPath() +125
> System.Web.UI.TemplateParser.GetParserCacheItem() +98
> System.Web.UI.ApplicationFileParser.GetCompiledApplicationType(String
> inputFile, HttpContext context, ApplicationFileParser& parser) +171
> System.Web.HttpApplicationFactory.CompileApplication(HttpContext
> context)
> +43
> System.Web.HttpApplicationFactory.Init(HttpContext context) +485
> System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext
> context) +170
> System.Web.HttpRuntime. ProcessRequestInternal(HttpWorkerRequest
wr) +414
>
>
>
> "Stefan [MSFT]" wrote:
>

djoledjole

2005-05-27, 7:56 am

Thanks for link, a did all that was suggested and now site is working
except that now when I click on Switch to edit site I receive
"HTTP Error 403 - Forbidden: Access is denied"
and of course I can't edit site content

Stefan [MSFT]

2005-05-27, 7:56 am

Hi,

check this article:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#7FBEEB3B-1EE9-4445-8811-840B1BBA315F

Cheers,
Stefan

--
This posting is provided "AS IS" with no warranties, and confers no rights

New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------

"djoledjole" <djdjokic@protected> wrote in message
news:9b50694d217d3c8099693b5be3eb3a75@lo
calhost.talkaboutsoftware.com...
> Thanks for link, a did all that was suggested and now site is working
> except that now when I click on Switch to edit site I receive
> "HTTP Error 403 - Forbidden: Access is denied"
> and of course I can't edit site content
>
>

djoledjole

2005-05-27, 7:56 am

Ok I solve the problem using Angus post, the key thing that I skip to do is
to set application poll to StsAppPoll1 and after that everything is going
OK with WebAuthor console. Regarding the Stefan's post I was unable to
find <drive>:\Program Files\Microsoft Content Management
Server\Server\MCMS\McmsHomeport directory so I can't set web.config as
mentioned also I didn't remove channel rendering script butt as I said
everything is working OK.I will post this message just to help anybody
with this problem and to show how I (or better Angus) just solved this .

Stefan [MSFT]

2005-05-27, 7:56 am

Hi,

seems you looked up the wrong article.
The articles I sent you is the following:

---

Topic: 0x80041206 Error indexing your MCMS site

When performing an index on your non-portal content with
http://localhost/channels. The index does not work, and the following is
logged in your gatherer log:

"The address could not be found, (0x80041206 - A server error occurred.
Check that the server is available.)"

If you browse to http://localhost/channels you see the following error:

"Debugging is not supported under current trust level settings."

Answer

Remove the channel rendering script on /Channels or modify the web.config
file located in <drive>:\Program Files\Microsoft Content Management
Server\Server\MCMS\McmsHomeport and ensure that you have set <trust
level="Full" originUrl="" />

For details on "trust level" see the following article:
http://msdn.microsoft.com/library/d...rustsection.asp

----

Topic: 403 Error when loading MCMS Site

After installing the MCMS Connector for SharePoint Technologies and
SharePoint Portal Server 2003, I now get a 403 when I load an MCMS site.

Answer

Look in the Internet Information Server (IIS) log. You will see a 403.18
which means "Cannot execute requested URL in the current application pool."
Ensure that MCMS and Sharepoint Portal Server are configured to use the same
application pool.

This is also explained in the following KB article: 835248

Cheers,
Stefan

--
This posting is provided "AS IS" with no warranties, and confers no rights

New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------

"djoledjole" <djdjokic@protected> wrote in message
news:c39dc98e50f461c96bc8e8997454d7f3@lo
calhost.talkaboutsoftware.com...
> Ok I solve the problem using Angus post, the key thing that I skip to do
> is
> to set application poll to StsAppPoll1 and after that everything is going
> OK with WebAuthor console. Regarding the Stefan's post I was unable to
> find <drive>:\Program Files\Microsoft Content Management
> Server\Server\MCMS\McmsHomeport directory so I can't set web.config as
> mentioned also I didn't remove channel rendering script butt as I said
> everything is working OK.I will post this message just to help anybody
> with this problem and to show how I (or better Angus) just solved this .
>