Quantcast
Channel: SBS 2011 with DCOM 10009 citing source server after recent updates
Viewing all 68 articles
Browse latest View live
↧

SBS 2011 with DCOM 10009 citing source server after recent updates

January 7, 2013, 11:53 pm
$
0
0

There are several articles and posts on this topic, you can take a look:

How to troubleshoot DCOM 10009 error logged in system event?

http://blogs.msdn.com/b/asiatech/archive/2010/03/16/how-to-troubleshoot-dcom-10009-error-logged-in-system-event.aspx

DCOM 10009 SBS2003 

http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/f75abdaf-9944-438e-bfd8-8acd76a49a36/

DCOM Event ID 10009:

http://support.microsoft.com/kb/957713

Sean Zhu

TechNet Subscriber Support

If you are TechNet Subscription user and have any feedback on our support quality, please send your feedbackhere.

Sean Zhu

TechNet Community Support

Sean

I can confirm what others here are saying (RE: DistributedCOM 10009 Error)

Point 1. No fragments in the AD for the old sbs 2003 server (so the suggestions you have posted are of no help)

Point 2. this is indeed related to BPA. (but its not new) to me at least (I have had the errors since mgrating sbs2003 to sbs 2008R2 6 months ago)

Point 3, the errors occur approx 2.00am to 2.10am in the morning

Point 4 they are related to BPA as running manually "DOES" recreate the errors.

So we have some precise repeateable info here.

How are you guys going on a solution.

Regards Peter

Frustrated IT Man.

↧
Search

SBS 2011 with DCOM 10009 citing source server after recent updates

December 27, 2012, 3:36 pm
$
0
0

Hody1, please let us know how it goes.

Sadly, my previous server was named 'Server' which is quite generic.  A search for 'server.domain.local' turned up nothing so I did a search for 'server' and it returned:

Using Navigation Nodes -> domain (local):
Server Management - Group
Server Operators - Group
Server - samServer

Using Global Catalog Search - domain.local:
Server Management - Group
Server Operators - Group
Server - classSchema (undeletable)
Server - samServer
Many more entries that contain 'server' plus other letters/words

Is it possible that the 'samServer' entry is the one I want to delete?  I don't know why but delete is not an option for the 'classChema' entry.  I don't want to delete something that I shouldn't.  Could someone else do a search for 'server' and see if this 'samServer' entry appears?

Thanks.

↧
↧

SBS 2011 with DCOM 10009 citing source server after recent updates

December 27, 2012, 7:24 am
$
0
0
I have the same problem and just did a Global Search for the old server using the Active Directory Administrative Center using both the Global Catalog Search and Navigation Nodes under the scope.  I was actually able to find more instances of my old server to delete that I hadn't been able to fine previously.  I haven't gotten my daily report yet to see if this fixed the error, but hope this helps.
↧

SBS 2011 with DCOM 10009 citing source server after recent updates

December 21, 2012, 7:20 am
$
0
0

I have a similar problem and errors on a freshly built, fully patched SBS2011 system.  This system was built from scratch as a new installation and was not migrated. 

At 2:06 am I see these errors - they are all sourced from Instrumentation and are Event ID 3

Cmdlet Invoke-MbcaModel reported warning Exception calling "TryLoadExchangeTypes" with "2" argument(s): "Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information."

Cmdlet Invoke-MbcaModel reported warning Cannot invoke this function because the current host does not implement it.

Cmdlet Invoke-MbcaModel reported warning The term 'get-spsearchservice' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Cmdlet Invoke-MbcaModel reported warning Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information.

Cmdlet Invoke-MbcaModel reported warning The term 'get-wbsummary' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Cmdlet Invoke-MbcaModel reported warning Microsoft SharePoint is not supported with version 4.0.30319.296 of the Microsoft .Net Runtime.

Cmdlet Invoke-MbcaModel reported warning Cannot find path 'C:\Windows\debug\dcpromo.log' because it does not exist.

Cmdlet Invoke-MbcaModel reported warning Method invocation failed because [System.String] doesn't contain a method named 'ToMb'.

Cmdlet Invoke-MbcaModel reported warning You cannot call a method on a null-valued expression.

↧

SBS 2011 with DCOM 10009 citing source server after recent updates

November 29, 2012, 3:48 pm
$
0
0
Ah, that makes sense.  So the latest BPA update must have done it.  But that doesn't answer the question of why BPA is looking at a removed/decomissioned server.  Where is this information?  Since nobody here has found any reference to it in the usual places, could it be in some sort of BPA cache?
↧
↧

SBS 2011 with DCOM 10009 citing source server after recent updates

November 29, 2012, 8:58 am
$
0
0

My situation precisely. I've lost count of the number of hours I've spent searching group policies, the registry, certificate authority, DNS, AD, etc.

