CS:2008 Blog Posts Randomly Fail, DynamicStyle.aspx fails to compile.

Reply

TheBlair Posted: Thu, May 15 2008 4:06 PM

rated by 0 users

Trying to set up a series of sample blog posts for a demonstration, I'm experiencing problems where certain entries simply won't post.  Instead, the browser indicates that it's "working" and eventually times out.  Taking the first three sentences from one of the troublesome posts, posting only the first two sentences succeeds, posting the third sentence fails the first time.  On a second attempt, the browser proceeds to the "This page is used to hold your data while you are being authorized for your request" and then times out again.

Looking into the server's event logs, I found an error message.  The DynamicStyle.aspx we copied from the Calypso theme is failing to compile.  The error message appears below, followed by the .ASPx file.

We haven't altered this page, so I don't understand why it wouldn't compile.  It's not clear whether this error is responsible for the failed posts, but it does seem like a reasonable place to start.

Any suggestions would be welcome.

Thanks in Advance.

- Blair

Event code: 3007
Event message: A compilation error has occurred.
Event time: 5/15/2008 3:36:13 PM
Event time (UTC): 5/15/2008 7:36:13 PM
Event ID: a50188f8f07642c493af0e4951425b33
Event sequence: 35
Event occurrence: 4
Event detail code: 0
 
Application information:
    Application domain: /LM/W3SVC/1662699242/Root/cs-4-128553532760956972
    Trust level: Full
    Application Virtual Path: /cs
    Application Path: C:\OtherSites\CommunityServer\Web\
    Machine name: OTSAGSSDW01
 
Process information:
    Process ID: 5648
    Process name: w3wp.exe
    Account name: NT AUTHORITY\NETWORK SERVICE
 
Exception information:
    Exception type: HttpCompileException
    Exception message: c:\OtherSites\CommunityServer\Web\Themes\oce_main_site\style\DynamicStyle.aspx(7): error CS0118: 'CommunityServer.Components.CSContext.SiteThemeData' is a 'property' but is used like a 'method'
 
Request information:
    Request URL: http://myncipreviewint.cancer.gov/cs/themes/oce_main_site/style/DynamicStyle.aspx
    Request path: /cs/themes/oce_main_site/style/DynamicStyle.aspx
    User host address: 156.40.130.97
    User: learnb
    Is authenticated: True
    Authentication Type: 
    Thread account name: NT AUTHORITY\NETWORK SERVICE
 
Thread information:
    Thread ID: 6
    Thread account name: NT AUTHORITY\NETWORK SERVICE
    Is impersonating: False
    Stack trace:    at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath)
   at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
   at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
   at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert)
   at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert)
   at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
   at System.Web.UI.PageHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
   at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
   at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
 
 
Custom event details:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

DynamicStyle.aspx

<%@ Page Language="C#" AutoEventWireup="true" %>
<%@ Import Namespace="CommunityServer.Components" %>
<%@ Import Namespace="System.Drawing" %>

<script language="C#" runat="server">

    protected ThemeConfigurationData themeData = CSContext.Current.SectionThemeData;

    protected override void OnInit(EventArgs e)
    {
        base.OnInit(e);
        Page.Response.ContentType = "text/css";
  
        Page.Response.Expires = 30;
    }

</script>

<%= themeData.GetStringValue("cssOverrides", string.Empty)%>

Reply

TheBlair replied on Thu, May 15 2008 4:18 PM

rated by 0 users

I solved half the problem.  The DynamicStyle.aspx that was failing to compile was in the main theme, not the blog theme.  (Because I was having problems with the blog, I assumed it was the blog copy.)  Apparently when we updated the test machine to use 2008 instead of 2007, I failed to replace that file in the custom theme, and one of the objects used by the code had a different interface that in the previous version.

This does not however solve the time out issue.  To recap:

Trying to set up a series of sample blog posts for a demonstration, I'm experiencing problems where certain entries simply won't post.  Instead, the browser indicates that it's "working" and eventually times out.  Taking the first three sentences from one of the troublesome posts, posting only the first two sentences succeeds, posting the third sentence fails the first time.  On a second attempt, the browser proceeds to the "This page is used to hold your data while you are being authorized for your request" and then times out again.

Suggestions are still quite welcome.

Thanks.

- Blair

Reply

TheBlair replied on Thu, May 15 2008 5:07 PM

rated by 0 users

Wheeee!  I love it when I get to solve my own impossible problems.

Digging into the IIS HTTP error log, I discovered the time out was due to the request body never arriving.  It eventually turned out that the sample blog post I was dealing with talked about grants to university and was being trapped as a SQL injection attack.

Now all I need is to find someone willing to tell the fellow seven levels up from me to stop using the word "grant" in his blog posts. :-)