Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Space required to run ISINTEG - fix

Posted on 2010-08-25
16
1,349 Views
Last Modified: 2012-05-10
We have succesfully run ESEUTIL /P /CREATESTM on a our exchange 2003 edb after an offline defrag trashed the STM.
We now have a number of emails which can neither be opened or deleted which was expected.

Reading into this I now need to run ISINTEG -FIX to resolve this. Does anyone know how much space is needed for the refer.mdb file or any other advice before we run this? The .edb is 45GB and the STM is about 400MB
0
Comment
Question by:omnisys
  • 8
  • 7
16 Comments
 
LVL 28

Expert Comment

by:sunnyc7
ID: 33520498
did you run eseutil /CC before running eseutil /p ?

insinteg -s SERVERNAME - FIX -Test Alltests

Isinteg doesnt need space. Those are required for TEMP.EDB files created during hard repair / offline defrag - for that 150% of space is advisable.

thanks
0
 
LVL 10

Expert Comment

by:dhruvarajp
ID: 33520644
i woud day that is the ramification of running /p
running /p and /d should be used as the last resort..

restoring is back up is always better and recomended

http://support.microsoft.com/kb/259851 

while isinteg -fix will  fix items at the store table level.. does not gatantuee
you will be able to open emails or attachments as the bad pages have been have been deleted by /p command

Thank you
Dhruv
0
 

Author Comment

by:omnisys
ID: 33521073
There was nothing wrong with the edb. We had to run /p /createstm because the .stm was the problem as it was corrupted during the defrag. We knew we would lose any mail held in the .stm. We are not hoping to open/recover any of the problem emails in the information store we just want to delete them but cannot. All the clients are outlook running in cached mode so we can recover any emails from the ost files on the local machines.

My question was really about the space required for running isinteg so thanks to sunnyc7 for the answer on that one.
My research has suggested that insinteg -s SERVERNAME - FIX -Test Alltests   will, if successful, allow us to delete these corrupt emails. I was wondering if anyone had found themselves in the same or similar situation and could advise?
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 28

Expert Comment

by:sunnyc7
ID: 33521175
omnisys - the emails are actually in the transaction logs I believe, not in STM files.
The STM file contains the mime data
http://www.messagingtalk.org/what-is-the-difference-between-a-stm-file-and-a-edb-file

If you are going to lose emails, that will be because the log files were not committed to the database.
That's why I was asking you about log-replay using eseutil /CC

Isinteg will run fine.
you will have to run it multiple times till you get ZERO errors. Same command.

I have done eseutil /p /d's many times, but didnt have to create STM files.

Let me know if you have any other questions.
0
 

Author Comment

by:omnisys
ID: 33521366
Thanks again sunnyc7. Do you think it's worth running /cc at this late stage? The 'disaster' was the weekend before last and we've backed up successfully every night since. Our main issue is just to get rid of the inaccessible emails.
0
 
LVL 28

Expert Comment

by:sunnyc7
ID: 33521394
I dont think /CC will help now :(

Infact a good test at this stage is this

eseutil /mh "c:\program files\exchsrvr\mdbdata\priv1.edb"

Check the shutdown state.
See the last date of full backup.
Check last committed log

start > run > calc
convert calc from DEC to HEX
enter the number there

that's the last committed log files.  in your c:\.....\log
0
 

Author Comment

by:omnisys
ID: 33521897
I ran eseutil /mh "c:\program files\exchsrvr\mdbdata\priv1.edb" before and after the repair and the shutdown state was clean. All the transaction logs are dated since last nights backup.
In your opinion, is it worth running isinteg - fix or are we stuck with these 'orphaned' emails?

Thanks again
0
 
LVL 28

Expert Comment

by:sunnyc7
ID: 33521924
You can run isinteg - fix.

then you can try eseutil /CC
then try to mount the DB.

We can give it a shot. Worst case it will error out.
0
 

Author Comment

by:omnisys
ID: 33522027
Ok, will give it go. Not sure when I'll get the opportunity to dismount the store but when I do I'll post the results.

Are we allowed to award points for good advice??

Cheers
0
 
LVL 28

Expert Comment

by:sunnyc7
ID: 33522089
ok hang on a minute @

I didnt know that stores were already mounted. In that case
Please dont run eseutil /CC

I was under the impression that after eseutil /p /d and isinteg the stores are not mounted.

If mail flow has started that will create new log files. It will be tough to get old log files to commit to exchange server and might corrupt the database.

Yes Definitely @ good Advice.
0
 

Author Comment

by:omnisys
ID: 33522551
The store has been mounted since we successfully ran /p /createstm. The reason for running isinteg -fix was to fix the problem with the orphaned emails and funnily enough I've just found this ExpertsExchange post where someone had the same symptoms and it worked for them!

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_21000880.html
0
 
LVL 28

Expert Comment

by:sunnyc7
ID: 33522684
Did you try isinteg -fix ?
0
 

Author Comment

by:omnisys
ID: 33523069
Not yet. Just wanted to be sure it was the right thing to do as we appear to be in quite a unique situation and there isn't a lot of information on this particular problem.
0
 
LVL 28

Accepted Solution

by:
sunnyc7 earned 500 total points
ID: 33523193
Usually the process is
a) Create a Blank Database, when you start defragging your EDB
Start mail flow using that. So that users can send / receive emails and Exchange is not out of action.
b) Do your eseutil's etc.
run isinteg's etc
run eseutil /cc
c) Load up the database in recovery storage group
d) Merge the EDB from RSG > to FSG

Given that you have already mounted the database, at this point we dont have anything other than isinteg -fix to test.
0
 

Author Comment

by:omnisys
ID: 33529283
I will give it a go and poast the results. Cheers.
0
 

Assisted Solution

by:omnisys
omnisys earned 0 total points
ID: 33929291
I was finally able to run isinteg -fix last weekend and we are now able to remove all the orphaned emails.

Thanks sunnyc7 for all your help.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Following basic email etiquette rules will help you write a professional email and achieve a good, lasting impression with your contacts.
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question