https://community.spiceworks.com/topic/503277-dcom-was-unable-to-communicate-to-removed-server-event-id-10028
Dear pros,
recently we migrated our DC from 2003 SP2 to WIN 2012 R2 and it went smooth but in
event viewer we started seeing error with event id# 10028.
details are below;
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 5/20/2014 10:32:07 PM
Event ID: 10028
Task Category: None
Level: Error
Keywords: Classic
User: SYSTEM
Computer: MAIN.COMPANY.COM
Description:
DCOM was unable to communicate with the computer ABCGW02. COMPANY.COM using any of the configured protocols; requested by PID dc8 (C:\Windows\system32\taskhost.exe).
what really bother us here that ABCGW02 server was removed atleast 7 years back but still it is looking for it.
can you please help us to sort this issue out??
Somewhere on this server you have some reference to the removed server. Did you have a share mapped to a local drive letter?
Compare teh list at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Shares with what you see from doing Net Share.
Hi...many thanks for the reply.. I have compared the registery with net share output and they are identical.
I have searched everywhere but couldnt find ABCGW02 server anywhere.
how often do you see the error?
You could possibly turn auditing on and look at what happens just prior to that error.
Was, by any chance, the removed server a domain controller?
thanks for reply...
I just started seeing this error after migrating from win 2003 SP2 to win 2012 R2 which is done five days back.
and I see this error 3 times daily .. it seems the job starts at 2 AM then 10 AM and finally at 6 PM which means it is schedule to run every 8 hours.
the server was a test gate way with isa 2000 and removed before 2004. no it wasnt a DC.
What job are you talking about ? If there is a job that is starting and this casues the error - more details about the job.
Could it be you have a proxy setup with that old server as the proxy?
Bottom line - somewhere on this server you have some sort of reference to the remote now extinct server. If you know accurately when the next failure will occur - - why not turn network monitoring on and look at what traffic is being attempted to the removte server.
Or just ignore it the error.
I just assumed that it could be triggered by a scheduled task as the error is reoccuring every 8 hours.
regarding being a proxy server.. I have checked in AD and group policies ,, there is no refrence.
great advise for turning network monitor on .. I will do that tonight and I will let you know the result tomorrow.
I used to get a lot of these, mostly for desktops, but some servers. I found, once I removed them from DNS, all of these errors went away.
I'm sorry that I exhume this discussion but my comparison isn't identical, how can I solve this?
remove the old servers if showing up from the server manager console in server 2012
I'm having the same problem with two entries. I've searched through AD Users and Computers, ADSI, DNS and can't find any instances of the systems.
Any luck with resolving that problem. Unfortunately I have same problem
I have the same issue too. an old server that was decomissioned a while ago. Looked at DNS, AD cannot find it anywhere. I have AD 2003 but server 2012. Did not even dare raising the functional level yet.
what is wierd is when I ran : certutil the same server pops up.
any luck guys?
I too am seeing this issue, but spiceworks-finder.exe is causing the error:
DCOM was unable to communicate with the computer 10.0.3.177 using any of the configured protocols; requested by PID 40 (C:\Program Files (x86)\Spiceworks\bin\spiceworks-finder.exe).
I looked at my DNS entries and the .177 belongs to a machine connected via our wireless interface. This machine does leave the building and reconnects when it returns. I have scavenging set up to clean out stale DNS records on a 5 day interval.
I found that I had set up server manager to monitor a server I had later disposed of.
This appears to have been the cause here, although I am sure not for everyone.
I looked at my DNS entries and the .177 belongs to a machine connected via our wireless interface. This machine does leave the building and reconnects when it returns. I have scavenging set up to clean out stale DNS records on a 5 day interval.
Rather than that - why not just wind down the DHCP lease time to your IP addresses?
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
扫一扫
