|
Navigation Menu |
|
|
|
|
|
|
|
Microsoft Windows Server Community |
|
|

|
|
|
|
|
Advertisement |
|
|
|
|
|
|
|  |
Category: Main/Microsoft/Exchange Server
Sort Links by: Title (A\D) Date (A\D) Rating (A\D) Popularity (A\D) Sites currently sorted by: Title (A to Z)
The available memory gradually decreases on your Exchange 2000 Server computer Description: On your Microsoft Exchange 2000 Server computer, the available memory decreases gradually over time. This symptom may be especially noticeable on a public folder server. When the available memory becomes too low, you must restart your server to regain functionality. Added on: 29-Nov-2004 Hits: 204 Rate this Site
The Badmail folder is disabled in Exchange Server 2003 SP1 Description: This article discusses an issue where, after you install Microsoft Exchange Server 2003 Service Pack 1 (SP1), e-mail messages are no longer written to the Badmail folder of an Exchange SMTP virtual server. Added on: 29-Nov-2004 Hits: 189 Rate this Site
The conferencing server stops responding to client requests, and event ID 12288 is logged on an Exch Description: You may experience the following symptoms on a computer that is running Microsoft Exchange 2000 Conferencing Server: Added on: 29-Nov-2004 Hits: 228 Rate this Site
The Exchange Connector for Lotus Notes service stops, and event IDs 8226 and 8227 are logged in the Exchange Server server Description: This article describes why the Microsoft Exchange Connector for Lotus Notes service may stop after event IDs 8226 and 8227 are logged in the Microsoft Exchange Server server that is running this service. Additionally, this article lists the steps that you can follow to resolve this problem. Added on: 28-Oct-2005 Hits: 183 Rate this Site
The Exchange Information Store service stops responding when you register an event sink on the syste Description: When you register a custom global information store event sink on a computer that is running Microsoft Exchange 2000 Server, the Microsoft Exchange Information Store service (Store.exe) may stop responding (hang). Added on: 29-Nov-2004 Hits: 244 Rate this Site
The Exchange Migration Wizard does not successfully move mailbox data from a Microsoft Exchange Serv Description: When you run Microsoft Exchange Migration Wizard to move mailbox data from a Microsoft Exchange Server 5.5-based computer to a Microsoft Exchange 2000 Server-based computer, the migration may not be successful. You notice this problem when you run Microsoft Exchange Migration Wizard after you create Active Directory users by using the Active Directory Migration Tool and after you set up the Active Directory Connector (ADC). Added on: 29-Nov-2004 Hits: 208 Rate this Site
The Exchange Server 2003 Recipient Update Service continually updates some recipients or public Description: The Microsoft Exchange Server 2003 Recipient Update Service continually updates some recipients or public folders with what appear to be random SMTP proxy addresses, and you experience the following symptoms: Added on: 24-Jan-2005 Hits: 193 Rate this Site
The Exchange Server 2003 Recipient Update Service continually updates some recipients or public folders with random SMTP proxy addresses Description: The Microsoft Exchange Server 2003 Recipient Update Service continually updates some recipients or public folders with what appear to be random SMTP proxy addresses. When this problem occurs, you experience one or more of the following symptoms: Added on: 12-Mar-2005 Hits: 180 Rate this Site
The ExMerge process is not successful, and the log file fills up the drive when you run the ExMerge Description: When you try to use the Mailbox Merge Wizard (ExMerge), the ExMerge process is not successful. The drive that holds the ExMerge log file becomes full. When the drive becomes full, the computer that is running ExMerge may stop responding. If you view the ExMerge log file, you see that the log is filled with entries that are similar to the following: Added on: 29-Nov-2004 Hits: 220 Rate this Site
The Information Store service stops responding in Exchange Server 2003 SP1 when a CDO 1.21-based program uses the SetLocaleIDs method to set the codep Description: Consider the following scenario. You use a Collaboration Data Objects (CDO) 1.21-based program in Microsoft Exchange Server 2003 Service Pack 1 (SP1). This CDO 1.21-based program uses the SetLocaleIDs method to set the codepage of a MAPI session. In this scenario, the CDO 1.21-based program fails. Additionally, you may find that the Information Store service stops resending in Exchange Server 2003 SP1. Added on: 28-Oct-2005 Hits: 166 Rate this Site
Select Page: [ << Previous Page ] 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 [ Next Page >> ] |
|
|
|  |
|
Advertisement |
|
|
|
|
|
|
|
Survey |
|
|
|
|
|
|
|
Login |
|
|
Don't have an account yet? You can create one. |
|
|
|
|
Big Story of Today |
|
|
There isn't a Biggest Story for Today, yet. |
|
|
|
|