Line 1: <%@ Application Codebehind="Global.asax.cs" Inherits="Woodgrove.Global" %>
Answer
This error commonly occurs when the project has been altered and needs to be rebuilt in Microsoft® Visual Studio® .NET. Typically, a codebehind page has been altered.
[Back to Top]
Topic: PlaceholderToBind Not Found
Error message:
Server Error in '/Woodgrove' Application.
[HtmlPlaceholderControl "PlaceholderHtmlControl1"] The PlaceholderToBind "HomeMainContent1" was not found.
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.
Answer
This happens when the placeholder object in the ASPX file is bound to a non-existent placeholder in the database. Placeholders associated with a template are stored in the template gallery item (TGI). You can view the collection of placeholders using the Microsoft® Visual Studio® .NET template property window.
[Back to Top]
Topic: Template debugging in Microsoft Visual Studio .NET
I tried to debug one of my templates but it does not work. How can I enable this?
Answer
The easiest way to achieve this is to use one of these methods:
Use the 'Debugging Start Page'
- In the web.config change debug to True.
- In IIS turn on ASP client and server side debugging for ASP (Home Directory -> Configuration)
- Create an HTML file in your project that has a link to a page using the CMS template that you want to step through (see example below)
- Set the HTML as the start page for the project (right-click the file in VS) - check each project
- Set the project properties to turn on ASP.Net debugging
- Set the web application project (not the webcontrollibrary - if you have one) as the startup project
- Start debugging and click the link to the page using the template that you want to debug
- Symbols can be added in the solution properties under 'Common Properties' -> 'Debug Symbol Files'
Example start page:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" >
<HTML>
<HEAD>
<META NAME="GENERATOR" Content="Microsoft Visual Studio 7.0">
<TITLE>Debugging Start Page for Woodgrove</TITLE>
</HEAD>
<BODY>
<a href="http://localhost/WoodgroveNet/About+Woodgrove/Press+Releases/August+30,+2001.htm">
Navigate to CMS and debug.</a>
</BODY>
</HTML>
Attach directly to the process:
- Open the project in Visual Studio .NET
- Set your breakpoints
- Click "Debug" - "Processes"
- Select the "aspnet_wp.exe" (IIS5) or "w3wp.exe" (IIS 6) process in the list (if it does not show up, select the "show processes in all sessions" button)
- Click "Attach..."
- Ensure that "Common Language Runtime" is selected
- Click "OK" and "Close"
- Open a new Internet Explorer instance and browse to your page. Visual Studio .NET will take control when the breakpoint is hit and let you debug your application.
[Back to Top]
Topic: Troubleshooting 500 server error
I receive 500 server errors. What could be wrong?
Answer
500 server errors are internal processing errors. Try the following troubleshooting suggestions:
- Ensure that there is no web.config or global.asax file in the root of your Web site as this can cause such issues.
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 templates check the web.config in your template project. If you receive the error using Site Manager or Authoring Connector, check the web.config in the /MCMS directory.
If it is .NET framework 1.0 ensure that the 'validateRequest' entry is NOT in the web.config.
-
Check whether there is a global.asax or a web.config in the root of your Web site. If one of these files exists, remove or rename it and test to see if the problem is gone. An error in one of these files can cause these kind of problems.
-
Check the event log for errors. Often an event log entry is written when a 500 error is reported
-
If this is a multiproc machine and/or hyperthreading is enabled and .NET framework 1.1 is installed then the following hotfix is required: 821157.
Update: this fix is now also included in Microsoft .NET framework 1.1 Service Pack 1 (Windows Server 2003 version, Windows 2000 version)
-
Run a virus scanner as a virus can cause such an errors.
-
If the problem happens in SiteManager try to access the following URL in a browser to see if an error occurs: http://localhost/NR/System/ClientUI/login.asp
If the problem happens during Site Deployment in SiteManager try to access the following URL in a browser to see if an error occurs: http://localhost/mcms/sitedeployment/cmsxmlstub.aspx
-
If neither of these help, try the request from a machine which is not the MCMS 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. Now use Network Monitor to take a trace to see the complete error response sent by MCMS.
[Back to Top]
Topic: Wrong image version
I find that the wrong versions of images are showing up on my site. What could be happening?
Answer
The issue of the wrong version of images is likely a caching problem. It can be a proxy server issue, or an Internet Explorer caching issue. MCMS will most likely limit the occurrence of this (since it will handle caching resources). But it is, of course, still possible to use files off the file system.
For example, Internet Explorer caches the pages it downloads to avoid downloading the same file again (saving bandwidth). This feature works by comparing the file dates of the locally cached file with that of the file on the server. Any server files older than those of the file in the user's Microsoft Internet Explorer cache, are not downloaded.
In some cases, the new version of the image was created after the older versions were last modified. When users visited the site, Microsoft Internet Explorer downloaded and cached the the old image because the file was newer. But when you roll back the images to the original, the file date of the original image file was older than the new file. When Microsoft Internet Explorer sent its request to the server, the server checked dates and reported that the old file (that Microsoft Internet Explorer cached) was still newer than the file on the server and Microsoft Internet Explorer did not download the file from the server.
To resolve this, we modified the dates on the server files so that they were all last modified today. This will force any browsers to download the new files and thus, the correct images will appear.
Even though the files are different, it does not mean they will be downloaded by web browsers; the modified date of the new file must be newer than that of its predecessor.
To check the fix, it should be confirmed on a work machine and a home user's machine (if there is a proxy) without clearing the file cache. File downloads should be monitored using Network Monitor. This is a global fix and should cause every visitor to the site to see the new file without having to clear the cache in their browser.
[Back to Top]
The information contained in this document represents the current view of
Microsoft Corporation on the issues discussed as of the date of publication.
Because Microsoft must respond to changing market conditions, it should not be
interpreted to be a commitment on the part of Microsoft, and Microsoft cannot
guarantee the accuracy of any information presented after the date of
publication.
This White Paper is for informational purposes only. MICROSOFT MAKES NO
WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS
DOCUMENT.
Complying with all applicable copyright laws is the responsibility of the user.
Without limiting the rights under copyright, no part of this document may be
reproduced, stored in or introduced into a retrieval system, or transmitted in
any form or by any means (electronic, mechanical, photocopying, recording, or
otherwise), or for any purpose, without the express written permission of
Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or
other intellectual property rights covering subject matter in this document.
Except as expressly provided in any written license agreement from Microsoft,
the furnishing of this document does not give you any license to these patents,
trademarks, copyrights, or other intellectual property.
© 2004 Microsoft Corporation. All rights reserved.
Microsoft, ActiveX, Visual Studio, Windows, and Windows Server are either
registered trademarks or trademarks of Microsoft Corporation in the United
States and/or other countries.
The names of actual companies and products mentioned herein may be the
trademarks of their respective owners.
| © 2004 Microsoft Corporation. All rights
reserved. |
