RE: Ex5.5 IS shuts down , but why ? how to prevent

  • From: <ian.dobson@xxxxxxxxxxxxx>
  • To: <exchangelist@xxxxxxxxxxxxx>
  • Date: Mon, 18 Oct 2004 13:37:49 +0100

That looks to me like your virus checking software is scanning the logs
area, which is not a good idea. 

-----Original Message-----
From: Shyam K M [mailto:shyamkm@xxxxxxxx] 
Sent: 18 October 2004 13:21
To: [ExchangeList]
Subject: [exchangelist] Ex5.5 IS shuts down , but why ? how to prevent

   This is a problem I am facing with an Exchange Server 5.5
installation.My IS needs to be restarted from the services.msc on
certain occassions - a senior colleague suggested that one of the
reasons is when an attachment whose size is larger than our permitted
limit arrives.He said that though a size limit is placed on attachment
sizes , this issue will happen , because as a result of a bug in
Microsoft Exchange 5.5 , this limit on attachment size is not enforced.
  But somehow , I am not convinced .So I have culled out the following
from my Event Viewer's Application Log (in the same order in which they
appeared in the Event Viewer's Application Log , top to bottom) :

Source : MS Exchange SA

Category : Monitoring

EID : 1005 (MS Ex)

Unexpected error <<0xc0040000 - The Microsoft Exchange Server computer
is not available. Either there are network problems or the Microsoft
Exchange Server computer is down for maintenance. Microsoft Exchange
Server Information Store ID no: 8004011d-0526-00000000>> occurred. 



Unexpected error <<0xc0040000 - Network problems are preventing
connection to the Microsoft Exchange Server computer. Microsoft Exchange
Server Information Store ID no: 80040115-0514-000006bf>> occurred. 


Source : ESE97

Category : Logging / Recovery

EID : 193

MSExchangeIS (2156) The database engine failed with error -510 while
trying to log the commit of a transaction.  To ensure database
consistency, the process was terminated.  Simply restart the process to
force database recovery and return the database to a consistent state. 


Source : ESE97
EID : 130
Category : Logging / Recovery
MSExchangeIS (2156) Error -1032 occurred while opening a newly created
log file. 


Source : ESE97
EID : 145
Cat : General

MSExchangeIS (2156) The database engine could not access the file called

Any help will be greatly appreciated. 


Shyam Kumar Mangayil.

List Archives:
Exchange Newsletters:
Exchange FAQ:
Other Internet Software Marketing Sites:
World of Windows Networking: Leading
Network Software Directory:
No.1 ISA Server Resource Site: Windows Security
Resource Site: Network Security Library: Windows 2000/NT Fax Solutions:
You are currently subscribed to this Discussion List as:
Ian.Dobson@xxxxxxxxxxxxx To unsubscribe visit
Report abuse to listadmin@xxxxxxxxxxxxxx


Nomura is proud to sponsor
at the V&A, London, 23 September-5 December 2004

Information and tickets:


PLEASE READ: The information contained in this email is confidential
and intended for the named recipient(s) only. If you are not an intended
recipient of this email you must not copy, distribute or take any
further action in reliance on it and you should delete it and notify the
sender immediately. Email is not a secure method of communication and
Nomura International plc cannot accept responsibility for the accuracy
or completeness of this message or any attachment(s). Please examine this
email for virus infection, for which Nomura International plc accepts
no responsibility. If verification of this email is sought then please
request a hard copy. Unless otherwise stated any views or opinions
presented are solely those of the author and do not represent those of
Nomura International plc. This email is intended for informational
purposes only and is not a solicitation or offer to buy or sell
securities or related financial instruments. Nomura International plc is
regulated by the Financial Services Authority and is a member of the
London Stock Exchange.

Other related posts: