Event Viewer Error 10010
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 13 Oct 2016 19:45:07 GMT by s_ac4 (squid/3.5.20)
Links Notable Members Current Visitors Recent Activity New Profile Posts Search Search titles only Posted by Member: Separate names with a comma. Newer Than: Search this thread only Search https://hardforum.com/threads/windows-8-1-event-viewer-errors-id-10010-dcom.1787186/ this forum only Display results as threads More... Recent Posts Menu Log in or Sign up [H]ard|Forum Forums > Bits & Bytes > Operating Systems > Windows 8.1 - Event Viewer Errors (ID 10010, DCOM) Discussion in 'Operating Systems' started by Milena, Oct 22, 2013. Oct 22, 2013 #1 Milena Limp Gawd Messages: 435 Joined: Aug 9, 2010 Upgraded my PC to 8.1 and event viewer so far everythings finished I only have one problem left, an Event ID 10010 error is being logged 2 times after every log in: The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout. I tracked this down in the registry and its related to Skydrive. I'm using a local account and not a Microsoft one so Skydrive isn't working, could that event viewer error be the cause? Anyone else is getting these events logged on their 8.1 install? If I switch to a Microsoft account for Windows 8.1, what will actually happen when I try to log in while my Internet connection is down? I didn't read up much on it but im generally not a friend of any kind of online-only features. Best regards Milena, Oct 22, 2013 Milena, Oct 22, 2013 #1 Oct 22, 2013 #2 luckman212 n00bie Messages: 3 Joined: Oct 13, 2009 Just chiming in - I got the same DCOM error on my 8.1 (upgraded from 8) box. I also use a local account and am not using SkyDrive. No fix yet, but the error seems to be just cosmetic and not causing any harm. Maybe someone else will have more advice on getting rid of it. luckman212, Oct 22, 2013 luckman212, Oct 22, 2013 #2 Oct 25, 2013 #3 Ultra Wide [H]ard|Gawd Messages: 1,394 Joined: Jul 23, 2000 I have the same error in the Event Log, I am also using a local account. The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout. Th