Dirty Shutdown: 0

Hi. Sorry if this is a silly question, but I'll ask it anyway.
Does "Dirty Shutdown: 0" in an ESE event 327 mean "Dirty Shutdown: No", i.e. the database shut down cleanly? I'm guessing "0" means "No"; and that "1" would mean "Yes, it *was* a dirty shutdown",
but I can't find this explicitly stated anyahere.
Reason I ask is that I dismounted a mailbox database in order to move EDB and log paths, the move failed, and the database then wouldn't mount for an hour. (After 30 auto-retries it succeeded.)
In looking for the cause of the problem, I found, among other Application Log entries:
"Information DD/MM/YYY HH:MM:SS ESE 103 General Information Store (3720) <Database-Name>: The database engine stopped the instance (4). Dirty Shutdown: 0"
and I'm trying to establish whether this means the shutdown was or wasn't dirty. Thanks.

Those are normal events and are to be expected when activating another store (1) versus dismounting and remounting a store (0).
Also the DB when mounted is ALWAYS in a dirty state and upon completion of a proper dismount it should be clean.
before you do a move I would take a look at the # of transaction logs since the more there are the longer it will take to complete the move. if there are an excessive # of logs you may want to do a full backup first to truncate the logs and then do
the move
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Similar Messages

Exchange DataBase is in Dirty ShutDown State

Hi ALL,
I am not able to mount the Data Base in Exchange Server 2010, I have run “Eseutil /mh” and confirm that Data base is in Dirty shutdown state.
Now, can any buddy tell me the step by step procedure to make it in Clean shutdown state.
Subs

HI Shubi,
Zahir have provided very good article to make clean shutdown your DB. Please try to run "eseutil /mk" swicth against check point file and see if any remain log files is not commited. In this case you can use "eseutil /r /e01" (Base file can be change) and
try to recover it.
Some more information.
Exchange Database Recovery – Using eseutil commands:
http://msexchangeguru.com/2009/07/12/exchange-database-recovery-using-eseutil-commands/
http://smtp25.blogspot.com/2007/05/eseutil-in-exchange-2007-and-lost-log.html
Anil MCC 2011,ITIL V3,MCSA 2003,MCTS 2010, My Blog : http://messagingschool.wordpress.com

Exchange 2010 Dirty Shutdown

hi ,
We have DAG implemented Server A & Server B , Server A is on production enviroment & server B is holding passive database when I am checking health of Server B database it is showing database is dirty shutdown . How can I fix that please help

How you check exchange health which likely to show as "database is dirty shutdown" ?
Though, you can run with Eseutil.Exe tool to repair corrupt database and recover the mailbox again.
Check-out this
link for detail information and step-wise process.
However, sometimes Eseutil does not correct the problems at the application level. In such scenario, you can have try this
utility which would a best approach and good solution in order to repair corrupt exchange database and restore all the data content in previous used values.

Exchange crash during move request, new DB in dirty shutdown

I had a hardware failure (storage controller in VM environment) during a mailbox move request to a new DB. After fixing that and rebooting, the old database came up and is fine which is great. The new database is in a dirty shutdown state right now with a few completed but most are still queued or in progress. If I try to remove the request on the completed mailboxes it has a message along the lines of, couldn't connect to mailbox database, it could be dismounted. Do you want to orphan the move request for user XYZ?
Will this cause any problems? I would like to remove the move requests and proceed recovery and repair of the dismounted DB. Thoughts?
Thanks,
Josh
This topic first appeared in the Spiceworks Community

Hi,
Thank you for sharing the resolution.
Please 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. Thanks Gen Lin-MSFT

How to recovery from a dirty shutdown

We had a powercut and my Exchange 2007 server has reported some dirty shutdown. Any one with information on how I can recover the database.
This topic first appeared in the Spiceworks Community

You may need to go to bios setup and go to boot setup and designate the optical drive as first boot device.

Database clean shutdown status Issues with ESEUTIL

hi all i am currently trying to go the process of taking my database backup from a dirty shutdown into a clean shutdown state with ESEUTIL.
a user has lost some items from there sent items folder so i am restoring it for them.
i have checked the state of the database and it shows dirty shutdown so i am running the command below to replay the log files.
C:\>eseutil /r E00 /l "C:\database recovery\Mailbox Database 1813862868\data" /d "C:\database recovery\Mailbox Database 1813862868\data" -verbose
it begins to process but them comes up with the following error suggesting i use the /a argument, i cant seem to find much information on this wondered if anyone had any suggestions. i ran the -verbose command to help try and narrow it down
can some one help with what the /a argument does or if they have had this issue themselves a possible way to resolve it.
many thanks
Gordon

Thanks for the information and;
1. I would start with your VSS backup provider Cloudberry since as part of the backup validation it shouldn't have passed if those files were missing and upon restore of the EDB it should have also provided all needed Log files. Now its possible they
were missing prior to backup and that could be for any number of reasons, i.e. Anti Virus if improperly configured could have deleted or quarantined them etc, however more concerning is that the backup provider called that backup good. I would look at
the backup logs to see what they reported as its possible they did report an issue during backup. The other possibility is that the files are within the backup but didn't restore for some reason and for that you would need to do another test restore
to validate. Also could be that upon restore the logs were deleted by your Anti Virus provider and of course you can check the AV logs and quarantine...
2. Running a /P against a restored backup for item level recovery is not as big of a deal as it would be if you were putting the db back into production. True you can still lose data with a /P but for what you were doing not an issue IMO especially if
you recovered the needed data.
3. The log loss also was in the middle of the needed log chain which is never a good sign. Sometimes you can get by that issue by removing all logs after the missing log file and just trying to play it up to that point in time.
P.S. If you are missing the log files post backup and want to avoid running a /P on an inconsistent/dirty database the only choices are to;
A: find the logs (Look at AV logs and quarantine or perhaps re restore the files again from backup)
B: do the /P
C: Check out our DigiScope product that can bypass most /P issues by using our Forensic mount to open the database and then extract the needed information to PST or restore it directly to any mailbox on the original or alternate exchange server (even alternate
versions i.e. 5.5-->2000-->2003-->2007-->2010-->2013 etc.)
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Installation problems with Solaris 8 on Intel

