locked
Not able to view site collection list in central administration RRS feed

  • Question

  • When we are trying to view the site collection list page from Central administration we are seeing many errors:

    Page url:Sitecollections.aspx, Owners.aspx [Once we select the site collection which I am working on from popup windows then below error occurs].

    Object reference not set to an instance of an object.   at Microsoft.SharePoint.ApplicationPages.SelectSiteDataSourceView.get_TotalRowCount()
       at Microsoft.SharePoint.WebControls.AdministrationDataSourceView.ExecuteSelect(DataSourceSelectArguments arguments)
       at System.Web.UI.DataSourceView.Select(DataSourceSelectArguments arguments, DataSourceViewSelectCallback callback)
       at System.Web.UI.WebControls.DataBoundControl.PerformSelect()
       at System.Web.UI.WebControls.BaseDataBoundControl.EnsureDataBound()
       at System.Web.UI.WebControls.CompositeDataBoundControl.CreateChildControls()
       at System.Web.UI.Control.EnsureChildControls()
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    Page url: CNTDBADM.aspx

    Object reference not set to an instance of an object.   at Microsoft.SharePoint.ApplicationPages.ContentDatabasesDataSourceView.FillDataTable(DataTable table, DataSourceSelectArguments selectArguments)
       at Microsoft.SharePoint.WebControls.DataTableDataSourceView.Select(DataSourceSelectArguments selectArguments)
       at Microsoft.SharePoint.WebControls.AdministrationDataSourceView.ExecuteSelect(DataSourceSelectArguments arguments)
       at System.Web.UI.DataSourceView.Select(DataSourceSelectArguments arguments, DataSourceViewSelectCallback callback)
       at System.Web.UI.WebControls.DataBoundControl.PerformSelect()
       at System.Web.UI.WebControls.BaseDataBoundControl.EnsureDataBound()
       at System.Web.UI.WebControls.CompositeDataBoundControl.CreateChildControls()
       at System.Web.UI.Control.EnsureChildControls()
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    And lastly, we are not able to create site collection from UI as well.

    There is an article which has the same issue mentioned..

    http://social.technet.microsoft.com/Forums/zh/sharepointadmin/thread/6201173f-a954-4c84-9b15-63dc8d4d222a

    But, there is no solution mentioned and a Microsoft engineer fixed the issue. Any help is greatly appreciated...

    -Praveen


    ASP.NET and SharePoint developer
    Company: http://www.rampgroup.com/
    Blog: http://praveenbattula.blogspot.com

    Wednesday, September 7, 2011 5:19 AM

All replies

  • If you run an enumsites command in STSADM against the application, do you see the restored site URL in the list?  Although everything is pointing towards a database scheme corruption, I'm thinking the site might just have been orphaned too, which would mean it doesn't show in the GUI.

    Also, how large was the site collection?


    Steven Andrews | SharePoint Professional | http://www.twitter.com/backpackerd00d | https://baron72.wordpress.com/
    Wednesday, September 7, 2011 9:03 AM
    Answerer
  • Hi Steven Andrews,

    Thanks for the quick response. I didn't restore the site yet. After delete site operation the problem started. And if we try to run the restore operation we end up with "Object reference not set to an instance of an object " error. So, there is no choice for us to do something here.
    In enumsites I am not seeing the site I have deleted. But, we are seeing the database associated with it in database. [For each site collection we are creating a database] and the total number of site collections exists under root site collection are 60. I am not seeing the site exists in SharePoint config database or any where. I believe it successfully deleted from the SharePoint side, [the database for that site collection is still exist].

    thanks


    ASP.NET and SharePoint developer
    Company: http://www.rampgroup.com/
    Blog: http://praveenbattula.blogspot.com
    Wednesday, September 7, 2011 9:15 AM
  • Hi,

    Execute STSADM preupgradecheck command in your environment and check if your deleted site exists in orphan state or not.

    I think you will find it as you have mentioned your problem here.

    Now you can delete it:

    http://sharenotes.wordpress.com/2007/11/19/deleting-purging-removing-orphaned-sites-or-site-collections/

    After this you can try restoring your site.

    I hope this will help you out.

     

     


    Thanks, Rahul Rashu
    Thursday, September 8, 2011 3:43 AM
  • Hi Rahul,

    I have ran the PreUpgradeCheck in the server and below is what I see.

    I am really surprised by seeing the result. Something is wrong here as all are showing "Aborted due to internal error". Any ideas?

    And in the final HTML file, it is showing this information.

    Failed
    Failed : Pending upgrade operation detected in this farm
    Pending upgrade is detected on this farm. Either upgrade has not been run, or has failed after a recent update of the SharePoint software.
    Run the SharePoint Products and Technologies Configuration Wizard to finish the pending upgrade. For more information about this rule, see KB article 954775 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.


    ASP.NET and SharePoint developer
    Company: http://www.rampgroup.com/
    Blog: http://praveenbattula.blogspot.com
    Friday, September 9, 2011 7:02 AM
  • Praveen,

    I suggest you to execute Sharepoint config wizard in your farm.

    Once completed then execute Preupgrade check again.

     


    Thanks, Rahul Rashu
    Friday, September 9, 2011 7:13 AM
  • Any issue if we run the configuration wizard? It is having many site collections with huge data...

    In error logs we are seeing this error:

    The following error occured while trying to read the DatabaseIds property.  Object reference not set to an instance of an object.

    -Praveen


    ASP.NET and SharePoint developer
    Company: http://www.rampgroup.com/
    Blog: http://praveenbattula.blogspot.com
    Friday, September 9, 2011 7:14 AM
  • OK.

    We have created an exact copy of production in DEV environment. And ran the SharePoint Configuration Wizard and it ran successful. We have restarted the server and still the issue didn't resolve.

    Any ideas which I can try? I have full control now on the server and database as all are in DEV environment. Please try to solve my problem as this is not giving option to create new site collection, new web site, not sending task emails etc... 

    thanks


    ASP.NET and SharePoint developer
    Blog: http://praveenbattula.blogspot.com
    Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you.
    Tuesday, November 8, 2011 7:40 AM
  • OK.

    We have created an exact copy of production in DEV environment. And ran the SharePoint Configuration Wizard and it ran successful. We have restarted the server and still the issue didn't resolve.

    Any ideas which I can try? I have full control now on the server and database as all are in DEV environment. Please try to solve my problem as this is not giving option to create new site collection, new web site, not sending task emails etc... 

    thanks


    ASP.NET and SharePoint developer
    Blog: http://praveenbattula.blogspot.com
    Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you.
    I had the same problem regarding failing due to internal error. Turns out for me I had to be logged in as someone with enough DB credentials to do the task ...
    Tuesday, December 20, 2011 12:00 AM