Why is Sharepoint Services Administration service disabled
- I noticed that my Sharepoint Services Administration service is disabled. Is this the default setting? And if so, why would I want to enable it?
- Moved byMike Walsh MVPMVP, ModeratorFriday, November 06, 2009 4:38 AMnot customization (From:SharePoint - Design and Customization)
Answers
That is not a default setting and it should be running, you should set it to automatic if it's not already and try and start it again... Check the logs to see if it fails to start, if it does look at the permissions of the account to make sure it have appropriate rights and can run the Timer Job... Very important, that SharePoint needs to run.
Look at the following link for more info... Let me know if that does anything for you?
http://technet.microsoft.com/en-us/library/cc560965.aspxThe 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". To start the service, use the section titled Start the administration service.
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 (see table below).
3. To assign the correct rights see the section entitled Assign sufficient permissions to the configuration data cache.
Account
Permissions
WSS_ADMIN_WPG
Read and Write
WSS_RESTRICTED_WPG
Read and Write
An alternate access mapping update failed
Look in the Windows Event log for any events with the Source = "Windows SharePoint Services 3" and event ID = "6397". These events will provide information needed to troubleshoot the problem, such as the Web application affected. To fix this, see the section titled Complete the alternate access mapping update.
You must be a member of the SharePoint Administrators group to perform this task:
To view alternate access mapping settings
1. In Central Administration, click Operations.
2. On the Operations page, in the Global Configuration section, click Alternate access mappings.
Failed to create a SharePoint site
Look in the Windows Event log for any events with the Source = "Windows SharePoint Services 3" and event ID = "6141". These events will provide information needed to troubleshoot the problem, such as the Web site affected.
Resolve
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.
Cause
Resolution
The Windows SharePoint Services Administration service is disabled
The service account has insufficient permissions to write to the configuration data cache
Assign sufficient permissions to the configuration data cache
An alternate access mapping update failed
A service instance provisioning failed
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, click Operations.
3. On the Operations page, in the Topology and Services section, click Services 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 the Custom option.
6. In the 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. To do this, see the Reprovision the service instance section.
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
The event string for event 6397 will provide the alternate access mapping that failed. 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 settings
1. In Central Administration, click Operations.
2. On the Operations page, in the Global Configuration section, click Alternate 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. For more information about this command-line operation, see Command-line reference for the SharePoint Products and Technologies Configuration Wizard (Windows SharePoint Services).
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
If the SharePoint Administration Service was restarted, run the Stsadm command stsadm -o execadmsvcjobs to ensure all tasks that required the administration service have been completed.
You must be a member of the SharePoint Administrators group to perform this task.
Kris Wagner, MCITP, MCTS Twitter @sharepointkris Blog: http://sharepointkris.com- Marked As Answer byRock Wang– MSFTMSFT, ModeratorFriday, November 13, 2009 10:20 AM
Hi,
SPAdmin (Windows SharePoint Services Administration) This is the administrative service for SharePoint. It runs on every SharePoint server locally and is in charge of checking the configuration database for changes. It keeps track of what server on a server farm is running what service, and is used by SharePoint to access local resources per server. This services runs as the WSSADMIN process in Task Manager.
Making backups with SharePoint does have a few gotchas. To help avoid some of them, remember these tips:
· Make sure the Windows SharePoint Services 3.0 Administrative Service is running. This service is often stopped on single-server installs. If you are doing a restore on a server farm, make certain that the Administrative service is running on all the frontend servers in the farm for the duration of the backup or restore.
It's a Windows service. You can start it by selecting "services" under your windows control panel / administrative tools.
Hope this helps.
Rock Wang
Rock Wang– MSFT- Marked As Answer byRock Wang– MSFTMSFT, ModeratorFriday, November 13, 2009 10:20 AM
All Replies
That is not a default setting and it should be running, you should set it to automatic if it's not already and try and start it again... Check the logs to see if it fails to start, if it does look at the permissions of the account to make sure it have appropriate rights and can run the Timer Job... Very important, that SharePoint needs to run.
Look at the following link for more info... Let me know if that does anything for you?
http://technet.microsoft.com/en-us/library/cc560965.aspxThe 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". To start the service, use the section titled Start the administration service.
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 (see table below).
3. To assign the correct rights see the section entitled Assign sufficient permissions to the configuration data cache.
Account
Permissions
WSS_ADMIN_WPG
Read and Write
WSS_RESTRICTED_WPG
Read and Write
An alternate access mapping update failed
Look in the Windows Event log for any events with the Source = "Windows SharePoint Services 3" and event ID = "6397". These events will provide information needed to troubleshoot the problem, such as the Web application affected. To fix this, see the section titled Complete the alternate access mapping update.
You must be a member of the SharePoint Administrators group to perform this task:
To view alternate access mapping settings
1. In Central Administration, click Operations.
2. On the Operations page, in the Global Configuration section, click Alternate access mappings.
Failed to create a SharePoint site
Look in the Windows Event log for any events with the Source = "Windows SharePoint Services 3" and event ID = "6141". These events will provide information needed to troubleshoot the problem, such as the Web site affected.
Resolve
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.
Cause
Resolution
The Windows SharePoint Services Administration service is disabled
The service account has insufficient permissions to write to the configuration data cache
Assign sufficient permissions to the configuration data cache
An alternate access mapping update failed
A service instance provisioning failed
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, click Operations.
3. On the Operations page, in the Topology and Services section, click Services 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 the Custom option.
6. In the 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. To do this, see the Reprovision the service instance section.
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
The event string for event 6397 will provide the alternate access mapping that failed. 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 settings
1. In Central Administration, click Operations.
2. On the Operations page, in the Global Configuration section, click Alternate 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. For more information about this command-line operation, see Command-line reference for the SharePoint Products and Technologies Configuration Wizard (Windows SharePoint Services).
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
If the SharePoint Administration Service was restarted, run the Stsadm command stsadm -o execadmsvcjobs to ensure all tasks that required the administration service have been completed.
You must be a member of the SharePoint Administrators group to perform this task.
Kris Wagner, MCITP, MCTS Twitter @sharepointkris Blog: http://sharepointkris.com- Marked As Answer byRock Wang– MSFTMSFT, ModeratorFriday, November 13, 2009 10:20 AM
Hi,
SPAdmin (Windows SharePoint Services Administration) This is the administrative service for SharePoint. It runs on every SharePoint server locally and is in charge of checking the configuration database for changes. It keeps track of what server on a server farm is running what service, and is used by SharePoint to access local resources per server. This services runs as the WSSADMIN process in Task Manager.
Making backups with SharePoint does have a few gotchas. To help avoid some of them, remember these tips:
· Make sure the Windows SharePoint Services 3.0 Administrative Service is running. This service is often stopped on single-server installs. If you are doing a restore on a server farm, make certain that the Administrative service is running on all the frontend servers in the farm for the duration of the backup or restore.
It's a Windows service. You can start it by selecting "services" under your windows control panel / administrative tools.
Hope this helps.
Rock Wang
Rock Wang– MSFT- Marked As Answer byRock Wang– MSFTMSFT, ModeratorFriday, November 13, 2009 10:20 AM
