More in this section
Forums / Bugs & Issues / Backend 404 - all cotent is blank

Backend 404 - all cotent is blank

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.
5 posts, 0 answered
  1. Stuart
    Stuart avatar
    33 posts
    Registered:
    01 Nov 2012
    22 Mar 2013
    Link to this post
    Hi,

    I can log in to the backend of my sitefinity instance and see the dashboard without issue. However, when I try to access "Pages", "Content", "Administration>Module Builder" etc... I get an alert box that says "IIS 7 Detailed Error: 404 Not Found". 

    There is a different sitefinity instance running on the same machine that is working without issue, so it appears to be something local to the project. 

    I have tried a hard reset of the codebase from the production head (which is working fine), and I have restored the database locally using a backup from the production database (which is working fine).

    I don't get any front-end errors; however, all dynamically served content was missing before I did the database restore. After the restore, the dynamically served content appeared, but I cannot actually see any of it in the backend.

    Trying to navigate directly to http://domain.com/page/Action/Edit gives me a .NET Object reference not set to an instance of an object error. The page does exist. 

     Help is appreciated...
    Stuart
  2. Stuart
    Stuart avatar
    33 posts
    Registered:
    01 Nov 2012
    22 Mar 2013 in reply to Stuart
    Link to this post
    I just tried creating a new AppPool and a new Website in IIS; same behavior. I'm pretty sure I've narrowed it down to an issue specific to this instance of Sitefinity. But I have no idea where to look from here. Below is the stack trace of the Object reference error:

    [NullReferenceException: Object reference not set to an instance of an object.]
       Telerik.Sitefinity.Configuration.ConfigElementLazyItem`1.get_Element() +111
       System.Linq.WhereSelectEnumerableIterator`2.MoveNext() +247
       System.Linq.WhereSelectEnumerableIterator`2.MoveNext() +164
       Telerik.Sitefinity.Web.UI.Definitions.DefinitionKeyedCollection`2..ctor(IEnumerable`1 configDictionary) +183
       Telerik.Sitefinity.Web.UI.ContentUI.ContentViewControlDefinition.get_Views() +440
       ASP.sfpageservice_f669d9a7_009d_4d83_ddaa_000000000001_10t722215470_default_aspx.__BuildControl__control21() in C:\inetpub\wwwroot\CorpWebsite\SFPageService\F669D9A7-009D-4D83-DDAA-000000000001_10T722215470_Default.aspx:39
       ASP.sfpageservice_f669d9a7_009d_4d83_ddaa_000000000001_10t722215470_default_aspx.__BuildControl__control20() in C:\inetpub\wwwroot\CorpWebsite\SFPageService\F669D9A7-009D-4D83-DDAA-000000000001_10T722215470_Default.aspx:39
       ASP.sfpageservice_f669d9a7_009d_4d83_ddaa_000000000001_10t722215470_default_aspx.__BuildControlContent() in C:\inetpub\wwwroot\CorpWebsite\SFPageService\F669D9A7-009D-4D83-DDAA-000000000001_10T722215470_Default.aspx:39
       ASP.sfpageservice_f669d9a7_009d_4d83_ddaa_000000000001_10t722215470_default_aspx.__BuildControlaspnetForm() in C:\inetpub\wwwroot\CorpWebsite\SFPageService\F669D9A7-009D-4D83-DDAA-000000000001_10T722215470_Default.aspx:18
       ASP.sfpageservice_f669d9a7_009d_4d83_ddaa_000000000001_10t722215470_default_aspx.__BuildControlTree(sfpageservice_f669d9a7_009d_4d83_ddaa_000000000001_10t722215470_default_aspx __ctrl) in C:\inetpub\wwwroot\CorpWebsite\SFPageService\F669D9A7-009D-4D83-DDAA-000000000001_10T722215470_Default.aspx:1
       ASP.sfpageservice_f669d9a7_009d_4d83_ddaa_000000000001_10t722215470_default_aspx.FrameworkInitialize() in c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\445ebcfb\e1edf5da\App_Web_f669d9a7-009d-4d83-ddaa-000000000001_10t722215470_default.aspx.d63928b6.1lfw_cs4.0.cs:0
       System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +67
       System.Web.UI.Page.ProcessRequest() +118
       System.Web.UI.Page.ProcessRequest(HttpContext context) +98
       ASP.sfpageservice_f669d9a7_009d_4d83_ddaa_000000000001_10t722215470_default_aspx.ProcessRequest(HttpContext context) in c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\445ebcfb\e1edf5da\App_Web_f669d9a7-009d-4d83-ddaa-000000000001_10t722215470_default.aspx.d63928b6.1lfw_cs4.0.cs:0
       System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +912
       System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +164
  3. Stuart
    Stuart avatar
    33 posts
    Registered:
    01 Nov 2012
    25 Mar 2013
    Link to this post
    Hi,

    I copied the codebase over from the dev server, pointed the new IIS website to that codebase, and pointed that codebase to the database that I restored from the working dev environment. Now everything is directly copied from a working server, with the only modified line of code being the DataConfig database location. I still am not able to access any content in the backend. 

    My other sitefinity instance is also not functioning. I haven't looked at it since I wrote the first post in this thread, so it apparently died sometime between then and now.

    The only other thing I can think of is to reinstall Sitefinity on the computer ... we are running 5.1 in production/dev, and I would like to run that locally as well so that I'm not developing against a different version. Is there somewhere I can procure that?

    Thanks,
    Stuart
  4. Stuart
    Stuart avatar
    33 posts
    Registered:
    01 Nov 2012
    25 Mar 2013
    Link to this post
    Hi,

    I appear to have solved the issue; apparently my IIS configuration changed without warning. 

    For future people who may encounter this problem:
    1) I watched the Network pane of the Inspector in Chrome while trying to access the Blog content type from the dropdown menu in the Sitefinity backend. 
    2) I noticed that the 404 error was specifically because http://localhost:XXXX/Sitefinity/Services/Content/BlogService.svc couldn't be found. I tried to navigate directly to that page and received a 404.3 not found error regarding script handlers/MIME types. 
    3) I nagivated to /Sitefinity/Services/Content and verified that BlogService.svc still existed. 
    4) I googled and found this Stack Overflow questions: http://stackoverflow.com/questions/6425442/http-error-404-3-not-found-in-iis-7-5
    5) I verified that the required components were enabled in Windows 
    6) I ran the command 
    %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -ir
    as administrator.
    7) I restarted IIS
    8) I tested the page
    9) It worked.

    Thanks,
    Stuart
  5. Monika
    Monika avatar
    2 posts
    Registered:
    14 Jun 2012
    14 Sep 2016
    Link to this post
    Thank you Stuart, this was very helpful!  
5 posts, 0 answered