Howdy,
I am having some problem with my installation of Solaris 8 on Intel. I am installing the system on a P133 (Asus TX97 motherboard). When I first start the installation and perform the system scan I get the following error:
The PnP ISA: IDE Controller programable device was unable to be programmed.
This could be caused by two possible reasons:
- Lack of resouces available
- There is a conflict with the following already-existing device: 8086,7111 - Bus Mastering IDE Controller
When I bring up the View/Edit device settings and I scroll to the IDE controller there is an ! mark beside the PCI IDE controller. The controler is specifying: Bus 0, device: 1, function: 1 port 1F0-1F7, 3F6, 170-177, 376, E000-E00F, 0 IRQ 14, 15
Does anyone have any suggestions on how to resolve this conflict? I tried removing the PCI IDE interface and then installing a ISA IDE interfact (for IRQ: 14, IRQ 15 automatically put a PnP IDE controller there). This seemed to resolve the conflict but then I received a: No Bootable devices have been found.
If anyone can help out with how to resolve the conflict, or what the No Bootable Devices have been found error it would be greatly appreciated.
Currently there is a partition set up with NT on it, but I wish to basically get rid of everything on the HD and install Solaris on it. FYI, when I check the HD's in NT it mentions I/0: 1F0-1F7 IRQ 14 and also I/O 170-177 IRQ 15.
Any help would greatly be appreciated.
Regards,
S.

When I close down Solais in the CDE I am taken back to the logon screen
and I turn the PC off.Don't do that. If you simply turn off the PC, the OS has no chance to
write back cached / modified disk data back to the HDD - this is also the
reason why solaris has to check the filesystems on the next boot and apparently
has to repair filesystem defects.
What you have to do is shutdown the machine, before you can power it off.
Login as user "root" and use the command
init 5
or
halt
"init 5" will shutdown system services, by executing commands from
/etc/rc0.d/K* with argument "stop". Then it'll sync all modified disk blocks to
the HDD, kills all remaining processes and unmounts all filesystems. In this
state it's safe to power off the machine!
"halt" is a quick-and-dirty shutdown. It does not stop system services (the
/etc/rc0.d/K* commands are not run). But, it syncs all modified disk blocks
to the HDD, kills all processes and unmounts all filesystems. "init 5" is preferred,
especially if you have services like a database server running on the machine,
which needs to be cleanly shutdown. On the other hand, with a default solaris
installation and no extra services, a simple "halt" should be OK.
Btw. if multiple users are logged in on the machine, you should also have a look
at the shutdown(1M) command. "shutdown" sends warnings to the logged in
users that the machine is about to be shut down, ...

Failed attempt to move log and database paths

