More in this section

Forums / Set-up & Installation / Path value null error

Path value null error

2 posts, 0 answered
  1. Richard
    Richard avatar
    3 posts
    13 May 2008
    08 Sep 2008
    Link to this post
    I've installed the Standard edition in IIS 7 on Vista x64 and have the admin site running for a Company template project.  A couple of oddities:
    1. 1. The admin site still thinks I have the IIS7 Integrated Pipeline Mode selected although the appropriate settings for the AppPool all reflect Classic, and
    2. 2. Entering the URL for the site with no page specified (e.g. /localhost/site/) gets me an unhandled exception for a null path.  The site does return a page when I enter a specific page (e.g. /localhost/site/default.aspx or /localhost/site/homepage.aspx).  The stack trace is:

    [ArgumentNullException: Value cannot be null.
    Parameter name: path]
       Telerik.Cms.Web.UrlHelper.GetParentPath(String path) +160
       Telerik.Cms.Web.UrlHelper.GetUrl(String url, Boolean skipSvcs) +934
       Telerik.Cms.Web.CmsHttpModule.BeginRequest(Object sender, EventArgs e) +1498
       System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +80
       System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +171

    I've moved the default.aspx default document to the top of the stack in IIS7 and even added homepage.aspx, but I still get the unhandled exception.


  2. Vlad
    Vlad avatar
    498 posts
    19 Jun 2017
    11 Sep 2008
    Link to this post
    Hello Richard,

    Yes, we are aware of this issue. As you described, it appears when your project is set as a virtual directory in IIS 7 with integrated pipeline mode and requesting an URL with no page specified.
    It is already fixed for the upcoming release.

    Please double-check that your site is working in classic mode. You should not get the message that the IIS7 Integrated Pipeline Mode is selected if the pipeline mode is classic, and also you should not get the error.

    Another approach to get around this problem is to set the web application as a Web Site in IIS.

    Kind regards,
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
2 posts, 0 answered