mark.coleman

I have an issue with one of my Exchange servers, The IMS will not start giving event ID 166, saying the Database engine has reached its limit, I'm running latest service packs on Enterprise.

Anyone, any ideas, thanks

Completely Stuck

Mark

DominicA

Diskpace??

ChristianR

iTrader: (1)

PSS ID Number: Q185457
Article last modified on 05-18-2000

winnt:4.0,5.0,5.5




================================================== ====================
-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Exchange Server, versions 4.0, 5.0, 5.5
-------------------------------------------------------------------------------

SYMPTOMS
========

The Microsoft Exchange information store service shuts down. In the Windows NT
application event log, the following event is logged:

Event ID:1112
Source: MSExchangeIS
Description: The database has reached the maximum allowed size.
Attempting to stop the Microsoft Exchange Information Store.

CAUSE
=====

The Microsoft Exchange information store utilizes the Exchange database engine.
The maximum allowed size of a single database in Exchange versions 4.0 and 5.0
is 16 GB (Priv.edb can be 16 GB and Pub.edb can be 16 GB). After the limit is
reached, the Exchange database engine stops taking transactions and notifies the
information store to shut down.

NOTE: Microsoft Exchange Server 5.5 Enterprise Edition information store
databases are not limited to 16 GB; they are limited only by available hardware.

WORKAROUND
==========

The database (Priv.edb or Pub.edb) that has hit the 16-GB limit must be
decreased so that the affected process can be started and remain started.

First, the affected database must be defragmented to reclaim any free space. This
can be accomplished by doing the following:

1. Defragment the database by running "edbutil /d /ispriv" (without the
quotation marks) or "edbutil /d /ispub" (without the quotation marks).

2. Start the information store service, let it run for a couple of minutes, and
then stop the service gracefully. (This is done to make sure all uncommitted
transactions are flushed into the database; see the "More Information" below
for details.)

3. After the process is back up and running, perform a FULL online backup.

-OR-

After the process is back up and running, stop the information store service
and perform an offline backup of the Exchsrvr\Mdbdata directory.

Defragmenting the database should result in a decrease in size of the database;
however, it is possible that the database will still be very close to the 16-GB
limit. Therefore, steps must be taken to decrease the amount of information in
that database. This can be accomplished by either moving some users from this
server to another server with more free space, or implementing personal
information store (PSTs) for users and having them move mail into PSTs. The
Mailbox Resources tab in the Microsoft Exchange Administrator program can assist
the system administrator in finding the largest mailboxes.

It is a good idea to implement storage limits on user mailboxes in the private
information store. Storage limits can be configured through the Exchange
Administrator program and will help prevent from the database reaching the 16-GB
limit.

For more information about use of personal folders and storage limits, see the
online documentation.

NOTE: If users are moved to another server, the information store should be
defragmented again by running "edbutil /d /ispriv" (without the quotation marks)
or "edbutil /d /ispub" (without the quotation marks) so as to reclaim the space
used by the users who were moved.

MORE INFORMATION
================

When the Exchange database is committing a transaction from a log file and that
transaction, if committed, will make the database surpass the 16-GB limit, the
Exchange database engine takes the following steps:

1. The transaction is wholly rolled back, meaning that no part of the
transaction succeeds, and the checkpoint holds a pointer to this transaction
in the log file where it was contained.

2. The Exchange database engine alerts the information store that the 16-GB
limit has been reached.

3. The information store then performs a graceful shutdown of the service.

After the database size has been decreased and the service is restarted, the
transactions that were not committed because the limit was reached will be
committed. To ensure this happens, do this: After the information store is
restarted following the defragmentation, stop the service again. This causes all
the log files to be committed into the database.

If you are using Exchange Server 5.5 Standard Edition and plan to upgrade to
Exchange Server 5.5 Enterprise Edition with unlimited storage, you do not need
to defragment the database. Run Setup.exe from the Exchange Server 5.5
Enterprise CD-ROM or Srvmax.exe from the Select CD-ROM.

Additional query words: JET_errOutOfDatabaseSpace -1012 Gig gigabyte

================================================== ====================
Keywords : exc4 exc5 exc55
Technology : kbExchangeSearch kbExchange500 kbExchange550 kbExchange400 kbZNotKeyword2
Version : winnt:4.0,5.0,5.5
Hardware : ALPHA MIPS x86
Issue type : kbprb
================================================== ===========================
Copyright Microsoft Corporation 2000.

ChristianR

iTrader: (1)

PSS ID Number: Q268000
Article last modified on 10-27-2000

winnt:5.5




================================================== ====================
-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Exchange Server, version 5.5
-------------------------------------------------------------------------------

SYMPTOMS
========

When you attempt to install Exchange Server 5.5 from the Microsoft Select CD,
using AutoRun from the Setup.exe program file, Exchange Server may alert you
that the 16-gigabyte (GB) database limit is reached.

CAUSE
=====

This issue can occur when you install the Standard Edition of Exchange Server
5.5. The information store databases (Priv.edb and Pub.edb) in this version are
limited to 16 GB each. After the limit is reached, the Exchange Server database
engine stops taking transactions and notifies the information store to shut
down.

RESOLUTION
==========

To resolve this issue, run the Srvmax.exe program file from the Select CD to
install the Enterprise Edition of Exchange Server 5.5. The Enterprise Edition
information store databases are limited only by available hardware resources.

Additional query words:

================================================== ====================
Keywords :
Component : Setup
Technology : kbExchangeSearch kbExchange550 kbZNotKeyword2
Version : winnt:5.5
Issue type : kbprb
Solution Type : kbfix
================================================== ===========================
Copyright Microsoft Corporation 2000.

ChristianR

iTrader: (1)

But since the problem is with the Microsoft Exchange Internet Mail Service, try checking the diskspace on the proxy server. If this is how you recieve your external mail.

What problems are users experiecing? And I presume you cannot send or receive external email?

mark.coleman

Disk space is not an issue with Enterprise, anyone know how to check whether Enterprise is installed.

Mark

David_Wallis

Can tell in admin, dont think you get the x400 connectors.. ?? depends what you have installed though... what about help about?

David

mark.coleman

David, I thought also it was what you had installed. Help about dosen't say much, I've been told you can tell by the build version, but I have nothing to compare it with.

Mark

ChristianR

iTrader: (1)

Sorry didn't read that you had enterprise installed.

Check the diskspace on the proxy server however, as this could be running low, or out.

To see if enterprise is installed, as already mentioned, load up Exchange Administrator, click on the server you want the info on, and go to properties.

Mr Footlong

iTrader: (7)

As far as I can remember, one easy way as mentioned above is to see if you have X.400 support. I have enterprise here and I can't see where it would tell you either....

Cheers,

Nick

mark.coleman

Here's the answer, In event viewer you will have a service for the relevant server setup 1216 for Standard and 1217 for Enterprise detailing the Information store limitations.

Thanks everyone.

Mark

mark.coleman

ChristianR, what should I see in properties to determine if I have Enterprise.

Thanks

Mark

[Edited by mark.coleman - 6/10/2002 12:17:08 PM]