How to determine whether the Stsadm.exe command-line tool was run successfully in Windows SharePoint Services 3.0 and in SharePoint Server 2007

View products that this article applies to.

INTRODUCTION

This article describes how to determine whether the Stsadm.exe command-line tool was run successfully in Microsoft Windows SharePoint Services 3.0 and in Microsoft Office SharePoint Server 2007.

The Stsadm.exe command-line tool in Windows SharePoint Services 3.0 and in SharePoint Server 2007 checks for syntax errors. However, the Stsadm.exe command-line tool does not display detailed messages about whether the operation was successful. Even when the Stsadm.exe operation is not successful, the Stsadm.exe command-line tool may display the "Operation completed successfully" message.

To determine whether the Stsadm.exe command-line tool was run successfully, review the Unified Logging Service (ULS) files that are located in the following folder:

Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS

Note The log file uses the ServerName-Date-Time.log format.

For example, when you use the Stsadm.exe command-line tool to enable or to install features that contain a ContentType element name that includes a trailing space, such as YourContentTypeName , you receive the following message:

Operation completed successfully.

In this case, because the ContentType element name includes a trailing space, the ContentType element is not created successfully. Additionally, the ULS log file contains the following error message:

STSADM.EXE (0x176C) 0x0A48 Windows SharePoint Services General 6t4c Unexpected SPContentTypeElement.ElementActivated(). Skipped activation because of InvalidName: 'YourContentTypeName '