Best thing to do is fire up ULS Log Viewer on the server and look at the logs
for that Correlation ID, that'll give you the right information on what the
issue is.
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
MacDonald, MM
Sent: Thursday, 1 December 2011 8:15
HI Chris,
Thank you for your response. Can you bullet at a high level how to do
that..Sorry, Ive never used the log viewer.
Thanks,
Mike
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Chris Walsh
Sent: Wednesday, November 30, 2011 3:19 PM
To: ozMOSS
Subject:
Hi,
What I usually do in that situation is edit the web.config and Enable Debugging
so SharePoint shows me the detailed error message in the browser - sometimes
that helps.
http://msdn.microsoft.com/en-us/library/ee231550.aspx
You could also use PowerShell to lookup your Correlation ID.
