RE: Database Corruption after Exchange SP 2
- From: v-chacez@xxxxxxxxxxxxx (chace zhang)
- Date: Mon, 07 Aug 2006 11:25:41 GMT
Hi,
Thanks for your update.
Did you perform a full backup for OS system state and exchange information,
I strongly recommend you restore from available tape media.
Based on my research third party antivirus software may also cause this
problem, please temporary disable them and check whether the problem
persists.
Yes, I agree with your action plan to recreate the mailbox store and
mailboxes.
To do so:
The Microsoft Exchange Mailbox Merge Program (Exmerge.exe), permits you to
extract/import data from mailboxes. Export all the data from all the
mailboxes, recreate the mailbox store and mailboxes, and import back.
For additional information about how to use the Exmerge.exe tool, click the
following URL to view the article in the Microsoft Knowledge Base:
174197.KB.EN-US: XADM: Microsoft Exchange Mailbox Merge Program
(Exmerge.exe) Information
http://support.microsoft.com/default.aspx?scid=KB;EN-US;174197
If the above methods failed, we may have to repair the database which may
cause lossing data. Run the eseutil /p command against all database (Ispriv
or Ispub) that reports that the database is corrupted, and then run isinteg
to see if there are no errors.
More information, see the following articles:
317014.KB.EN-US XADM: Exchange 2000 Server Eseutil Command Line Switc
http://support.microsoft.com/default.aspx?scid=KB;EN-US;317014
182081 Description of the Isinteg utility
http://support.microsoft.com/?id=182081
Regarding the 1202 error Events, I recommend you try the following steps to
check the issue on the computer:
1. A conflict in Group Policy can cause these events to occur. These error
messages can occur if the "Rename Administrator Account" security policy is
enabled and then set to an account name that is already in use. Please
verify if you had set the "Rename Administrator Account" policy or not,
if it is true, please disable this policy on the computer/domain.
You can take a look at the following URL for more information:
260715 Event ID 1000 and 1202 After Configuring Policies
http://support.microsoft.com/?id=260715
2. When you install the Microsoft Windows Server 2003 Administration Tools
Pack in Microsoft Windows XP and then use the Group Policy Editor in
Windows XP to configure domain policies, you may find that the policies do
not work on Microsoft Windows 2000-based computers and get the 1202 error
message.
So please make sure that you had configure the policy on the DC directly
instead of the client computers.
Also if you had imported a security template which contained specific
unique settings to Windows XP / 2003 and was attempting to apply them to
the Windows 2000
machines, this error will occur too. Make sure that you did not set the
settings like this.
3. If you attempt to add users from other domains into a Restricted group
in your domain, the error message of 1202 will occur too.
Please make sure that you use only users and groups in your local domain
when you add to Restricted groups.
Also it is better for you to disable the Group Policy object (GPO) that
defines restricted groups and then check the issue again.
4. This problem can also occur if the local Group Policy database file is
corrupt. However if the issue occurs on all the windows 2000 computer, this
may not be the root cause of this issue. I just provide this information
for your reference. You can take a look at the following URL for more
information:
278316 ESENT Event IDs 1000, 1202, 412, and 454 are logged repeatedly in the
http://support.microsoft.com/?id=278316
Regarding NTDS database corrupted, you can refer to the following article
to use the Ntdsutil tool to recover the database.
816120 How To Use Ntdsutil to Manage Active Directory Files from the Command
http://support.microsoft.com/?id=816120
Hope this helps, I look forward to your update.
Have a nice day!
Best Regards,
Chace Zhang (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: Database Corruption after Exchange SP 2
| thread-index: Aca5l8rruPxgsFIiTeaJefWYIT+mZw==
| X-WBNR-Posting-Host: 66.142.82.233
| From: =?Utf-8?B?UmdhcmNpYQ==?= <Rgarcia@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <1C9A32DD-414A-4333-BBAC-4864D23C6BBD@xxxxxxxxxxxxx>
<97BE0371-B5D5-4E98-8759-3326ABBD087F@xxxxxxxxxxxxx>
<bQLbUertGHA.5840@xxxxxxxxxxxxxxxxxxxxx>
<4ADDB95D-093E-4E39-9737-87429E872F4B@xxxxxxxxxxxxx>
| Subject: RE: Database Corruption after Exchange SP 2
| Date: Sun, 6 Aug 2006 13:35:02 -0700
| Lines: 49
| Message-ID: <52BC4F43-12EF-48A1-92A5-2C234E6BF449@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGXA01.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:287427
| NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Also, I noticed that there is the following Warning:
| Event Source: SceCli
| Event ID: 1202
| Description: Security policies are propagated with warning. 0x4b8 : An
| extended error has occurred.
|
| I believe this is also related to Active Directory or the local security
| policy. I found this article on how to fix it but I wanted your input
about
| it. http://support.microsoft.com/kb/278316/
|
| This is what I got after running CHKDSK and rebooting the server. I'm
still
| having the same issues.
|
| Checking file system on C:
| The type of the file system is NTFS.
|
|
| A disk check has been scheduled.
| Windows will now check the disk.
| Cleaning up minor inconsistencies on the drive.
| Cleaning up 441 unused index entries from index $SII of file 0x9.
| Cleaning up 441 unused index entries from index $SDH of file 0x9.
| Cleaning up 441 unused security descriptors.
| CHKDSK is verifying Usn Journal...
| Usn Journal verification completed.
|
| 312295535 KB total disk space.
| 39248644 KB in 54768 files.
| 18540 KB in 5271 indexes.
| 0 KB in bad sectors.
| 662671 KB in use by the system.
| 65536 KB occupied by the log file.
| 272365680 KB available on disk.
|
| 4096 bytes in each allocation unit.
| 78073883 total allocation units on disk.
| 68091420 allocation units available on disk.
|
| Internal Info:
| 80 f0 00 00 93 ea 00 00 7d 40 01 00 00 00 00 00 ........}@......
| 0a 01 00 00 03 00 00 00 2b 05 00 00 00 00 00 00 ........+.......
| 14 53 a3 04 00 00 00 00 ae cd 48 2c 00 00 00 00 .S........H,....
| 52 a2 ef 0c 00 00 00 00 00 00 00 00 00 00 00 00 R...............
| 00 00 00 00 00 00 00 00 32 12 dd 79 00 00 00 00 ........2..y....
| f0 a7 d2 b2 00 00 00 00 18 3b 07 00 f0 d5 00 00 .........;......
| 00 00 00 00 00 10 8c 5b 09 00 00 00 97 14 00 00 .......[........
|
| Windows has finished checking your disk.
| Please wait while your computer restarts.
|
.
- Follow-Ups:
- RE: Database Corruption after Exchange SP 2
- From: Rgarcia
- RE: Database Corruption after Exchange SP 2
- References:
- RE: Database Corruption after Exchange SP 2
- From: chace zhang
- RE: Database Corruption after Exchange SP 2
- Prev by Date: Re: SBS 2003 KB885918 error installing SP1
- Next by Date: Re: SBS Backup And Exchange
- Previous by thread: RE: Database Corruption after Exchange SP 2
- Next by thread: RE: Database Corruption after Exchange SP 2
- Index(es):
Relevant Pages
|
