RE: Event log errors

  • From: "Dolly Bareqet" <Dolly.Bareqet@xxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Mon, 9 May 2005 18:08:16 +0200

 

8250 -
http://216.64.118.243/evtbkstart.asp?EventID=8250&Name=Demo&Email=Demo&k
ey=N1251D9-U10-4269-RLFEF-JJFG-16&MsgSearchByEvent=true

 

9153 -
http://216.64.118.243/evtbkstart.asp?EventID=9153&Name=Demo&Email=Demo&k
ey=N1251D9-U10-4269-RLFEF-JJFG-16&MsgSearchByEvent=true

 

9154 -
http://216.64.118.243/evtbkstart.asp?EventID=9154&Name=Demo&Email=Demo&k
ey=N1251D9-U10-4269-RLFEF-JJFG-16&MsgSearchByEvent=true

 

2103 -
http://216.64.118.243/evtbkstart.asp?EventID=2103&Name=Demo&Email=Demo&k
ey=N1251D9-U10-4269-RLFEF-JJFG-16&MsgSearchByEvent=true

 

2114 -
http://www.eventid.net/display.asp?eventid=2114&eventno=2458&source=MSEx
changeDSAccess&phase=1

 

8026 -
http://216.64.118.243/evtbkstart.asp?EventID=8026&Name=Demo&Email=Demo&k
ey=N1251D9-U10-4269-RLFEF-JJFG-16&MsgSearchByEvent=true

 

 

 

  _____  

From: David Goldstein [mailto:dgoldstein@xxxxxxxxxxxxxxxxx] 
Sent: Monday, May 09, 2005 4:15 AM
To: [ExchangeList]
Subject: Dolly.Bareqet@xxxxxxxxxxxx - Found word(s) list error in the
subject - [exchangelist] Event log errors

 

http://www.MSExchange.org/

The exchange server has been getting the same errors in the application
event viewer twice a day. Thanks in advance for pointing me in the right
direction troubleshooting this problem .

 

 

8250    MSExchangeAL

The Win32 API call 'DsGetDCNameW' returned error code [0x54b] The
specified domain either does not exist or could not be contacted.  The
service could not be initialized.  Make sure that the operating system
was installed properly. 

2102  MSExchangeDSAccess     

Process MAD.EXE (PID=1736). All Domain Controller Servers in use are not
responding: 

xxxx.xxxx.local 

 

 

 9153 MSExchangeSA

Microsoft Exchange System Attendant reported an error '0x80004005' when
setting DS notification. 

 

 

9154  MSExchangeSA

DSACCESS returned an error '0x80004005' on DS notification. Microsoft
Exchange System Attendant will re-set DS notification later. 

 

  2103 MSExchangeDSAccess  

Process MAD.EXE (PID=1736). All Global Catalog Servers in use are not
responding: 

xxxx.xxxx. local 

 

2114  MSExchangeDSAccess

Process MAD.EXE (PID=1736). Topology Discovery failed, error 0xffffffff.


 

8026  MSExchangeAL

LDAP Bind was unsuccessful on directory rremcdc.rremc.local for
distinguished name ''. Directory returned error:[0x51] Server Down.    

 

 

------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com
Leading Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSEXchange.org Discussion List as:
Dolly.Bareqet@xxxxxxxxxxxx
To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx 


The information contained in this e-mail is intended only for the personal and 
confidential use of the recipient(s) named above. If you are not the intended 
recipient(s) or the person responsible for delivering this communication to the 
intended recipient(s), you are hereby notified that you have received this 
communication in error and that any review, dissemination, distribution, or 
copying of this message is strictly prohibited. Please notify the sender 
immediately via e-mail and delete this e-mail from your system. iMDsoft shall 
not be liable for any damage of whatsoever nature in connection with any 
information received in error.





Other related posts: