Troubleshooting Common Issues in SharePoint Foundation 2010 (Windows SharePoint Services)

Troubleshooting Common Issues in SharePoint Foundation 2010 (Windows SharePoint Services)

SharePoint Foundation 2010 (Windows SharePoint Services) remains in use in many environments. This article provides a practical, step-by-step troubleshooting guide for the most common issues administrators encounter, with quick checks, likely causes, and actionable fixes.

1. Site not loading / “Service Unavailable” or 503 errors

• Quick checks: Confirm IIS application pools are running; check SharePoint services on the server; review event logs and IIS logs.
• Likely causes: Stopped application pool, identity/password change for service account, or app pool recycling due to rapid-fail protection.
• Fixes:
  1. Open IIS Manager → Application Pools → restart the relevant app pool (e.g., SharePoint – 80).
  2. If crashing, check the app pool identity credentials and re-enter updated password.
  3. Disable rapid-fail protection temporarily while diagnosing: Application Pool → Advanced Settings → Rapid-Fail Protection → set to False.
  4. Check Event Viewer (System & Application) for .NET or w3wp.exe errors and address underlying exceptions.

2. “Access Denied” for users who should have permissions

• Quick checks: Confirm user is in correct SharePoint group and that the site inherits or has correct unique permissions; validate web application policy.
• Likely causes: Broken inheritance with missing permissions, denied permissions in parent, or missing “Full Control” for farm/admin accounts for certain operations.
• Fixes:
  1. Site Settings → Site Permissions → check for unique permissions and re-inherit if needed.
  2. Use “Check Permissions” (Site Actions → Site Permissions) to see effective permissions.
  3. In Central Administration → Manage web applications → User Policy, ensure required accounts have correct web-app level permissions.
  4. For permission sync issues, run stsadm.exe -o sync or use PowerShell to reapply permissions as necessary.

3. Search not returning expected results

• Quick checks: Verify Search Service is running; confirm content crawl completed; check crawl logs for errors.
• Likely causes: Crawl rules blocking content, search index corruption, or service account permission issues.
• Fixes:
  1. Central Administration → Manage service applications → Search Service Application → check crawl status and logs.
  2. Restart Search services (Windows Service: SharePoint Server Search) and perform a full crawl.
  3. If index is suspected corrupt: reset index (Central Admin → Search Service Application → Index Reset) then perform full crawl.
  4. Ensure crawler account has read access to the content and necessary local rights.

4. Slow page performance

• Quick checks: Monitor CPU/memory on servers, check SQL Server performance, review ULS logs for throttling or long-running requests.
• Likely causes: Insufficient hardware, misconfigured SQL (auto-grow, single large files), heavy custom code or large lists/libraries.
• Fixes:
  1. Use Performance Monitor on SharePoint and SQL servers to identify bottlenecks (CPU, Memory, Disk Queue Length).
  2. Review SQL Server settings: pre-size database files, configure autogrowth appropriately, optimize tempdb.
  3. Investigate large lists—apply indexing, folders, or list throttling thresholds; paginate or limit CAML queries in custom code.
  4. Enable output caching for publishing pages or configure BLOB cache in web.config if applicable.
  5. Examine ULS logs (use ULS Viewer) for slow requests and address the root cause.

5. Workflow failures or stuck workflows

• Quick checks: Inspect the Workflow History and Workflow Status pages; check SharePoint Timer Service.
• Likely causes: Corrupted workflow instances, timer service stopped, or errors in custom workflow code.
• Fixes:
  1. Restart the SharePoint Timer Service (Windows Service: SharePoint 2010 Timer).
  2. Review ULS logs and workflow history for exceptions; if workflow definitions corrupt, republish from SharePoint Designer or Visual Studio.
  3. Use PowerShell or stsadm to terminate stuck workflow instances.
  4. Ensure accounts running workflows have required permissions on destination lists/sites.

6. Database connectivity errors or content database issues

• Quick checks: Verify SQL Server is online; check SQL connectivity from SharePoint servers; review SQL and SharePoint event logs.
• Likely causes: SQL service down, network issues, SQL authentication failures, or database in suspect mode.
• Fixes:
  1. Ensure SQL services are running and that SQL Server accepts connections.
  2. Check SQL Server logs for database status; run DBCC CHECKDB if corruption suspected.
  3. Restore from backup if a content database is corrupt or in suspect mode.
  4. Use Central Administration → Manage Content Databases to check attachment and size limits.

7. Custom solutions or web parts causing errors

• Quick checks: Identify recent deployments; check ULS and event logs for exceptions tied to a solution or assembly.
• Likely causes: Incompatible or poorly coded solutions, missing assembly or feature dependencies, GAC conflicts.
• Fixes:
  1. Retract and remove recent WSPs via Central Administration or stsadm/PowerShell.
  2. Test in a dev environment and fix code issues; ensure assemblies are strongly named and correct trust levels set.
  3. Clear the SharePoint configuration cache on each server after solution changes.

8. Email (incoming/outgoing) issues

• Quick checks: Verify SMTP server settings in Central Administration; check outgoing email and incoming email settings at the web app and list level.
• Likely causes: SMTP service misconfiguration, firewall blocking, or insufficient permissions on the SMTP server.
• Fixes:
  1. Central Administration → System Settings → Configure outgoing e-mail settings: validate SMTP server, from and reply-to addresses.
  2. For incoming e-mail, ensure the SMTP drop folder and receive settings are correct and that SharePoint has rights to process the folder.
  3. Test using telnet or an SMTP client from the SharePoint server to the SMTP host.

9. Failing upgrades or patches

• Quick checks: Review patch logs, check disk space, ensure services are stopped when required, and confirm farm account privileges.
• Likely causes: Missing prerequisites, customizations blocking upgrade, or insufficient permissions.
• Fixes:
  1. Follow Microsoft’s documented update steps: put farm into maintenance, back up, run the patch installer, then run PSConfig on each server.
  2. Resolve any feature or solution conflicts before rerunning PSConfig.
  3. Review upgrade logs in 14\LOGS and the %temp% folder for errors.

10. Useful tools and logs summary

• Tools to use:
  • ULS Viewer (for real-time SharePoint logs)
  • Event Viewer (Windows & Application logs)
  • IIS logs (C:\inetpub\logs\LogFiles)
  • SQL Server Management Studio (for DB checks)
  • Performance Monitor and Network Monitor
• Logs to check first: ULS logs (14 hive\LOGS), Event Viewer, IIS logs, and Search crawl logs.

Preventive best practices

• Keep a regular backup schedule and test restores.
• Patch test environments before production.
• Monitor server health (CPU, memory, disk) and set alerts.
• Limit direct edits to production; use source control for custom solutions.
• Document architecture, accounts, and configuration to speed troubleshooting.

Quick triage checklist (first 10 minutes)

1. Confirm server services (IIS, Timer, Search, SQL) are running.
2. Check Event Viewer and recent ULS entries for errors.
3. Verify application pool identities and passwords.
4. Test SQL connectivity and database status.
5. Restart affected services and re-test the issue.

If you want, I can create a printable one-page checklist, PowerShell commands to automate common fixes, or step-by-step ULS log filters for a specific error message.