If I run BPA manually, they (the two DCOM 10009 errors referencing the old SBS 2003 machine) show up.

And every night at 2:05 and some seconds, there they are again.

↧

SBS 2011 with DCOM 10009 citing source server after recent updates

October 22, 2012, 4:31 pm
$
0
0

Hi all,

Thank you for your replies and suggestions.  I am still experiencing this problem but since the only negative issue, to my knowledge, is the error reported in the daily report emails, I have but it on the back burner for now.  I will get back to it eventually, but in the meantime please post any solutions should they be found.

Have a great day!

↧

SBS 2011 with DCOM 10009 citing source server after recent updates

October 22, 2012, 11:02 am
$
0
0
Same issue here. It have narrowed it down to having to do with the SBS Best Practices Analyzer. I installed the rollup 3 for the BPA recently and that is when they started. If you manually invoke the SBS BPA you will see the entries appear in the logs. I have searched AD and the registry and there is no trace of the original source server but at 2:06 AM every night and whenever I invoke the BPA manually I get the DCOM and Instrumentation errors. Possibly someone with better scripting skills than mine could look at the BPA rule set and see what is happening.
↧
Search

SBS 2011 with DCOM 10009 citing source server after recent updates

August 3, 2012, 3:19 pm
$
0
0

I have seen this once. The old source server started to appear in DCOM event log errors, even if was decommissioned properly several months ago and all cleanup was done.

It finally appeared that the SBS Monitoring had got messed up somehow. As a side effect, the SBS console crashed every time when trying to go to the monitoring page.

In my case the resolution was to recreate the database with these instructions: http://blogs.technet.com/b/sbs/archive/2011/08/22/how-to-recreate-the-sbsmonitoring-database.aspx

But for more information, please check first http://technet.microsoft.com/en-us/library/gg680308.aspx

↧
↧

SBS 2011 with DCOM 10009 citing source server after recent updates

August 3, 2012, 5:51 am
$
0
0
Check dssite.msc,do you see source server listed in there?
↧

SBS 2011 with DCOM 10009 citing source server after recent updates

August 3, 2012, 2:57 am
↧

SBS 2011 with DCOM 10009 citing source server after recent updates

August 1, 2012, 6:06 pm
$
0
0

Thank you for your reply Sean but this doesn't solve my problem...at least directly.  I have already come across those articles you've posted but none appear to apply. 

These errors didn't begin showing up until 7/12.  I had already successfully demoted my previous sbs2003 box and this sbs2011 box had been running for months w/o this error.  The sbs2003 box hasn't been turned on since then.  I do not understand how this came out of nowhere or how to find the reference to SOURCE.domain.local so that I can remove it.

This started after installing a bunch of updates on 7/11.  They occur around 2:07am every night.  These DCOM errors are followed by a bunch of Event ID 3 Instrumentation warnings which are mostly repeats but contain 3-6 different warning descriptions, each one of them mentioning Cmdlet Invoke-MbcaModel.  I assume these warnings are all due to the DCOM error and the fact that this machine is no longer online.

If there is something in Active Directory that shouldn't be there, how can I find it before trying to blindly remove it?  I tried using the 'Search Active Directory' tool but could not locate it.

Or could this reference be coming from somewhere else?  Again, a ping and nslookup cannot resolve the IP of SOURCE.domain.local so I don't think anything is in DNS.

Please help me determine why this is happening.  I believe the resolution will be simple after that.

Thank you.

↧

SBS 2011 with DCOM 10009 citing source server after recent updates

July 25, 2012, 8:15 pm
$
0
0

There are several articles and posts on this topic, you can take a look:

How to troubleshoot DCOM 10009 error logged in system event?

http://blogs.msdn.com/b/asiatech/archive/2010/03/16/how-to-troubleshoot-dcom-10009-error-logged-in-system-event.aspx

DCOM 10009 SBS2003 

http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/f75abdaf-9944-438e-bfd8-8acd76a49a36/

DCOM Event ID 10009:

http://support.microsoft.com/kb/957713

Sean Zhu

TechNet Subscriber Support

If you are TechNet Subscription user and have any feedback on our support quality, please send your feedbackhere.

Sean Zhu

TechNet Community Support

↧
↧

SBS 2011 with DCOM 10009 citing source server after recent updates

July 25, 2012, 5:15 pm
$
0
0
Nobody?  Can I provide any additional information?
↧

SBS 2011 with DCOM 10009 citing source server after recent updates

July 23, 2012, 7:13 pm
$
0
0

Hello,

After installing some updates a few weeks ago I started noticing DCOM 10009 errors that read:

DCOM was unable to communicate with the computer SOURCE.domain.local using any of the configured protocols.

