the problem should be the queue database.  If you stop the ExchangeTransport Service, delete or rename the queue database and then restart the Transport Service, the issue could be resolved.

Please follow the steps below:

1). Stop Msexchange transport service manually on it.

2). Go to path below: c:\program files\Microsoft\Exchange Server\TransportRoles\Data\Queue on mailbox server.(by default for EX13)

3). Rename mail.que to mail.que.old

4). Startup Msexchangetransport service manually on server.

 

 

In a previous article I demonstrated how to restore Exchange Server 2013 databases using Windows Server Backup. In that scenario an entire database that had been lost needed to be recovered.

However in other recovery scenarios you may only want to recover one or several mailboxes, or even specific mailbox items, from a point in time without having to overwrite the entire database.

In Exchange Server 2013 we can do this with recovery databases, which operate basically the same as Exchange Server 2010 recovery databases. A recovery database allows us to mount a copy of a database on an Exchange server without having any impact on the live copy of that same database. In fact we can even use recovery databases to mount copies of databases from other servers within the same Exchange organization, thanks to database portability.

When a recovery database is mounted we can inspect it and restore items or mailboxes from it, but no clients can connect to it. So as the name suggests it can only be used for recovery purposes, not for active mailbox functionality.

Restoring an Exchange Server 2013 Database Using Windows Server Backup

Some backup applications have the capability to handle some or all of the process of creating a recovery database, restoring the database files, and extracting the desired mailboxes or items to a destination.

When using Windows Server Backup to perform a recovery you need to do pretty much all of the work yourself, so it is a good exercise for learning how to recovery Exchange 2013 databases.

In Windows Server Backup click Recover to start a new recovery.

Choose the location where the backup is stored. In this example my backups are stored on the same server.

Choose the backup date and time that you wish to restore.

When recovering entire databases we would normally choose “Applications” and restore every database that was backed up on the server. However when working with recovery databases we can chooseFiles and folders and only restore the specific database and log files we need.

Browse through the tree of available items and choose the database and log files you want to restore. I am restoring DB02 in this example. Note that restoring the database and logs will be two separate restore jobs if they are located in folders where you can’t select both at the same time.

Choose to restore to Another location, and select a folder that has enough free space to hold the restored data.

Confirm your selections and click Recover to begin the restore.

You can close the progress window if you like and the job will continue running in the background.

I’ve also run a second recovery job to restore the log files for DB02.

After you’ve completed your file restores the next step is making the database mountable.

Making the Restored Database Mountable

So far we’ve restored the database and transaction log files from a recent backup, but haven’t created the actual recovery database yet. If we created the recovery database right now, pointing it at the restored database and log files, and then tried to mount it, the database would fail to mount.

The reason for this is that the restored database is in a “dirty shutdown” state, which you can see by navigating to the restored database folder and running eseutil.exe.

I have abbreviated the output of the above command, but basically you are looking for the “State” shown in the command output.

So we need to get the database file to a “clean shutdown” state before it can be mounted.

In my example I have:

• A database file named DB02.edb in F:RecoveryDB
• Transaction logs with the filename prefix E01 in F:RecoveryLogs

So my eseutil “soft recovery” command line will be:

What that command means:

• /r for “recovery” mode
• E01 for the log file name  prefix
• /l (lower-case L) to specify the path to the log files
• /d to specify the path to the database file (but do not include the name of the file itself)

After the command has completed check the state of the database with eseutil /mh again.

If soft recovery does not bring the database to a clean shutdown state you may consider a hard recovery, which will make the database mountable but risks some data loss in the process.

When the database is in a clean shutdown state you can create the recovery database.

Creating a Recovery Database in Exchange Server 2013

Creating a recovery database is performed using the New-MailboxDatabase cmdlet with the -Recovery switch. Notice that in this example I am using the same database and log file locations as my restored data.

For more information about the warning to restart the Information Store service read this article. For a recovery database that you are only mounting for a short period of time an Information Store service restart may not be necessary.

Mount the recovery database.

Working with Recovery Databases

With the recovery database mounted you can use Get-MailboxStatistics to confirm that it contains mailbox database.

After you have confirmed that data is available for restore you can begin your mailbox or item recovery.

from Power shell

Get-Recipient | Select Name -ExpandProperty EmailAddresses | Select Name, SmtpAddress | Export-csv c:\temp\AllEmailAddress.csv


Get-Mailbox | Select UserPrincipalName,EmailAddresses | Export-Csv C:\Temp\Addresses.csv

Export E-mail Address List From Exchange 2010

On the Remove Exchange Server page, you can remove Exchange from the computer.

