Dcom Error 10016 Iis
Contents |
Microsoft Tech Companion App Microsoft Technical Communities Microsoft Virtual Academy Script Center Server and Tools Blogs TechNet Blogs dcom error 10016 windows xp TechNet Flash Newsletter TechNet Gallery TechNet Library TechNet Magazine dcom error 10016 server 2003 TechNet Subscriptions TechNet Video TechNet Wiki Windows Sysinternals Virtual Labs Solutions Networking Cloud and Datacenter Security
Dcom Error 10016 Windows 7
Virtualization Downloads Updates Service Packs Security Bulletins Windows Update Trials Windows Server 2012 R2 System Center 2012 R2 Microsoft SQL Server 2014 SP1 Windows 8.1
Dcom Error 10016 Server 2008 R2
Enterprise See all trials » Related Sites Microsoft Download Center TechNet Evaluation Center Drivers Windows Sysinternals TechNet Gallery Training Training Expert-led, virtual classes Training Catalog Class Locator Microsoft Virtual Academy Free Windows Server 2012 courses Free Windows 8 courses SQL Server training Microsoft Official Courses On-Demand Certifications Certification overview MCSA: Windows distributedcom error 10016 10 Windows Server Certification (MCSE) Private Cloud Certification (MCSE) SQL Server Certification (MCSE) Other resources TechNet Events Second shot for certification Born To Learn blog Find technical communities in your area Support Support options For business For developers For IT professionals For technical support Support offerings More support Microsoft Premier Online TechNet Forums MSDN Forums Security Bulletins & Advisories Not an IT pro? Microsoft Customer Support Microsoft Community Forums United States (English) Sign in Home Windows Server 2012 R2 Windows Server 2008 R2 Library Forums We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Application Server COM COM Security Policy Configuration COM Security Policy Configuration Event ID 10016 Event ID 10016 Event ID 10016 Event ID 10002 Event ID 10003 Event ID 10004 Event ID 10015 Event ID 10016 Event ID 10017 Event ID 10018 Event ID 10019 Event ID 10020 Event ID 1
ComicOctober 28, 20080 0 0 0 Typically after a SharePoint installation when you use separate accounts for the different services, you will notice DCOM errors in the Event Log on the SharePoint server. This is because the accounts for the Application Pools don't
The Application Specific Permission Settings 10016
have the necessary rights to launch the IIS WAMREG Admin Service. If you iis wamreg admin service properties disabled view one of the errors, it should look something like this: We are specifically looking for a message like this: dcom error 10016 windows 10 The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {61738644-F196-11D0-9953-00C04FD919C1} To resolve these errors, we need to grant Launch and Activation rights to the Application https://technet.microsoft.com/en-us/library/dd337789(v=ws.10).aspx Pool accounts. By default, it should have the SharePoint managed groups (local accounts) WSS_WPG and WSS_ADMIN_WPG already. If it doesn't (most likely you are running Kerberos) you'll need to add these as well. Open the Component Services tool Start > Run > dcomcnfg.exe Navigate the Component Services tree Computers > My Computer > DCOM Config. At the Services list, scroll to IIS WAMREG Admin Service Here you https://blogs.technet.microsoft.com/sharepointcomic/2008/10/28/sharepoint-causes-dcom-errors-event-id-10016/ will see the GUID (Application ID) as referenced in the error message.
To assign the permissions, right-click on the object and select Properties. Click the Security tab, make sure the Customize radio button is selected and then click the Edit button. The final step is to add the Local server groups and Application Pool service accounts to give them permission. For the Local server groups Click the Add button, and then set the Location to the Local Machine Then add the groups WSS_WPG and WSS_ADMIN_WPG Click the OK button For the Application Pool accounts (assuming domain accounts) Click the Add button, and then set the Location to the Domain Then add the application pool accounts Click the OK button After adding the users you need to make sure they have Local Activation privileges Select the account and check the Allow checkbox for “Local Activation” permission. Repeat this step for each of the account groups. When you have finished for all users/accounts, click the OK button This process needs to be completed for each web front end server - Dan Tags Errors SharePoint Comments (0) Cancel reply Name * Email * Website Follow UsPopular TagsSharePoint Tips Shaany issues. Fix the SharePoint DCOM 10016 error on Windows Server 2008 R2 Tags: SharePoint, Security, Windows Server 2003, Windows http://www.wictorwilen.se/Post/Fix-the-SharePoint-DCOM-10016-error-on-Windows-Server-2008-R2.aspx Server 2008, Windows Server 2008 R2 Tuesday, August 18, 2009 1:52:24 http://www.sharepointblogs.be/blogs/vandest/archive/2012/11/29/fixing-sharepoint-dcom-errors-the-easy-way.aspx AM If you have been installing SharePoint you have probably also seen and fixed the DCOM 10016 error. This error occurs in the event log when the SharePoint service accounts doesn't have the necessary permissions (Local Activation to the IIS WAMREG admin service). Your farm will still dcom error function, but your event log will be cluttered. On a Windows Server 2003 or Windows Server 2008 machine you would just fire up the dcomcnfg utility (with elevated privileges) and enable Local Activation for your domain account. But for Windows Server 2008 R2 (and Windows 7, since they share the same core) you cannot do this, the property dcom error 10016 dialog is all disabled due to permission restrictions. It doesn't matter if you are logged in as an administrator or using elevated privileges. The change is probably due to some new security improvements. The reason for it being disabled is that this dialog is mapped to a key in the registry which the Trusted Installer is owner of and everyone else only has read permissions. The key used by the IIS WAMREG admin is: HKEY_CLASSES_ROOT\AppID\{61738644-F196-11D0-9953-00C04FD919C1} Image on the left shows the default permissions for Windows Server 2008 R2 and on the right the default settings for Windows Server 2008. To be able to change the Launch and Activation Permissions with dcomcnfg you have to change the ownership if this key. Start the registry editor (regedit), find the key, click Advanced in the Permissions dialog of this key and select the Owner tab. Now change the owner of the key to the administrators group for example, then set full control to the administrators group. Make sure not to change the permissions for
TypesCross Site QueryDebuggingCustom Field TypesExchange ServerInternet ExplorerWindowsjQuery/JavaScriptAdvanced Computed FieldInfoPathFS4SPSandbox SolutionsOffice Web ApplicationsClaimsFBAWorkflowBIWUGTaxonomyRibbonSPC12TroubleshootingVisual StudioNintexOffice 365 Home Contact Fixing SharePoint DCOM errors the easy way Tagline: Fix your SharePoint DCOM issues with a single click ! Update 8/05/2014: Scripts were revised to work with Windows Server 2008 R2 and Windows Server 2012 with User Account Control enabled. Revised post: Fixing SharePoint DCOM errors the easy way - revised Direct download: DCOMFIX-revised.zip Problem The dreaded DCOM error (10016, DistributedCOM, Local Activation, IIS WAMREG admin Service) has seen the light ever since SharePoint 2007. It carried over to SharePoint 2010 and now it seems to SharePoint 2013 as well. Fixing it wasn’t all that hard. You had to identifiy the DCOM app based on the GUID, identify the user(s) affected and then modify the Local Activation permissions accordingly. Windows Server 2008 R2 and higher made that a bit harder. You first have to set the permissions of the DCOM app in the registry, but that requires changing the owner, granting permissions on the registry key, granting local activation, and then undoing your permission and owner change on the registry key (keep things tidy, you know). Automation Quite some manual steps to take so I decided to automate them. At first I decided to PowerShell it, but I’m not a PoSH hero and decided to use some ready available tools, along with a bit of batch scripting. The two tools required are: DComPerm This tool is provided as sample source code by Microsoft, but I’ve included a compiled version in the download. It takes various parameters to list, set or remove permissions on various DCOM objects. DevxExec This tool allows you to run a process from different credentials, including TrustedInstaller which will make our life a lot easier. » Link: DevxExec This tool eliminates the need to change the permissions in the registry, since our TrustedInstaller account already has them and we’re impersonating that account! Putting it together I have two scripts using the dcomperm tool; one for displaying the current permissions, one for setting the permissions. Note that the APPID and USER (can be user or group) in both files are currently configured for the IIS