Hi,got a very weird morning with my exchange server.just did my usual checkup when i saw this event: ":An error occurred on database "Sixth Storage Group\****SGroupName****". Function name or description of problem: SLINK::EcUpdate Error: 0x8004010f " it showed up 8 times (exactly the same event). Also There is no real issue or problem with the mail boxes in that storage.culled not found any thing on the web.can anyone help?

Hi,Please have a look at this post,maybe it will be helpful.http://www.eggheadcafe.com/software/aspnet/28476801/-event-1025-slinkecu.aspxFrank Wang

Hi, It could be some kind of Logical corruption to the database. You should Run ISINTIG utility on the database to fix it. See more on this below. http://www.winserverkb.com/Uwe/Forum.aspx/exchange-admin/49846/Event-1025-SLINK-EcUpdate Hope this helps. Thanks.Vishal Ramnani | MCITP - Exchange 2007 | MCSE Messaging | MCTS - Win 2008 Config

Have you seen below article? Event ID 1025 is logged two times in the Application log with the "EcGenerateNRN: Error: 0x80070005" and "EcGenerateReadReport: Error: 0x80070005" error codes on a computer that is running Exchange Server 2003 or Exchange 2000 Server http://support.microsoft.com/kb/899393Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

Hi,first, thank you all!but... as far as i read all of those article are abut exchange 2000 and 2003, my exchange server is 2007 SP2 (probably should have said it before).

i couldn't find anything either but i think you should try ISINTEG anyway. Thanks. Vishal Ramnani | MCITP - Exchange 2007 | MCSE Messaging | MCTS - Win 2008 Config

well... if that's what you all say... let us defrag! i'll update how it went.

On Tue, 17-Nov-09 06:55:03 GMT, rrdor wrote:>>>well... if that's what you all say... let us defrag! i'll update how it went. Isinteg isn't Eseutil.If you're going to defrag the database that's okay -- but it won't fixany problems with the internal organization of the data. Just be sureto run isinteg after eseutil completes -- and run it at least twice.The 1st execution of isinteg is going to spew a bunch of fixes,warnings, and maybe an error or two. Run it again. If there were stille fixed in the 2nd pass, or if there were stillwarnings and errors, run it again. In most cases running t twice isall that's necessary, but sometimes a fix made in the 1st pass turnsup something wrong in the 2nd pass, etc. You want to run isinteg untileither there are no more fixes, warnings, or errors -- or until thenumber of warnings and errors no longer changes and there are no fixesbeing made.After that, be sure to pay attention to the fact that the log filesfor the database (and, therefore, the storage group) are no longerusable. Make a full (normal) backup of the storage group immdiatelyafter remounting the database.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

well... if that's what you all say... let us defrag! i'll update how it went. Hi,Haveyou defraged the database? And any update?Frank Wang