2014年4月3日 星期四

事件檢視出現找不到來自來源 DCOM 之事件識別碼 10016 的描述的解法


最近客戶端Server事件檢視器常常出現一個訊息:
找不到來自來源 DCOM 之事件識別碼 10016 的描述。本機電腦可能並未安裝引發此事件的元件,或安裝已損毀。您可以在本機電腦上安裝或修復該元件。
如果事件源自其他電腦,則儲存它們時必須一併儲存顯示資訊。
下列資訊已隨附於該事件:
應用程式特定 
本機 
啟用 
{0C0A3666-30C9-11D0-8F20-00805F2CD064} 
NT AUTHORITY 
NETWORK SERVICE 
S-1-5-20
通常面對如{0C0A3666-30C9-11D0-8F20-00805F2CD064} 這樣的ClassID可以調查Registry的HKEY_CLASSES_ROOT\CLSID機碼,如圖(一)。
圖(一)、找到的{0C0A3666-30C9-11D0-8F20-00805F2CD064}的ClassID機碼
image
image
發現此機碼就是Microsoft的指令碼偵錯管理員MDM.EXE (Machine Debug Manager)所註冊的機碼。因為ASP.NET所執行的Network Service並沒有權限進行偵錯而導致此訊息的發生。如圖(二)
image
圖(二)、為Microsoft的指令碼偵錯管理員MDM.EXE (Machine Debug Manager)
image 
解決方式可以透過Dr. Watson來改變系統預設的偵錯管理員,可在開始工具列執行:
drwtsn32 –i
引數-i表示Install的意思,這會將Dr. Watson安裝為系統預設的錯誤處理器此問題即可解決!
註:此問題解法只適用於Windows XP/2003,在Vista/7/2008機制以不同,也找不到機碼{0C0A3666-30C9-11D0-8F20-00805F2CD064},當然也找不到drwtsn32.exe

以下為WIN8.1錯誤劃面




文章來源  : http://www.dotblogs.com.tw/gelis/archive/2010/10/23/18533.aspx


 以下為win8 處理方法

Don't reinstall - you'll just end up in the same place. I actually saw this on my own machine, and something is messing with security. To put it back to the way it should be (and have it work), do the following, in this order: 

1. Open the registry editor to the following key - HKEY_CLASSES_ROOT\AppID\{ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D} 

2. Change the permissions on the key itself by right-clicking on the {ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D} key, and selecting "permissions" 
Click image for larger version 

3. This will open up a permissions dialog box. Click the "Advanced" button: 
Name:  wpn_srumon_server_DCOM_02.png
Views: 15893
Size:  22.9 KB

4. The key is owned by trustedinstaller - this needs to change before we continue, so click the "Change" link: 
Click image for larger version 

5. Assuming the account you're using is part of the Administrators group, just type in "Administrators" in the box and click the "OK" button: 
Name:  wpn_srumon_server_DCOM_04.png
Views: 15884
Size:  10.8 KB

6. Click the "Apply" button, then click the "OK" buttons until the permissions dialog window closes: 
Click image for larger version 

7. You will need to right-click the registry key again (from step 2) and select "Permissions" again from the list: 
Click image for larger version 

8. With "Administrators" highlighted, click to place a check into the "Full Control"/"Allow" box: 
Name:  wpn_srumon_server_DCOM_06.png
Views: 15851
Size:  22.4 KB

9. Click the "Apply" button, then click "OK" again until the permissions dialog window closes: 
Name:  wpn_srumon_server_DCOM_07.png
Views: 15891
Size:  22.6 KB

10. Now, go to the start screen and type "dcomcnfg" - this should show up in the search, and you will need to click on it to open the Component Services window. 

11. Once the Component Services window is open, browse to Console Root > Component Services > Computers > My Computer > DCOM Config, and find "WPN Srumon Server" from the icon list - right-click on this icon and select "Properties": 
Click image for larger version 

12. Click the "Security" tab, and click the "Edit" button in the "Launch and Activation Permissions" section: 
Click image for larger version 

13. Click the "Add" button: 
Name:  wpn_srumon_server_DCOM_10.png
Views: 15841
Size:  19.4 KB

14. Type in the user name from your error dialog *exactly* as it appears in the error dialog from the event viewer (for example, I'm using "Administrator" here, but if your error message says "<computer name>\Donald", then the user name you would use would be "Donald") - again, I'm using the user "Administrator" as an example here; replace with your user name from your machine as necessary, and click the "OK" button: 
Name:  wpn_srumon_server_DCOM_11.png
Views: 15865
Size:  10.9 KB

15. With that new user you entered selected from the "Group or user names" list, click to place a check in the "Local Activation"/"Allow" box: 
Name:  wpn_srumon_server_DCOM_12.png
Views: 15822
Size:  21.3 KB

16. Click the "OK" button: 
Name:  wpn_srumon_server_DCOM_13.png
Views: 15878
Size:  20.8 KB

17. Click the "Apply" button, then keep clicking "OK" to close the permissions window: 
Click image for larger version 

Reboot, and the error should go away (you've just given the user account in your error message the permissions it's complaining about missing).