I have 4 storage groups, each with one database, on two Exchange 2007 SP2 mailbox servers. Three of the four database are now getting event ID: 1025, source: MSExchangeIS Mailbox Store, "An error occurred on database "SG1\mailDB1". Function name or description of problem: SLINK::EcUpdate Error: 0x8004010f." I called Microsoft support, and they said to either run ISINTEG (would take too long) or to create new databases and move users over, skipping corrupted messages. So I'm doing the latter. All four of the existing databases were configured to use Local Continuous Replication. I've now built two new servers with only the mailbox role but without LCR due to lack of disk space. I've moved only one mailbox so far as a test, and now that I moved it, the SG/database in question gets this error on backups: event ID: 225, source: ESE, "MSExchangeIS (2836) SG5: No log files can be truncated." I obviously cannot move forward until I have this resolved. I found several people mentioning to check this key with ADSIEdit: CN=Configuration\CN=Services\CN=Microsoft Exchange\CN=<org name>\CN=Administrative Groups\CN=Exchange Administrative Group (FYDIBOHF23SPDLT)\CN=Servers\CN=<Servername>\CN=InformationStore\CN=<Storage Group Name> But I don't even have a "CN=Configuration" container, much less anything below it. Our Active Directory is Windows 2003 R2, and these two new mailbox servers are Windows Server 2008 (not R2). All Exchange servers run 2007 SP2. Everything is Standard Edition. I also noticed that when I moved the mailbox, it appears Exchange disabled the LCR on the SG/database I moved from and changed it from 'healthy' to 'suspended.' I just re-enabled that. I am stumped as to where I go from here. Any help very much appreciated! layout: Exchange1 -- client access role, Exchange2 -- hub transport, mailbox using LCR, Exchange3 -- mailbox using LCR. The new ones are Exchange4 -- mailbox without LCR, Exchange5 -- mailbox without LCR. We hope to decommission Exchange3 when all users are moved.

When opening ADSI Edit, connect to the Configuration name space. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Thanks, that got me in. The only thing listed under the CN=InformationStore keys is CN=SG5 with CN=mailDB5 under it. Format is the same for all 4 new storage groups, each storage group showing its database. I looked at the older servers and they are identical, even though they use LCR (and show as 'healthy' in the console) and the new ones don't. I don't see a msExchStandbyCopyMachines key at all. Any ideas on my next step? Since they're brand-new, no config has been done to them beyond creating the storage groups and databases..

I reread your original post and I don't really understand what your problem is. If your backup can't truncate log files, then focus on finding out why it doesn't. That's likely a problem with the backup program or VSS. Are there any messages in the event log around the time the backup is running that tell you anything?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

What type of backup are you doing? Full/Incremental/bring level or what? lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

How do you backup the database, via NTBackup or other third party software? Please assure that only Full backups and Incremental backups will purge the committed transaction logs. Meanwhile, I would like to share you the following article to troubleshoot the event ID 225. http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=6.5.7596.0&EvtID=225&EvtSrc=ESE&LCID=1033 Thanks. NovakPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Sorry for muddying the issue: It's event ID: 225, source: ESE, "No log files can be truncated." I'm trying to move to new mailbox servers to get past this logical corruption I have in other databases. But until I get this log deletion issue resolved, I cannot use the new boxes. Some backups they get deleted, others they do not. It's very inconsistent. I have tried with both NTBackup and with NetBackup v.7.1.0. Always full backups, only one at a time.

Just thought I'd post what appears to be the answer... drives me nuts when people post issues & then never bother posting the outcome for others. Appears it was just me being overly-cautious! I inherited this mess, and all the current databases have logical corruption, so I need to vacate them. I wanted to be absolutely, positively that certain that everything on the new server was in flawless shape, because MS refuses to help on the old stuff because it's virtualized (VMware vSphere 4.1, Win2K3 R2/Exchange 2007 SP2). So I was running my backups when not enough had changed to commit any logs. I'd send test emails back & forth with attachments, but it just didn't generate enough. I was too nervous to move any users besides myself and a few others until my backups worked the way I expected them to work half-a-dozen times in a row. That explains the event logs about not truncating logs. Now that I'm actually generating substantial logs on every storage group/database between backups, it's working properly and purging them.

Thanks for posting. Glad that you're all good.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."