The Correlation ID error seemed to be especially common in Beta versions of SharePoint Server 2010. However, I have managed to surface this one a few times in RTM. The screen print below illustrates what the error looks like on the Web page.
The error doesn't provide much information about the root cause. So, to uncover the details, it makes sense to investigate further by examining the log files. Here is how to do that:
1. Note the date and time of the error message.
2. Open a local console or RDP session to a SharePoint server in the farm.
3. From Windows Explorer, navigate to Program Files > Common Files > Microsoft Shared > Web Server Extensions > 14 > Logs.
4. Sort the log files by Date Modified, Descending. Then, open the file containing the event using a text editor, such as Notepad.
5. CTRL +F to locate instances of the word "Error." Then match the date/time stamp.
Subscribe to:
Post Comments (Atom)
Blog Archive
-
▼
2010
(60)
-
▼
December
(7)
- Windows Server: Enable Execution of PowerShell Sc...
- Windows Server 2008: MSInfo32 and Winver
- Microsoft Word 2010: Hanging Indent
- SharePoint 4.0: Locating or Verifying Farm Versio...
- SharePoint 4.0: Records Center Behaviors? or Bugs!
- SharePoint 4.0: Where to Locate Details for Error...
- SQL Server 2008: Edit Top 200 Rows
-
▼
December
(7)
Events / Conferences / User Groups
- AIIM Conference
- Boston Area SharePoint User Group
- Boston Azure User Group
- Collaborate
- DevConnections
- DevIntersection
- Enterprise Search Summit
- Microsoft Build
- Microsoft SharePoint Conference
- Microsoft TechEd
- New England ASP.NET Professionals User Group
- New England Oracle Applications User Group
- Oracle Applications User Group (OAUG)
- Oracle OpenWorld
- PeopleSoft Government Contractor Special Interest Group
- PeopleSoft Southern New England Users Group
- Quest International Users Group
- SharePoint Saturday
- SPTechCon
- SQL PASS
- SQL Saturday
- Startup Weekend
1 comment:
I will like to use ULS Viewer @
http://archive.msdn.microsoft.com/ULSViewer
Post a Comment