We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Project Server 2010 PWA unexpected error

AJN-IT
AJN-IT asked
on
Medium Priority
2,514 Views
Last Modified: 2012-05-11
Hi..

Hope someone can help with this

Setup:
- SharePoint 2010 (2 APP servers + 2 Frontend Servers)
- Project Server 2010 installed and configured on all 4 servers
- All databases are on SQL 2008 R2 Failover cluster
- Created PWA site under http://>portalnam>/PWA

Following steps are used to create the PWA page:
1.Create a content database to host the PWA site and its associated project workspaces.
2.Temporarily lock down existing content databases.
3.Create the PWA site itself.
4.Lock down the PWA content database to prevent additional site collections being added.
5.Unlock existing content databases.

PWA site provision is done and up to this point, everything is provisioned and created smoothly and with no errors

Issue:
At this point I should be able to  access the new PWA site, but I am getting the following error:

An unexpected error has occurred.
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: 56078739-4765-45cb-bcee-493816474e9e  <-- changes whenever I refresh!!
Comment
Watch Question

Leandro IaconoSenior Premier Field Engineer

Commented:
It is normal for the correlation ID to refresh everytime you refresh the page.
The correlation ID corresponds to a every new request sent to sharepoint. You can use this correlation id to track the specific error in the sharepoint ULS logs.

What happened in previous version of sharepoint, was that it was hard to track an error message in the ogs because when an error was to be logged inside the logs, sometimes multiple lines had to be written to these logs. Because multiple lines were written, sometimes other stuff was written in between corresponding to another error or process (in essence lots of noise being logged) and you would have to manually go through the logs to determine which lines corresponded to the error message you were looking for.

So, now, we tag every request with a correlation id. This makes it easier because you can filter your ULS logs by that column and correlation id and you can see which lines in the log belong to that specific error.

anyways, the point is, refresh the page and copy the correlation id.
open the ULS log with your faviourte sharepoint uls log viewer (mine is http://archive.msdn.microsoft.com/ULSViewer) and filter by that correlation id. You'll only see the errors and lines which are actually related to the reuqest you made which failed, instead of all the additional noise you would see before.

Anyways, with that, you should be able to get more info on the specific problem you have.

Without additional information, we won't be able to tourbleshoot that unexpected error message.
Post what you get back form ULS logs :)
Commented:
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview

Author

Commented:
It worked for me and I was able to complte my configuration
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.