Hi. Can anyone offer any advice on what might have caused an attempt to move Exchange 2010 (SP3) mailbox database and log folder paths to fail? I can't diagnose it, and would appreciate any advice.
We have two databases in a two-node DAG, one mounted on each node. I removed the passive copy of each database before the move attempts. The first moved ok. The second failed. Here's a summary of what happened:
Task 1:
DAG-NODE-A ----------------------------DAG-NODE-B
MAILBOX-DB-01                               MAILBOX-DB-01
MOUNTED                                        HEALTHY (passive)
- Dismount database
- Remove passive copy.
- Move logfolder path from R: to L:
and move EDB path from S: to M:
- Succeeded.
- Mount datbase.
- Re-add passive copy
All ok.
Task 2:
DAG-NODE-A ----------------------------DAG-NODE-B
MAILBOX-DB-02                               MAILBOX-DB-02
HEALTHY (passive)                           MOUNTED
- Dismount database
- Remove passive copy.
- Move logfolder path from R: to L:
and move EDB path from S: to M:
- Failed. Paths not moved.
- Database now won't mount.
- Database eventually mounts
after approx. 30 auto retries.
- Abandon attempt to move paths.
- Re-add passive copy.
END
Here's some more detail, included event log and shell output:
So, as per the above, with Mailbox-DB-01 (active copy on DAG-NODE-A), Exchange moved the paths without a hitch and I was then able to mount the database and re-add the passive copy. I then tried to move the paths for Mailbox-DB-02 (active copy on DAG-NODE-B),
but after a few minutes Exchange aborted the move, outputting errors to the Shell, the application log and the MSExchange Management log. A second attempt failed because Exchange found that "The .edb file path is not available. There is already a file
named M:\Mailbox-DB-02\Mailbox-DB-02.edb" - Exchange had created an EDB file in the target location, but the source EDB file was still in the source location and the path was unchanged. Rather than re-trying the move again, I decided to try to mount the
database, to check it was ok, but it wouldn’t mount.
I left it alone for an hour or so to have a think about what to do, came back to it and found Exchange had mounted the database (without moving the paths) after around 30 automatic retries. I was then able to re-add the passive copy.
I’m not keen to re-try the move without knowing why it failed, why the database then wouldn’t mount, and why it subsequently recovered. Any advice would be appreciated. Many thanks.
Output included
- a WinRM error in the Shell’;
- an App Log error event from my attempt to mount the database after the move failure, saying an attempt to open the EDB file for read / write access failed with system error 32 because the file was being used by another process;
- events recording failure to configure and start the database, and noting a serious error which caused it to terminate its functional activity;
- Event ID 3154 from MSExchangeRepl, saying an Active Manager operation failed / database action failed / MapiExceptionCallFailed;
- Event ID 10056 from source MSExchangeIS Mailbox Store in the App Log just before Exchange successfully mounted the troublesome database, saying “Patch all ID counters for database Mailbox-DB-02.”
One other thing which may or may not be relevant – the MSExchange Service Host service stops soon after being started on DAG-NODE-B (reboots have made no difference). On DAG-NODE-A, it runs consistently.
Here’s what seems to me to be the most relevant output from the Application Log and the MSExchange Management Log on DAG-NODE-B, and from the Exchange Shell:
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 10:46:19 ESE 327 General "Information Store (3720) Mailbox-DB-02: The database engine detached a database (4, S:\Mailbox-DB-02\Database\Mailbox-DB-02.edb). (Time=6 seconds)
Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.000, [4] 0.000, [5] 0.000, [6] 6.188, [7] 0.156, [8] 0.016, [9] 0.015, [10] 0.016, [11] 0.031.
Revived Cache: 0"
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 10:46:19 ESE 103 General "Information Store (3720) Mailbox-DB-02: The database engine stopped the instance (4).
Dirty Shutdown: 0
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 10:46:19 MSExchangeIS Mailbox Store 9539 General The Microsoft Exchange Information Store database "Mailbox-DB-02" was stopped.
==================================================================================
DAG-NODE-B, MSExchange Management log
Information DD/MM/14 10:46:19 MSExchange CmdletLogs 1 General Cmdlet succeeded. Cmdlet Dismount-Database, parameters {Identity=Mailbox-DB-02}.
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 10:46:19 MSExchangeRepl 3161 Service Active Manager dismounted database Mailbox-DB-02 on server DAG-NODE-B.company.corp.
==================================================================================
DAG-NODE-B, MSExchange Management log
Error DD/MM/14 10:46:20 MSExchange CmdletLogs 6 General Cmdlet failed. Cmdlet Get-PublicFolderDatabase, parameters {Status=True, Identity=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx}.
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 10:46:21 MSExchange Assistants 9002 Assistants Service MSExchangeMailboxAssistants. Stopped processing database Mailbox-DB-02 (xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx).
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 10:46:21 MSExchange Assistants 9002 Assistants Service MSExchangeMailSubmission. Stopped processing database Mailbox-DB-02 (xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx).
==================================================================================
DAG-NODE-B, Application Log:
Error DD/MM/2014 10:51:08 MSExchange Search Indexer 104 General Exchange Search Indexer failed to enable the Mailbox Database Mailbox-DB-02 (GUID = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx) after 10 tries. The last failure was: MapiExceptionMdbOffline: Unable to
get CI watermark (hr=0x80004005, ec=1142)
==================================================================================
DAG-NODE-B, MSExchange Management log
Warning DD/MM/14 11:06:44 MSExchange CmdletLogs 4 General Cmdlet stopped. Cmdlet Move-DatabasePath, parameters {Identity=Mailbox-DB-02, EdbFilePath=M:\Mailbox-DB-02\Mailbox-DB-02.edb, LogFolderPath=L:\Mailbox-DB-02\Logs}.
==================================================================================
DAG-NODE-B, Exchange Management Shell output
Processing data from remote server failed with the following error message: The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote
Management service is enabled. For more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OperationStopped: (System.Manageme...pressionSyncJob:PSInvokeExpressionSyncJob) [], PSRemotingTransportException
+ FullyQualifiedErrorId : JobFailure
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 11:23:42 MSExchangeIS Mailbox Store 1000 General Attempting to start the Information Store "Mailbox-DB-02".
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 11:23:43 ESE 102 General "Information Store (3720) Mailbox-DB-02: The database engine (14.03.0162.0000) is starting a new instance (4).
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 11:23:43 ESE 105 General "Information Store (3720) Mailbox-DB-02: The database engine started a new instance (4). (Time=0 seconds)
==================================================================================
DAG-NODE-B, Application Log:
Error DD/MM/2014 11:23:53 ESE 490 General "Information Store (3720) Mailbox-DB-02: An attempt to open the file ""S:\Mailbox-DB-02\Database\Mailbox-DB-02.edb"" for read / write access failed with system error 32 (0x00000020): ""The
process cannot access the file because it is being used by another process. "". The open file operation will fail with error -1032 (0xfffffbf8).
==================================================================================
DAG-NODE-B, Application Log:
Error DD/MM/2014 11:23:53 MSExchangeIS 9519 General "The following error occurred while starting database Mailbox-DB-02: 0xfffffbf8.
Failed to configure MDB. "
==================================================================================
DAG-NODE-B, Application Log:
Error DD/MM/2014 11:23:53 MSExchangeIS 9519 General "The following error occurred while starting database Mailbox-DB-02: 0xfffffbf8.
Start DB failed.. "
==================================================================================
DAG-NODE-B, Application Log:
Error DD/MM/2014 11:23:53 ExchangeStoreDB 215 Database recovery At 'DD/MM/2014 11:23:53' the Microsoft Exchange Information Store Database 'Mailbox-DB-02' copy on this server experienced a serious error which caused it to terminate its functional activity.
The error returned by the remount attempt was "There is only one copy of this mailbox database (Mailbox-DB-02). Automatic recovery is not available.". Consult the event log on the server for other storage and "ExchangeStoreDb" events for
more specific information about the failures.
==================================================================================
DAG-NODE-B, Application Log:
Error DD/MM/2014 11:23:53 ExchangeStoreDB 231 Database recovery At 'DD/MM/2014 11:23:53', the copy of database 'Mailbox-DB-02' on this server encountered an error during the mount operation. For more information, consult the Event log on the server for "ExchangeStoreDb"
or "MSExchangeRepl" events. The mount operation will be tried again automatically.
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 11:23:54 ESE 103 General "Information Store (3720) Mailbox-DB-02: The database engine stopped the instance (4).
Dirty Shutdown: 0
==================================================================================
DAG-NODE-B, Application Log:
Error DD/MM/2014 11:23:54 ExchangeStoreDB 231 Database recovery At 'DD/MM/2014 11:23:54', the copy of database 'Mailbox-DB-02' on this server encountered an error during the mount operation. For more information, consult the Event log on the server for "ExchangeStoreDb"
or "MSExchangeRepl" events. The mount operation will be tried again automatically.
==================================================================================
DAG-NODE-B, Application Log:
Error DD/MM/2014 11:23:54 MSExchangeRepl 3154 Service Active Manager failed to mount database Mailbox-DB-02 on server DAG-NODE-B.company.corp. Error: An Active Manager operation failed. Error The database action failed. Error: Operation failed with message:
MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-1032)
==================================================================================
NOTE:repeat events similar to some of the above continue until Exchange eventually manages to mount the database:
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 12:15:56 MSExchangeIS Mailbox Store 1000 General Attempting to start the Information Store "Mailbox-DB-02".
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 12:15:56 ESE 102 General "Information Store (3720) Mailbox-DB-02: The database engine (14.03.0162.0000) is starting a new instance (4).
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 12:15:56 ESE 105 General "Information Store (3720) Mailbox-DB-02: The database engine started a new instance (4). (Time=0 seconds)
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 12:15:57 ESE 326 General "Information Store (3720) Mailbox-DB-02: The database engine attached a database (5, S:\Mailbox-DB-02\Database\Mailbox-DB-02.edb). (Time=0 seconds)
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 12:15:57 MSExchangeIS Mailbox Store 10056 General Patch all ID counters for database Mailbox-DB-02.
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 12:15:57 MSExchangeIS Mailbox Store 1133 General Allocating message database resources for database "Mailbox-DB-02".
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 12:15:58 MSExchangeIS Mailbox Store 9523 General "The Microsoft Exchange Database ""Mailbox-DB-02"" has been started.
Database File: S:\Mailbox-DB-02\Database\Mailbox-DB-02.edb
Transaction Logfiles: R:\Mailbox-DB-02\Logs\
Base Name (logfile prefix): E03
System Path: R:\Mailbox-DB-02\Logs\
(Start Duration=00:00:01.844) "
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 12:15:58 MSExchangeRepl 3156 Service Active Manager successfully mounted database Mailbox-DB-02 on server DAG-NODE-B.company.corp.
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 12:16:06 MSExchange Assistants 9001 Assistants Service MSExchangeMailSubmission. Started to process mailbox database Mailbox-DB-02 (xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx).
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 12:16:09 MSExchange Assistants 9001 Assistants Service MSExchangeMailboxAssistants. Started to process mailbox database Mailbox-DB-02 (xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx).
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 12:16:12 MSExchange Assistants 9017 Assistants Service MSExchangeMailboxAssistants. Managed Folder Mailbox Assistant for database Mailbox-DB-02 (xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx) is entering a work cycle. There are 125 mailboxes on
this database.
==================================================================================
DAG-NODE-B, Application Log:
Information DD/MM/2014 12:16:30 MSExchange Search Indexer 108 General Exchange Search Indexer has enabled indexing for the Mailbox Database Mailbox-DB-02 (GUID = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx).
==================================================================================


