Component Services Dcom Error
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Wed, 05 Oct 2016 23:50:38 GMT by s_hv1002 (squid/3.5.20)
additional information might be available elsewhere. Thank you for searching on this message; your search helps us identify those https://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows+Operating+System&ProdVer=5.2&EvtID=10016&EvtSrc=DCOM areas for which we need to provide more information. If the product or version you are looking for is not listed, you can use this search box to search TechNet, the Microsoft Knowledge Base, and TechNet Blogs for more information. Enter the product name, event source, and event ID. For example: Vista Application Error 1001.
error only indicates https://www.mavention.nl/blog/resolving-component-services-dcom-error-in-windows-2008-r2 that you've forgotten one step during the installation. :)A. http://serverfault.com/questions/633418/dcomcnfg-cant-set-launch-and-activation-permissions-windows-server-2012 Solving this is quite easy:1. Open Component Services2. Navigate to DCOM Config and select IIS WAMREG admin Service3. Choose Properties, select tab Security4. At Launch and Activation Permissions, select Edit5. Choose Add6. Select from the dcom error local users and groups the group WSS_Admin_Wpg7. Give this group Local Launch and Local Activation rights8. OK that.9. Now the error will not occur anymore.Now when I was installing MOSS onto a Windows 2008 R2 machine I found the following situation:B. As you can dcom error windows see, this dialog is disabled. It turns out that Windows 2008 R2 gives full rights to the TrustedInstaller instead of giving rights to Administrators. This results in you being administrator not being able to edit anything. You can solve this by doing the following:1. Open RegEdit2. Search for the IIS WAMREG admin Service guid {61738644-F196-11D0-9953-00C04FD919C1}3. Select Permissions (as you can see Administrators only have Read rights)4. Click Advanced5. Click on the tab Owner and select Administrators6. Click OK7. Close RegEdit8. Close Component Services (if hadn't done that already)9. Open Component Services10. Now the dialog is enabled so you can perform the steps in section A. Naar mavention Saturnusstraat 60 2516 AH Den Haag Unit 40 in de Caballero Fabriek Contact met mavention info@mavention.nl 070 820 02 31 Home Copyright© 2016
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top dcomcnfg - Can't set Launch and Activation Permissions - Windows Server 2012 up vote 4 down vote favorite I need to modify the Launch and Activation Permissions for the netman area under the Component Services / DCOM Config. However, this area is disabled preventing any changes. I am in the Administrators group I launched dcomcnfg with elevated Administrator privileges. What do I need to do to modify the settings here? windows-server-2012 dcom share|improve this question asked Oct 3 '14 at 19:57 bigwavesoftware 15616 add a comment| 1 Answer 1 active oldest votes up vote 4 down vote accepted From this blog post, Look for HKEY_CLASSES_ROOT\AppID{APPID-GUID}. That should tell you the name of the offending COM component. All you have to do now is go back to the Component Services snapin, find the name of that component, go the security properties of it, and edit the security ACL of that component such that what ever account the event log was bitching about is given whatever access it wanted. If you find that that the security properties of the component are greyed out so that you can't edit it, that's probably because TrustedInstaller has that on lockdown. Go back to the registry, find the corresponding reg key, take ownership/give yourself permissions to it as necessary, restart the service (or reboot the OS,) and then you will be able to modify the security settings on that COM component. I saw this myself just yesterday with the "SMS Agent" DCOM application. The SMS (or SCCM) agent came preinstalled on the standard OS image that was being deployed to the machines I was working on. What's happening here is you can't change the permissions, because the permissions are tied to a registry key that you don't have permissions to change because TrustedInstaller has ownership of it, and you need to take ownership of the re