RE: MS Exchange Error
- From: "itnewbie via WinServerKB.com" <u23362@uwe>
- Date: Tue, 24 Oct 2006 13:22:43 GMT
Steven,
I will try what you suggested, but to correct one thing. You're advise was
for an Exchange 2000 server but I have Small Business Server 2003 with
Exchange 2003. Will, what you suggested work in the same way? Also can you
help me out with the following two new error's that showed up in the log file
today?
Source Event ID Last Occurrence
Total Occurrences
MSExchangeDSAccess 2102 10/23/2006 1:58 PM 3 *
Process MAD.EXE (PID=5264). All Domain Controller Servers in use are not
responding: scidfw2.SCIDFW.local For more information, click
http://www.microsoft.com/contentredirect.asp.
Source Event ID Last Occurrence
Total Occurrences
MSExchangeDSAccess 2114 10/23/2006 1:52 PM 1
Process EMSMTA.EXE (PID=4856). Topology Discovery failed, error 0x80040a02.
For more information, click http://www.microsoft.com/contentredirect.asp.
Steven Zhu [MSFT] wrote:
Hi,
Thank you for posting here.
From your post, my understanding on this issue is: you received thefollowing event error every 15 minutes on your Exchange 2000 server.
Event Source: MSExchangeIS Mailbox Store
Event ID: 7200
Description: Background thread FDoUpdateCatalog halted on database "First
Storage Group\Private Information Store (Computer Name)" due to error code
0x80070005.
If I''m off base, please feel free to let me know.
Based on my research, that the FDoUpdateCatalog has been halted may
indicate that full-text indexing was originally set with the interval time
set to always, and then the service was disabled and the interval time was
not set back to never. This issue can occur if Exchange 2000 reads this
interval time and the service is not running; Exchange 2000 logs the error
because Exchange 2000 determines that the service should be on. Please
perform the action plan below to see if we can resolve the problem.
Action Plan
========
Step 1
=====
Please apply the latest Exchange 2000 service pack, which can be obtained
from the link below.
Exchange 2000 post service pack 3
http://www.microsoft.com/downloads/details.aspx?FamilyId=43F5CDF6-D1E6-4476-
B5F2-E17371236C3C&displaylang=en
Step 2
=====
You may also be able to use the following steps resolve this issue:
1. Enable full-text indexing for the information store that is being
affected:
a. Start Exchange System Manager for Exchange 2000.
b. Click to expand the Organization object, click to expand the Site
object, and then click to expand the Servers object. Click the Server_name
object, click the Storage_group_name object, and then click the Mailbox
Store object.
c. Right-click the Mailbox Store object, and then click Create
Full-Text Indexing on the shortcut menu.
d. Click OK to the catalog path.
2. Wait until full-text indexing is enabled; this may take some time for
large information stores. Right-click the Mailbox Store object, and then
click Properties on the shortcut menu.
NOTE: If the information store database (on which you are setting up the
index) is very large, you may need to schedule this process for a time when
production will not be interrupted because indexing occurs on all of the
mailboxes.
3. Click the Full-Text Indexing tab, and then change the interval back to
Never .
4. Disable full-text indexing for the information store:
a. Click to expand the Organization object, click to expand the Site
object, and then click to expand the Servers object. Click the Server_name
object, click the Storage_group_name object, and then click the Mailbox
Store object.
b. Right-click the Mailbox Store object, and then click Delete the
Full-Text Indexing on the shortcut menu.
c. Click OK to the catalog path.
5. After 15 minutes, refresh the Application event logs; the error messages
should be gone.
For more information about this issue, please refer to the following
article.
XADM: Event ID 7200 for MSExchangeIS Mailbox Store Is Logged in Application
Event Log Every 15 Minutes
http://support.microsoft.com/?id=293370
I hope the above information helps.
Have a nice day.
Best Regards,
Steven Zhu
MCSE
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
======================================================
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD were
updated on February 14, 2006.? Please complete a re-registration process
by entering the secure code mmpng06 when prompted. Once you have
entered the secure code mmpng06, you will be able to update your profile
and access the partner newsgroups.
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
--
Message posted via WinServerKB.com
http://www.winserverkb.com/Uwe/Forums.aspx/sbs-2003/200610/1
.
- Follow-Ups:
- RE: MS Exchange Error
- From: Steven Zhu [MSFT]
- RE: MS Exchange Error
- References:
- MS Exchange Error
- From: itnewbie via WinServerKB.com
- RE: MS Exchange Error
- From: Steven Zhu [MSFT]
- MS Exchange Error
- Prev by Date: Re: Folder redirection
- Next by Date: Re: VPN for branch offices
- Previous by thread: RE: MS Exchange Error
- Next by thread: RE: MS Exchange Error
- Index(es):
Relevant Pages
|
