| Event Id | 6141 |
| Source | Windows SharePoint Services 3 |
| Description | The site %1 could not be created. The following exception occured: %2. |
| Event Information | According to Microsoft : Diagnose: The can be caused due to following reasons. 1.The Windows SharePoint Services Administration service is stopped or disabled. 2.The farm service account has insufficient permissions to write to the configuration data cache. 3.An alternate access mapping update failed. 4.Failed to create a SharePoint site. 5.A service instance provisioning failed. The Windows SharePoint Services Administration service is stopped or disabled In the Services MMC snap-in, check the "Windows SharePoint Services Administration" service. It should be started and configured as "Automatic". The account has insufficient permissions to write to the configuration data cache 1.Navigate to the %systemdrive%\inetpub\wwwroot\wss\config directory and open its property pages. 2.On the Security tab, check that the following accounts have these permissions. An alternate access mapping update failed You must be a member of the SharePoint Administrators group to perform this task: To view alternate access mapping settings 1.In Central Administration, clickOperations. 2.On the Operations page, in theGlobal Configuration section, click Alternate access mappings. Failed to create a SharePoint site Resolution: To resolve this issue, use the resolution that corresponds to the cause you identified in the Diagnose section. After performing the resolution, see the Verify section to confirm that the feature is operating properly. Start the administration service You must be a member of the SharePoint Administrators group to perform this action. To start the Windows SharePoint Services Administration service (if you can use at least one instance of Central Administration) 1.Ensure that you can logon to at least one instance of Central Administration. 2.In Central Administration, clickOperations. 3.On the Operations page, in theTopology and Services section, clickServices on server. 4.On the Services on server page, select the server you want to start the administration service on from the Server drop-down list. 5.Select theCustom option. 6.In theb>Start services in the table below section, next to Central Administration, click Start. If the Windows SharePoint Services 3.0 Administration service still will not start, you need to reprovision Windows SharePoint Services 3.0. Assign sufficient permissions to the configuration data cache Ensure that the WSS_ADMIN_WPG and WSS_RESTRICTED_WPG local groups have been granted permissions to write to the %systemdrive%\inetpub\wwwroot\wss\config folder. You must have Modify permissions to the folder to perform this task. Complete the alternate access mapping update You can try to re-create the mapping using Central Administration.You must be a member of the SharePoint Administrators group to perform this task. To view or change alternate access mapping settings1.In Central Administration, click Operations. 2.On the Operations page, in the Global Configuration section, clickAlternate access mappings. 3.To edit the mapping, click the mapping. Reprovision the service instance On the specified server, re-provision the service by using the Psconfig command. You must be a member of the SharePoint Administrators group to perform this action. To reprovision Central Administration by using the Psconfig command-line tool 1.On the affected server, navigate to the Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN directory. 2.Open the command line and type the following: psconfig -cmd adminvs -unprovision. 3.This will unprovision the service instance. 4.Open the command line and type the following: psconfig -cmd adminvs -provision -port-windowsauthprovider onlyusentlm.5.This will reprovision the service instance. The administration service should now work. Verify : f the SharePoint Administration Service was restarted, run the Stsadm command stsadm -o execadminsvcjobs to ensure all tasks that required the administration service have been completed. |
| Reference Links | Event ID 6141 from Source Windows SharePoint Services 3 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.