SHAREPOINT服务器每天凌晨都会出现2次错误在单机上架设了SHAREPOINT服务器,域控制器,SQL2008R2也在这台服
SHAREPOINT服务器每天凌晨都会出现2次错误
在单机上架设了SHAREPOINT服务器,域控制器,SQL2008R2也在这台服务器上.内存24G.
目前的状态是:每天凌晨6点左右会爆下面这2个错误出来,请问这是什么问题,怎么解决
同步 Web 应用程序 b40bb46c-1abb-4bda-87a8-e97a5e7a1bf6、ContentDB 6c6bdf88-4038-4883-8149-02c15b2bb42e 的尝试失败 异常消息为 Microsoft.Office.Server.UserProfiles.UserProfileApplicationNotAvailableException: 没有用户配置文件应用程序可用于处理请求。请与您的服务器场管理员联系。
在 Microsoft.Office.Server.Administration.UserProfileApplicationProxy.get_ApplicationProperties()
在 Microsoft.Office.Server.Administration.UserProfileApplicationProxy.get_PerfmonInstanceHandle()
在 Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer..ctor(ELogType logType, SPContentDatabase cdb, SPJobState jobState)
在 Microsoft.Office.Server.UserProfiles.WSSProfileSyncJob.Execute()
同步 Web 应用程序 ce97d16d-a122-495e-8301-e9821a82adae、ContentDB 177b1119-e178-4b96-a273-a61beaa0949c 的尝试失败 异常消息为 Microsoft.Office.Server.UserProfiles.UserProfileApplicationNotAvailableException: 没有用户配置文件应用程序可用于处理请求。请与您的服务器场管理员联系。
在 Microsoft.Office.Server.Administration.UserProfileApplicationProxy.get_ApplicationProperties()
在 Microsoft.Office.Server.Administration.UserProfileApplicationProxy.get_PerfmonInstanceHandle()
在 Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer..ctor(ELogType logType, SPContentDatabase cdb, SPJobState jobState)
在 Microsoft.Office.Server.UserProfiles.WSSProfileSyncJob.Execute()
[解决办法]UserProfileApplication没有配置好:
http://blogs.technet.com/b/meamcs/archive/2010/12/23/sharepoint-2010-user-profile-service-part-1a-configuration.aspx
[解决办法]或者进入User Profile Service管理页面，在Synchronization 下面有个Configure Synchronization Timer Job，点击进入。之后Run Now
[解决办法]http://www.harbar.net/articles/sp2010ups2.aspx,这片文章说的很清楚啊,Incorrect Permissions,
The UPS Service Instance Service Identity.
Firstly, you must run the UPS Service Instance as the Farm Account. Just because its possible to change the service identity in Manage Service Accounts, doesn’t mean it will work, and more importantly it is unsupported. So don’t change it.
Next, the Farm Account must be a local administrator of the machine running the UPS Service Instance during provisioning only. When we hit Start in Services in Server a series of tasks are run, which are akin to running the second stage of the Forefront Identity Manager setup. Many of these tasks require local machine administrator rights. You must grant this right before hitting start, and more importantly they must be applied. As the Farm Account is running services on your box (SPTimerV4 and the Central Admin app pool) we must simulate a log off and log on for the change in rights to be applied. You can do this by restarting SPTimerV4, or better yet, rebooting the machine. Once UPS is provisioned you can remove the Farm Account from the local administrators group.
[Update] Please note that any event in your farm that requires the UPS service instance to be provisioned will require the Farm Account be a local admin. Such events include the re provisioning of the service instance following the deployment of a SharePoint Cumulative Update and performing a Farm Backup from Central Administration (which stops and starts the UPS service instance). Don’t forget to ensure that the correct rights are assigned (and actually taking effect) when planning and scheduling your farm operational maintenance tasks.
Also, the Farm Account must have Log on Locally rights on the machine running the UPS Service Instance. Now be careful, you may think the account has these rights, and it will do if you made it a local administrator. However once you remove the admin rights, you may not have Log On Locally. If you don’t various operations will fail.
The Synchronization Connection Account
The Synchronization Connection Account must have Replicating Directory Changes on the Domain you are syncing with. It is the only way sync will work. It’s a hard requirement. Despite the scary name the Replicating Directory Changes permission makes zero changes to AD. It provides a change log capability, which improves the speed of operations such as Sync.
If you are syncing with a Windows Server 2003 functional level domain, the Synchronization Connection Account must be a member of the Pre-Windows 2000 Compatible Access group.
If you wish to do an Export, the Synchronization Connection account must have Create Child Objects and Write permissions on the OUs you are syncing with. Watch out for a common gotcha, that these rights are set on the container level only, you must ensure that This object and all descendants is selected.
楼主check下相应的权限有没有.
