Skip to main content

MOSS 2007: The specified web does not contain a reporting metadata list

While working with Microsoft Office SharePoint Server (MOSS) 2007, I encountered an unexpected error when attempting to access Audit Log Reports under Site Collection Administration.

The following error appeared:

The specified web does not contain a reporting metadata list

Unfortunately, SharePoint provided no additional information explaining why the error occurred.

Environment and symptoms

The issue occurred in the root site collection of our MOSS environment.

A few details were worth noting:

  • The error appeared when selecting Audit Log Reports from Site Collection Administration.
  • The affected site collection was not migrated from an earlier SharePoint version.
  • The problem occurred in our root site collection.
  • The error message did not provide further diagnostic information.

Resolution: Activate the Reporting feature

I resolved the issue by activating the SharePoint Reporting feature using the STSADM command-line tool with the -force parameter.

The command used was:

stsadm -o activatefeature -name Reporting -url http://[server]/[sitecollection]/ -force

Replace the example URL with the URL of the affected site collection.

After executing the command, I was able to access Audit Log Reports successfully.

Why did this happen?

I couldn’t establish the underlying cause of the problem.

The site collection had not been migrated from a previous SharePoint version, so migration-related issues did not explain the behaviour in this particular case.

Although activating the Reporting feature resolved the error, that observation alone does not establish why the feature was unavailable or not functioning correctly beforehand.

Important considerations

This solution was used in a MOSS 2007 on-premises environment.

Before attempting a similar fix:

  • Confirm that the error and SharePoint version match your environment.
  • Verify the feature name and target site collection URL.
  • Ensure you have the necessary SharePoint administrative permissions.
  • Exercise caution with the -force parameter and test changes before applying them in production.

The STSADM command shown here is legacy SharePoint administration guidance and is not applicable to SharePoint Online.

Conclusion

If you encounter the error “The specified web does not contain a reporting metadata list” when accessing Audit Log Reports in MOSS 2007, checking the Reporting feature may be a useful troubleshooting step.

In my environment, activating the feature using STSADM with the -force parameter resolved the issue, although the original cause remained unknown.

Historical troubleshooting note: This article documents an issue and resolution observed in MOSS 2007. It is retained for administrators researching legacy SharePoint environments.


Labels:

Comments

Post a Comment

Popular posts from this blog

SharePoint Designer Workflow Failed to Start - Cancelled by System Account

I was working on a List workflow the other day in SharePoint Designer 2010. This list already had a workflow which was working perfectly fine and I needed another manual workflow in it. No matter what I tried the workflow would fail and would log a message in the history list that Workflow failed to start and it was cancelled by System Account . I observed that the same happened with new workflows in that list, new workflows in other lists and I even tried creating new subsites and workflows were behaving the same way. I googled for a while and there were many suggestions to clear SPD cache which did not help me. I played with SPD 2010 for a while and observed that the workflow xml and xoml files were checked out. I read in some blogs that this could cause this issue as well. I tried to check those files in but then I was greeted with a new error! " Cannot perform this operation. The file is no longer checked out or has been deleted ." I had no clue what was happening...
10 comments
Read more

Difference between the architectures of SSPs and SharePoint Service Application

SharePoint 2010 has some new features and components, which help to overcome difficulties such as redundancy and service-sharing that we faced while using SharePoint 2007.  Services in MOSS 2007 were implemented with the help of Shared Service Providers or SSPs. But we cannot use the services of one SSP for another SSP. So each SSP has to have its own set of services and applications, which increases redundant data in the farm.  For example, different managers in the same organization use a SharePoint site to maintain official data associated with an SSP. This SSP is associated with different services, such as Search service, BDC service, and a user profile service. A project manager in this organization requests an exclusive user profile service to maintain project data security. To provide this, we first need to create a separate SSP for the project manager and then a separate service called user profile service - project name. Next, we need to associate the SSP with ...
5 comments
Read more

Document Property disabled under Quick Parts in Word 2010

Document Property under Quick Parts sometimes appears grayed out or disabled in Word client and we can see that Compatibility mode written on the Word client on the top part. This happens because Word disables certain features to make our document compatible with previous versions of Office. To workaround we have to change the compatibility feature. To do that click File on the Word ribbon and select Info. Click on Convert button and click OK on the pop up message. This enables the disabled features and now we can access the Document Properties under Quick Part.
5 comments
Read more