to implement SaaS operations of Microsoft Dynamics CRM and Exchange Server, Microsoft deploys a mandatory HMC component MPs (Microsoft provisioning system). For details, see products? Familyid = F0B76D08-69B0-4A3D-AC97-10708B665EB8 & displaylang = EN), which isolates ou and ou in husting AD, each of which is a tenant (Tenant ). In addition to domain control, this component must have three roles: mpssql (SQL server2005 must be installed with the English Enterprise Edition), mpseng, and mpsweb, mpsweb is the interface (http://mpsweb.contoso.corp/mpsws/HostedActiveDirectory/Service.asmx) that exposes hosting ad to the outside world, mpseng and mpsweb communicate through socket, and mpseng has a service provisioning Queue Manager service.
The following errors are frequently found on mpseng:
failed while picking up the queued jobs from server mpssql; mpftranlogdata with error code 80004005. if these error are seen very frequently please escalte it.
This error maybe be either due to connectivity issue with transaction log database or due to some deadlock and background pickup thread was choosen as a deadlock victim.
For more information, seeHttp://go.microsoft.com/fwlink/events.aspHelp and Support Center.
Found a lotArticleThere is no way to solve this problem, including foreigners.
If it is initially suspected that there is a deadlock problem on mpftranlogdata, by executing sp_who_lock, no deadlock is found. If it is found that the startup account contoso of provisioning Queue Manager Service is found. corp \ mpfserviceacct. This user is in the mpfserviceaccts group on the DC. In mpssql, mpfserviceaccts only has the public and mpfservicerole permissions on mpftranlogdata. Therefore, it is promoted to grant db_owner permissions, then restart mpssql, then restart mpseng, and finally restart mpsweb. The starting sequence must be like this. Otherwise, the problem persists. Finally, the mpseng finds that this error does not occur and the problem is solved.