Re: Exchange 2000 Event 704 Information Store 1760
From: Timothy McMichael [MSFT] (timmcmic_at_online.microsoft.com)
Date: 03/12/04
- Next message: J.H: "Re: Exchange 2000 Event 704 Information Store 1760"
- Previous message: J.H: "Re: Exchange 2000 Event 704 Information Store 1760"
- In reply to: J.H: "Re: Exchange 2000 Event 704 Information Store 1760"
- Next in thread: J.H: "Re: Exchange 2000 Event 704 Information Store 1760"
- Reply: J.H: "Re: Exchange 2000 Event 704 Information Store 1760"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 12 Mar 2004 14:19:12 -0500
JH:
Here is what you should do.
Dismount each store on this server.
Open a command prompt, go to the exchsrvr\bin directory.
Run the following command:
isinteg -s <servername> -fix -test alltests -verbose -l c:\isinteg.log (You
do not need <> around servername).
When this commands starts, it will produce a list of all the databases on
this server, and should be showing offline.
Select the first database on the list, and let the command complete.
When the command completes, review the log file. At the end is a number of
errors, if the number of errors is greater then zero, rerun the same
command, and select the same database. Continue to run the command on the
same database until you get zero errors, or the same number of errors twice.
If you get the same number of errors after successive runs, let me know.
If you run the command on the database, and get zero errors, or reach zero
errors after successive runs, rerun the command and select the next database
on the list and follow the same log file review instructions.
Once the isinteg is done on all the databases, you need to offline defrag
them.
Offline defrag will require a disk space location that can accommodate 110%
the size of the database. So, if you database is 10 gig, you will need a
drive that has 12 gig free in order to do the defrag.
To run the defrag, use a command prompt in the exchange bin directory.
Run the following command
eseutil /d "d:\program files\exchsrvr\mdbdata\priv.edb" /tx:\temp.edb
Notice that there is no space between the X and the /t. The X drive
represents a drive with enough free space to defrag the database.
Let me know if I can do anything else.
Take care.
Tim
-- Timothy McMichael timmcmic@online.microsoft.com This posting is provided "AS IS" with no warranties, and confers no rights. "J.H" <jpthsd@hotmail.com> wrote in message news:ObL8TOGCEHA.628@TK2MSFTNGP10.phx.gbl... > Hi Timothy, > > Thanks for your quick response. > > In this situation, what action with isinteg should I run on my > database ? Should I do isiteng with check for the clean-shutdown first ? > If it is clean shutdown, I should go straight to do the defrag eseutils ? > > And if it is dirty shutdown, should I use isiteng to fix ? and then > mount the database and then run full online backup and then let it > online defrag running as scheduled ? > > Thanks, > J.H > > "Timothy McMichael [MSFT]" <timmcmic@online.microsoft.com> wrote in message > news:utYLXEGCEHA.3308@TK2MSFTNGP10.phx.gbl... > > J.H. > > > > Scanning the M drive could cause issues. You should never scan the M > drive, > > backup the m drive with a file level backup utility, or scan the M drive > > with antivirus. > > > > I suggest that you dismount the stores and run an isinteg on them, and > > follow it up with a defrag. This should be done for all stores on this > > server. > > > > Let me know if you require specific instructions. > > > > Tim > > > > -- > > Timothy McMichael > > timmcmic@online.microsoft.com > > > > This posting is provided "AS IS" with no warranties, and confers no > rights. > > "J.H" <jpthsd@hotmail.com> wrote in message > > news:uR6N16FCEHA.3184@TK2MSFTNGP09.phx.gbl... > > > >> It is just started 2 days ago, > > > It was a time when my boss was running 'search program' on > > > the server and caused the server highly consumed of VM, then > > > the information store was reporting fragmented VM, I then restarted > > > the information store (while he was still performing the search in M > > drive), > > > it then caused the server shutdown unexpectedly (blue-screen), we > > > cold-restarted > > > the server!, > > > >> For making sure, after the server restarted, we did one more time > > > safe-restart. The server was successfully restarted, information store > > > restart great, > > > every thing is good, operational. > > > > > > >> Only happening 2 days ago, the online defragmentation of priv1.edb > was > > > stopped > > > unexpectedly per event below!! Any suggestion of troubleshooting this > > error > > > ? > > > > > > Source: ESE > > > Event ID: 704 > > > Information Store (1760) Online defragmentation of database > > > 'D:\Exchsrvr\mdbdata\priv1.edb' > > > was interrupted and terminated. The next time online defragmentation is > > > started on > > > this database, it will resume from the point of interruption. > > > > > > For more information, click > http://www.microsoft.com/contentredirect.asp. > > > > > > Regards, > > > J.H > > > > > > > > > > > >
- Next message: J.H: "Re: Exchange 2000 Event 704 Information Store 1760"
- Previous message: J.H: "Re: Exchange 2000 Event 704 Information Store 1760"
- In reply to: J.H: "Re: Exchange 2000 Event 704 Information Store 1760"
- Next in thread: J.H: "Re: Exchange 2000 Event 704 Information Store 1760"
- Reply: J.H: "Re: Exchange 2000 Event 704 Information Store 1760"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|