Prev: an error occurred while configuring a component
Next: 4125 RWW Not working Properly
From: Ace Fekay [MVP-DS, MCT] on 12 Mar 2010 01:14
""Robbin Meng [MSFT]"" <v-robmen(a)online.microsoft.com> wrote in message news:TU63LaZwKHA.2536(a)TK2MSFTNGHUB02.phx.gbl...
>
> Hi yaro,
>
> Thanks for your post and Ace's input.
>
> The error that you mentioned in the "Symptoms" section is frequently a network communications error. The following are possible causes of this error:
> o Name resolution errors are occurring.
> o All TCP ports on the server are being used.
> o TCP port collisions are occurring.
>
> To troubleshoot DCOM 10009 errors, use the following methods.
>
> Method 1: Verify that name resolution is working correctly
> The activation page for a COM+ proxy application contains a Remote Server Name (RSN) property. The RSN property can be an IP address, a Fully Qualified Domain
> Name (FQDN), or a NetBIOS name. To troubleshoot this issue, use the ping command to test connectivity to the remote server by using the IP address, the FQDN, and the
> NetBIOS name.
>
> Method 2: Verify TCP port usage
> When a client makes DCOM calls to a COM+ server application, each connection may use a different TCP port. Therefore, all TCP ports on the server may be used. When
> this condition occurs, the server cannot accept additional connections.
>
> For more information about how to determine TCP port usage when you troubleshoot TCP/IP connectivity issues, click the following article numbers to view the articles in the
> Microsoft Knowledge Base:
> KB832919 New features and functionality in PortQry version 2.0
> KB301512 Many TCP connections are established for COM+ proxy/stub
>
> Method 3: Verify basic network connectivity to troubleshoot TCP collision issues
> For more information about how use basic network troubleshooting to resolve TCP collision errors, click the following article number to view the article in the Knowledge
> Base:
> KB325487 How to troubleshoot network connectivity problems
>
> More information about Event 10009 in SBS 2008 server:
>
> "Windows SBS 2008 Known Post Installation Event Errors"
> http://support.microsoft.com/kb/957713
>
> Hope this helps.
>
>
>
> Best regards,
> Robbin Meng(MSFT)
> Microsoft Online Newsgroup Support
>
> ==================================================================
> Please post your SBS 2008 related questions to the SBS newsgroup on Connect website:
> https://connect.microsoft.com/sbs08/community/discussion/richui/default.aspx
>
> Please post your EBS related questions to the EBS newsgroup on Connect website:
> https://connect.microsoft.com/ebs08/community/discussion/richui/default.aspx
>
> If you want to use a newsreader other than a web forum to access these newsgroups,
> please refer to the following blog to apply NNTP password and configure a newsreader:
> http://msmvps.com/blogs/bradley/archive/2008/11/02/signing-up-for-the-sbs-2008-newsgroups.aspx
> ==================================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ==================================================================
>
>
>


Thanks for posting that info, Robbin. I don't think I was aware of specifics in the past to address this error.

Thanks again,

Ace
First  |  Prev  | 
Pages: 1 2
Prev: an error occurred while configuring a component
Next: 4125 RWW Not working Properly