none
Create new site collection: page cannot be displayed.

    Question

  • Hi all,

    I've had this problem twice now, so let's see if someone has a solution for it.

    I have installed SharePoint 2013 Foundation and ran the configuration tool using an Admin account. For a specific situation, we need a site collection using classic windows authentication. So I created a web application using Windows Authentication through SharePoint 2013 Management Shell. Got the warning, but the web application is succesfully created.

    After that, I create a new site collection in this web application in SharePoint 2013 Central Admin. It says the site collection had been succesfully created. I made the Admin account sitecollection administrator. However, browsing the site collection using this user, is says: "Page cannot be displayed".

    Why is this and how can I solve it?

    The first time, I read a blog where someone was saying the configuration wizard should be run with the same user that was used to run the setup of SharePoint Foundation. Then, it seemed to solve the problem (meaning: it was gone!). However, now is doesn't.

    Any help would be greatly appreciated!

    Cheers,

    Ruud.

    Tuesday, October 29, 2013 7:28 AM

Answers

  • Thanks for your reply Romeo.

    Although your reply was not the solution in itself, it put me in the right direction, so thanks! What I did:

    My default site collection (created by the configuration tool) was on, lets say, http://sitecolinstance1. I tried to create the new webapplication on http://sitecolinstance1wa (pay attention to the addition "wa"). I did this the first time and it wasn't a problem then. Nevertheless, I figured it might be better to keep it http://sitecolinstance1 and set it on port 2013. After I created the web application using Windows Authentication through the Management Shell, I explicitly gave the Admin account full control to the web application using the user policies in Central Administration.

    After that, I created the site collection and now it works just fine. Not exactly shure which of the two was the real solution to the problem... ;-)

    Cheers, Ruud.

    • Marked as answer by Ruud Hunnekens Tuesday, October 29, 2013 8:07 AM
    Tuesday, October 29, 2013 8:07 AM

All replies

  • Hi

    generally speaking

    how can you try to browse the new site

    using a specific page or only the URL or IP address. By default , SP create a home page, default home page when a site collection is created

    if you try to browse another page which doesn't exist it's normal to receive that error message

    So first try to access the site using

    http://your_domain

    or

    http://IP_ADDRESS:TCP_PORT

    depending how and if you configured your DNS and AAM in SP server

    Next , if it's ok, check which page is displayed by default.

    If isn't , open your site collection using SP designer , and set a page as a default page for your site, and chech again to browse your site.


    Romeo Donca, Orange Romania (MCSE, MCITP, CCNA) Please Mark As Answer if my post solves your problem or Vote As Helpful if the post has been helpful for you.

    Tuesday, October 29, 2013 7:35 AM
  • Thanks for your reply Romeo.

    Although your reply was not the solution in itself, it put me in the right direction, so thanks! What I did:

    My default site collection (created by the configuration tool) was on, lets say, http://sitecolinstance1. I tried to create the new webapplication on http://sitecolinstance1wa (pay attention to the addition "wa"). I did this the first time and it wasn't a problem then. Nevertheless, I figured it might be better to keep it http://sitecolinstance1 and set it on port 2013. After I created the web application using Windows Authentication through the Management Shell, I explicitly gave the Admin account full control to the web application using the user policies in Central Administration.

    After that, I created the site collection and now it works just fine. Not exactly shure which of the two was the real solution to the problem... ;-)

    Cheers, Ruud.

    • Marked as answer by Ruud Hunnekens Tuesday, October 29, 2013 8:07 AM
    Tuesday, October 29, 2013 8:07 AM
  • Hi

    welcome! ;)

    as i said was an issue with name resolving

    using http://sitecolinstance1wa , your browser doesn't resolve the name and can't display the page

    Permission access issues , are upper than accessing the page

    When you browse a page, first, after the browser resolve the name and find the web/remote machine , will show the page is anonymous access is permited, or will ask for credentials.


    Romeo Donca, Orange Romania (MCSE, MCITP, CCNA) Please Mark As Answer if my post solves your problem or Vote As Helpful if the post has been helpful for you.

    Tuesday, October 29, 2013 10:12 AM