Exchange Server 2007
- A non-standard address space of '{1}' was found on recipient policy '{3}'. Contact your vendor to obtain a proxy address ...
- A notification of a configuration change has been received for %1 but the new configuration could not be read. Please check ...
- A portion of this component was not successfully installed, but Setup is proceeding with the remainder of this component. ...
- A postmaster address must be configured for the postmaster to receive mail. You can configure a mailbox specifically for ...
- A potential performance issue was found with the location of the Exchange data files, SMTP server queues, TEMP or TMP directories. ...
- A potential performance issue was observed from the disk performance counters. One or more disks is exhibiting a performance ...
- A potential performance issue was observed from the disk performance counters. One or more disks is exhibiting a performance ...
- A previous installation for this product is in progress. You must undo the changes made by that installation to continue. ...
- A previous version of Exchange Server is already installed on this computer. Run Exchange 2007 Setup from a different computer ...
- A problem occurred during delivery of this message. Microsoft Exchange will not try to redeliver this message for you. Please ...
- A problem occurred during the delivery of this message. Microsoft Exchange will not try to redeliver this message for you. ...
- A problem occurred during the delivery of this message. Microsoft Exchange will not try to redeliver this message for you. ...
- A problem occurred while doing OST sync operation for user %1. The message last attempted to sync was: Parent folder name: ...
- A problem occurred while getting the properties for the Copy/Move rule for %1. Error code: %2. Try to clear the rules or ...
- A problem occurred while getting the properties for the Out of Office message from %1. Error code: %2. Try to clear the rules ...
- A problem occurred while trying to change password. If the problem continues, contact technical support for your organization. ...
- A problem occurred while trying to use your mailbox. If the problem continues, contact technical support for your organization. ...
- A process for generating e-mail addresses is already in progress, and only one process can run at a time. Try again later. ...
- A processing restriction in the e-mail system prohibits the handling of this e-mail message. The sender should try creating ...
- A Proxy Address Calculation client did not have rights to access the RPC interface. The 'Access Recipient Update Service' ...
- A proxy generator DLL on server {0} could not be found or failed to initialize. Proxy addresses for the current recipient ...
- A public folder database already exists on the server that you specified. Each server can contain a maximum of one public ...
- A public folder store is present on Exchange front-end server {2}. This can cause data accessibility and system reliability ...
- A read operation on the file "%4" at offset %5 for %6 bytes failed %7 times over an interval of %8 seconds before finally ...
- A receive connector can only be created on an Edge Transport or a Hub Transport server. Please specify an Edge Transport ...
- A recent change in the Microsoft Anti-spam Update service mode has been detected. The Content Filter agent is being reinitialized. ...
- A recovery storage group exists on server {2}. This should only exist during data recovery. Once recovery is complete, the ...
- A reminder cannot be set for a single occurrence of a series of meetings when no reminder is set for the series. To set a ...
- A replica of public folder %1 was added. Expiration interval: %2 Database "%8". Folder-wide expiration interval: %3 Schedule: ...
- A replica of public folder %1 was modified. Expiration interval: %2 (%3) Database "%14". Folder-wide expiration interval: ...
- A replica of the offline address book (OAB) '{3}' (folder: {1}) was not found on server {2}. This may result in OAB generation ...
- A request to read from the file "%4" at offset %5 for %6 bytes succeeded, but took an abnormally long time (%7 seconds) to ...
- A request to read from the file "%4" at offset %5 for %6 bytes succeeded, but took an abnormally long time (%7 seconds) to ...
- A request to stop e-mail address generation has been received. This process will be stopped momentarily, upon completion ...
- A request to write to the file "%4" at offset %5 for %6 bytes succeeded, but took an abnormally long time (%7 seconds) to ...
- A request to write to the file "%4" at offset %5 for %6 bytes succeeded, but took an abnormally long time (%7 seconds) to ...
- A required resource could not be loaded, probably due to insufficient memory. Close some applications or windows, and try ...
- A required security operation could not be performed during delivery of this e-mail message. Either the credentials are incorrect, ...
- A restore map already exists for the specified component. You can only specify a restore map when performing a full restore. ...
- A rule synchronization error (%1) has occurred on mailbox database "%6". The mailbox folder is %2. The distinguished name ...
- A rule synchronization error (%1) has occurred on Public Folder Store "%5". The public folder is %2. There are %3 of %4 retries ...
- A secure connection from domain-secured domain '%1' on connector '%2' failed to authenticate because validation of the Transport ...
- A secure connection to domain secure domain '%1' on connector '%2' could not be established because the validation of the ...
- A secure connection to domain-secured domain '%1' on connector '%2' could not be established because the validation of the ...
- A secure connection to the domain %1 could not be established because the Transport Layer Security (TLS) certificate for ...
- A secure connection with Exchange server %1 could not be established because the protocol negotiation did not find a mutually ...
- A security error occurred while trying to deliver your e-mail message. Security policies prohibit further explanation of ...
- A server object for this server ("%s") already exists in the Administrative Group "%s". If you are attempting to recover ...
- A server object for this server ("%s") must exist in the Active Directory in order to recover this server. If you are attempting ...
- A Server Roles specification is invalid with this operation. To list the available command line parameters, type Setup /? ...
- A Setup failure previously occurred while installing the {1} role. Either run Setup again for just this role, or remove the ...
- A single replica of folder '{1}' for offline address list '{3}' exists in the organization. To increase performance and resilience, ...
- A single replica of the free/busy folder for administrative group '{3}' exists in the organization and more than 10,000 users ...
- A single replica of the free/busy folder for administrative group '{3}' exists in the organization. In some situations, multiple ...
- A situation where the server is configured to loop back on itself was detected. If you have multiple SMTP virtual servers ...
- A stack exception was thrown in module %1; some parameters and their values were %2. A significant section of the call stack ...
- A subscribed Edge Transport server receives the following data from the Microsoft Exchange EdgeSync service: Send connector ...
- A system resource cannot be loaded, probably due to insufficient memory. Close some applications or windows, and try again. ...
- A temporary database exists at '{0}'. Seeding is already in progress, or a previous seeding attempt failed. Please delete ...
- A test message was addressed to SMTP domain '{1}', but no recipient policy matches this address. Please ensure that this ...
- A test-only prereq has failed. If you see this and didn't expect to, delete the registry key HKLM\Software\Microsoft\Exc ...
- A TLS failure occured because the certificate presented by the remote has expired. The Error Code = {0} and the Message = ...
- A TLS failure occured because the certificate presented by the remote was not trusted. The Error Code = {0} and the Message ...
- A TLS failure occured because the local certificate specified was not found in the local store. The Error Code = {0} and ...
- A TLS failure occured because the remote certificate does not have the Enhanced Key Usage needed. The Error Code = {0} and ...
- A TLS failure occured because the remote certificate presented has been revoked. The Error Code = {0} and the Message = {1}. ...
- A TLS failure occured because the remote end disconnected while TLS negotiation was in progress. The Error Code = {0} and ...
- A TLS failure occured because the target name specified in its certificate is incorrect. The Error Code = {0} and the Message ...
- A TLS failure occured during TLS negotiation. Either the local certificate is unusable or the remote does not trust it. The ...
- A top-level auto attendant is one that has one or more extensions configured. It will answer incoming calls to one or more ...
- A torn-write was detected during hard recovery in logfile %4. The failing checksum record is located at position %5. This ...
- A torn-write was detected during soft recovery in logfile %4. The failing checksum record is located at position %5. The ...
- A torn-write was detected while restoring from backup in logfile %4 of the backup set. The failing checksum record is located ...
- A transaction log file in the sequence of logs accessed during transaction log replay is missing or mismatched with the other ...
- A transient failure has occurred. The problem may resolve itself in a while. The service will retry in %1 minutes. Message: ...