If you used the steps outlined in this TechNet article - http://technet.microsoft.com/en-us/library/dd979782.aspx - then you should have been OK. I will say that I read one
article that said to work one database at a time, then when you are sure it is operational to go back and do the next, etc.
(I also assume by your shorthand at the beginning of this document that you performed the tasks on the active node when you did this work. If so, that's the best way to do it, so if it failed, it wasn't because you used the wrong steps or did them
on the wrong system.)

Can i get a mac mini to boot by default when plugged in?

I am searching very long for a solution for this:
I want my mac mini to start by plugging in or an external switch even if there was no power failure. (which can be set in the energy saver preferences, box checked))
I found a thread which partly seems to concern this question, but i am not sure, may be some members here with more knowledge than me could help me, i would be very pleased:
https://discussions.apple.com/message/12111266#12111266
there i found the following:
"edited /usr/libexec/upsshutdown to send "shutdown -hu now" in both a normal shutdown or UPS shutdown. the -u simulates a dirty shutdown (see man shutdown) so when the UPS does powercycle it brings the Mac back online." posting by Glenn Gerrad
This seems to me as if i could use this change just to simulate dirty shut down indepenedent of having this APC UPS this thread is about, but i am not sure how to start this change for i am not used to work with the terminal and im afraid of ruining something because i am really unsure about the whole meaning of this thread. May be someone experienced can help me what to do?
Thank you !
(at the moment i am using hibernate, which works but i would prefer restart, because i eperienced some strange things which i could avoid by a clean start up.)

1.) Open Automator (Applications) and choose "Application" on startup.
2.) Find "Run AppleScript" in the list on the left side
3.) Drag & Drop that action to the right side
4.) In the text field of the script insert
do shell script "sudo shutdown -hu now" with administrator privileges
5.) Save that application to your hard drive and you can double click it.
6.) When running that application you have to enter your password, and it will shutdown the mac.
7.) You can hard code your password to the program with
do shell script "sudo shutdown -hu now" with administrator privileges password "yourpassword"
But the password isn't encrypted in the Shell Script!
Be aware: double clicking that application will immediately shut down the computer without asking for saving changed files - they'll be lost!

Replay only particular logs (before a certain date) to restored Exchange 2010 database?

Hello,
I'm doing Exchange 2010 database full backup using windows server backup (windows 2008 R2) every weekend. I have a Mac user which Mac Outlook 2011 which somehow managed to corrupt his mailbox. I.e. on Wednesday many messages and contacts disappeared (all
contact gone) after his Outlook told his something about "corrupted database". I'm not sure what Mac Outlook did, but fact is that his mailbox has zero contacts and many inbox message are gone. Hard deleted items don't contain lost messages.
So I have DB backup from weekend before and weekend after. No circular logging, so all logs in place.
Is there a way how I can restore his mailbox back to the point in time? I want to restore his mailbox how it was on Wednesday morning. For it looks obvious that since I have log files from Monday to Friday, it should be possible to replay logs until certain
time.
I tried to did thick trick by removing Friday and Thursday logs and doing soft recovery, but got Operation terminated with error -543 (JET_errRequiredLogFilesMissing, The required log files for recovery is missing.) They indeed missing:
dbtime: 2221857861 (0x846edc45)
State: Dirty Shutdown
Log Required: 2895446-2895464 (0x2c2e56-0x2c2e68)
Log Committed: 0-2895465 (0x0-0x2c2e69)
Log Recovering: 2838005 (0x2b4df5)
Log required are logs from they day of backup, so they are really missed in that case, but that's what I want - restore DB with less/older logs to get back in time, when mailbox was not corrupted.
Is that possible?
Thanks

