February 2007 Documentation Update Notes
Topic Last Modified: 2007-01-23
The following topics are new:
-
Exchange Server Analyzer articles
-
ADAM not Installed on the Local Computer
-
Database Recovery
-
ESE 454 -515: Missing Required Transaction Log File
-
ESE 455 -1811 (0xfffff8ed): Missing Current (Exx.log) Transaction Log File
-
Long-latency MAPI operations found
-
Long-running MAPI 'FindRow' operation
-
Long-running MAPI operation
-
Long-running MAPI 'SaveChangesMessage' operation
-
MSExchangeIS 1003: Insufficient Free Space Remaining on Exchange Database Drive
-
MSExchangeIS 1088: Cannot mount database because of invalid legacyExchangeDN
-
MSExchangeIS 5000 (0x3f5): Invalid Service Account Configured for the Information Store Service
-
MSExchangeIS 5000 (0x80004005): Cannot Mount Database Because of Incorrect Service Account or Missing SeSecurityPrivilege Permissions or Incorrect Group Membership
-
MSExchangeIS 5000 (0x8004010f): Cannot Mount Database Because of Incorrect Permissions or Invalid Characters in the Organization Name
-
MSExchangeIS 5000 (0x80040154): Missing or Corrupted SMTP Service Extensions
-
MSExchangeIS 5000 (0xc004038a): Cannot Mount Database Because of Incorrect Permissions or Deleted Routing Group
-
MSExchangeIS 9518 (0xfffff745): Unable to Create or Access TMP Files
-
MSExchangeIS 9518 (0xfffff764): Missing or Inaccessible Streaming File
-
MSExchangeIS 9518 (0xfffffc01): Incorrect Database or Transaction Log Drive or Directory
-
MSExchangeIS 9518 (0xfffffd9a): Missing Checkpoint File, and More Than 1,008 Transaction Log Files Exist
-
MSExchangeIS 9518 (0xfffffddc): Exceeded the Maximum Number of Transaction Logs Available for this Storage Group
-
MSExchangeIS 9518 (0xfffffea8): Mismatched Database Time Stamp in the Database File
-
MSExchangeIS 9519 (0x3f3): Unchecked "This database can be overwritten by a restore" Check Box After Restore
-
MSExchangeIS 9519 (0xfffff05b): Database or Logs Compressed on a Server Running Exchange Server 2000 SP3 or Higher
-
MSExchangeIS 9519 (0xfffffa84): Missing or Corrupted Database Indexes
-
MSExchangeIS 9519 (0xfffffb3a): Detected Multiple Databases With Same Signature In Use
-
MSExchangeIS 9519 (0xfffffbda): Missing Double Byte Character Set Locale Configured as the Default System Locale
-
MSExchangeIS 9519 (0xfffffe07): Unable to Mount Database Due to Running Backup Process
-
Write-Back Cache Not Enabled
-
ADAM not Installed on the Local Computer
-
Microsoft Exchange Server Intelligent Message Filter v2 Operations Guide
-
How to Create a Connection Filtering Rule
-
How to Create an Intelligent Message Filter
-
How to Enable Connection Filtering
-
How to Enable Intelligent Message Filtering
-
How to Specify IP Address Configuration Data for Connection Filtering
-
How to Specify IP Address Configuration Data for Sender ID Filtering
-
How to Specify Sender ID Filtering Options
-
How to Create a Connection Filtering Rule
The following topics have been updated for this release:
-
Administration Guide for Exchange Server 2003
-
Managing Mailbox Stores and Public Folder Stores
-
Tools That Are Used with Exchange
-
Managing Mailbox Stores and Public Folder Stores
-
Exchange 2003 Disaster Recovery Operations Guide
-
Repairing Exchange Databases
-
Repairing Exchange Databases
-
Exchange Server Client Access Guide
-
How to Specify a Mobile Operator for Up-to-Date Notifications on a Device
-
How to Specify a Mobile Operator for Up-to-Date Notifications on a Device
-
Exchange Server Deployment Guide
-
How to Create an Answer File for Running Unattended Exchange Setup
-
Upgrading from Exchange 2000 Server to Exchange Server 2003
-
How to Create an Answer File for Running Unattended Exchange Setup
-
Exchange Server Transport and Routing Guide
-
How to Use Nslookup to Verify MX record configuration
-
How to Use Nslookup to Verify MX record configuration
-
Technical Reference Guide for Exchange Server 2003
-
How to Enable Diagnostics Logging for the SMTP Service in Exchange System Manager
-
How to Enable Diagnostics Logging for the SMTP Service in Exchange System Manager
-
Using Recovery Storage Groups in Exchange Server 2003
-
Exchange 2003 Transaction Log File Considerations
-
Exchange 2003 Transaction Log File Considerations
-
What Is New in Exchange Server 2003
-
Storage Features of Exchange Server 2003
-
Storage Features of Exchange Server 2003
-
Microsoft Exchange Server Intelligent Message Filter v2 Operations Guide
-
Understanding Exchange Server Intelligent Message Filter
-
Configuring and Enabling Exchange Server Intelligent Message Filter
-
Customizing Exchange Server Intelligent Message Filter
-
Updating the Exchange Server Intelligent Message Filter
-
Planning Your Exchange Server Intelligent Message Filter
-
Monitoring and Troubleshooting Exchange Server Intelligent Message Filter
-
Understanding Exchange Server Intelligent Message Filter
-
Exchange Server Analyzer articles
-
A Secure Sockets Layer Certificate Will be Expiring Soon
-
Aging Clean Interval for a mailbox store is non-default
-
Aging Keep Time interval for database is non-default
-
All versions of Outlook are allowed to access the server
-
ASP.NET Rootver is damaged
-
At least one corrupted message has been identified
-
Background Cleanup for a mailbox store is non-default
-
Background Cleanup interval for a mailbox store is missing
-
Background Cleanup interval for a public folder store is missing
-
Cannot remove public folder database
-
Certificate Principal Mismatch
-
Checkpoint file placement
-
Circular logging is disabled
-
Circular logging is enabled
-
Client/Server RPC compression is disabled
-
Consider implementing storage quotas
-
Custom public folder referral list
-
Database Aging Keep Time interval has been modified from default
-
Database and log files stored on same disk volume
-
Databases in this storage group are set to zero pages during backup
-
Default public folder store is remote
-
Deletion Thread Period for a mailbox store is non-default
-
Disable MAPI clients warning
-
DSAccess configuration cache value is non-default
-
DSNs are currently being rendered as messages
-
ESE 428 (0xfffff8f0): Insufficient Free Space Remaining on Transaction Log Drive
-
ESE Maximum open tables has been hard-coded
-
Exchange database files are being written to a compressed folder
-
Exchange database files are being written to a non-NTFS partition
-
Exchange database files are being written to an encrypted folder
-
Exchange database online maintenance schedule is set to Never
-
Exchange resident on domain controller that is not a global catalog server
-
Exchange transaction logs are being written to a non-NTFS partition
-
Exchange transaction logs are written to a compressed folder
-
Exchange transaction logs are written to an encrypted folder
-
Global Catalog NSPI port has been overridden
-
Ignore Bad Oof Rule registry parameter has been set
-
IIS 6.0 MaxFieldLength parameter not set correctly
-
IIS 6.0 MaxRequestBytes parameter not set correctly
-
IMAIL exception handling has been manually disabled
-
Initial memory percentage has been set
-
Journaling recipient is not valid
-
Journaling recipient points to a deleted object
-
Journaling recipient points to a disabled account
-
Journaling recipient points to the local server
-
Journaling recipient should be hidden
-
LimitEmbeddingDepth parameter has been manually set
-
LimitRecipients parameter has been manually set
-
Log buffers may not be sufficient for servers with large numbers of mailboxes that are running Exchange Server 2003
-
Mailbox Cache Age Limit has been set
-
Mailbox Store Database size limit has been set
-
Mailbox store has not had a full backup in more than 60 days
-
Mailbox store has not had a full backup in more than 8 days
-
Mailbox store online maintenance schedules overlap
-
Mailbox store prohibit send and receive limits are too similar
-
Mailbox store will not mount on startup
-
Maximum attachment per message submission has been changed
-
Maximum incoming message size has not been set
-
Maximum incoming message size is set too high (>30MB)
-
Maximum incoming message size maybe set too low (<1MB)
-
Maximum open folder objects per logon has been changed
-
Maximum open folder views per logon has been changed
-
Maximum open message objects per logon has been changed
-
Maximum Polling Frequency is non-default
-
MaxOpenMessagesPerLogon has been set
-
Message tracking logs are being written to a compressed folder
-
Message tracking logs are being written to a non-NTFS partition
-
Message tracking logs are being written to an encrypted folder
-
Message-only journaling is enabled
-
MTA data files are being written to a non-NTFS partition
-
MTA data files are being written to an encrypted folder
-
Offline address book is not associated with a particular mailbox store
-
Online defragmentation has been disabled
-
Port conflict: Store HTTP
-
Port conflict: Store TCP
-
Port conflict: System Attendant HTTP
-
Port conflict: System Attendant HTTP NSPI
-
Port conflict: System Attendant NSPI
-
Port conflict: System Attendant RFR
-
Public folder store has not had a full backup in more than 60 days
-
Public folder store has not had a full backup in more than 8 days
-
Public folder store will not mount on start-up
-
Recovery storage group enabled
-
Recovery storage group functionality disabled
-
Reserve increment size set
-
Reverse DNS lookups have been enabled in the metabase but not on the associated SMTP server in the Active Directory
-
RPC binding does not match DNS resolved name
-
RPC Compression Minimum Size is non-default
-
Server is a Virtual PC
-
Single global catalog is present in topology
-
Store HTTP port is below 5000
-
Store working directory is missing or incorrect
-
Store: HTTP port is non-default
-
Suppress out-of-office messages to distribution lists has been set
-
System Attendant HTTP NSPI port is below 5000
-
System Attendant HTTP port is below 5000
-
System Attendant legacyExchangeDN value is missing
-
System Attendant NSPI port has been manually overridden
-
System Attendant service is not running as LocalSystem
-
System Attendant: HTTP port value is non-default
-
The Edge Transport role cannot be installed on the local computer
-
The Exchange Database exceeds 100 GB in size
-
The Exchange Information Store service is not configured to run as LocalSystem
-
The Exchange Information Store service is not running
-
The Exchange Store TCP/IP port has been manually overridden
-
The Exchange System Attendant service is not running
-
The legacyExchangeDN for this Exchange database does not correspond to the Exchange server
-
The LegacyExchangeDN for this Exchange server does not match the parent administrative group
-
The LegacyExchangeDN for this Exchange server is invalid
-
The legacyExchangeDN value is missing from this Exchange database
-
The local computer is a domain controller of a child domain
-
The local computer is already running Exchange Server
-
The Network News Transport Service is currently installed
-
The schema master is running Windows 2000 Server
-
The Simple Mail Transport Protocol is currently installed
-
The SMTP AdditionalPoolThreadsPerProc registry value has been manually set
-
The SMTP GlitchRetrySeconds registry value has been manually set
-
The SMTP IgnorePFTimeLimit registry value has been manually set
-
The SMTP MaxDSNSize value has been manually set
-
The SMTP MaxPercentPoolThreads registry value has been manually set
-
The SMTP MsgHandleAsyncThreshold registry value has been manually added but may no longer be needed
-
The threshold value that controls how many times a corrupted message is allowed to pass through the store has been changed
-
There are more than 900 connectors in a Routing Group
-
There is a discrepancy with the fully-qualified domain name setting between the Active Directory and metabase
-
This Exchange server is also a domain controller, which is not a recommended configuration
-
This server has 1 GB or more of physical memory and HeapDeCommitFreeBlockThreshold has not been set to 262144
-
Tracing has been enabled on the Microsoft Exchange Information Store service for all users
-
A Secure Sockets Layer Certificate Will be Expiring Soon
