Re: I've never seen these errors before! please help

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Vassilis Contogeorgos (vcon_at_hate_spam_hol.gr)
Date: 04/27/04 

Date: Tue, 27 Apr 2004 15:43:26 +0300

i run netdiag on the server and all tests are passed. No error no failed.
The dcdiag gives an error
"the procedure entry point dsismangleddnw could not be located in the
dynamic link library NTDSAPI.dll"

"Amy-Leigh Mack[MSFT]" <amyma@online.microsoft.com> wrote in message
news:#LzeOqELEHA.3472@TK2MSFTNGP09.phx.gbl...
> I don't know that the problem is DNS. Without DCDiag and Netdiage as I
have
> outlined then I have nothing to work from. I cannot tell you what changed
> in your environment since at this point in time I only have the
application
> log events to work from. If you have further questions you may want to
try
> calling Microsoft support for further assistance.
>
>
> amyma@online.microsoft.com
> Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Vassilis Contogeorgos" <vcon@hate_spam_hol.gr> wrote in message
> news:uQeMTVCLEHA.556@tk2msftngp13.phx.gbl...
> > ok, i agree with what you're saying, but:
> > I'm using internal DNS in my tcp/ip and not external.
> > The machine is working almost flawless for two years now
> > Why the errors now and not before. I mean if it's a name resolution or
> > something with wrong DNS why the error now ? What triggered the events ?
> >
> > thank you
> >
> >
> > "Amy-Leigh Mack[MSFT]" <amyma@online.microsoft.com> wrote in message
> > news:OEdpbN8KEHA.2236@TK2MSFTNGP09.phx.gbl...
> > > Netdiag and dcdiag will give you information regarding the health of
> > network
> > > at tcp/ip level and dcdiag will indicate if there are any problems
such
> as
> > > replication on the domain controllers. It is impossible to tell based
on
> > the
> > > information you provided specifically why msexchangedsaccess cannot
> speak
> > to
> > > your domain controllers.
> > >
> > > I have seen outside DNS servers as preferred dns servers in tcp/ip,
> while
> > > ping will work exchange uses DNS and outside DNS servers generally do
> not
> > > have internal domain server records or access to them. This is a case
> > where
> > > netdiag would give you the information.
> > >
> > > If you need more assistance you may want to consider calling Microsoft
> > > Product Support for further troubleshooting.
> > >
> > > amyma@online.microsoft.com
> > > Please do not send email directly to this alias. This alias is for
> > > newsgroup purposes only.
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > "Vassilis Contogeorgos" <vcon@hate_spam_hol.gr> wrote in message
> > > news:uLUAlm6KEHA.268@TK2MSFTNGP11.phx.gbl...
> > > > Yes but why?
> > > > while this was happening, i could ping everything on the servers and
> > > > including the domain. The exchange server is on the domain contoller
> and
> > > > global catalog was working fine.
> > > >
> > > > "Amy-Leigh Mack[MSFT]" <amyma@online.microsoft.com> wrote in message
> > > > news:uCYWIZ6KEHA.240@TK2MSFTNGP10.phx.gbl...
> > > > > I would not worry about the MSExchangeAL errors. I would think
they
> > are
> > > > > mearly a result of the fact this Exchange server cannot currenlty
> talk
> > > to
> > > > > any DC/GC. You may want to start with running netdiag from the
> > Windows
> > > > > support tools. Also running dcdiag on the domain controllers also
a
> > > part
> > > > of
> > > > > the windows support tools. These 2 things may give you some more
> > > tangible
> > > > > things to look at.
> > > > >
> > > > >
> > > > > amyma@online.microsoft.com
> > > > > Please do not send email directly to this alias. This alias is
for
> > > > > newsgroup purposes only.
> > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > > "Vassilis Contogeorgos" <vcon@hate_spam_hol.gr> wrote in message
> > > > > news:e4K$dL6KEHA.912@tk2msftngp13.phx.gbl...
> > > > > > Hi, ex2k SP3 , w2k server sp4 domain controller.
> > > > > > The machine was working great. Suddenly no outlook and at the
> server
> > > we
> > > > > get
> > > > > > the following messages
> > > > > > ==================
> > > > > > Event Type: Error
> > > > > > Event Source: MSExchangeDSAccess
> > > > > > Event Category: Topology
> > > > > > Event ID: 2102
> > > > > > Date: 26/4/2004
> > > > > > Time: 16:35:29
> > > > > > User: N/A
> > > > > > Computer: NAME
> > > > > > Description:
> > > > > > Process MAD.EXE (PID=2800). All Domain Controller Servers in use
> are
> > > not
> > > > > > responding:
> > > > > > server.domain.net
> > > > > > server2.domain.net
> > > > > >
> > > > > >
> > > > > > For more information, click
> > > > http://www.microsoft.com/contentredirect.asp.
> > > > > > ----------
> > > > > >
> > > > > > Event Type: Error
> > > > > > Event Source: MSExchangeAL
> > > > > > Event Category: LDAP Operations
> > > > > > Event ID: 8270
> > > > > > Date: 26/4/2004
> > > > > > Time: 16:35:33
> > > > > > User: N/A
> > > > > > Computer: Name
> > > > > > Description:
> > > > > > LDAP returned the error [32] Insufficient Rights when importing
> the
> > > > > > transaction
> > > > > > dn: CN=Recipient Update Service (Enterprise
> > > > > >
> > > > > > Configuration),CN=Recipient Update Services,CN=Address Lists
> > > > > > Container,CN=Name,CN=Microsoft
> > > > > >
> > > > > > Exchange,CN=Services,CN=Configuration,DC=name,DC=name
> > > > > > changetype: Modify
> > > > > > msExchServer1LastUpdateTime:20040426133533.0Z
> > > > > > msExchServer1HighestUSN:836585
> > > > > > msExchServer1HighestUSNVector:SERVER1:836585
> > > > > > : SERVER2:763574
> > > > > > -
> > > > > >
> > > > > >
> > > > > > For more information, click
> > > > http://www.microsoft.com/contentredirect.asp.
> > > > > > ---------
> > > > > > Event Type: Error
> > > > > > Event Source: MSExchangeAL
> > > > > > Event Category: LDAP Operations
> > > > > > Event ID: 8270
> > > > > > Date: 26/4/2004
> > > > > > Time: 16:35:33
> > > > > > User: N/A
> > > > > > Computer: NAME
> > > > > > Description:
> > > > > > LDAP returned the error [32] Insufficient Rights when importing
> the
> > > > > > transaction
> > > > > > dn: CN=Recipient Update Service (DOMAIN),CN=Recipient Update
> > > > > >
> > > > > > Services,CN=Address Lists Container,CN=Name,CN=Microsoft
> > > > > > Exchange,CN=Services,CN=Configuration,DC=name,DC=name
> > > > > > changetype: Modify
> > > > > > msExchServer1LastUpdateTime:20040426133533.0Z
> > > > > > msExchServer1HighestUSN:836585
> > > > > > msExchServer1HighestUSNVector:SERVER1:836585
> > > > > > : SERVER2:763581
> > > > > > -
> > > > > >
> > > > > >
> > > > > > For more information, click
> > > > http://www.microsoft.com/contentredirect.asp.
> > > > > > ------------
> > > > > > Event Type: Error
> > > > > > Event Source: MSExchangeAL
> > > > > > Event Category: LDAP Operations
> > > > > > Event ID: 8270
> > > > > > Date: 26/4/2004
> > > > > > Time: 16:35:33
> > > > > > User: N/A
> > > > > > Computer: NAME
> > > > > > Description:
> > > > > > LDAP returned the error [32] Insufficient Rights when importing
> the
> > > > > > transaction
> > > > > > dn: CN=Recipient Update Service (NAME),CN=Recipient Update
> > > > > >
> > > > > > Services,CN=Address Lists Container,CN=Domain,CN=Microsoft
> > > > > > Exchange,CN=Services,CN=Configuration,DC=NAME,DC=net
> > > > > > changetype: Modify
> > > > > > msExchServer1LastUpdateTime:20040426133533.0Z
> > > > > > msExchServer1HighestUSN:836585
> > > > > > msExchServer1HighestUSNVector:SERVER1:836585
> > > > > > : SERVER2:763581
> > > > > > -
> > > > > >
> > > > > >
> > > > > > For more information, click
> > > > http://www.microsoft.com/contentredirect.asp.
> > > > > > -------------
> > > > > > Event Type: Error
> > > > > > Event Source: MSExchangeDSAccess
> > > > > > Event Category: Topology
> > > > > > Event ID: 2103
> > > > > > Date: 26/4/2004
> > > > > > Time: 16:36:30
> > > > > > User: N/A
> > > > > > Computer: NAME
> > > > > > Description:
> > > > > > Process MAD.EXE (PID=2800). All Global Catalog Servers in use
are
> > not
> > > > > > responding:
> > > > > > server1.domain.net
> > > > > >
> > > > > >
> > > > > > For more information, click
> > > > http://www.microsoft.com/contentredirect.asp.
> > > > > > -----------------
> > > > > > Event Type: Error
> > > > > > Event Source: Userenv
> > > > > > Event Category: None
> > > > > > Event ID: 1000
> > > > > > Date: 26/4/2004
> > > > > > Time: 16:39:20
> > > > > > User: NT AUTHORITY\SYSTEM
> > > > > > Computer: NAME
> > > > > > Description:
> > > > > > Windows cannot query for the list of Group Policy objects . A
> > message
> > > > that
> > > > > > describes the reason for this was previously logged by this
policy
> > > > > >
> > > > > > engine.
> > > > > > -----------------
> > > > > > Event Type: Error
> > > > > > Event Source: MSExchangeSA
> > > > > > Event Category: General
> > > > > > Event ID: 9154
> > > > > > Date: 26/4/2004
> > > > > > Time: 16:41:30
> > > > > > User: N/A
> > > > > > Computer: NAME
> > > > > > Description:
> > > > > > DSACCESS returned an error '0x80004005' on DS notification.
> > Microsoft
> > > > > > Exchange System Attendant will re-set DS notification later.
> > > > > >
> > > > > > For more information, click
> > > > http://www.microsoft.com/contentredirect.asp.
> > > > > > --------------
> > > > > > Event Type: Error
> > > > > > Event Source: MSExchangeDSAccess
> > > > > > Event Category: Topology
> > > > > > Event ID: 2102
> > > > > > Date: 26/4/2004
> > > > > > Time: 16:41:30
> > > > > > User: N/A
> > > > > > Computer: NAME
> > > > > > Description:
> > > > > > Process MAD.EXE (PID=2800). All Domain Controller Servers in use
> are
> > > not
> > > > > > responding:
> > > > > > server1.domain.net
> > > > > > server2.domain.net
> > > > > >
> > > > > >
> > > > > > For more information, click
> > > > http://www.microsoft.com/contentredirect.asp.
> > > > > > ------------------
> > > > > >
> > > > > > We didn't change anything on the domain or the server. I have
> never
> > > seen
> > > > > > this errors before. The machine didn't have the latest two
patches
> > > > > > (835732,828741) and we had the SSL port open for OWA. Does this
> has
> > > > > anything
> > > > > > to do with the announcement from Microsoft about a script that
is
> > > around
> > > > ?
> > > > > > if not what is the problem ?. I install the patches rebooted and
> > > > > everything
> > > > > > come up fine.
> > > > > > I don't want this to happened again so I'm desperate for
> advices...
> > > > > >
> > > > > > thank you
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Cant find DC after running DCPROMO
    ... I have a windows 2000 server with two NIC's. ... Netdiag and dcdiag disagree. ... List of NetBt transports currently configured: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Login issues for Active Directory Users. Unsure of root cause
    ... Run dcdiag, netdiag and repadmin in verbose mode. ... the PCs or Server. ... Directory/Shared folders for the roaming profiles permissions nixed? ...
    (microsoft.public.windows.server.active_directory)
  • Re: Windows cannot obtain the domain controller name for your computer
    ... If you don't have the support tools installed, install them from your server ... Run dcdiag, netdiag and repadmin in verbose mode. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Old DC with problem
    ... If you don't have the tools installed, install them from your server ... Run dcdiag and netdiag in verbose mode. ... If I change connection in AD User & Computers to new Domain Controller, ...
    (microsoft.public.win2000.active_directory)
  • Re: FSMO
    ... If you don't have the support tools installed, install them from your server install disk. ... Run dcdiag, netdiag and repadmin in verbose mode. ... If you download a gui script I wrote it should be simple to set and run (DCDiag and NetDiag). ...
    (microsoft.public.windows.server.active_directory)