ok so the problem is you have the dreaded -1018 error and this is a very serious issue. -1018 is not a good deal at all, in short your DB has corruption within it
and it is usually caused by a hardware or firmware related issue. Most of the time these occur somewhere within the storage subsystem, i.e. firmware upgrade or lack of firmware upgrade, Controller issue, cabling, disk, disk arrays, etc, however they can
also be caused by memory upgrades or failures, Motherboard issues etc.   The -1018 tells you the DB is already damaged and if you see these its very bad and needs to be addressed ASAP else the DB's are sure to fail and the more stress you put on
them the faster the chance of failure, i.e. database backups, defrag;s and repairs etc are not recommended at all until you solve the hardware issue. So here is what I would recommend:
A: Lets try to ensure the box is stable and whatever caused the DB to get the -1018's is solved before we do anything else.
General Review: Whats changed recently? i.e. any hardware, memory, motherboard, any firmware updates on anything at all?
Event Log Review: Look at your Application Log, how long have these 1018's been occurring?   Look at your System event log for errors and pay close attention to any errors regarding disk, memory or MB and report back
Protect: I would dismount the database & copy it and any others off to a secure, safe drive that is NOT connected to this system
Action: Depending on what you find in your review there are really two options
     i: If you had a recent change that is easily identifiable you may be able to correct it and then we can look at finding a clean copy of the EDB and rolling up the logs OR we opt to repair the DB you have
     ii: if you cannot find the issue in short order then I would suggest that you build a new Exchange Server on new hardware and migrate your mailboxes immediately.
B: Once you have addressed the -1018 issue then;
1. We need to find a database from your backups that does NOT have the -1018 result code when attempting a rollup.
2. Once you have a non -1018 result you can then grab a fresh copy of the EDB along with all logs from that point forward and make a consistent DB via rollup up to the 18th as desired.
3. If you cannot find a good copy of the EDB then you are stuck with the latest data you have and should either move all mailboxes to a new EDB on that server but ONLY IF the source of the -1018 is found and resolved, else you will just be making thing s
worse. IF you CANNOT resolve the issue that causes the -1018 then build a brand new server and move all users over to it ASAP, else you are headed for a major failure on all users.
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Get-mailboxdatabasecopystatus -identity DBNAME | fl gives errors "The Microsoft Exchange Replication service encountered an error while attempting to start a replication instance for". DB is mounted and the DB copies are in healthy status.

We are getting a SCOM alert " Database copy isn''''t keeping up with the changes on the active database copy and has failed."
When we go to the mailbox server and check we found all the Mailbox DB's are mounted properly and their copies are in healthy state. Further digging to this problem we found that there are no critical events to this DB in the eventviewer.
When we runt he get-mailboxdatabasecopystatus -identity DBNAME | Fl then in the ErrorMessage section we get error "The Microsoft Exchange Replication service encountered an error while attempting to start a replication instance for . If the copy doesn't
recover automatically, administrator intervention may be necessary. Error: The directory is not empty."
ErrorEventID : 4126
In the event viewer we get a Information event 4114 saying the DB redundancy health check passed and in the details section we get the same error message mentioned above.
Also we observed that the "MSExchange Replication" counter "Failed" is set to 1 for this perticular DB but is is set to 0 for the other DB's. Tried restarting the MSEXChange replication service but still the "Failed" counter
is 1 and the SCOM alert is still active.
The version is Exchange 2010 SP3 UR5
Any clues???

Hi,
From your description, this issue only affect one mailbox datatabase.
Please use the Update-MailboxDatabaseCopy command to check result.
If it doesn't work, please dismount your active database copy and check if this is Clean Shutdown, if it's dirty shutdown, please bring to clean shutdown and mount this database copy. Then run the Update-MailboxDatabaseCopy command again to check result.
Best regards,
Belinda Ma
TechNet Community Support

#550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error.

Hi,
I created a mailbox few days before, everythign was working fine and suddenly when some one tried to send email on that mailbox it bounced back with following error:
There's a problem with the recipient's mailbox. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message, or provide the following diagnostic text to your system administrator.
Sent by Microsoft Exchange Server 2007
Diagnostic information for administrators:
Generating server: Mail01.abc.com
[email protected]
#550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error. The following information should help identify the cause of this error: "MapiExceptionNotFound:16.18969:9A000000, 17.27161:00000000CC000000000000000600000000000000,
255.23226:00000000, 255.27962:FE000000, 255.17082:0F010480, 0.26937:94000000, 4.21921:0F010480, 255.27962:FA000000, 255.1494:00000000, 255.26426:FE000000, 4.7588:0F010480, 4.6564:0F010480, 2.17597:00000000, 2.25805:00000000, 4.8936:0F010480, 4.14312:0F010480,
4.2199:0F010480, 2.25805:00000000, 4.8936:0F010480, 2.22957:00000000, 2.19693:00000000, 2.17917:00000000, 2.27341:00000000, 4.8936:0F010480, 4.17097:0F010480, 4.8620:0F010480, 255.1750:0F010480, 0.26849:0F010480, 255.21817:0F010480, 0.26297:0F010480, 4.16585:0F010480,
0.32441:0F010480, 4.1706:0F010480, 0.24761:0F010480, 4.20665:0F010480, 0.25785:EC030000, 4.29881:0F010480". ##
Original message headers:
Received: from Mailbox.abc.com ([fe80::892d:93d6:b1ac:b70a]) by mail01
([10.72.0.95]) with mapi; Fri, 11 Jan 2013 14:04:55 +0500
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: Anwar Amjad <[email protected]>
To: All-HEC <[email protected]>
Date: Fri, 11 Jan 2013 14:04:53 +0500
Subject: FW: Suggestions & New Arrival in HEC Library
Thread-Topic: Suggestions & New Arrival in HEC Library
Thread-Index: Ac3vHgwR50OLs2BnQuOzo9jWg4e1gQAvJtUw
Message-ID: <[email protected]>
References: <[email protected]>
In-Reply-To: <[email protected]>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: <[email protected]>
MIME-Version: 1.0
X-Auto-Response-Suppress: DR, OOF, AutoReply
After this error, i treid to send email again and there is no error and email was delivered. What was the cause of this error?
Hasan

