The Microsoft SharePoint 2010 Administration Toolkit is a suite of specialized tools designed to help IT professionals manage, troubleshoot, and optimize SharePoint 2010 server environments. Fixing common errors within this toolkit typically requires resolving underlying configuration mismatches, SQL Server permissions, or systemic interface quirks. Tool-Specific Failures and Fixes 1. SPDiag 3.0 (SharePoint Diagnostic Studio) Errors
The Problem: SPDiag fails to parse ULS log data, or date/time filtering within reports completely breaks.
The Fix: Switch the tool’s local runtime language settings. SPDiag 3.0 requires the host operating system’s language format to be strictly set to US-English. Non-US date formats prevent the application from correctly indexing and querying consolidated time logs.
2. Event ID 6398: “You do not have permission to run ‘SP_TRACE_CREATE’”
The Problem: The central administration farm account throws severe diagnostic blockages when running background tracing jobs or using the toolkit’s performance indicators.
The Fix: Adjust database permissions directly inside SQL Server Management Studio. The SharePoint farm account must be explicitly granted the “Alter Trace” and “Alter Settings” permissions on the hosting SQL Server. Additionally, ensure the farm account is a member of the Performance Monitor Users group on the database server. 3. User Profile Replication Engine (UPRE) Failures
The Problem: Profile and social data replication jobs between User Profile Service Applications (UPA) or older Shared Services Providers (SSP) fail mid-transit.
The Fix: Audit cross-version scope properties. If syncing between SharePoint 2007 and SharePoint 2010, you must disable social activity mapping. Legacy 2007 SSP instances lack structural data containers for social tags and feeds, meaning only standard property profiles can safely transfer. 4. Load Testing Kit (LTK) Synchronization Drops
The Problem: The kit errors out when attempting to convert IIS logs into simulated user stress tests using Visual Studio Team System.
The Fix: Verify and clean source formatting. The LTK depends heavily on precise, sequential Windows SharePoint Services IIS log headers. Ensure that extended logging properties (like Cookie fields or Username variables) are checked inside IIS logs, and filter out corrupted metadata lines before attempting to seed a synthetic load. Core Troubleshooting Checklist for Toolkit Stability
When diagnosing persistent administrative toolkit failures, walk through these fundamental infrastructure layers: Top 10 mistakes made by SharePoint 2010 administrators
Leave a Reply