[ExchangeList] Re: DSAccess Topology Discovery Fails.

  • From: James Chong <jchong@xxxxxxxxxxxxxx>
  • To: "exchangelist@xxxxxxxxxxxxx" <exchangelist@xxxxxxxxxxxxx>
  • Date: Tue, 5 Feb 2008 16:30:32 -0500

BTW: Have you tried disabling Chimney offload and receive side scaling? This can cause the pool memory issue that you’re seeing as well.

 

KB936594

 

 

James

 

From: exchangelist-bounce@xxxxxxxxxxxxx [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Mahadevan Subramanian
Sent: Thursday, January 31, 2008 9:47 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: DSAccess Topology Discovery Fails.

 

Hello All,

 

Thanks for your responses and suggestions. But I could not find any Memory or DNS issues. We have taken this issue with Microsoft and now even they are pulling their hairs to get it solved. Till now even they could not find any issues or root cause. Even they had the same suspisions which we all had.. (like kernel mem issue or DNS issue).

 

Till now we have given all the reports to them and will let you know surely the cause of this issue if identified and solved.... :-)

 

Regards... Maha

On Jan 30, 2008 11:11 AM, Sudeep Raikar <raikar.sudeep@xxxxxxxxx> wrote:

http://www.msexchange.org
-------------------------------------------------------Try Closing Down the DNS Client Service after the Re-Boot.
This is the service tha mostly causes the problems most of the time.
The only possible reason that I can think of is because there is a
problem with the DNS resulution.
when you have the problem please try to connect to ROOTDSE Using Adsiedit.
Then try the solution above...

Let us know if this works....