Hi,
I tried to start seeding again but it is at same status. I will try again and hopefully it will get resolved.
But, yesterday i ran in to the most complex issue i have ever seen with Exchange.
There was a unexpected power cut at our datacentre due to which both the nodes went down.
After that both the nodes came up. But the all 3 databases were dismounted.
Therefore, i ran Eseutil /mh resulting dirty shutdown.
I was able to repair 2 databases.
But the 3rd one was not mounting with below error.
Microsoft Exchange Error
Failed to mount database 'Mailbox Database'.
Mailbox Database
Failed
Error:
Exchange is unable to mount the database that you specified. Specified database: XXXXX\First Storage Group\Mailbox Database; Error code: MapiExceptionJetErrorAttachedDatabaseMismatch: Unable to mount database. (hr=0x80004005, ec=-1216).
I was able to mount database somehow. There are 7 User mailboxes (Tier 1) on this database.
All emails sent to the users in this database are bouncing back with the below error.
This storage groups holds the mailboxes of my Senior Managements. And their mailboxes are down for almost 20 Hrs. I am spinning my head since yesterday but not able to find any fix. Can you please guide me in this concern.
Best Regards
K2
Kapil Kashyap

Active Directory Not Replicating

Hey Guys,
I have a Windows 2012 server but it has a demo license, this is also my DC. I am trying to create another DC and let it replicate so I can license the new properly and stuff. I have the DNS of each server pointing to each other as the primary and themselves
as the alternative. When I check my SYSVOL folder and go to domains, its empty, as I shutdown my original DC the other one the entries disappear and I get errors. When I go to the event log on my new DC I get errors with event IDs 1202 and 2213. Any assistance
with this issue i'm having will be greatly appreciated, thanks!
Regards,
Jevon.

Please follow this , it should help expecially this section:
For environments that have two domain controllers
Determine whether a dirty shutdown was detected (event ID 2213) on either domain controller. You may find the second domain controller
is waiting to complete initialization of SYSVOL, This is because after promotion, it will have logged a 4614 event that indicates that DFS Replication is waiting to perform initial replication, and it will not have logged a 4604 event signaling that
DFS Replication has initialized SYSVOL.
If content freshness is enabled on both domain controllers
If the second domain controller is waiting to perform initial synchronization (event 4614 logged without the 4604 anti-event), follow
the section of article 2218556 to
set the first domain controller as authoritative. You do not have to configure the second domain controller as nonauthoritative, because it is already waiting to perform initial synchronization.
Or, if the second domain controller is healthy and SYSVOL is shared, perform the following steps:
Back up all SYSVOL contents of the first domain controller.
Evaluate if the second domain controller's SYSVOL data is up to date. If it is not, you may want to copy updated SYSVOL files to the second domain controller from the first domain controller. Otherwise, any existing data
present on first domain controller not present on the second will go into the 'PreExisting' and 'Conflict and Deleted' folders.
Set the first domain controller as nonauthoritative by disabling the membership per 2218556.
Confirm that an event ID 4114 is logged to indicate the membership is disabled.
Enable the first domain controller's membership, and wait for the 4614 and 4604 events that report completion of the initial synchronization. If it is necessary, restore any updated files from "PreExisting" to the
original location.
If content freshness is not enabled or triggered on both domain controllers
If the first domain controller is in the event ID 2213 state and the second domain controller has never completed initialization
after it was promoted and content freshness has not been triggered, perform the following steps:
Run the ResumeReplication WMI method on the first domain controller as instructed in the 2213 event.
After replication resumes, it will log an event ID 4602 that indicates that DFS Replication initialized the SYSVOL replicated folder and designated it as the primary member.
Run the dfsrdiag pollad command on the second domain controller to trigger it to complete initial sync (event ID 4614). As soon as initial sync is finished, event ID 4604 is logged, signaling SYSVOL
has completed initialization.
Or, if the first domain controller is in the 2213 state and the second domain controller is healthy (SYSVOL is shared), run theResumeReplication WMI
method on the first domain controller. It will log event ID 2214 at the completion of dirty shutdown recovery.
This post is provided AS IS with no warranties or guarantees, and confers no rights.
~~~
Questo post non fornisce garanzie e non conferisce diritti

Help with mailbox recovery

