Re: Weird System Undeliverable Messages (Outlook 2003/Exchange 2003) and some Exchange Server errors? Advice?




markm75 wrote:
I'm getting this weird undeliverable error message with about 2 or 3
people now (Cant find much on the way on this online though):

Your message did not reach some or all of the intended recipients.
This message could not be sent. Try sending the message
again later, or contact your network administrator. Error is
[0x80004005-00000000-00000000].

I had both users turn off "cached" mode.. and so far so good, but this
isnt an adequate solution...

xxxxxxxxxxxxxxxxxxx
On the Server (Exchange 2003 SP2) I am getting a bunch of errors in the
event viewer:

EventID 623: Source ESE
nformation Store (2996) First Storage Group: The version store for this
instance (0) has reached its maximum size of 155Mb. It is likely that a
long-running transaction is preventing cleanup of the version store and
causing it to build up in size. Updates will be rejected until the
long-running transaction has been completely committed or rolled back.
Possible long-running transaction:
SessionId: 0x7FD335E0
Session-context: 0x00000000
Session-context ThreadId: 0x0000161C
Cleanup: 1

xxxxxxxxxxxxxxxx

EventID 1025; Source MSExchangeIS Mailbox

An error occurred on database "First Storage Group\Mailbox Store
(EXCHANGE01)".
Function name or description of problem: EcGenerateNDR:
Error: 0xfffff9bf
xxxxxxxxxxxxxxxxxxxx

EventID 1022; Source MSExchangeIS Mailbox

Logon Failure on database "First Storage Group\Mailbox Store
(EXCHANGE01)" - Windows 2000 account domain\userx; mailbox
/o=domain-org/ou=First Administrative
Group/cn=Recipients/cn=first.lastname.
Error: -1069

**This error occurred around the time the System Undeliverable was sent
back to this user, who sent the original email.
xxxxxxxxxxxxxxxxxxxxxxxxxx


I would have to guess that some of the server based errors are
related.. but I cant seem to find a direct fix for any of them.

Has anyone run into any of these before.

Thanks


markm75 wrote:
I'm getting this weird undeliverable error message with about 2 or 3
people now (Cant find much on the way on this online though):

Your message did not reach some or all of the intended recipients.
This message could not be sent. Try sending the message
again later, or contact your network administrator. Error is
[0x80004005-00000000-00000000].

I had both users turn off "cached" mode.. and so far so good, but this
isnt an adequate solution...

xxxxxxxxxxxxxxxxxxx
On the Server (Exchange 2003 SP2) I am getting a bunch of errors in the
event viewer:

EventID 623: Source ESE
nformation Store (2996) First Storage Group: The version store for this
instance (0) has reached its maximum size of 155Mb. It is likely that a
long-running transaction is preventing cleanup of the version store and
causing it to build up in size. Updates will be rejected until the
long-running transaction has been completely committed or rolled back.
Possible long-running transaction:
SessionId: 0x7FD335E0
Session-context: 0x00000000
Session-context ThreadId: 0x0000161C
Cleanup: 1

xxxxxxxxxxxxxxxx

EventID 1025; Source MSExchangeIS Mailbox

An error occurred on database "First Storage Group\Mailbox Store
(EXCHANGE01)".
Function name or description of problem: EcGenerateNDR:
Error: 0xfffff9bf
xxxxxxxxxxxxxxxxxxxx

EventID 1022; Source MSExchangeIS Mailbox

Logon Failure on database "First Storage Group\Mailbox Store
(EXCHANGE01)" - Windows 2000 account domain\userx; mailbox
/o=domain-org/ou=First Administrative
Group/cn=Recipients/cn=first.lastname.
Error: -1069

**This error occurred around the time the System Undeliverable was sent
back to this user, who sent the original email.
xxxxxxxxxxxxxxxxxxxxxxxxxx


I would have to guess that some of the server based errors are
related.. but I cant seem to find a direct fix for any of them.

Has anyone run into any of these before.

Thanks

After spending some time with MS tech support, the solution to this
problem was with SP2 and a registry change that was needed(though I
thought it was done/correct before):

After installing SP2 you need to change a few registry settings.

One in particular allows for priv1.mdb database sizes greater than
16GB.. our database was hitting the 16gb point and people were having
issues connecting.

The following is from a KB article.. Note that is case sensitive.. in
my case the "Limit in GB" was "Limit in Gb" hence the database never
expanded beyond 16gb. Also there is a handy tool I wasnt aware of that
will let you know of any settings that need changed on your Exchange
box...

The program is called the Exchange Server Best Practices Analyzer Tool
(It has updatable components too).. You can find it on Microsofts site.

Here is the reg. change that had to be corrected (again):

All registry settings discussed in this topic are created in the
following registry location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<SERVER
NAME>\Private-013e2e46-2cd7-4a8e-bfec-0e4652b94b00
The GUID in this key (Private-013e2e46-2cd7-4a8e-bfec-0e4652b94b00) is
an example and should match the value of the objectGUID attribute on
the database's Active Directory object.
Note
By default, registry entries mentioned in this article are not present;
when you create the entry, you override the default value set in code.
Note
All of registry values mentioned in this article are in decimal, not
hexadecimal.
· The following new registry settings are available with SP2:
· Database Size Limit in GB
· Database Size Buffer Warning in Percentage
· Database Size Check Start Time in Hours from Midnight
Top of page
Database Size Limit in GB
The Database Size Limit in GB setting is the configurable maximum size
of a database not to exceed the maximum licensed size of your database.
For Standard Edition, you can set the database size limit between 1 and
75 GB. By default, the limit is 18 GB. For Enterprise Edition you can
set the database size limit between 1 and 8,000 GB. By default, there
is no limit.
The following registry value controls the Configurable Database Size
Limit:

Data type Name Value (in GB) Default (in GB)
REG_DWORD Database Size Limit in GB Standard: 1-75
Enterprise: 1-8000 Standard: 18
Enterprise: 8,000 Unlimited

.



Relevant Pages

  • Re: Distributing application
    ... > rather than the system registry because for security reasons there's a ... you can make changes to the registry ... database there. ... user's section of the registry would be a good place to store the list. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Exchange SP2 Mailbox Size 18GB ?
    ... rebooted the server and I have stop/started the IS Store? ... If the physical size of this database minus its logical ... For the Exchange Server 2003 Standard Edition, ... overwritten by editing the "Database Size Limit in GB" registry key. ...
    (microsoft.public.exchange.admin)
  • RE: How do I determine Mailbox Store GUID?
    ... Open one of the following registry keys: ... The registry entries have to be made on each individual Store. ... name\Private-Mailbox Store GUID ... For the value name type: Database Size Limit in Gb. ...
    (microsoft.public.exchange.admin)
  • Re: Password Protected Program: How to do it?
    ... Store an encrypted version in the database, the registry, or in a text file ... > I'm writing a program that interacts with databases. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: public and private mailboxes randomly dismounting
    ... When posting logs an important piece is the Event ID and Source. ... Information Store First Storage Group: An attempt to move the file ... An error occurred while writing to the database log file of storage group ...
    (microsoft.public.windows.server.sbs)