An Error Occurred On Database First Storage Group Slink
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered function name or description of problem: slink::ecupdate error: 0x8004010f by: EventID 1025 MSExchangeIS Mailbox Store Previous Versions of Exchange event id 1025 exchange 2007 > Exchange Previous Versions - Administration, Monitoring, and Performance Question 0 Sign in to vote At pfdavadmin 2:54 PM today, the following error message was logged 55 times:An error occurred on the database "First Storage Group\Mailbox Database"Function name or description of problem:
Isinteg
SLINK::ecUpdateError 0x8004010fEvent ID is in subject line.Windows 2008 SP1Exchange 2007 SP1 RU9Is this something I need to act on? Is it serious?This is the first time this has occurred. It has never been logged before.Should I follow the procedure outlined here:http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_21170636.html???????????? Tuesday, February 09, 2010 9:21 PM Reply | Quote Answers 0 Sign in to vote Generally speaking you can ignore these events.Active Directory, 4th Edition - www.briandesmond.com/ad4/ Marked as answer by David M (LePivert) Friday, March 12, 2010 2:35 PM Friday, February 12, 2010 1:38 AM Reply | Quote All replies 0 Sign in to vote Nothing since. No one has mentioned any problems.Question:eseutil /gandisinteg -test alltestsare read only operations and involve no risk of data loss unlike eseutil /p or (?) isinteg -fixIs that right?Assuming that these tests are the appropriate response...Anyone? Wednesday, February 10, 2010 4:41 PM Reply | Quote 0 Sign in to vote Hi,Sorry for delay response.Eseutil /GUsing this tool to test database integrity is a safe approach because the check is performed in a read-only mode. It is important to detect specific types of anomalies or inconsistencies to take proper steps to fix the database. You should recover the database to a clean
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > SLINK::EcUpdate Error: 0x8004010f Want to Advertise Here? Solved SLINK::EcUpdate Error: 0x8004010f Posted on 2004-10-15 Exchange 1 Verified Solution 7 Comments 21,859 Views 1 Ratings Last Modified: 2013-02-20 Event Source: MSExchangeIS Mailbox Type: Warning Category: https://social.technet.microsoft.com/Forums/en-US/690330c3-859b-4f7c-96b7-846c00d8b87d/eventid-1025-msexchangeis-mailbox-store?forum=exchangesvradminlegacy General Event ID: 1025 An error occurred on database "First Storage Group\Mailbox Store". Function name or description of problem: SLINK::EcUpdate Error: 0x8004010f The above error popped up once this morning on my Exchange 2K Server, didn't notice it at all until the end of the day. I took a look at the MS KB on the issue and did the following: 1) Ran an eseutil https://www.experts-exchange.com/questions/21170636/SLINK-EcUpdate-Error-0x8004010f.html /g which reported NO curruption 2) Ran the offline defrag anyway to recreate the db 3) Ran some diags on my HD's to check for any I/O problems, no issues here 4) Ran a Full backup of the information store Question is, if my database wasn't currupt and the eseutil /g came up clean, why did I get this message? Also, if curruption DID come up, the MS instructions say to simply run the defrag. Does running the defrag actually repair the database? I thought you had to use the repair switch to do that. Thanks. 1 Question by:jschweg Facebook Twitter LinkedIn Google LVL 21 Best Solution bymarc_nivens Question 1: There are different types of corruption in Exchange. Running an eseutil /g will only show corruption at the Jet level (page damage, checksum errors, etc...). The error you are seeing Go to Solution 7 Comments LVL 10 Overall: Level 10 Exchange 10 Message Expert Comment by:munichpostman2004-10-16 I suspect that the corruption may have been a soft one, which means that no data was damaged and it was probably resolved during store maintenance. You have followed all of the correct troubleshooting steps and
not hundreds) of these Event ID 1025 Warning messages: An error occurred on database "First Storage Group\Mailbox Database". Function name http://www.networksteve.com/exchange/topic.php/Event_ID_1025_-_Run_ISINTEG_with_-FIX_parameter/?TopicId=21198&Posts=14 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, an error 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 an error occurred 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! December 10th, 2010 12:27pm 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? Free Windows Admin Tool Kit Click here and download it now December 10th, 2010 12:45pm 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