We recently implemented retention policies at one of our sister companies. In preparation for that, the owner of that company (and of all of our company's) needed to setup rules to keep all messages to/from a specific list of senders. While processing those
multiple rules, the rules created massive amounts of duplicates and ballooned his mailbox to 553GB, which obviously caused other side effects, with log file growth, free space, backups, etc. We've opened a PSS ticket to assist with determining why the rules
behaved as they did.
So moving forward, I think we've decided (unless someone here has a better idea) to restore a version of his mailbox to a pst, from the night before the rules began running. Then the team who created the rules will handle final resolution of his mailbox.
We run full backups on Friday evenings, and differentials on the other days. I've used our 3rd party backup software (Arkeia) to restore the raw database & log files to a restore folder, but I cannot get the database state to become clean in
order to mount it into the recovery database. What I find odd about this restore is that it restored one .edb and 46,456 log files (e03001e544b.log through e03001f09c0.log). The Exchange build is 14.3.158.1.
The path of the restored edb & logs is: G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database
After the restore completed, I made a backup copy of the .edb and placed it here: G:\Restore
Using the non-backup copy of the .edb, below is what I receive. I've already ran these commands once, am I'm running them again for documentation purposes... not sure if there is a side effect to running them multiple times?
-----snip---
G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database>eseutil /mh "G:\Restore\program files\microsoft\exchange server\v14\mailbox\
ahp mailbox database\ahp mailbox database.edb"
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.03
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating FILE DUMP mode...
         Database: G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database\ahp mailbox database.edb
DATABASE HEADER:
Checksum Information:
Expected Checksum: 0x565185ef
Actual Checksum: 0x565185ef
Fields:
        File Type: Database
         Checksum: 0x565185ef
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
Format ulVersion: 0x620,17
Engine ulVersion: 0x620,17
Created ulVersion: 0x620,17
     DB Signature: Create time:07/31/2013 16:25:04 Rand:494601362 Computer:
         cbDbPage: 32768
           dbtime: 1314255407 (0x4e55f22f)
            State: Dirty Shutdown
     Log Required: 2034091-2034111 (0x1f09ab-0x1f09bf)
    Log Committed: 0-2034112 (0x0-0x1f09c0)
   Log Recovering: 2033344 (0x1f06c0)
GenMax Creation: 08/01/2014 17:33:38
         Shadowed: Yes
       Last Objid: 352545
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
     Repair Count: 0
      Repair Date: 00/00/1900 00:00:00
Old Repair Count: 0
Last Consistent: (0x1BC139,8,1F) 07/01/2014 19:14:51
      Last Attach: (0x1BC13A,9,86) 07/01/2014 19:14:51
      Last Detach: (0x0,0,0) 00/00/1900 00:00:00
             Dbid: 1
    Log Signature: Create time:07/31/2013 16:25:04 Rand:494597472 Computer:
       OS Version: (6.1.7601 SP 1 NLS ffffffff.ffffffff)
Previous Full Backup:
        Log Gen: 1987659-1987678 (0x1e544b-0x1e545e) - OSSnapshot
           Mark: (0x1E545F,8,16)
           Mark: 07/25/2014 17:37:47
Previous Incremental Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00
Previous Copy Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00
Previous Differential Backup:
        Log Gen: 1987659-2028177 (0x1e544b-0x1ef291) - OSSnapshot
           Mark: (0x1EF292,8,16)
           Mark: 07/31/2014 20:03:37
Current Full Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00
Current Shadow copy backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00
     cpgUpgrade55Format: 0
    cpgUpgradeFreePages: 0
cpgUpgradeSpaceMapPages: 0
       ECC Fix Success Count: none
   Old ECC Fix Success Count: none
         ECC Fix Error Count: none
     Old ECC Fix Error Count: none
    Bad Checksum Error Count: none
Old bad Checksum Error Count: none
Last checksum finish Date: 00/00/1900 00:00:00
Current checksum start Date: 00/00/1900 00:00:00
      Current checksum page: 0
Operation completed successfully in 0.141 seconds.
G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database>
---snip---
So it is a dirty shutdown and the logs required are 2034091-2034111 (0x1f09ab-0x1f09bf), which is e03001f09ab.log-e03001f09bf, which I have:
---snip---
G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database>dir e03001f09a*
Volume in drive G is Database
Volume Serial Number is F0B8-EE92
Directory of G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database
08/13/2014 04:20 PM         1,048,576 e03001f09a0.log
08/13/2014 04:20 PM         1,048,576 e03001f09a1.log
08/13/2014 04:20 PM         1,048,576 e03001f09a2.log
08/13/2014 04:20 PM         1,048,576 e03001f09a3.log
08/13/2014 04:20 PM         1,048,576 e03001f09a4.log
08/13/2014 04:20 PM         1,048,576 e03001f09a5.log
08/13/2014 04:20 PM         1,048,576 e03001f09a6.log
08/13/2014 04:20 PM         1,048,576 e03001f09a7.log
08/13/2014 04:20 PM         1,048,576 e03001f09a8.log
08/13/2014 04:20 PM         1,048,576 e03001f09a9.log
08/13/2014 04:20 PM         1,048,576 e03001f09aa.log
08/13/2014 04:20 PM         1,048,576 e03001f09ab.log
08/13/2014 04:20 PM         1,048,576 e03001f09ac.log
08/13/2014 04:20 PM         1,048,576 e03001f09ad.log
08/13/2014 04:20 PM         1,048,576 e03001f09ae.log
08/13/2014 04:20 PM         1,048,576 e03001f09af.log
              16 File(s)     16,777,216 bytes
               0 Dir(s) 134,549,012,480 bytes free
G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database>dir e03001f09b*
Volume in drive G is Database
Volume Serial Number is F0B8-EE92
Directory of G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database
08/13/2014 04:20 PM         1,048,576 e03001f09b0.log
08/13/2014 04:20 PM         1,048,576 e03001f09b1.log
08/13/2014 04:20 PM         1,048,576 e03001f09b2.log
08/13/2014 04:20 PM         1,048,576 e03001f09b3.log
08/13/2014 04:20 PM         1,048,576 e03001f09b4.log
08/13/2014 04:20 PM         1,048,576 e03001f09b5.log
08/13/2014 04:20 PM         1,048,576 e03001f09b6.log
08/13/2014 04:20 PM         1,048,576 e03001f09b7.log
08/13/2014 04:20 PM         1,048,576 e03001f09b8.log
08/13/2014 04:20 PM         1,048,576 e03001f09b9.log
08/13/2014 04:20 PM         1,048,576 e03001f09ba.log
08/13/2014 04:20 PM         1,048,576 e03001f09bb.log
08/13/2014 04:20 PM         1,048,576 e03001f09bc.log
08/13/2014 04:20 PM         1,048,576 e03001f09bd.log
08/13/2014 04:20 PM         1,048,576 e03001f09be.log
08/13/2014 04:20 PM         1,048,576 e03001f09bf.log
              16 File(s)     16,777,216 bytes
               0 Dir(s) 134,549,012,480 bytes free
---snip---
So let's check the log files...I snipped out the middle due to the number of log files but but only one log is shown as bad, and it's not one which is needed by the .edb file:
---snip---
G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database>eseutil /ml "G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database\e03" > logtest.txt
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.03
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating FILE DUMP mode...
Verifying log files...
     Base name: e03
      Log file: G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database\e03001e544b.log - OK
      Log file: G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database\e03001e544c.log - OK
      Log file: G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database\e03001e544d.log - OK
      Log file: G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database\e03001f06c0.log - OK
      Log file: G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database\e03001f06c1.log
                ERROR: Cannot read log file header. Error -4001.
      Log file: G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database\e03001f06c2.log - OK
      Log file: G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database\e03001f09c0.log - OK
      Log file: G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database\E03.log - OK
Operation terminated with error -4001 (JET_errFileIOBeyondEOF, a read was issued to a location beyond EOF (writes will expand the file)) after 392.374 seconds.
---snip---
Let's try to replay the log files into the database:
---snip---
G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database>eseutil /r E03 /l "G:\Restore\program files\microsoft\exchange server\v14\ma
ilbox\ahp mailbox database" /s "G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database" /d "G:\Restore\program files\microsoft\exch
ange server\v14\mailbox\ahp mailbox database"
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.03
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating RECOVERY mode...
    Logfile base name: E03
            Log files: G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database
         System files: G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database
   Database Directory: G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database
Performing soft recovery...
                      Restore Status (% complete)
          0    10   20   30   40   50   60   70   80   90 100
          |----|----|----|----|----|----|----|----|----|----|
          X
Operation terminated with error -4001 (JET_errFileIOBeyondEOF, a read was issued to a location beyond EOF (writes will expand the file)) after 0.702 seconds.
---snip---
State still shows dirty, even after deleting the *.chk file. Trying to repair the db at this point gives me this:
---snip---
G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database>eseutil /p /t c:\tempdb /g "G:\Restore\program files\microsoft\exchange serv
er\v14\mailbox\ahp mailbox database\ahp mailbox database.edb"
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.03
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating REPAIR mode...
        Database: G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database\ahp mailbox database.edb
Temp. Database: c:\tempdb
Operation terminated with error -1032 (JET_errFileAccessDenied, Cannot access file, the file is locked or in use) after 30.62 seconds.
G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database>
---snip---
Where am I doing incorrectly? I've never restored an incremental or differential backup on Exchange. Since this is just the full backup, and I also need to add in the differential from a few days later, do I need to mount the full first and somehow import
the logs from the differential? Or don't mount the db until the differential logs are played back ...??
Sorry for the novel, just trying to be proactive.
Thanks,
Jim

Hello JimCass,
From the information, we have one corrupted transaction logs which make the soft recovery(eseutil /r) failed, thus we try to hard repair the database EDB file, however it also report error message as the below:
=============================================
Command we use:
eseutil /p
/t c:\tempdb /g "G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database\ahp mailbox database.edb"
Error message:
Operation terminated with error -1032 (JET_errFileAccessDenied, Cannot access file, the file is locked or in use) after 30.62 seconds.
=============================================
From the command we use, I noticed that we want to set the temp database location, right? If so, the command is incorrect. Please use this command instead:
eseutil /p
/t “c:\tempdb\tempdb.edb” /g "G:\Restore\program files\microsoft\exchange server\v14\mailbox\ahp mailbox database\ahp mailbox database.edb"
How to Run Eseutil /P (Repair) in Different Scenarios
http://technet.microsoft.com/en-us/library/aa997215(v=exchg.65).aspx
Note: When we specify the temp database location, it should contains
the full location of the temp EDB file. And the folder “c:\tempdb” should exist otherwise error message like “invalid path” will occur.
In light of above, please refer to above command to repair the database EDB file. But please aware of that database repair could cause data loss since we have transaction logs can’t be replayed to the EDB file.
Meanwhile, to merge the differential backup data to the mailboxes, we can first restore the full backup data(250GB), then we can got the mailbox data on 8/1, take the mailbox to production.
After that, for the differential backup data, also use the same method to get the EDB file to clean shutdown, use your method to restore the data to PST, then import the PST data to the mailbox which have been production. Or we also can use Recovery Database
to restore the data to a production mailbox.
Regards, Eric Zou

Database can not mount in exchange server 2013 due to Unable to mount database. (hr=0x80004005, ec=-543)

Hello All,
Database can not mount. In this Database domain Administrator mailbox have.
Please suggest. It's very important
The error:
[PS] C:\Windows\system32>Mount-Database -Identity MBX-01 -Force
Confirm
At least one committed transaction log file is missing. Mounting this database will result in data loss. If you can
locate the missing log files, don't continue. Are you sure you want to continue?
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): a
Failed to mount database "MBX-01". Error: An Active Manager operation failed. Error: The database action failed.
Error: Operation failed with message: MapiExceptionJetErrorRequiredLogFilesMissing: Unable to mount database.
(hr=0x80004005, ec=-543)
Diagnostic context:
    Lid: 65256
    Lid: 10722   StoreEc: 0xFFFFFDE1
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 45120   dwParam: 0x51FF5F0
    Lid: 57728   dwParam: 0x51FF68C
    Lid: 46144   dwParam: 0x51FF709
    Lid: 34880   dwParam: 0x51FF709
    Lid: 34760   StoreEc: 0xFFFFFDE1
    Lid: 41344   Guid: 1c2c8cab-ae3f-40c8-8024-ffc776b22360
    Lid: 35200   dwParam: 0x2EFC
    Lid: 46144   dwParam: 0x51FFA55
    Lid: 34880   dwParam: 0x51FFA55
    Lid: 56264   StoreEc: 0x1388
    Lid: 46280   StoreEc: 0xFFFFFDE1
    Lid: 1750    ---- Remote Context End ----
    Lid: 1047    StoreEc: 0xFFFFFDE1 [Database: MBX-01, Server: EG-EXCHG-01.ABC.com]
    + CategoryInfo          : InvalidOperation: (MBX-01:ADObjectId) [Mount-Database], InvalidOperationException
    + FullyQualifiedErrorId : [Server=EG-EXCHG-01,RequestId=ca57e784-43c7-4357-9ab6-08881c87bb77,TimeStamp=9/18/2014 5
   :31:08 AM] [FailureCategory=Cmdlet-InvalidOperationException] 51350054,Microsoft.Exchange.Management.SystemConfigu