On 1/3/08, James Chong <jchong@xxxxxxxxxxxxxx> wrote:
>
>
> Anything in your event viewer? Usually you should get some pool memory
> exhausted events.
>
>
>  James Chong
>  Sr. Systems Engineer
>  InPhonic, Inc.
>  11130 Sunrise Valley Dr.
>  Reston, VA 20191
>  O (703) 657-4612
>  C (703) 863-1483
>
>
> From: exchangelist-bounce@xxxxxxxxxxxxx
> [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Mahadevan
> Subramanian
>  Sent: Thursday, January 03, 2008 11:23 AM
>  To: exchangelist@xxxxxxxxxxxxx
>  Subject: [ExchangeList] Re: DSAccess Topology Discovery Fails.
>
>
>
>
> Yes Michael,
>
>
>
> Thanks for your quick response.
>
>
>
> Even i suspected the same and ran poolmon during the time when the problem
> persists.
>
> But Paged and Non-Paged values are normal during that time.... ;-(
>
>
>
> Regards...
>
> Mahadevan
>
>
>
> On 1/3/08, Michael B. Smith <michael@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
>
> Sounds more and more like a non-paged-pool memory leak.
>
>  Regards,
>
>  Michael B. Smith
>  MCSE/Exchange MVP
>  http://TheEssentialExchange.com
>
>
> From: exchangelist-bounce@xxxxxxxxxxxxx
> [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Mahadevan
> Subramanian
>  Sent: Thursday, January 03, 2008 11:05 AM
>
>
>  To: exchangelist@xxxxxxxxxxxxx
>  Subject: [ExchangeList] Re: DSAccess Topology Discovery Fails.
>
>
>
>
>
> Hello James,
>
>
>
> Yeah i checked the 2080 events... As the normal topology discovery happens
> every 15 min, this 2080 event should also be listed every 15 min. But once
> the problem is started this event does not occur since the DS bind itself
> fails with all DCs. Instead the several list of events which i have
> mentioned in my previous mail gets populated. But the last topology
> discovery before the problem starts (ie: before 15 min) will be succesfull
> and we will get a 2080 event with normal values for CDG.
>
>
>
> Regards...
>
> Mahadevan
>
>
>
> On 1/3/08, James Chong <jchong@xxxxxxxxxxxxxx> wrote:
>
>
> I have seen problems with discovery failures due to SACL issues; but this
> would be an all or nothing deal ie. It would work or wouldn't. Your issue is
> strange since it works on an off. Is there an event id 2080. If so; can you
> see what values you get for reachability and SACL and post?
>
>  Event Type: Information Event Source: MSExchangeDSAccess Event Category:
> Topology Event ID: 2080
>
>  Event ID 2080 from MSExchangeDSAccess
>  http://support.microsoft.com/kb/316300
>
>  James Chong
>  Sr. Systems Engineer
>  InPhonic, Inc.
>  11130 Sunrise Valley Dr.
>  Reston, VA 20191
>  O (703) 657-4612
>  C (703) 863-1483
>
>
> From: exchangelist-bounce@xxxxxxxxxxxxx
> [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Mahadevan
> Subramanian
>  Sent: Thursday, January 03, 2008 9:48 AM
>  To: exchangelist@xxxxxxxxxxxxx
>  Subject: [ExchangeList] Re: DSAccess Topology Discovery Fails.
>
>
>
> Hello Michael,
>
>
>
> The access to the port is not actually gone. We are able to telnet the DS
> servers in 389 port from the affected Exchange Server during the problem.
> But rest of the tools like DCdiag, Netdiag.... etc is not running during the
> time when the problem persists. Only thing is the Topology Discovery fails
> to bind with any of the DS serevrs. We have got multiple DCs which are
> detected in-site, once this problem happens it is trying to get the Topology
> information using some boot strap server and DS bind fails with all DCs and
> hence going to Out-Site DC and even that is getting failed.
>
>
>
> This does not look like a AD issue as other Exchange Servers in the site are
> also using the same DCs in the DSAccess Auto Discovery mode.
>
>
>
> Any suggestions for throwing light in this dark issue is appreciated... :-)
>
>
>
> Regards...
>
> Mahadevan
>
>
>
> On 1/2/08, Michael B. Smith <michael@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
>
> Can you "telnet <ds-server> 389" ?? That is, is access to the port actually
> gone?
>
>  If so, this isn't an Exchange issue per se – the Exchange problem is just a
> symptom of a larger problem.
>
>  Regards,
>
>  Michael B. Smith
>  MCSE/Exchange MVP
>  http://TheEssentialExchange.com
>
>
> From: exchangelist-bounce@xxxxxxxxxxxxx
> [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Mahadevan
> Subramanian
>  Sent: Wednesday, January 02, 2008 11:00 AM
>  To: exchangelist@xxxxxxxxxxxxx
>  Subject: [ExchangeList] DSAccess Topology Discovery Fails.
>
>
>
>
>
> Hello All,
>
>
>
> Windows 2003 AD With Native Mode
>
> Exchange 2003 SP2 with Native Mode
>
>
>
> We have vague issue in DSAccess Topology discovry only in one particular
> Front End Exchange server which we use it as Mobility Server.Every week the
> topology discovery will fail with 2110, 2115, 2114, 2095, 2102,
> 2103...... events. The main error is " Process MAD.EXE (PID=1908). Could not
> bind to DS server XXXXXXXX Error 5a in Port 389". There is no use in running
> any tests like netdiag, nltest, policy test during this time because it is
> not able to communicate with port 389. The only temporary slution which we
> have is Reboot the Exchange server after which it will work fine for another
> week.
>
>
>
> Did the following things..
>
>
>
> Increased Diagnostic Logging for DSAccess and hence got the above mentioned
> events...
>
> Ran ExBPA and found nothing fishy, except 3GB switch enabled in the Front
> End Server which is not there in any other FE servers.
>
> Memory usage is normal.
>
>
>
> We are planning to take this up with Microsoft but before that just thought
> of getting any of your suggestions if any one has faced this issue.
>
>  --
>  Regards... Mahadevan
>
>
>
>
>
>  --
>  Regards... Maha
>
>
>
>  --
>  Regards... Maha
>
>
>
>  --
>  Regards... Maha
>

-------------------------------------------------------
List Archives: http://www.freelists.org/archives/exchangelist/
MSExchange Newsletter: http://www.msexchange.org/pages/newsletter.asp
MSExchange Articles and Tutorials: http://www.msexchange.org/articles_tutorials/
MSExchange Blogs: http://blogs.msexchange.org/
-------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com
-------------------------------------------------------
To unsubscribe visit http://www.msexchange.org/pages/exchangelist.asp
Report abuse to listadmin@xxxxxxxxxxxxxx




--
Regards... Maha

Other related posts: