Archive for 'solutions'
Event Id 1159 While Backing Up Exchange Database
March 10th, 2010. Published under solutions. No Comments.
With the following event ID in application log, the information store gets dismounted frequently and hence none of the operation can be performed with completeness: Event Type: Error Event Source: MSExchangeIS Event Category: General Event ID: 1159
Description: Database error 0xfffffd9a occurred in function JTAB_BASE::EcUpdate while accessing the database ““. Some of the users also report that they have discovered unclean backups due to this error. The backups die after a few stage of completion. The problem is critical as at the time you need Exchange Server recovery, having the full and good backup is must. Actually, this problem arises because of large numbers of uncommitted ESE (Extensible Storage Engine) log files in the storage group, which has a limit to keep 1024 transactions log files at a time.
As soon as this number reaches to 1008, the unusual behavior of dismounting along with the mentioned error gets started, resulting glitches in the on-going process of backups. Mostly, restarting the MS Exchange Information store service will solve the problem but the ESE log files created while the backup process may stop the backup software to respond. As a result, the backup does not get completed. Before you could realize this fact, if the corruption in the database occurs; you left to look for the alternatives for EDB recovery. Though Exchange Server gives you an inbuilt utility called Eseutil, but I would recommend not to use this as you have better option in the form EDB repair software. The inbuilt utility work out Exchange Server repair by deleting the corrupted pages, rather EDB recovery software would give you the safe results.
Exchange Server recovery software have intuitive look, read-only nature and superb conducting stuff for complete EDB repair. Stellar Phoenix Mailbox Exchange Recovery can work most effectively to have Exchange Server repair. This uses the powerful scanning algorithms to extract the mailboxes from the corrupted database. This EDB recovery application will give output in the form of PST files. You can get all database objects recovered including e-mails, notes, journals, appointments, tasks and further.
Event Id 474 in Exchange Server
March 9th, 2010. Published under solutions. No Comments.
Errors are a part of each application, but those causing data loss are really hard to accept. MS Exchange Server is a widely used application, but the problem as follows can in fact make you think of Exchange Server recovery options: • The connected users find it impossible to send or receive e-mail messages or start Outlook.
The application log signifies you of faults with the database with the event ID 474 and error messages like: “Information store “2680″ the database page read from the file “C:\Program Files\Exchsrvr\mdbdata\priv1.edb” at offset 4050944 (0x00000000003dd000) for 4096 (0×00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 1537063750 (0x5b9dbb46) and the actual checksum was 1536998214 (0x5b9cbb46). The read operation will fail with error – 1018 (0xfffffc06).
If this condition persists then please restore the database from a previous Backup”
The Exchange MTA (Message Transfer Agent) may not start at all All these issues are the clear indicative that the information store database of Exchange Server, which possesses all the EDB and STM files, has got corrupted. This is the critical situation as all of the mailboxes are at the risk of complete loss. If you will search for the reason what causes the event ID 474 to occur, you will find that this can be out of two reasons, either the firmware problem or hardware malfunctions. So depending upon the cause, the EDB recovery way can be accepted. Nothing can be greater; if you have the backup of the database or rather you can also try to move the mailboxes to some other Exchange Server system and then copying the transaction log files for complete Exchange server repair. However, if you look to most working options for EDB repair; you would discover the name of EDB recovery software and services. The cases where no physical harm is bothering the storage media, Exchange Server repair software would do the commendable job or else you need to take help through Exchange Server recovery services. At different stages of EDB repair services, experts also make use of the software utilities to give the results. So you need to choose the EDB recovery help which is complete in each respect. Stellar Information Systems Limited is a place where you find all the solutions for EDB recovery.
The Exchange Server repair software called Stellar Phoenix Mailbox Exchange Recovery software has the best scanning procedure to repair and restore the corrupted database due to logical problems. However, for Exchange Server recovery services, you would find Class 100 Clean Rooms availability and expert conduct of EDB recovery associates. They have all the tools and applications to recover the database intact.