rationTasks.MountDatabase
    + PSComputerName        : eg-exchg-01.ABC.com

Hi,
This issue indicate corrupted database or corrupted logs. I suggest you to check and repair the database or check and repair the database log.
1. Check the state of database by following command: eseutil /mh "Path of the database"
Ps: Default path of the database is “C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database\Mailbox Database.edb”
Default path of the log files is “C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database\E00”
2. If the state is in clean shutdown, move all the log files from the Transaction logs folder location and then mount the database.
3. If the state is in dirty shutdown, check if the log files that is indicated as Logs required is available or not.
4. You can run Eseutil ml “Path of the log file\e00” to make sure that the log files is required is in a Clean state. This command will help you check the health of all the log files in the location.
5. If the log files are healthy, then try Soft recovery with the command Eseutil /r e00 /l ”Path of log files” /p “Path of the database”
Note:
Make sure you make a backup of the database before attempting any kind of repairs
6. Once the command completes successfully, then mount the database.
7. In case the required log files are not available in a clean state or missing, either restore from a successful back up or perform Hard repair with defragment.
Refer to this file about hard repair:
http://gallery.technet.microsoft.com/Step-by-Step-Exchange-2013-f8bed401
Hope this will be helpful for you

Dirty Shutdown: 0

Similar Messages

Maybe you are looking for