• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2285
  • Last Modified:

Error when running ISINTEG..!

The text below is the log which ISINTEG generates when we run the ISINTEG -PRI -TEST ALLTESTS. It would be most appreciated if you could shed some light on why we are getting this error.

Thanks

S2KI

Microsoft Exchange Information Store Integrity Checker v5.5.2653.22
Copyright (c) 1986-1997 Microsoft Corp.    All rights reserved.
Started:    11/05/03 07:50:45
Server name: bbpd-dby1-exc1.bbrail.com
Store path: E:\exchsrvr\MDBDATA\PRIV.EDB
Store size: 5752496128 bytes
Output log: c:\Exchtests.log
Check mode: check and fix
Options: -PRI -FIX -TEST ALLTESTS -L c:\Exchtests.log

The Information Store has not been shut down clean.
Hence enabling the Row Count/Dumpster Count test.
You may also specify -test rowcounts (or) -test dumpsterref to run these tests
Fix: Folder : Deleted Invalid Property 0x00000102 from Folders table.
Fix: Folder : Deleted Invalid Property 0x00000048 from Folders table.
Fix: Folder : Deleted Invalid Property 0x00000040 from Folders table.
Fix: Folder : Deleted Invalid Property 0x00000014 from Folders table.
Fix: Folder : Deleted Invalid Property 0x00000002 from Folders table.
Fix: Folder : Deleted Invalid Property 0x00000003 from Folders table.
Fix: Folder : Deleted Invalid Property 0x00000004 from Folders table.
Fix: Folder : Deleted Invalid Property 0x00000005 from Folders table.
Fix: Folder : Deleted Invalid Property 0x00000006 from Folders table.
Fix: Folder : Deleted Invalid Property 0x00000007 from Folders table.
Fix: Folder : Deleted Invalid Property 0x0000000B from Folders table.
Fix: Folder : Deleted Invalid Property 0x0000000D from Folders table.
Starting test 1 of 22, 'Categorization Tables'
Finished Categorization Tables. Time: 0h:0m:0s
Starting test 2 of 22, 'Restriction Tables'
Finished Restriction Tables. Time: 0h:0m:0s
Starting test 3 of 22, 'Search Folder Links'
Finished Search Folder Links. Time: 0h:0m:1s
Starting test 4 of 22, 'Global'
Finished Global, number of rows = 1. Time: 0h:0m:0s
Starting test 5 of 22, 'Delivered To'
Finished Delivered To, number of rows = 129. Time: 0h:0m:4s
Starting test 6 of 22, 'Search Queue'
Finished Search Queue. Time: 0h:0m:0s
Starting test 7 of 22, 'Timed Events'
Timed event are : Expiration = 4,
Finished Timed Events, number of rows = 4. Time: 0h:0m:0s
Starting test 8 of 22, 'reference table construction'
ref table construction on INID returned JET_errKeyDuplicate

. . . . . SUMMARY . . . . .
Total number of tests : 22
Total number of warnings : 0
Total number of errors : 0
Total number of fixes : 0
Total time : 0h:0m:5s
0
S2KI
Asked:
S2KI
  • 6
  • 4
1 Solution
 
AicoCommented:
Have you tried installing the latest service pack? Service Pack 4 for Exchange 5.5?
0
 
S2KIAuthor Commented:
Yes the latest Service Pack is installed.
0
 
AicoCommented:
support.microsoft.com has several documents concerning the JET_errKeyDuplicate error. But why do you want to run ISINTEG, do you have any problems with the current Exchange database?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
S2KIAuthor Commented:
the exchange information store is crashing on a regular basis, leaving the following errors in the server logs.

7201 -Background thread FDoMaintenance encountered a problem. Error Code .......
and also
1101 - Error 0x8004010f  Occured during Background cleanup on message No ........


The Knowledge base recomends running the ISINTEG utility
0
 
AicoCommented:
Is it a clustered Exchange server or single machine?
0
 
AicoCommented:
By the way. It wouldn't hurt running the Service Pack again.
0
 
S2KIAuthor Commented:
It's clustered, but it is the private information store on our exchange server which is causing the problem.

Just to try and give you some more info, we recently had to delete a mailbox in raw mode because it was corrupt and it seemed to be the only way we could get rid of it..!
0
 
AicoCommented:
I suppose you checked the support documents of Microsoft concerning this error in combination with clustered exchange servers?
0
 
S2KIAuthor Commented:
We have been in touch with the other parts of the business, who's exchange servers are clustered with our's. Some of the people in the other parts of the business are quite well informed when it comes to exchange matters, and they have looked at the logs but can't give a solution, hence the reason for my post. It is very rare that an exchnage problem can't be fixed in house, which leads me to believe that this is a strange error. Unfortunately, although there are people within our organisation who know a lot about Exchange I don't think we could call any one an expert.

Sorry to go off topic a bit, I have not checked any documentation to do with clustered servers, because it did not seem relavent as the problem is a local one. No body else is getting this error.

To be fair to myself, I do not have the greatest knowledge of exchange, especially the back end stuff, like the databases etc.
0
 
AicoCommented:
Ok, I understand. Most of the documents on support.microsoft.com recommend installing the latest Service pack when this particular problem occurs. I know that there are post-SP4 patches available for Exchange 5.5. You might try these. You can find these by searching the download section of Microsoft.

Also in the next documents Microsoft mentions a registry key which might cause the problem. You can take a look at these too.

http://support.microsoft.com/default.aspx?scid=kb;en-us;178311

http://support.microsoft.com/default.aspx?scid=kb;en-us;168309

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now