Deployment and topology (Health model)
Applies To: Windows SharePoint Services 3.0
Several features of Microsoft Windows SharePoint Services 3.0 rely on scheduled background processes called timer jobs. Administrators can configure and schedule timer jobs by using Central Administration. When you use the Services on Server page in Central Administration to start or stop a service, a timer job is used to perform this action.
To improve the performance of Windows SharePoint Services 3.0, much of the data in the configuration database is kept in a local file-system cache, called the configuration data cache. Windows SharePoint Services 3.0 uses the timer service to keep this cache synchronized with the configuration database. Alternate access mapping is a feature of Windows SharePoint Services 3.0 that enables administrators to configure a load-balanced system by mapping an incoming URL to alternate URLs used by Windows SharePoint Services. Windows SharePoint Services enables administrators to create new SharePoint sites. Site owners and (depending on the site settings) site visitors can also create subsites.
Events
| Event ID | Source | Message |
|---|---|---|
Windows SharePoint Services 3 |
The site %1 could not be created. The following exception occured: %2. |
|
Windows SharePoint Services 3 |
Insufficient permissions to write to the configuration data cache. More information is included below. %1 |
|
Windows SharePoint Services 3 |
Alternate Access Mapping failed to be updated. Web Application affected: %1. Current user: %2. More information is included below. %3 |
|
Windows SharePoint Services 3 |
An attempt to start/stop instance %1 of service %2 on server %3 did not succeed. Re-run the action via UI or command line on the specified server. Additional information is below. %4 |
|
Windows SharePoint Services 3 |
%1 |
Related Management Information
Windows SharePoint Services 3.0 farm (Health model)