Exchange 2007 SP2 On December 3, around 12 PM (12:00) the Application Log of Event Viewer was filled with dozens (if not hundreds) of these Event ID 1025 Warning messages: An error occurred on database "First Storage Group\Mailbox Database". Function name or description of problem: SLINK::EcUpdate Error: 0x8004010f Reading another discussion about this error, I noticed that it was recommended to run ISINTEG with the -FIX and -TESTS parameter. Preparing to do this tomorrow, I noticed, however, in a Technet article concernant isinteg that the -FIX option: "[This option] tests and corrects errors in the information store that you specify. Therefore, it is best to use this option only when instructed to do so by a Microsoft Customer Support Services representative." Do you think my situation, as I described it, warrants running first, perhaps, the eseutil /g and then the isinteg commands? This is what I have for ISINTEG syntax: isinteg -s servername -fix -test rowcounts isinteg -s servername -test alltests #############################3 Note: - There have been no more of these warnings for 1 week. - Email functions normally in every respect (or at least for the components that we use). Please advise. Thank you in advance!

Hmmm... http://technet.microsoft.com/en-us/library/bb125144(EXCHG.80).aspx Looks like I would only (?) run this for the 1025 Warning message: isinteg -test search Can someone (from MS if possible) please confirm? Perhaps I should run the above and post resulting logs?

Backup the database offline before you do anything with ISinteg or ESEutil I wouldn't bother running the /G since it will only tell you if you have an issue an will do nothing to fix it. First run "isinteg -s servername -fix -test alltests" and run this until there are 0 errors. i.e. at the end of the run it will tell you how many errors remain and if they are greater then zero then run the command again. If the error you are getting persist then run ESEUTIL /D and then "isinteg -s servername -fix -test alltests" and run this until there are 0 errors Troy Werelius www.Lucid8.com

I thought it would be safest to run this test, since it is read-only (unlike -fix), and see if there were any errors: isinteg -s Server1 -test alltests Unforttunately, it will not run. Why not? [PS] C:\>isinteg -s Server1 -test alltests Databases for server Server1: Only databases marked as Offline can be checked Index Status Database-Name Storage Group Name: First Storage Group 1 Offline Mailbox Database Storage Group Name: Second Storage Group 2 Online Public Folder Database Enter a number to select a database or press Return to exit. 1 You have selected First Storage Group / Mailbox Database. Continue?(Y/N)y Isinteg: the request to cancel verification process failed. Isinteg: the request to stop verification process failed. The verification has probably been interrupted. Please review the log file for more information. [PS] C:\>isinteg -s Server1 -test search Databases for server Server1: Only databases marked as Offline can be checked Index Status Database-Name Storage Group Name: First Storage Group 1 Offline Mailbox Database Storage Group Name: Second Storage Group 2 Online Public Folder Database Enter a number to select a database or press Return to exit. 1 You have selected First Storage Group / Mailbox Database. Continue?(Y/N)y

Sounds like: http://support.microsoft.com/kb/941775 An error message occurs when you run the "Isinteg" command on a newly created Exchange 2007 database

That could very well be. I am still at Exchnage 2007 SP2 (no rollups). By the way, where are these logs located? Log File The log file enables you to specify the log file for output. Defaults: Private. Database path of private DB\Isinteg.pri Public. Database path of public DB\Isinteg.pu

Logs should be in the directory with the databases However as the article Andy sent you over says that you should install the SP2 RU http://support.microsoft.com/kb/971534/ or IMO you should just jump to SP3 http://www.microsoft.com/downloads/en/details.aspx?FamilyID=1687160b-634a-43cb-a65a-f355cff0afa6&displaylang=en Troy Werelius www.Lucid8.com

1. Logs should be in the directory with the databases I see a folder named "catalogdata-xxxxx-xxxxx-xxxxxx-xxxxx etc I see file named "Mailbox Database.edb" > (this is our MBX DB) That's all. Hidden files and folders are checked to be shown.

Hmm hard to say have you tried searching your drives for *.PRI I would update to the SP3 RU or SP3 as previously stated and then try again BTW you DID take the database you wanted to run this agings OFFLINE, i.e. DISMOUNT it first, yes? Troy Werelius www.Lucid8.com

3. BTW you DID take the database you wanted to run this agings OFFLINE, i.e. DISMOUNT it first, yes? Affirmative (yes). These were the commands I used (note: I ran ESEUTIL /G just before for the heck of it, which would not have been possible if the DB was mounted): [PS] C:\>Get-MailboxDatabase Name Server StorageGroup Recovery ---- ------ ------------ -------- Mailbox Database MailServer1 First Storage Group False [PS] C:\>Dismount-Database "MailServer1\Mailbox Database" Confirm Are you sure you want to perform this action? Dismounting database "MailServer1\Mailbox Database". [Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"): y [PS] C:\>eseutil /g "E:\EXDB\Mailbox Database.edb"

1. Hmm hard to say have you tried searching your drives for *.PRI Yes, but using the GUI. I've NEVER been able to get used to this since Vista / W2K8. Nothing showed up. So I just tried it now the old fashioned way: C:\>dir /s *.pri [snip] isinteg.pri 1 File(s) 292 bytes Note: yes, I had moved the MBX DB to a different spindle in accordance with best practices (OS, DB, Logs on different RAID arrays). I'll take a look at that file now.

This forum's software just obliterated my formating again! Anyway, to summarize, I found it in the DEFAULT location of the MBX DB, not on the spindle where I moved the DB.

Here you go guys, for what it's worth: Started: 12/11/10 07:25:06 Server name: MailServer1.myDomain.loc Database name: First Storage Group\Mailbox Database Output log: isinteg.pri Check mode: check only Options: -log -RefDbLoc -Test testSearch Error: FULLCHKMGR::EcReadRowCountGlobalFlag failed with error JET_wrnColumnNull So it looks like I'll have to install the RU - or simply SP3.

As stated earlier and as the article Andy sent you over says that you should install the SP2 RU http://support.microsoft.com/kb/971534/ or IMO you should just jump to SP3 http://www.microsoft.com/downloads/en/details.aspx?FamilyID=1687160b-634a-43cb-a65a-f355cff0afa6&displaylang=en Troy Werelius www.Lucid8.com

Following up for anyone who might come across this post in the future. Installing RU5 resolved the issue and I was able to run isinteg and fix the errors. (Looks like even RU1 would allow this too - http://support.microsoft.com/kb/941775) I opted not to go straight to SP3 since that requires a schema update and would require more planning - and probably downtime.