|
Home > Archive > microsoft.public.exchange2000.admin > October 2002 > ISINTEG and Corrupt Store...
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
ISINTEG and Corrupt Store...
|
|
|
| Good day,
I recently discovered that a specific user store was corrupted. What I
did to remedy the situation was export what I could out from the store out
to a PST and then delete the associated mailbox. I then created another
mailbox and imported from the PST. I am worried about more corruption, how
do I use the ISINTEG utility to verify that everything is ok? I know MS has
a article regarding the tool, but is there anything I can do to just test
the database without making modifications? The article I read is not very
clear to me.
Thanks,
M
| |
| Dave Howe [MS] 2002-10-05, 8:32 pm |
| Open your Exchange System Manager.
Dismount your mailbox store.
Open a command prompt and navigate to the exchsrvr\bin folder.
Run: ISINTEG -s ServerName -l -Test Alltests
Then, locate the ISINTEG.PRI file, and open it with NotePad.
Each test will tell you the number of errors and/or fixes it would have
made.
To fix these problems, run:
ISINTEG -s ServerName -l -fix -test alltests
If you see any fixes, run it again until all fixes have been made.
--
Dave Howe
Microsoft PSS
This posting is provided "AS IS" with no warranties, and confers no rights.
"M" <do_not_send_mail@please.com> wrote in message
news:#WZwAffSCHA.1768@tkmsftngp13...
> Good day,
> I recently discovered that a specific user store was corrupted. What
I
> did to remedy the situation was export what I could out from the store out
> to a PST and then delete the associated mailbox. I then created another
> mailbox and imported from the PST. I am worried about more corruption,
how
> do I use the ISINTEG utility to verify that everything is ok? I know MS
has
> a article regarding the tool, but is there anything I can do to just test
> the database without making modifications? The article I read is not very
> clear to me.
>
> Thanks,
> M
>
>
| |
|
| This is a generally safe procedure? How long would this take on a 20GB
store?
Thanks
M
"Dave Howe [MS]" <daveh@online.microsoft.com> wrote in message
news:eEmAzxfSCHA.3252@tkmsftngp12...
> Open your Exchange System Manager.
> Dismount your mailbox store.
> Open a command prompt and navigate to the exchsrvr\bin folder.
> Run: ISINTEG -s ServerName -l -Test Alltests
> Then, locate the ISINTEG.PRI file, and open it with NotePad.
> Each test will tell you the number of errors and/or fixes it would have
> made.
>
> To fix these problems, run:
>
> ISINTEG -s ServerName -l -fix -test alltests
>
> If you see any fixes, run it again until all fixes have been made.
>
> --
> Dave Howe
> Microsoft PSS
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "M" <do_not_send_mail@please.com> wrote in message
> news:#WZwAffSCHA.1768@tkmsftngp13...
> > Good day,
> > I recently discovered that a specific user store was corrupted.
What
> I
> > did to remedy the situation was export what I could out from the store
out
> > to a PST and then delete the associated mailbox. I then created another
> > mailbox and imported from the PST. I am worried about more corruption,
> how
> > do I use the ISINTEG utility to verify that everything is ok? I know MS
> has
> > a article regarding the tool, but is there anything I can do to just
test
> > the database without making modifications? The article I read is not
very
> > clear to me.
> >
> > Thanks,
> > M
> >
> >
>
>
|
|
|
|
|