+1-888-365-2779
Try Now
More in this section

Forums / Bugs & Issues / Invalid Page request! The CMS entry point should never be called directly.

Invalid Page request! The CMS entry point should never be called directly.

20 posts, 0 answered
  1. WebGeek
    WebGeek avatar
    186 posts
    Registered:
    20 Dec 2006
    18 Apr 2008
    Link to this post
    I am getting this error when my project opens for the first time.
  2. Brook
    Brook avatar
    39 posts
    Registered:
    21 Mar 2007
    21 Apr 2008
    Link to this post
    I just set-up a site for a non-profit client using the Community Sp1 project and I get this message also when first access the site.  Tried setting up twice and still get the same result, if you try entering in hicountryv8.org in your browser and hit the enter key, you pretty much get the error everytime.

    I have a commercial version site runnin for anotehr client and we do not get this issue occurring.

    Brook
  3. Brook
    Brook avatar
    39 posts
    Registered:
    21 Mar 2007
    21 Apr 2008
    Link to this post
    I did a bit more experimenting and here is what i found..if I open a fresh browser session and key in hicountryv8.org with or without the http:// I get the error...which on the server itself is stated as the 'CMS entry point error'.

    The resulting url left in the browser is:
    http://hicountryv8.org/sitefinity/cmsentrypoint.aspx?AspxAutoDetectCookieSupport=1

    If you clear away everything after http://hicountryv8.org and hit enter you get the home page.  as long as that browser is open you can get the homepage, but again if you start a new browser window, the error will occur. 

    I have dbl checked the Network Services has full access, extra mapping for asp.net have been added, etc...  so not sure what I am missing here.  this site is on server 2003, iis 6. 
  4. Nikifor
    Nikifor avatar
    232 posts
    Registered:
    18 May 2013
    23 Apr 2008
    Link to this post
    Hello Brook,

    In fact Sitefinity CMS does not allow requests made to the cmsentrypoint. It seems that there is something in your project which generates these requests. We are not able to reproduce this error locally, so it would be really helpful if you can provide us with additional information. Please let us know if you have made any configuration setup of your project. Also, could you please send us the web.config and the machine.config files of your server. This is their destination folder: C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG

    Greetings,
    Nikifor
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
  5. Brook
    Brook avatar
    39 posts
    Registered:
    21 Mar 2007
    23 Apr 2008
    Link to this post
    Nikor,

    As far as I know we have made no changes to the machine Config and only turned off debugging and health monitoring in the web.config.  I have bot config files for you, but apparently cannot upload them from here, so if OK will open a support ticket from my Client account and upload them there for you.  Appreciate your help on this.

    Brook

  6. Roy
    Roy avatar
    28 posts
    Registered:
    20 Jan 2009
    13 Feb 2009
    Link to this post
    Hello,

    I'm faced with the same error. The first attempt to open the site in new browser window (not a tab) will cause the error to appear. The 2nd attempt is sucessful.

    The strack trace is:
    [HttpException (0x80004005): Invalid Page request! The CMS entry point should never be called directly.]
       Telerik.Cms.Web.InternalPage.OnPreInit(EventArgs e) +641
       System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +663
    
    Is there a solution for this problem?

    Kind regards,

    Roy


  7. Brook
    Brook avatar
    39 posts
    Registered:
    21 Mar 2007
    13 Feb 2009
    Link to this post
    I solved this by reinstalling my site and using a fresh download of SF Community Edition.  I think the issue was permissions and/or the ASP.Net version not being set in the right order.

    • remove your site from IIS
    • delete the folder containing the SF files
    • create a new folder for your site, make sure to apply the permissions to the folder to allow the NetworkService account to have full rights to the folder and any child folders.  Old habits die hard, I usually set the asp.net account with the same
    • COPY your SF files into the new folder, do not cut and paste, this is where I think I may have messed myself up.  I dont copy the root folder over.  I open the source folder with my SF files and subfolders in it, highlight and copy them out of the root folder into the target root folder.
    • Within IIS, set-up the new site and point to the new site folder you just populated.
    • make sure you apply the ASP.Net 2.0 Framework to the site from within IIS.  Even if the default is ASP.Net 2.0, I usually reapply just to be sure.
    • Set-up your special extension mappings to the asp.net framework (e.g. .rss, .tmb,.template and .sflb)
    • Depending on your database set-up, either set-up on SQLExpress, File DB or SQL Server

    This method of setting up new sites on my server or moving sites developed on my dev machine seems to work everytime.  Everyone's environment may be slightly different, but this seems to work for me.  I can do a complete install in under 15 mins now.

  8. Greg
    Greg avatar
    4 posts
    Registered:
    01 Jul 2005
    03 Mar 2009
    Link to this post
    This is happening to me as well, but ONLY when trying to run the site in debug mode in Visual Studio 2008.  No matter how I set the startup, it reverts to the dreaded "CMS Entry Point' error.  Clear out all the extra crap added to the URL, then the site appears for debugging.

    It would be nice to know why this is even doing it at all.  If I tell the sitefinity website (in IIS) that its startup should be http://localhost/test/  or http://localhost/test/Default.aspx , then do THAT, period!  I don't get why this error appears.  I don't want it going anywhere into the Sitefinity subfolder, ever, for any reason.

    It's a minor nuisance, but ff anyone knows how to relieve this one, at least within Visual Studio, that would be great.

    Kuba
  9. Georgi
    Georgi avatar
    3583 posts
    Registered:
    28 Oct 2016
    04 Mar 2009
    Link to this post
    Hi Kuba Cole,

    All requests to Internal pages (such that are stored in the database) go through cmsentrypoint.aspx. When you request a certain page, the logic behind this page (InternalPage class) takes out the page from the database and serve it to the browser. That is why if we call cmsentrypoint directly, Sitefinity will not know which page to serve.

    I suppose that Visual Studio and Cassini are somehow calling the cmsentrypoint directly. Here is what I suggest you though:
    • Set a home page, if you haven't set already
    • Change the built-in Cassini server with IIS
    Let me know if this helps.
    Kind regards,
    Georgi
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Check out the tips for optimizing your support resource searches.
  10. Greg
    Greg avatar
    4 posts
    Registered:
    01 Jul 2005
    26 Mar 2009
    Link to this post
    Hi Georgi,

    Sorry for the delayed response...

    I do, in fact use IIS and not the Cassini server.  I've tried setting a home page in the project startup, and without.  I've tried changing he startup page defined in IIS, yet the problem persists.

    Again, this only happens when launching the site in Visual Studio in debug mode.  Running the site outside of Visual Studio, it's not a problem.

    I should note that I am running in Vista, with IIS 7.

    Thanks, Kuba
  11. Greg
    Greg avatar
    4 posts
    Registered:
    01 Jul 2005
    26 Mar 2009
    Link to this post
    Hi Georgi,

    I figured out what the problem is, at least with Vista and IIS 7...

    1. Open IIS Management
    2. Select your site
    3. Click on "Session State"
    4. Under Cooking Settings, Change the Mode from "Auto Detect" to "Use Cookies"

    For any who might wander to this post... this may alleviate one of those little problems that just bug you!!! :)

    Thanks, Kuba

  12. Georgi
    Georgi avatar
    3583 posts
    Registered:
    28 Oct 2016
    26 Mar 2009
    Link to this post
    Hello Kuba Cole,

    I am really glad you found this. If I should be honest, I haven't though this could be the problem.
    Thank you for sharing the solution here.

    Kind regards,
    Georgi
    the Telerik team

    Check out Telerik Trainer , the state of the art learning tool for Telerik products.
  13. Scott Bradley
    Scott Bradley avatar
    27 posts
    Registered:
    20 Jan 2010
    22 Nov 2010
    Link to this post
    I am also having this problem, but none of the above threads have helped me.  I have deny unauthenticated users, I'm running on IIS.  When I go to the site for the first time and land on the homepage, it redirects me to the login page as it should; however, the return url on the query string is the the cmsentrypoint page.  Any ideas why that might be?
  14. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    22 Nov 2010
    Link to this post
    Hello Scott,

    All page requests pass through cmsentrypoint.aspx. The file inherits InternalPage.cs which implements methods for page management- getting  the mode of the page, name of the ICms Page, instance of CmsManager, optional page settings like EnableViewState, returns the name of the Theme to be set for the current page . Our CmsHttpModule rewrites the URL to cmsentrypoint.aspx, which is the page handler for each CMS page in the Sitefinity. It seems that something in your project forces calling an internal handler before page internal check and you are redirected to our cmsentrypoint.aspx.


    1. Send the error and the full stack of it, so we could try to figure out what causes the issue

    2. Open your site web.config file and check whether you have set publicEntryPoint  in your web.config. If so remove it.

    3. Make sure that you do not have two Sitefinity project connected to the same database.

    4. <deny users "?"/ > setting in the web.config could cause this issue

    5. Please make sure that you do not have any custom code that runs on each request and causes calling cmsentrypoint.aspx.

    6. If you use an older version of Sitefinity please upgrade to the latest official release.

    Greetings,
    Ivan Dimitrov
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  15. Scott Bradley
    Scott Bradley avatar
    27 posts
    Registered:
    20 Jan 2010
    22 Nov 2010
    Link to this post
    Ah, you might have caught the problem.  I stumbled onto some issues early on in the project and rebuilt a new project, but wanted to leverage what was existing. What happens when you point a new site at an existing database?  I merged the sitefinity CMS with the custom database I was trying to integrate with. (Custom meaning data unrelated to sitefinity).  Is it recommended then to have two separate databases?

    Feeling stupid?  I know I am!
    Homer J Simpson
  16. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    22 Nov 2010
    Link to this post
    Hello Scott,

    If your logic does not adds or removes some data from our database there should not be a problem to use a single database. It would be better to have a separate database for your custom data, so you can easily extract it and port it into another project with the custom code you have.

    Sincerely yours,
    Ivan Dimitrov
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  17. Scott Bradley
    Scott Bradley avatar
    27 posts
    Registered:
    20 Jan 2010
    24 Nov 2010
    Link to this post
    So I fixed the problem by creating a new site; however, it showed up again when I moved the files (and the database) to another server.  That server was getting that error, and then so too was my development environment.  When I recreated the site, I made it to a new database. Deployment was a backup and restore to a new server (so I could keep the CMS pages I created).  Any ideas?
  18. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    24 Nov 2010
    Link to this post
    Hi Scott,

    Most probably you are making some redirects that changes the request or something in your server authentication causes this issue. Is there are stack trace of the error that you can share so it would give some more details?

    Regards,
    Ivan Dimitrov
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  19. Scott Bradley
    Scott Bradley avatar
    27 posts
    Registered:
    20 Jan 2010
    24 Nov 2010
    Link to this post
    I found an earlier post that said I couldn't have <deny users="?"/> in the web.config.  Which I did. So how do I deny unauthenticated users access to the site?

    Hopefully an easier question.
  20. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    24 Nov 2010
    Link to this post
    Hi Scott,

    Yes this was step "4". Anyway, this attribute is valid only for static files. Sitefinity works with dynamic data and actually this setting will protect only some physical files.

    • You can use IP restriction form IIS.
    • You can set Deny Anonymous  to True for all pages that you do not want to be seen by not authenticated users
    • You can create a custom HttpModule or HttpHandler to deny the entire request.

    Best wishes,
    Ivan Dimitrov
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
Register for webinar
20 posts, 0 answered