When you remove Exchange from the computer, the following are removed:

• All server roles.
• All installation files.
• The Exchange server object and all its child objects from Active Directory.

  Important:
  If you used Setup.exe /NewProvisionedServer to provision the server, you must use Setup.exe /RemoveProvisionedServer after Exchange has been removed from the computer to remove the Exchange server object and all its child objects from Active Directory.

Removing Exchange from a computer doesn’t remove any Exchange-related databases or log files. You must remove those files manually.

Step-by-Step Guide to Migrate from Exchange Server 2007 to Exchange Server 2013
Posted by Ajit Singh on 7 September 2015, 2:20 pm
Before planning your Exchange Server 2013 migration ensure you are familiar with all its features like virtualization, retention, modern public folders, managed availability, transport, unified messaging, EWS, Outlook Web App etc.
As Exchange is critical to the communication network, it is important to do a smooth Exchange migration which causes minimum or zero interruption to the organizational communication. In this blog, we will see how to migrate all users and services from Exchange 2007 to Exchange 2013 and finally decommission the old Exchange 2007.
The high-level steps that we will take to devise the migration are:
Deploying Exchange 2013 as new environment
Configuring Digital Certificates for the new Exchange
Configuring Name Space and Virtual Directories
Offline Address Book (OAB) configuration
Mail Flow Configurations
Moving Client Access to Exchange 2013
Moving Mailboxes to Exchange 2013
Moving Public Folders to Exchange 2013 and decommissioning old Exchange Server
1. Deploying Exchange 2013 as new environment
Active Directory Preparation
When we install Exchange Server it needs to store User mailboxes’ and Exchange Server’s configuration information in the organization. So it is important that Active Directory is duly prepared before you install Exchange 2013 in the organization. Following things need to be done before you deploy Exchange Server 2013 in the environment: a> Extend Active Directory Schema b> Prepare Active Directory and 3> Prepare Active Directory Domains. To ensure that AD preparation is done correctly, verify that the rangeUpper property on ms-Exch-Schema-Version-Pt is set to the correct value. After this force AD replication.
Exchange Server 2013 Installation
When you are ready for running Exchange Server setup ensure that server is fully updated with latest patches. To install Windows Features using PowerShell Run Windows PowerShell as Administrator and paste the following command:
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
After the installation is complete restart your server. And after the reboot, download and install Microsoft Unified Communications Managed API 4.0. Core Runtime 64-bit, Microsoft Office 2010 Filter Packs 64 bit, Microsoft Office 2010 Filter Packs SP1 64 bit.
2. Configuring Digital Certificates
You should be using as few certificates and host names as possible for cost control since certificate providers charge a fee based on number of host names you add to your certificate. By default, Exchange comes with self-signed certificates, we will replace this certificates with the ones relevant to our case.
mail.contoso.com: FQDN for most connections to Exchange including Microsoft Outlook, Outlook Web App, Outlook Anywhere, the Offline Address Book, Exchange Web Services, POP3, IMAP4, SMTP, Exchange Control Panel, and ActiveSync.
autodiscover.contoso.com: FQDN used by clients that support Auto discover, including Microsoft Office Outlook 2007 and later versions, Exchange ActiveSync and Exchange Web Services clients.
legacy.contoso.com: FQDN used by all external and internal clients for old server i.e. Exchange Server 2007.
Next we will create certificate request, for this open EMS and run the New-ExchangeCertificate cmdlet command:
Once the certificate is created, get it signed by the appropriate certification authority (CA) and use the Import-ExchangeCertificate to import the certificate.
Then Exchange Server 2013 need to be configured to use the certificates using the Enable-ExchangeCertificate command.
Please note that Enable-ExchangeCertificate cmdlet cannot be used to enable a wildcard certificate for POP and IMAP services, also it cannot be used to enable a certificate for federation.
Use private key to export the certificate and import it on Exchange 2007 CAS servers using the same steps.
3. Configuring Name Space and Virtual Directories for Exchange Server
Follow the given steps to configure Exchange Server 2013 virtual directories using EMS:
Exchange Control Panel
To configure Exchange Control Panel (ECP) virtual directories properties, use Set-EcpVirtualDirectory cmdlet.
Outlook Web App
To configure Outlook Web App virtual directories use Set-OwaVirtualDirectory cmdlet.
Offline Address Book
To configure offline address book virtual directory use Set-OABVirtualDirectory cmdlet.
ActiveSync
Use Set-ActiveSyncVirtualDirectory cmdlet to configure the Microsoft Exchange ActiveSync settings on specified virtual directory.
Web Services
To modify Exchange Web Services virtual directory use Set-WebServicesVirtualDirectory cmdlet on the server running Exchange Server 2013.
AutoDiscover
To set properties on specified Client Access Server objects use Set-ClientAccessServer cmdlet.
Outlook Anywhere
To set properties on a computer running Microsoft Exchange Server 2013 enabled for Microsoft Outlook Anywhere use Set-OutlookAnywhere cmdlet.
4. Offline Address Book (OAB) configuration
In Exchange Server 2013, OABGen (Offline Address Book Generation) service which runs on Mailbox server generates offline address book.
Change the default OAB on Exchange 2013 database using Get-MailboxDatabase and Set-MailboxDatabase
5. Mail Flow Configurations on Exchange 2013
Receive Connector
To create this connector use the New-ReceiveConnector cmdlet.
Send Connector
Now add the new Exchange Server to the existing send connector by the Set-SendConnector cmdlet.
Transport Rules:
Transport rules cannot be migrated from Exchange Server 2007 to 2013. So you need to do the following to get Transport rules in Exchange Server 2013.
Use Export-TransportRuleCollection cmdlet to export all transport rules from Exchange Server 2007.
Copy the exported Transport Rule file to the system which has Exchange Server 2013 installed on it.
Use Import-TransportRuleCollection cmdlet to import the Transport Rules from the file to the Exchange Server 2013.
6. Moving Client Access to Exchange 2013
In the Exchange 2007 management shell you need to run the following commands.
Outlook Web App
Use Set-OwaVirtualDirectory cmdlet to modify properties of MS Outlook Web App virtual directories.
Offline Address Book
Use Set-OABVirtualDirectory cmdlet to configure offline address book virtual directory.
ActiveSync
Use Set-ActiveSyncVirtualDirectory cmdlet to configure the Microsoft Exchange ActiveSync settings on specified virtual directory.
Web Services
To modify Exchange Web Services virtual directory use Set-WebServicesVirtual Directory cmdlet on the server running Exchange Server 2007.
Unified Messaging
To modify an existing Exchange Unified Messaging virtual directory, run the Set-UMVirtualDirectory cmdlet.
Outlook Anywhere
To set Microsoft Outlook Anywhere properties on Microsoft Exchange Server 2007 use Set-OutlookAnywhere cmdlet.
Threat Management Gateway Rules
Now create and update your TMG publish rules.
Next update your publish rules for Exchange 2007 to accept connections for Legacy name space. And then publish Exchange Server 2013 using TMG.
Domain Name System Configurations:
In the Internal DNS, point mail.contoso.com and autodiscover.contoso.com to Exchange 2013 server. And in Legacy.contoso.com new record points to Exchange 2007 Server. In the Public DNS, point mail.contoso.com and autodiscover.contoso.com to TMG listener and for Legacy.contoso.com point new record to TMG Listener.
7. Moving Mailboxes to Exchange 2013
Next you can use New-MoveRequest cmdlet to start mailbox or personal archive migration. To check mailbox readiness before starting to move mailboxes you can use WhatIf parameter. You can also create batch move if you want.
8. Moving Public Folders to Exchange 2013 and decommissioning old Exchange
To start with, take snapshot of the current Public Folders in Exchange Server 2007 EMS using the following commands: Get-PublicFolder, Get-PublicFolderStatistics and Get-PublicFolderClientPermission.
Next create CSV files using scripts (Export-PublicFolderStatistics.ps1 and PublicFolderToMailboxMapGenerator.ps1). In this way you will get the CSV file mapping PFs to new PF mailboxes.
In the Exchange 2013, create PF mailboxes using New-Mailbox –PublicFolder cmdlet. Migrate PF content using New-PublicFolderMigrationRequest cmdlet.
Before starting the final migration, lock down Exchange Server 2007 using the following cmdlets.
Set-OrganizationConfig –PublicFoldersLockedForMigration $True (In Exchange 2007)
Set-PublicFolderMigrationRequest <name> -PreventCompletion $False (In Exchange 2013)
Resume-PublicFolderMigrationRequest <name> (In Exchange 2013)
Test new public folders to ensure everything is alright. Then us the following cmdlet to unlock the PF migration.
Set-OrganizationConfig -PublicFolderMigrationComplete:$true
Decommissioning Exchange Server 2007
Open Exchange Server 2007 management shell and run the following command to remove mailbox databases.
Get-MailboxDatabase | Remove-MailboxDatabase
Remove the public database and in the cmd run the following command to uninstall Exchange:
Setup.com /mode:uninstall
Thus we complete the entire Exchange Server 2007 to 2013 migration process.