SharePoint 2010 error not found in logs, how to configure logging?

Question

We have a SharePoint 2010 feature that works fine on my development machine, but won't activate on the staging system. It's SiteCollection scoped, the containing solution was successfully deployed on one WebApplication.

When we try to activate the feature, we get an error message with a Correlation ID. But we can't find this ID or the name of the feature in the SharePoint Logs nor in the Windows Event Log.

Maybe logging wasn't configured right or there is an error with ULS on the machine, but we haven't changed the SharePoint Logging options from the state they were after installation. Where can I find exception / error messages that happen in ULS? How must Logging be configured to allow the failed feature activation to be logged?

Answer 1

Under SharePoint 2010, go to Central Administration. There is a Monitoring link. Click there and under reporting is a Configure Diagnostic logging link. If you set the Least Critical event to Trace and Least Critical Event items to verbose, you should get more information in the SharePoint log files. Make sure you switch back though after diagnosing because the process is chatty and can result in extra IO and large files.

Out of the box, I don't believe logging is set. You can also verify the location of the log files to make sure they are not on setup elsewhere on this page.

More information at TechNet

Answer 2

从此处下载ULS Viewer工具： 链接文本并按相关ID过滤。

Answer 3

You can always get information from the logs from all servers in the farm using the Merge-SPLogFile cmdlet. The example below filters on a correlation ID, but there are more filter options (tip: Get-Help Merge-SPLogFile -Full).

$corrID="some correlation id"
Merge-SPLogFile -Path "path to output file" -Correlation $corrID

Answer 4

This is an old post, but if soone gets the same problem, please try the following:

1. Check who is your farm account user (the user under which SharePoint Timer Service is running).
2. Add this user to local administrators
3. Restart Timer Service.

Please mark this as answer if my solution works for you.

Answer 5

It is worth emphasizing that the OP's substantive question,

Where can I find exception / error messages that happen in ULS?

is answered by the OP himself in a comment to @noebierzo,

I found the log entry ... by checking all log files on all front-end servers.

So be aware if you have a multi-server farm; look at all servers in the farm when checking or searching for errors and trace log messages.

Fortunately Microsoft recently released an updated ULS Viewer v16.0.3129.1000 that provides basic multi-server aggregation of the trace logs. Bill Baer, Senior Technical Product Manager for SharePoint at Microsoft has a nice blog post on the new version which outlines this feature.

The new version of ULS Viewer is available from the Microsoft Download Center . Note that this version of ULS Viewer requires at least .NET 4.0 which your SharePoint 2010 farm may or may not have installed. Bill blogs about this but doesn't comment on the impact of installing .NET 4.0 on your SharePoint 2010 farm.

If you want the old version of ULS Viewer v2.0.3530.27850 that only requires .NET 2.0 you can no longer count on Microsoft as they took down the Archive Gallery where it used to live. Fortunately a few people have posted it online, include Benjamin Athawes on his blog .

Given the .NET version dependency, and the fact that SharePoint 2010 is still a supported product, Microsoft really should keep an official link around for this prior version ULS Viewer. Suggest you ask Bill about this on his blog. Perhaps SharePoint 2010 SP2 is fully supported side-by-side with .NET 4.0, it would be good to know.