0

I have installed SharePoint 2016 Server on Windows Server 2012 with SQL Server 2014. I have created a content database and enabled SP features using below cmd. 

Enable-SPFeature pwasite -URL $http://XYZ/sites/pwa

I received success message but when I trying to access URL using Site Primary Administrator account, then system redirected me to an error page saying:

"Sorry, something went wrong An unexpected error has occurred."

I am stuck with this issue for a couple of days and not able to setup project server 2016.

Please help, Thanks in advance

Improve this question
1
  • Have you checked the log/event viewer? Commented Nov 5, 2017 at 9:39

2 Answers 2

Reset to default
1

Looks like the PWA Instance is not configured properly, you should first enable Project Server License using the below cmdlet

 Enable-ProjectServerLicense -Key xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

Note: Although Project Server 2016 is included as part of the SharePoint Server 2016 Enterprise installation, it still requires a separate license. (Trial key:Y2WC2-K7NFX-KWCVC-T4Q8P-4RG9W)

To configure Project Server 2016, you should do the following:

  • Enable Project Server 2016 License.
  • Creating a Project Server 2016 service application.
  • Deploy Project Web App.
    • Create a Web Application.
    • Create a PWA Content Database.
    • Lock Down PWA Content Database to prevent any new site collections being added except PWA site.

  • Finally, use Powershell to Create PWA Site and Enable PWA Site Feature

    #Create a PWA site collection New-SPSite -ContentDatabase PWA_Content -URL http://epm/sites/PWA -Template pwa#0 #enable PWA Site Feature Enable-SPFeature pwasite -URL http://epm/sites/PWA

Please check the details steps at

Or use the below script to auto-configure Project Server 2016

Improve this answer
1
  • Comments are not for extended discussion; this conversation has been moved to chat. Commented Nov 5, 2017 at 12:12
0

After several days of R&D, I came to know that The server farm account is also used by below:

Web Application Pool - SharePoint - 80

Which leads to fail SPTimerService (SPTimerV4).

Thanks M.Qassas for your support so far.

Improve this answer

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.