The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
| Version |
Location |
Description |
Submitted by |
Date submitted |
| Printed |
Page 151
3rd line |
There should be no space between the /M and the site or monitor name. There
should be a between the monitor name and the server name. I think there
should also be a between the site and the monitor name.
FYI-I use Exchange 5.5 SP4.
|
Anonymous |
|
| Printed |
Page 545
third line from the bottom of the page, Technet article Q224336 |
is referenced - this should read Q224436.
|
Anonymous |
|
| Printed |
Page 568
2nd paragraph |
I think the text for "Recovery" and "Repair" modes using eseutil.exe is
still scrambled up (the syntax descriptions are switched between "Recovery"
and "Repair"), even after the corrections to the 5/01 reprint. There's also
a mix-up in using "repair" and "recovery" in the 5th & 6th sentences of the
"Repair" description paragraph. I believe the text should read (check Microsoft
Q182903 for confirming syntax details) as follows:
"Recovery mode
eseutil can attempt to recover a database that's in an inconsistent state. This
is called a soft recovery, since it won't cause any data loss and is generally
nondestructive. When you use eseutil's recovery mode, it attempts to bring the
database to a consistent state by replaying any uncommitted transactions from
the log files. When recovery runs, eseutil uses the checkpoint file (EDB.CHK)
to confirm which log files still contain uncommitted transactions. Recovery
mode has the following syntax:
eseutil /R { /IS | /DS } [/L logPath] [/S systemPath] [/O]
The interesting switch here is the one that controls whether the recovery
runs against the IS or DS. You can specify either, but not both, and
eseutil will automatically look up the location of the log and database
files in the registry-you can't manually override those values. The /L, /S,
and /O switches work the same way here as in the other modes.
Repair mode
This mode is scary because it can cause data loss. When you tell eseutil
to recover a database, it will freely truncate any database page it can't
cleanly recover. While this will normally restore your database to a
consistent and usable state, it will also normally cause you to lose some
message and/or mailbox data. Don't use this mode except as a last resort.
If you run an integrity check and it shows errors, always run a recovery
first. If that doesn't fix everything, you have two choices: restore from a
good backup (hopefully with no data loss), or run a repair. Any time you're
tempted to choose the latter option, call Microsoft support first to see
whether there are any other alternatives for recovery. MS has an array of
specialized tools that they can give you to fix specific problems, but only
if you call them. Repair mode has the following syntax:
eseutil /P database [/T tempName] [/D] [/V] [/X] [/O]
database
Specifies what database you want to repair. Use /ds, /ispub, or /is
priv as the database name to tell eseutil to look up the database
name and path in the registry, or provide the full path and
database name.
/D
Specifies that eseutil should test the database for errors
without repairing it.
The /T, /V, /X, and /O switches have the same function here as in the
previous modes."
|
Anonymous |
|