SOURCE is the server I migrated from.  It was an SBS 2003 box.  I cannot locate this server name in DNS or AD.  A ping to SOURCE.domain.local results in "...could not find host..." 

Does anyone have any idea why SBS 2011 is trying to contact the source server?  And why did this just happen after recent updates?

Any tips in locating and/or removing whatever entry is causing this would be much appreciated.

Thank you!

↧
Search

SBS 2011 with DCOM 10009 citing source server after recent updates

January 7, 2013, 11:53 pm
$
0
0

There are several articles and posts on this topic, you can take a look:

How to troubleshoot DCOM 10009 error logged in system event?

http://blogs.msdn.com/b/asiatech/archive/2010/03/16/how-to-troubleshoot-dcom-10009-error-logged-in-system-event.aspx

DCOM 10009 SBS2003 

http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/f75abdaf-9944-438e-bfd8-8acd76a49a36/

DCOM Event ID 10009:

http://support.microsoft.com/kb/957713

Sean Zhu

TechNet Subscriber Support

If you are TechNet Subscription user and have any feedback on our support quality, please send your feedbackhere.

Sean Zhu

TechNet Community Support

Sean

I can confirm what others here are saying (RE: DistributedCOM 10009 Error)

Point 1. No fragments in the AD for the old sbs 2003 server (so the suggestions you have posted are of no help)

Point 2. this is indeed related to BPA. (but its not new) to me at least (I have had the errors since mgrating sbs2003 to sbs 2008R2 6 months ago)

Point 3, the errors occur approx 2.00am to 2.10am in the morning

Point 4 they are related to BPA as running manually "DOES" recreate the errors.

So we have some precise repeateable info here.

How are you guys going on a solution.

Regards Peter

Frustrated IT Man.

↧

SBS 2011 with DCOM 10009 citing source server after recent updates

December 27, 2012, 3:36 pm
$
0
0

Hody1, please let us know how it goes.

Sadly, my previous server was named 'Server' which is quite generic.  A search for 'server.domain.local' turned up nothing so I did a search for 'server' and it returned:

Using Navigation Nodes -> domain (local):
Server Management - Group
Server Operators - Group
Server - samServer

Using Global Catalog Search - domain.local:
Server Management - Group
Server Operators - Group
Server - classSchema (undeletable)
Server - samServer
Many more entries that contain 'server' plus other letters/words

Is it possible that the 'samServer' entry is the one I want to delete?  I don't know why but delete is not an option for the 'classChema' entry.  I don't want to delete something that I shouldn't.  Could someone else do a search for 'server' and see if this 'samServer' entry appears?

Thanks.

↧
↧

SBS 2011 with DCOM 10009 citing source server after recent updates

December 27, 2012, 7:24 am
$
0
0
I have the same problem and just did a Global Search for the old server using the Active Directory Administrative Center using both the Global Catalog Search and Navigation Nodes under the scope.  I was actually able to find more instances of my old server to delete that I hadn't been able to fine previously.  I haven't gotten my daily report yet to see if this fixed the error, but hope this helps.
↧

SBS 2011 with DCOM 10009 citing source server after recent updates

December 21, 2012, 7:20 am
$
0
0

I have a similar problem and errors on a freshly built, fully patched SBS2011 system.  This system was built from scratch as a new installation and was not migrated. 

At 2:06 am I see these errors - they are all sourced from Instrumentation and are Event ID 3

Cmdlet Invoke-MbcaModel reported warning Exception calling "TryLoadExchangeTypes" with "2" argument(s): "Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information."

Cmdlet Invoke-MbcaModel reported warning Cannot invoke this function because the current host does not implement it.

Cmdlet Invoke-MbcaModel reported warning The term 'get-spsearchservice' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Cmdlet Invoke-MbcaModel reported warning Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information.

Cmdlet Invoke-MbcaModel reported warning The term 'get-wbsummary' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Cmdlet Invoke-MbcaModel reported warning Microsoft SharePoint is not supported with version 4.0.30319.296 of the Microsoft .Net Runtime.

Cmdlet Invoke-MbcaModel reported warning Cannot find path 'C:\Windows\debug\dcpromo.log' because it does not exist.

Cmdlet Invoke-MbcaModel reported warning Method invocation failed because [System.String] doesn't contain a method named 'ToMb'.

Cmdlet Invoke-MbcaModel reported warning You cannot call a method on a null-valued expression.

↧

SBS 2011 with DCOM 10009 citing source server after recent updates

November 29, 2012, 3:48 pm
$
0
0
Ah, that makes sense.  So the latest BPA update must have done it.  But that doesn't answer the question of why BPA is looking at a removed/decomissioned server.  Where is this information?  Since nobody here has found any reference to it in the usual places, could it be in some sort of BPA cache?
↧
Viewing all 68 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>