Error 404 When Accessing PWA Site RRS feed

  • Question

  • Hi,

    I have PWA installed with SharePoint 2013.

    The main site is on port 80 and can be accessed by using server name 

    e.g. : http://servername/ 

    and also using the url which has been assigned


    The PWA site can be accessed by using the server name 

    e.g. : http://servername/PWA

    but it cannot be accessed using the url

    e.g. :

    The PWA uses the same web application as the main site and is this on the same default port 80.

    AAM should be fine as the root site can be accessed from other machines and even the PWA site can be accessed using server name, it just cannot be accessed using the URL.

    Thanks for your help in advance.

    Tuesday, December 23, 2014 9:52 AM

All replies

  • Hello,

    When creating the root site collection http://servername/, it may be created using host name. That's why may be you were able to access

    But when creating http://servername/PWA, you might not have used host name. That's why may be you were not able to access the

    The below URL explains how to move Path Based to Host Named Site Collections but it is for SharePoint. As the PWA is already provisioned here you cannot use this method.


    Wednesday, December 24, 2014 4:54 PM
  • Thanks for your reply. 

    I was able to resolve the 404 error by extending the web application to port 88 and then setting the public url for that as So now I do not have 404 error.

    However, what is happening now is that when I access the site from another machine (not the server) then I can access the site properly and see all content e.g. project lists/tasks etc when using the fqdn or server name i.e. http://servername/PWA but when I use the then I can see the PWA Site and home page etc but when I click on Projects to see list of projects or tasks it shows blank box in next page with the error:

    "Cannot communicate with the server. Verify your connection and try again."

    I dont understand how it can communicate with the server with fqdn or server name but not the url.

    Wednesday, December 24, 2014 11:15 PM