| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Eventid 10016 fills up system event log . |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 5
|
|
| Author |
|
|
jsobry@gmail.com
Cruncher Canada Joined: Jan 11, 2008 Post Count: 31 Status: Offline Project Badges: 
|
Copy of event info:
*********************************************************** Event Type: Error Event Source: DCOM Event Category: None Event ID: 10016 Date: 08/04/2009 Time: 3:58:09 PM User: YOUR-4DACD0EA75\boinc_master Computer: YOUR-4DACD0EA75 Description: The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {5F36DC27-B076-4D0C-BD8C-7AEE14022193} to the user YOUR-4DACD0EA75\boinc_master SID (S-1-5-21-1891380956-1541415802-3028849237-1014). This security permission can be modified using the Component Services administrative tool. ********************************************************* Has anybody seen this problem? It started after installing the latest BOINC software Version 6.4.7 and wxWidgets Version 2.8.7. I don't use widgets in any case. HP PC m7690n with Windows XP SP3 (Media Center). Is this caused by the new boinc userid?? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Our recommended BOINC version is 6.2.28.
|
||
|
|
jsobry@gmail.com
Cruncher Canada Joined: Jan 11, 2008 Post Count: 31 Status: Offline Project Badges:
|
How come I got a red message stating that I should move to the latest release of Boinc?
|
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Ask Dr.Anderson. The message in red has already been followed by 3 more releases due bug fixes... and more to come.
----------------------------------------The WCG version 6.2.28 only tells you when WCG thinks it's ready for their volunteers in the broadest sense and has withstood scrutiny in multiple areas. Reality is, you only need 6.6 if you do GPU/CUDA crunching.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
jsobry@gmail.com
Cruncher Canada Joined: Jan 11, 2008 Post Count: 31 Status: Offline Project Badges:
|
Just for everyone's enlightenment I should perhaps relate the following.
I did uninstall Boinc 6.4.7 and installed 6.2.28 but that did not fix the problem with the event log filling up with DCOM errors, eventid 10016. I eventually figured out that the problem with DCOM was that MSDTC service was not running and could not be started even by DCOM. I noticed that there was no MSDTC service running at all and that it even did not show up in the table or list of services. I did some research and microsoft reports a problem with SQL in Windows server 2003 that is vaguely similar to this problem. However in their solution to the server 2003 problem they had a very short procedure to reinstall MSDTC. Please refer to the bottom of an article called "Troubleshooting problems with MSDTC" at http://msdn.microsoft.com/en-us/library/aa561924.aspx. To save you the trouble of looking for this you can just issue the following commands from a Command Shell: msdtc -uninstall msdtc -install In typical microsoft fashion I did not get a single message saying that these commands were successful or not. However to give you peace of mind you can go look in Event viewer and they actually do log some information there. You will get eventid 4105 for successful removal followed by 4104 for successful install. Then you have to go to the services screen (I get there from adminisrtative tasks but there are other ways) and scan down for the MSDTC service which you will find named "Distributed Transaction Coordinator" and start it manually. You will then get an eventid 2444 log entry in event viewer stating that MSDTC properly started. After that your event viewer log will no longer fill up with eventid 10016 as soon as you start BOINC. Unless of course you have a different problem giving the same symptoms. Now, if I could just get BOINC to connect to the internet and start running properly again. But more on that later ... |
||
|
|
|