Database offline - Unable to remount Exchange 2013

Hi all,
I'm kinda pulling my hair out here. I had a power outage which looks to have corrupted the mailstore. Running eseutil /r and eseutil /d have completed successfully but the database still isn't mounting.
I end up with this message:
Couldn't mount the database that you specified. Specified database: Mailbox Database 2093613246; Error code: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionDatabaseError: Unable to
mount database. (hr=0x80004005, ec=1108) Diagnostic context:    Lid: 65256      Lid: 10722   StoreEc: 0x454         Lid: 1494    ---- Remote Context Beg
----    Lid: 45120   dwParam: 0x569817    Lid: 57728   dwParam: 0x56995F    Lid: 46144   dwParam: 0x569A97    Lid: 34880   dwParam: 0x569A97   
Lid: 34760   StoreEc: 0xFFFFFE0B    Lid: 46144   dwParam: 0x56A13F    Lid: 34880   dwParam: 0x56A13F    Lid: 54472   StoreEc: 0x1388       
Lid: 42184   StoreEc: 0x454         Lid: 1750    ---- Remote Context End ----    Lid: 1047    StoreEc: 0x454      [Database: Mailbox Database
2093613246, Server: R-FS1.webrooster.local].
I've tried restarting the server without any luck either.
Any suggestions? (no backup to restore from unfortunately - that was my next shot)

Hi all,
I have an issue where my mailstore has been corrupted following a power outage. I've run eseutil /r and eseutil /d on the database which has completed successfully, and inspecting the properties now shows the database in a clean shutdown state. However, I still
can't mount the database, and get the following error.
Couldn't mount the database that you specified. Specified database: Mailbox Database 2093613246; Error code: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionDatabaseError: Unable
to mount database. (hr=0x80004005, ec=1108) Diagnostic context:    Lid: 65256      Lid: 10722   StoreEc: 0x454         Lid: 1494    ---- Remote Context
Beg ----    Lid: 45120   dwParam: 0x569817    Lid: 57728   dwParam: 0x56995F    Lid: 46144   dwParam: 0x569A97    Lid: 34880   dwParam: 0x569A97   
Lid: 34760   StoreEc: 0xFFFFFE0B    Lid: 46144   dwParam: 0x56A13F    Lid: 34880   dwParam: 0x56A13F    Lid: 54472   StoreEc: 0x1388       
Lid: 42184   StoreEc: 0x454         Lid: 1750    ---- Remote Context End ----    Lid: 1047    StoreEc: 0x454      [Database: Mailbox Database
2093613246, Server: R-FS1.webrooster.local].
Does anyone have any suggestions? (unfortunately no backup exists to restore from).
Thanks,
John

Similar Messages

  • Is it possible to access the Public Folders in Exchange 2013 during a migration from Exchange 2007 to verify the files are there?

    This is a migration from Exchange 2007 to Exchange 2013.  We're in the middle of migrating the Public Folders.  Is it possible to configure a database to point to the Exchange 2013 public folders so I can verify the data before the final cut?
     If so what are the steps to do that?  Thanks in advance.

    To my knowledge no.  It's an all or nothing thing with public folders.
    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

  • Can no longer log into ECP on Exchange 2013

    I am no longer able to log into my Exchange 2013 SP1 ECP site.   Here are a few items to consider:
    Installed replacement UC on 5/7/14.  Configured services POP, IMAP, SMTP, IIS. Removed IIS from existing UC which still had 6 days of life.  Both certs identical.  I did no further changes for this new cert other than install it through ECP.
    "Old" cert died 5/13/14 @ 8a.  New cert took over without any problems.  
    Continued to use ECP through close of business 5/14/14.  Late on 5/14/14 I attempted to log into ECP remotely thru a VPN to migrate users from our Exch 2007 server.  Could not access ECP.
    When I attempt to access ECP, I enter <domain>\<username> and password.  When I hit "enter" or "sign in", the page flashes and the password field is empty.
    I am still able to log into OWA
    I cannot log into ECP using the server name, localhost or cert name.
    Currently using default settings of FBA and Basic authentication
    UC is correctly bound to both front and backend of IIS (443, 444)
    Everything else is working correctly for the Exchange site.  I have been continuing my migrations through Powershell.  I just can't log into ECP.
    I created a new Exchange Admin user only to find I still could not log into ECP.
    Short Version:  I was able to login and then, after a four hour stretch, I was not able to login.  No errors on the web page or Event logs.  Exchange is routing mail correctly.
    I have scoured the web for that past couple of days looking for a solution but the issues I find are throwing up a web page with an error of some sort.  Since I'm not experiencing that issue, I'm a bit stumped.  I'm no expert, but I'm not a novice.
     Since 2013 is a new rebuild, I thought it best to ask for a little assistance.  Any advice/assistance would be appreciated.

    You might consider rebuilding the ECP virtual directory:
    http://technet.microsoft.com/en-us/library/ff629372.aspx
    With the EMS, procedure should be the same for Exchange 2010 and 2013.
    Since you state that everything else is working, other virtual directories included (OWA for ex.), it's most likely something with the ECP virtual directory.
    But even before that, I would try to look at the (rather cryptic) IIS logs and see if you cannot find any useful information there:
    http://social.technet.microsoft.com/Forums/exchange/en-US/935eeb5b-d996-4933-9cbd-0347ebad801d/how-can-i-view-exchange-iis-logs?forum=exchange2010
    There were some ideas in this thread but i think you may have seen it already?
    http://social.technet.microsoft.com/Forums/exchange/en-US/1736b5ab-e69b-4637-aa59-f2d9bd54ead2/unable-to-access-exchange-2013-eacecp-webpage?forum=exchangesvrdeploy
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Deploy Exchange 2013 Edge Transport Server for multi-site environment

    Hi,
    I have a multi-site Exchange 2013 environment. The configurations are as below.
    Active Directory Sites and Exchange Servers.
    SiteA - EXMB1 & EXCAS1
    SiteB - EXMB2 & EXCAS2
    SiteC - EXMB3 & EXCAS3
    All sites are connected via VPN. (Good speed. No latency issues)
    All the three Mailbox Servers are in DAG. Only one mailbox database. All servers running Exchange 2013.
    I am planning to deploy Edge Servers in the infrastructure (I am doing it for the first time). Normally, it will be in DMZ.
    Now, I can deploy 2 Edge Servers for reliability.
    Question.
    1. Can I deploy 2 Edge Servers and create subscription to all the mailbox server in 3 different site? Or, is it like one edge server can make subscription to only mailbox servers in one Active Directory Site? I am not sure about this and could not find much
    information from TechNet.
    One Edge Server can make subscription to all 3 mailbox server in 3 sites. Similarly, I can make the subscriptions in the second edge server as well. Configure 2 external MX records with the same priority so that there will be some load balancing.
    Also, in such a case if the mailbox database become active from a different site, I need not make any new changes to the Edge Servers right?
    2. If the first way is not correct, I will have to deploy 1 Edge Server each for each of the Active Directory Site. (In DMZ only, not in domain)
    Make Edge Subscription to the mailbox server in corresponding site.
    Make 1 MX record and point it to the Edge Server which is subscribed to the Mailbox Server from which the Database is Active. The problem is, every time will have to change the DNS record when ever the database copy is activated from a different mailbox
    server. And the issues with propagation.. delay..
    I am not sure which of the above 2 ways will work. Appreciate suggestions from anyone who have previous experience with similar infrastructure.
    Thanks in advance. :)

    Hi 
    One or more Edge Transport servers can be subscribed to a single Active Directory site. However, an Edge Transport server can't be subscribed to more than one Active Directory site. If you have more than one Edge Transport server deployed, each server can be
    subscribed to a different Active Directory site. Each Edge Transport server requires an individual Edge Subscription.
    A subscribed Edge Transport server is associated with a particular Active Directory site. If more than one Mailbox server exists in the site, any of them can replicate data to the subscribed Edge Transport servers.
    I don't think there is a solution to subscribe  edge servers for more than 1 site. Edge Servers can be scoped only to one site.
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
    (MVP)

  • Exchange 2013 Mailbox Size Limits

    Are there any hard limits on mailbox sizes in Exchange 2013 (either in terms of mailbox size or item count)?
    Note: I am aware of the public folder mailbox size limits as well as the hard limit of 2TB for mailbox databases.

    I believe the max mailbox size is 100 GB
    http://blogs.technet.com/b/ashwinexchange/archive/2012/12/17/3541150.aspx
    Major changes in Information Store
    Managed Store
    Newly rewritten Information Store processes, Microsoft.Exchange.Store.Service.exe and Microsoft.Exchange.Store.Worker.exe.
    Each database runs under its own process, allowing for isolation of store issues to a single database.
    Tightly integrated with MSExchangeRepl.exe to provide higher availability through improved resiliency.
    Public Folder Database no longer exist.
    Exchange 2013 it supports up to 100 GB of Mailbox size, with OL2013 OST file size can be controlled.
    Exchange 2013 Enterprise Edition can only mount 50 databases on a mailbox server

  • 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

  • Public Folder Mailbox causes database failover Exchange 2013

    Hi , we are completing a migration from Exchange 2007 to Exchange 2013.  All was going swimmingly until we migrated our legacy public folders.  Now every now and again ( once a day generally ) the Exchange Database hosting the Public Folder Mailbox
    crashes and fails over to another DAG member.
    We are using CU5 and our old 2007 server is offline but not removed from the organization yet.
    The error message is as follows :
    Event ID 1013
    The mailbox with mailboxguid "xxxxxxxxxxxx" caused crash or resource outage on database (GUID="xxxxxxxxxxx")
    along with :
    Event ID 1001
    Microsoft Exchange Server Information Store has encountered an internal logic error. Internal error text is (Unable to apply maintenance GetNonKeyColumnValuesForPrimaryKey-norow, index corruption?) with a call stack of (   at Microsoft.Exchange.Server.Storage.Common.ErrorHelper.AssertRetail(Boolean
    assertCondition, String message)
    and :
    Event ID 1002
    Unhandled exception (Microsoft.Exchange.Diagnostics.ExAssertException: ASSERT: Unable to apply maintenance GetNonKeyColumnValuesForPrimaryKey-norow, index corruption?
    The Mailbox Guild matches the Public Folder Mailbox GUID and the Database GUID matches the Database where the mailbox is mounted.
    The error seems to be the same as this question :
    https://social.technet.microsoft.com/Forums/office/en-US/7e823810-29f4-48f2-ad60-37e6ac147d3e/exchange-2013-database-dismounts-unexpectedly
    However I'm after a bit more concrete information as to what actually causes this and if an upgrade to CU6 is required.  This link appears to suggest moving the mailbox will help.  Has anyone else come across this with CU5 and will a mailbox move
    correct it ?
    http://blogs.technet.com/b/exchange/archive/2014/10/03/those-pesky-lazy-indices.aspx

    Hello,
    Thank you for your post.
    This is a quick note to let you know that we are performing research on this issue.
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Unable to send to external email recipients - Multi Tenant Exchange 2013 - MultiRole servers in DAG

    Greetings all, I hope someone can help.
    I have created a Exchange 2013 multi-tenant organization, with two servers, both multi-role - CAS and Mailbox roles.
    Internal mail flow is fine (external email addresses can send to the domain).
    External firewall port forwards ports 443 and 25 to the Internal DAG IP address.
    There are two multi-role Exchange servers that are members of the DAG.
    I am able to connect to OWA and ECP via https://externalIP/OWA and https://alias.domain.com/OWA
    No SSL certificates have been purchased or installed yet.
    Exchange URLs have not been changed since default configuration at install.
    OWA and ECP works both internal and external.
    External DNS works with SPF and PTR records correctly configured
    Exchange RCA - Send test only fails with one Spam Listing (this Blacklist provider now flags all domains and you cannot ask to be removed)
    Send Connectors are the default ones created during install. Receive connector is standard configuration with  - * - 
    When sending email to an external address, I receive a failure notice
    ServerName.test.corp.int gave this error:
    Unable to relay 
    Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.
    More Info - 
    ServerName.test.corp.int
    Remote Server returned '550 5.7.1 Unable to relay'
    I have been troubleshooting this for many hours with no progress.
    I have created new Send Connectors for the server that is advising that it is unable to relay, but they have all failed.
    I have tried setting the Internal IP address for Exhange Server 1 (Exchange Server 2 reports failure), with most combinations of Security (Anonymous, Exchange Users, etc).
    I have also tried with the IP range 192.168.11.0/24 to allow the whole the subnet, I still receive the unable to relay failure notice.
    I have tried this guide - hxxps://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/ - with different combinations, still no resolution.
    I am at a loss as to why I can't send out with the default configuration. I would assume that email would flow out without any changes, but this does not happen.
    Can someone please assist before I lose my sanity.
    Thanks in advance,
    Terry

    Greetings all, I hope someone can help.
    I have created a Exchange 2013 multi-tenant organization, with two servers, both multi-role - CAS and Mailbox roles.
    Internal mail flow is fine.
    Incoming mail from external senders is also fine. - 
    external email addresses can send to the domain).
    External firewall port forwards ports 443 and 25 to the Internal DAG IP address.
    There are two multi-role Exchange servers that are members of the DAG.
    I am able to connect to OWA and ECP via https://externalIP/OWA and https://alias.domain.com/OWA
    No SSL certificates have been purchased or installed yet.
    Exchange URLs have not been changed since default configuration at install.
    OWA and ECP works both internal and external.
    External DNS works with SPF and PTR records correctly configured
    Exchange RCA - Send test only fails with one Spam Listing (this Blacklist provider now flags all domains and you cannot ask to be removed)
    Receive Connectors are the default ones created during install. Send connector is standard configuration with  - * - 
    When sending email to an external address, I receive a failure notice
    ServerName.test.corp.int gave this error:
    Unable to relay 
    Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.
    More Info - 
    ServerName.test.corp.int
    Remote Server returned '550 5.7.1 Unable to relay'
    I have been troubleshooting this for several days with no progress.
    I have created new Receive Connectors for the server that is advising that it is unable to relay, but they have all failed.
    I have tried setting the Internal IP address for Exhange Server 1 (Exchange Server 2 reports failure), with most combinations of Security (Anonymous, Exchange Users, etc).
    I have also tried with the IP range 192.168.11.0/24 to allow the whole the subnet, I still receive the unable to relay failure notice.
    I have tried this guide - hxxps://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/ - with different combinations, still no resolution.
    Even more info - Further troubleshooting -
    I found my one of my Exchange servers had an extra NIC. I have since added a second NIC to the other server, so now both Exchange servers have dual NICs. I removed the DAG cleanly and recreated the DAG from scratch, using this link -
    hxxp://careexchange.in/how-to-create-a-database-availability-group-in-exchange-2013/ 
    The issue still exists, even with a newly created DAG. I also found that the Tenant Address Books were not 'applied'. I applied them but still no resolution
    I think the issue is related to multi-tenant configuration even though the error says that it can't relay. The unable to relay message can appear when sending from a domain that the Organization does not support. Like trying to email as [email protected]
    when you domain name is apple.com - But through extensive research I still can't resolve the issue.
    Can someone please assist before I lose my sanity.
    Thanks in advance,
    Terry

  • Unable to access ECP on a new Exchange 2013 Install

    I have a standalone exchange 2010 server (setup with all roles) and yesterday went ahead to setup an Exchange 2013 Server. Installed both CAS and mailbox roles for Exchange 2013 but after the install, I am unable to access the Exchange Admin Center. 
    If i try to access to https://EXCHANGE 2013 FQDN\ecp , after inserting my login information, it asks for the login information again and redirects to webmail. I have read all posts of users experiencing similar issues and tried all possible measures. 
    As the 2013 coexists with Exchange 2010 and mailboxes still reside on 2010, I have tried the URL
    https://EXCHANGE 2013 FQDN/ecp?ExchClientVer=15 but got the same result.
    Also, the CAS is installed on the server and i see the ECP virtual directory and URL.
    please see below the output for Get-ExchangeServer | FL and Get-EcpVirtualDirectory | FL
    [PS] C:\Windows\system32>Get-ExchangeServer | FL
    RunspaceId                      : bdd191f7-2d42-4930-88b6-0b61f0a4e95d
    Name                            : NYC-HQXCH-02
    DataPath                        : C:\Program Files\Microsoft\Exchange Server\V14\Mailbox
    Domain                          : company.loc
    Edition                         : Enterprise
    ExchangeLegacyDN                : /o=company/ou=Exchange Administrative Group
                                      (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=NYC-HQXCH-02
    ExchangeLegacyServerRole        : 0
    Fqdn                            : NYC-HQXCH-02.company.loc
    CustomerFeedbackEnabled         :
    InternetWebProxy                :
    IsHubTransportServer            : True
    IsClientAccessServer            : True
    IsExchange2007OrLater           : True
    IsEdgeServer                    : False
    IsMailboxServer                 : True
    IsE14OrLater                    : True
    IsE15OrLater                    : False
    IsProvisionedServer             : False
    IsUnifiedMessagingServer        : False
    IsFrontendTransportServer       : False
    NetworkAddress                  : {ncacn_vns_spp:NYC-HQXCH-02, netbios:NYC-HQXCH-02, ncacn_np:NYC-HQXCH-02,
                                      ncacn_spx:NYC-HQXCH-02, ncacn_ip_tcp:NYC-HQXCH-02.company.loc, ncalrpc:NYC-HQXCH-02}
    OrganizationalUnit              : company.loc/NYC-HQXCH-02
    AdminDisplayVersion             : Version 14.3 (Build 123.4)
    Site                            : company.loc/Configuration/Sites/NewYorkHQ
    ServerRole                      : Mailbox, ClientAccess, HubTransport
    ErrorReportingEnabled           :
    StaticDomainControllers         : {}
    StaticGlobalCatalogs            : {}
    StaticConfigDomainController    :
    StaticExcludedDomainControllers : {}
    MonitoringGroup                 :
    WorkloadManagementPolicy        :
    CurrentDomainControllers        : {}
    CurrentGlobalCatalogs           : {}
    CurrentConfigDomainController   :
    ProductID                       : 02064-110-8022196-75756
    IsExchangeTrialEdition          : False
    IsExpiredExchangeTrialEdition   : False
    MailboxProvisioningAttributes   :
    RemainingTrialPeriod            : 00:00:00
    Identity                        : NYC-HQXCH-02
    IsValid                         : True
    ExchangeVersion                 : 0.1 (8.0.535.0)
    DistinguishedName               : CN=NYC-HQXCH-02,CN=Servers,CN=Exchange Administrative Group
                                      (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=company,CN=Microsoft
                                      Exchange,CN=Services,CN=Configuration,DC=company,DC=loc
    Guid                            : 1745c93f-419d-402c-b832-708958fc502c
    ObjectCategory                  : company.loc/Configuration/Schema/ms-Exch-Exchange-Server
    ObjectClass                     : {top, server, msExchExchangeServer}
    WhenChanged                     : 4/2/2014 1:50:56 PM
    WhenCreated                     : 8/25/2013 11:12:43 AM
    WhenChangedUTC                  : 4/2/2014 6:50:56 PM
    WhenCreatedUTC                  : 8/25/2013 4:12:43 PM
    OrganizationId                  :
    OriginatingServer               : SVR-DC-01.company.loc
    ObjectState                     : Unchanged
    RunspaceId                      : bdd191f7-2d42-4930-88b6-0b61f0a4e95d
    Name                            : NYC-HQARC-02
    DataPath                        : C:\Program Files\Microsoft\Exchange Server\V14\Mailbox
    Domain                          : company.loc
    Edition                         : Enterprise
    ExchangeLegacyDN                : /o=company/ou=Exchange Administrative Group
                                      (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=NYC-HQARC-02
    ExchangeLegacyServerRole        : 0
    Fqdn                            : NYC-HQARC-02.company.loc
    CustomerFeedbackEnabled         :
    InternetWebProxy                :
    IsHubTransportServer            : False
    IsClientAccessServer            : False
    IsExchange2007OrLater           : True
    IsEdgeServer                    : False
    IsMailboxServer                 : True
    IsE14OrLater                    : True
    IsE15OrLater                    : False
    IsProvisionedServer             : False
    IsUnifiedMessagingServer        : False
    IsFrontendTransportServer       : False
    NetworkAddress                  : {ncacn_vns_spp:NYC-HQARC-02, netbios:NYC-HQARC-02, ncacn_np:NYC-HQARC-02,
                                      ncacn_spx:NYC-HQARC-02, ncacn_ip_tcp:NYC-HQARC-02.company.loc, ncalrpc:NYC-HQARC-02}
    OrganizationalUnit              : company.loc/NYC-HQARC-02
    AdminDisplayVersion             : Version 14.3 (Build 123.4)
    Site                            : company.loc/Configuration/Sites/NewYorkHQ
    ServerRole                      : Mailbox
    ErrorReportingEnabled           :
    StaticDomainControllers         : {}
    StaticGlobalCatalogs            : {}
    StaticConfigDomainController    :
    StaticExcludedDomainControllers : {}
    MonitoringGroup                 :
    WorkloadManagementPolicy        :
    CurrentDomainControllers        : {}
    CurrentGlobalCatalogs           : {}
    CurrentConfigDomainController   :
    ProductID                       : 02064-110-8022196-75187
    IsExchangeTrialEdition          : False
    IsExpiredExchangeTrialEdition   : False
    MailboxProvisioningAttributes   :
    RemainingTrialPeriod            : 00:00:00
    Identity                        : NYC-HQARC-02
    IsValid                         : True
    ExchangeVersion                 : 0.1 (8.0.535.0)
    DistinguishedName               : CN=NYC-HQARC-02,CN=Servers,CN=Exchange Administrative Group
                                      (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=company,CN=Microsoft
                                      Exchange,CN=Services,CN=Configuration,DC=company,DC=loc
    Guid                            : c07f34f4-92f1-49f0-a412-d7094eaaba3b
    ObjectCategory                  : company.loc/Configuration/Schema/ms-Exch-Exchange-Server
    ObjectClass                     : {top, server, msExchExchangeServer}
    WhenChanged                     : 4/2/2014 1:50:57 PM
    WhenCreated                     : 9/9/2013 3:27:16 PM
    WhenChangedUTC                  : 4/2/2014 6:50:57 PM
    WhenCreatedUTC                  : 9/9/2013 8:27:16 PM
    OrganizationId                  :
    OriginatingServer               : SVR-DC-01.company.loc
    ObjectState                     : Unchanged
    RunspaceId                      : bdd191f7-2d42-4930-88b6-0b61f0a4e95d
    Name                            : SVR-EXCH-01
    DataPath                        : C:\Program Files\Microsoft\Exchange Server\V15\Mailbox
    Domain                          : company.loc
    Edition                         : StandardEvaluation
    ExchangeLegacyDN                : /o=company/ou=Exchange Administrative Group
                                      (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=SVR-EXCH-01
    ExchangeLegacyServerRole        : 0
    Fqdn                            : SVR-EXCH-01.company.loc
    CustomerFeedbackEnabled         :
    InternetWebProxy                :
    IsHubTransportServer            : True
    IsClientAccessServer            : True
    IsExchange2007OrLater           : True
    IsEdgeServer                    : False
    IsMailboxServer                 : True
    IsE14OrLater                    : True
    IsE15OrLater                    : True
    IsProvisionedServer             : False
    IsUnifiedMessagingServer        : True
    IsFrontendTransportServer       : True
    NetworkAddress                  : {ncacn_vns_spp:SVR-EXCH-01, netbios:SVR-EXCH-01, ncacn_np:SVR-EXCH-01,
                                      ncacn_spx:SVR-EXCH-01, ncacn_ip_tcp:SVR-EXCH-01.company.loc, ncalrpc:SVR-EXCH-01}
    OrganizationalUnit              : company.loc/SVR-EXCH-01
    AdminDisplayVersion             : Version 15.0 (Build 847.32)
    Site                            : company.loc/Configuration/Sites/Chicago-COLO1
    ServerRole                      : Mailbox, ClientAccess
    ErrorReportingEnabled           :
    StaticDomainControllers         : {}
    StaticGlobalCatalogs            : {}
    StaticConfigDomainController    :
    StaticExcludedDomainControllers : {}
    MonitoringGroup                 :
    WorkloadManagementPolicy        : DefaultWorkloadManagementPolicy_15.0.825.0
    CurrentDomainControllers        : {}
    CurrentGlobalCatalogs           : {}
    CurrentConfigDomainController   :
    ProductID                       :
    IsExchangeTrialEdition          : True
    IsExpiredExchangeTrialEdition   : False
    MailboxProvisioningAttributes   :
    RemainingTrialPeriod            : 179.06:13:25.2449639
    Identity                        : SVR-EXCH-01
    IsValid                         : True
    ExchangeVersion                 : 0.1 (8.0.535.0)
    DistinguishedName               : CN=SVR-EXCH-01,CN=Servers,CN=Exchange Administrative Group
                                      (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=company,CN=Microsoft
                                      Exchange,CN=Services,CN=Configuration,DC=company,DC=loc
    Guid                            : 91eb6d6b-bfd0-4ce0-80ce-67585e7cbeae
    ObjectCategory                  : company.loc/Configuration/Schema/ms-Exch-Exchange-Server
    ObjectClass                     : {top, server, msExchExchangeServer}
    WhenChanged                     : 5/13/2014 6:54:13 PM
    WhenCreated                     : 5/13/2014 6:41:08 PM
    WhenChangedUTC                  : 5/13/2014 11:54:13 PM
    WhenCreatedUTC                  : 5/13/2014 11:41:08 PM
    OrganizationId                  :
    OriginatingServer               : SVR-DC-01.company.loc
    ObjectState                     : Unchanged
    [PS] C:\Windows\system32>Get-EcpVirtualDirectory | FL
    RunspaceId                      : bdd191f7-2d42-4930-88b6-0b61f0a4e95d
    AdminEnabled                    : True
    OwaOptionsEnabled               : True
    Name                            : ecp (Default Web Site)
    InternalAuthenticationMethods   : {Basic, Ntlm, WindowsIntegrated}
    MetabasePath                    : IIS://NYC-HQXCH-02.company.loc/W3SVC/1/ROOT/ecp
    BasicAuthentication             : True
    WindowsAuthentication           : True
    DigestAuthentication            : False
    FormsAuthentication             : False
    LiveIdAuthentication            : False
    AdfsAuthentication              : False
    OAuthAuthentication             : False
    DefaultDomain                   : company.loc
    GzipLevel                       : High
    WebSite                         : Default Web Site
    DisplayName                     : ecp
    Path                            : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\ecp
    ExtendedProtectionTokenChecking : None
    ExtendedProtectionFlags         : {}
    ExtendedProtectionSPNList       : {}
    AdminDisplayVersion             : Version 14.3 (Build 123.4)
    Server                          : NYC-HQXCH-02
    InternalUrl                     : https://webmail.companytravel.com/ecp
    ExternalUrl                     :
    ExternalAuthenticationMethods   : {Fba}
    AdminDisplayName                :
    ExchangeVersion                 : 0.10 (14.0.100.0)
    DistinguishedName               : CN=ecp (Default Web
                                      Site),CN=HTTP,CN=Protocols,CN=NYC-HQXCH-02,CN=Servers,CN=Exchange Administrative
                                      Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=company,CN=Microsoft
                                      Exchange,CN=Services,CN=Configuration,DC=company,DC=loc
    Identity                        : NYC-HQXCH-02\ecp (Default Web Site)
    Guid                            : 0963f097-ff86-4d8f-a98a-8be409068eae
    ObjectCategory                  : company.loc/Configuration/Schema/ms-Exch-ECP-Virtual-Directory
    ObjectClass                     : {top, msExchVirtualDirectory, msExchECPVirtualDirectory}
    WhenChanged                     : 4/2/2014 1:50:57 PM
    WhenCreated                     : 8/30/2013 1:06:50 PM
    WhenChangedUTC                  : 4/2/2014 6:50:57 PM
    WhenCreatedUTC                  : 8/30/2013 6:06:50 PM
    OrganizationId                  :
    OriginatingServer               : SVR-DC-01.company.loc
    IsValid                         : True
    ObjectState                     : Changed
    RunspaceId                      : bdd191f7-2d42-4930-88b6-0b61f0a4e95d
    AdminEnabled                    : True
    OwaOptionsEnabled               : True
    Name                            : ecp (Default Web Site)
    InternalAuthenticationMethods   : {Basic, Fba}
    MetabasePath                    : IIS://SVR-EXCH-01.company.loc/W3SVC/1/ROOT/ecp
    BasicAuthentication             : True
    WindowsAuthentication           : False
    DigestAuthentication            : False
    FormsAuthentication             : True
    LiveIdAuthentication            : False
    AdfsAuthentication              : False
    OAuthAuthentication             : False
    DefaultDomain                   :
    GzipLevel                       : Low
    WebSite                         : Default Web Site
    DisplayName                     : ecp
    Path                            : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\ecp
    ExtendedProtectionTokenChecking : None
    ExtendedProtectionFlags         : {}
    ExtendedProtectionSPNList       : {}
    AdminDisplayVersion             : Version 15.0 (Build 847.32)
    Server                          : SVR-EXCH-01
    InternalUrl                     : https://svr-exch-01.company.loc/ecp
    ExternalUrl                     :
    ExternalAuthenticationMethods   : {Fba}
    AdminDisplayName                :
    ExchangeVersion                 : 0.10 (14.0.100.0)
    DistinguishedName               : CN=ecp (Default Web Site),CN=HTTP,CN=Protocols,CN=SVR-EXCH-01,CN=Servers,CN=Exchange
                                      Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                      Groups,CN=company,CN=Microsoft
                                      Exchange,CN=Services,CN=Configuration,DC=company,DC=loc
    Identity                        : SVR-EXCH-01\ecp (Default Web Site)
    Guid                            : 052fdd05-42f4-471b-8759-525e93d6b97d
    ObjectCategory                  : company.loc/Configuration/Schema/ms-Exch-ECP-Virtual-Directory
    ObjectClass                     : {top, msExchVirtualDirectory, msExchECPVirtualDirectory}
    WhenChanged                     : 5/13/2014 6:52:11 PM
    WhenCreated                     : 5/13/2014 6:52:11 PM
    WhenChangedUTC                  : 5/13/2014 11:52:11 PM
    WhenCreatedUTC                  : 5/13/2014 11:52:11 PM
    OrganizationId                  :
    OriginatingServer               : SVR-DC-01.company.loc
    IsValid                         : True
    ObjectState                     : Changed

    Ok. Went ahead and tried https://<EX2013_FQDN/ecp/?ExchClientVer=15
    Still took me to the webmail.
    I also tried creating a user on 2013 mailbox database. gave all permissions. Still no luck.

  • How do you delete specific message from users in Exchange 2013 DAG database?

    Our network has been inundated with spam from INTUIT.COM with the SUBJECT: PAYMENT OVERDUE and contains a link to download a form from a Dropbox. Obviously, very suspicious and clearly spam. We're using Postini as our Edge Transport/ Spam filter but messages
    are still getting in. I've enable anti-spam on all my mailbox servers, set the SCL values but that hasn't worked.
    I understand that Exchange Edge Transport role has the more aggressive spam fighting features but Microsoft also recommends an online spam filter. 
    Needless to say, we've taken steps to quarantine those messages based on subject and sender in Postini but now would like to delete those messages from the users in went to. My users are two different DAG mailbox databases. I found this article http://www.techieshelp.com/delete-mail-from-multiple-mailboxes/ but
    the command didn't work. I'm thinking its because I have DAG and a couple of databases. I even tried "get-mailbox -database "databasename" | search-mailbox -searchquery subject: "Payment Overdue"" and that didn't work. 
    I'm running Exchange 2013 SP1 DAG across two sites comprised of four 2013 SP1 mailbox servers.

    Check this out
    http://technet.microsoft.com/en-us/library/ff459253%28v=exchg.150%29.aspx and specifically look at the section titled  "Search messages and log the search results"
    Or you can use this
    http://technet.microsoft.com/en-us/library/aa996371%28v=exchg.150%29.aspx with the WHATIF parameter
    Alternatively if you are open the 3rd party solutions check out Lucid8's DigiScope
    http://www.lucid8.com/product/digiscope.asp
    which would allow you to see the search results and then delete OR if desired you can set the On FIND action to Export to PST and then Delete so that you can preserve and then remove messages on the fly as the search system finds
    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

  • Unable to connect to local Exchange 2013 server when opening Exchange Management shell

    Hi Everyone
    Yesterday evenything was working fine, and then this morning, I`m unable to establish a connection with the Exchange shell. I receive the following errors. Any help is appreciated.
             Welcome to the Exchange Management Shell!
    Full list of cmdlets: Get-Command
    Only Exchange cmdlets: Get-ExCommand
    Cmdlets that match a specific string: Help *<string>*
    Get general help: Help
    Get help for a cmdlet: Help <cmdlet name> or <cmdlet name> -?
    Show quick reference guide: QuickRef
    Exchange team blog: Get-ExBlog
    Show full output for a command: <command> | Format-List
    Tip of the day #55:
    Want to view the mounted status of all mailbox databases? Type:
     Get-MailboxDatabase -Status | Format-Table Name, Server, Mounted
    VERBOSE: Connecting to C-EXCH02.BLCLAB.CA.
    New-PSSession : [c-exch02.blclab.ca] Connecting to remote server c-exch02.blclab.ca failed with the following error
    message : The client cannot connect to the destination specified in the request. Verify that the service on the
    destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
    running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
    command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
    the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
       gTransportException
        + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
    VERBOSE: Connecting to C-EXCH02.BLCLAB.CA.
    New-PSSession : [c-exch02.blclab.ca] Connecting to remote server c-exch02.blclab.ca failed with the following error
    message : The client cannot connect to the destination specified in the request. Verify that the service on the
    destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
    running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
    command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
    the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
       gTransportException
        + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
    VERBOSE: Connecting to C-EXCH01.BLCLAB.CA.
    New-PSSession : [c-exch01.blclab.ca] Connecting to remote server c-exch01.blclab.ca failed with the following error
    message : The client cannot connect to the destination specified in the request. Verify that the service on the
    destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
    running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
    command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
    the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
       gTransportException
        + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
    VERBOSE: Connecting to C-EXCH02.BLCLAB.CA.
    New-PSSession : [c-exch02.blclab.ca] Connecting to remote server c-exch02.blclab.ca failed with the following error
    message : The client cannot connect to the destination specified in the request. Verify that the service on the
    destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
    running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
    command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
    the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
       gTransportException
        + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
    VERBOSE: Connecting to C-EXCH01.BLCLAB.CA.
    New-PSSession : [c-exch01.blclab.ca] Connecting to remote server c-exch01.blclab.ca failed with the following error
    message : The client cannot connect to the destination specified in the request. Verify that the service on the
    destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
    running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
    command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
    the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
       gTransportException
        + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
    Failed to connect to an Exchange server in the current site.
    Enter the server FQDN where you want to connect.:
    VERBOSE: Connecting to .
    New-PSSession : Cannot bind parameter 'ConnectionUri'. Cannot convert value
    "http:///powershell?serializationLevel=Full;ExchClientVer=15.0.516.32;clientApplication=ManagementShell;TargetServer="
    to type "System.Uri". Error: "Invalid URI: The hostname could not be parsed."
    At line:1 char:30
    + New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
    +                              ~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidArgument: (:) [New-PSSession], ParameterBindingException
        + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.NewPSSessionCommand
    [PS] C:\Windows\system32>
    Ernie Prescott
    Updated information.
    I can succussfully connect to the exchange powershell from a remote computer, using this method.
    $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri
    http://<FQDN of Exchange 2013 Client Access server>/PowerShell/ -Authentication Kerberos
    Import-PSSession $Session
    So the problem is localised on the server.
    Regards

    Hi
    Try the steps for Error 1 on this link
    http://www.petenetlive.com/KB/Article/0000477.htm
    Hope it will help
    Cheers
    If you have any feedback on our support, please click
    here
    Zi Feng
    TechNet Community Support

  • Exchange 2013 - Cannot remove DataBase due to Arbitration Mailboxes

    Dear Experts,
    I'm running MS Exchange 2013 on Server 2012 R2.  I am cleaning/merging databases and have ran into a problem due to the arbitration mailboxes.  I am unable to delete a database because of the arbitration mailboxes.  
    First, I identified all the mailboxes in the DB I wanted to move (DB01)
    Get-Mailbox -Database "DB01" -Arbitration
    I did the below to move the arbitration and user mailboxes to a different DB
    Get-Mailbox -Database "DB01" | New-MoveRequest -TargetDatabase "DB02"
    Get-Mailbox -Database "DB01" - Arbitration | New-MoveRequest -TargetDatabase "DB02"
    The move was successful, but I was unable to delete DB01 because of an error related to the arbitration mailboxes when I attempted to delete it.
    After researching this problem I used
    Get-Mailbox -Arbitration | Set-Mailbox -Arbitration -Database "DB02"
    I have verified the active arbitration mailboxes are on DB02 by using
    Get-Mailbox -Arbitration | Ft Name, Database
    Currently DB01 is dismounted and from what I can tell not doing anything except eating up a license.  Arbitration mailboxes still reside on DB01, but they are not active.  If anyone has any experience on how I can force the deletion of this database
    or remove the arbitration mailboxes for good it would make my boss and I so happy.  Thanks to everyone in advance.

    Dear Experts,
    I'm running MS Exchange 2013 on Server 2012 R2.  I am cleaning/merging databases and have ran into a problem due to the arbitration mailboxes.  I am unable to delete a database because of the arbitration mailboxes.  
    First, I identified all the mailboxes in the DB I wanted to move (DB01)
    Get-Mailbox -Database "DB01" -Arbitration
    I did the below to move the arbitration and user mailboxes to a different DB
    Get-Mailbox -Database "DB01" | New-MoveRequest -TargetDatabase "DB02"
    Get-Mailbox -Database "DB01" - Arbitration | New-MoveRequest -TargetDatabase "DB02"
    The move was successful, but I was unable to delete DB01 because of an error related to the arbitration mailboxes when I attempted to delete it.
    After researching this problem I used
    Get-Mailbox -Arbitration | Set-Mailbox -Arbitration -Database "DB02"
    I have verified the active arbitration mailboxes are on DB02 by using
    Get-Mailbox -Arbitration | Ft Name, Database
    Currently DB01 is dismounted and from what I can tell not doing anything except eating up a license.  Arbitration mailboxes still reside on DB01, but they are not active.  If anyone has any experience on how I can force the deletion of this database
    or remove the arbitration mailboxes for good it would make my boss and I so happy.  Thanks to everyone in advance.
    Please post the exact error when the database is mounted and you try to remove it.
    Is this a multi domain forest? Set: set-adserversettings -viewentireforest $true
    then check where the arbitration mailboxes are again:
    get-mailbox -arbitration
    Twitter!:
    Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2013 Database does not shrink

     Hi
    I'm  migrating  from  lotus  notes to exchange 2013  unfortunately  when converted  emails  from lotus  to pst  and imported into  exchange  I realized  later  that  a lot of replica
    folders with  similar content were present  in users  mailboxes  hence this impacted a lot on the growth of  edb[database]
    Problem
      I have delegated  access- full  logged  into user mailbox  deleted  the folders  and the  content . infact  on mailbox usage on the  mailbox properties  I see markable reduction of the  size of
    the  mailbox   however all this does not replicate to  the database  size  the space it occupies on the  disk /drive.
      I have deleted   and emptied the  deleted folders  and set the  default retention to 0 days.  
    But no change
    [PS] C:\Windows\system32> Get-MailboxDatabase -Status | select ServerName,Name,DatabaseSize
    ServerName                              Name                                   
    DatabaseSize
    S-HQ-EXMBX-01                           DB01                                   
    200 GB (214,748,364,800 bytes)
    S-HQ-EXMBX-01                           DB02                                   
    228.8 GB (245,618,442,240 bytes)
    S-HQ-EXMBX-01                           DB04                                   
    235.8 GB (253,134,635,008 bytes)
    S-HQ-EXMBX-01                           DB03                                   
    239.6 GB (257,295,384,576 bytes)
    Database
    Drive
    Total Storage
    Available Storage
    DB01
    F
    250 GB
    6.29 GB
    DB02
    G
    247 GB
    6.15 GB
    DB03
    H
    253 GB
    3.34 GB
    DB04
    I
    250 GB
    4.60 GB
    Total
    1000
    19 GB
    Logs are on different  drive . L
      Any help or advise the storage is extremely limited  

    So Ed is correct with his answer to shrink the DB's, however a few other issues to check and consider
    Where are your log files located, i.e. if on the same drive it could be that you have allot of space being taken up by the log files, especially post import so I would check that first.  Normally these should be truncated/cleaned up post successfully
    Exchange aware backup however I have seen the backup choke if there are too many logs.
    If the deleted data is now marked as white space then as Ed states the external physical size will remain the same until you defrag or move all the mailboxes to a new DB. However this is going to depend upon your deleted item and mailbox retention settings,
    i.e. if the deleted items have not past the current retention time frame then defrag nor the mailbox move will save you any space until those items have past the retention point.  You can of course set it to a lesser value
    http://technet.microsoft.com/en-us/library/bb123971%28v=exchg.150%29.aspx and then let it sit for a day, check the white space and if its an ample amount continue with the defrag or MB move.
     What is the available white space within each database?   Run the following from Exchange PowerShell "Get-MailboxDatabase
    -Status | select Name, AvailableNewMailboxSpace"
    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

  • Exchange 2013 database dismounts unexpectedly

    Errors logged on Exchange 2013:
    Log Name:      Application
    Source:        MSExchangeIS
    Date:          12/09/2013 8:22:28 AM
    Event ID:      1001
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      
    Description:
    Microsoft Exchange Server Information Store has encountered an internal logic error. Internal error text is (Unable to apply maintenance insert, index corruption?
    Log Name:      Application
    Source:        MSExchangeIS
    Date:          12/09/2013 8:22:29 AM
    Event ID:      1002
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      
    Description:
    Unhandled exception (Microsoft.Exchange.Diagnostics.ExAssertException: ASSERT: Unable to apply maintenance insert, index corruption?
    Log Name:      Application
    Source:        MSExchange Common
    Date:          12/09/2013 8:22:37 AM
    Event ID:      4999
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      
    Description:
    Watson report about to be sent for process id: 11204, with parameters: E12, c-RTL-AMD64, 15.00.0712.024, M.E.Store.Worker, M.E.S.Storage.LazyIndexing, M.E.S.S.L.LogicalIndex.HandleIndexCorruptionInternal, M.E.Diagnostics.ExAssertException, 213a, 15.00.0712.000.
    ErrorReportingEnabled: True
    KB2846288 appeared to be related but we are already on CU2:
    Name                : XXXXXXXX
    Edition             : Standard
    AdminDisplayVersion : Version 15.0 (Build 712.24)
    Anyone else?
    Ramu V Ramanan

    Randomly approx once per week. Always on the same mailbox database. 
    Drives have plenty of space, memory and pagefile are fine.
    Log Name:      Application
    Source:        MSExchangeIS
    Date:          7/05/2014 11:46:53 a.m.
    Event ID:      1001
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:     
    Description:
    Microsoft Exchange Server Information Store has encountered an internal logic error. Internal error text is (Unable to apply maintenance insert, index corruption?
    Log Name:      Application
    Source:        MSExchangeIS
    Date:          7/05/2014 11:46:53 a.m.
    Event ID:      1002
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      
    Description:
    Unhandled exception (Microsoft.Exchange.Diagnostics.ExAssertException: ASSERT: Unable to apply maintenance insert, index corruption?
    Log Name:      Application
    Source:        MSExchangeIS
    Date:          7/05/2014 11:46:53 a.m.
    Event ID:      1013
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      
    Description:
    The mailbox with mailboxguid "xxxxxxxxxxxxxx" caused crash or resource outage on database (GUID="xxxxxxxxxxxxxxx")
    Log Name:      Application
    Source:        MSExchange Common
    Date:          7/05/2014 11:46:53 a.m.
    Event ID:      4999
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:     
    Description:
    Watson report about to be sent for process id: 18108, with parameters: E12, c-RTL-AMD64, 15.00.0775.038, M.E.Store.Worker, M.E.S.Storage.LazyIndexing, M.E.S.S.L.LogicalIndex.HandleIndexCorruptionInternal, M.E.Diagnostics.ExAssertException, 213a, 15.00.0775.008.
    ErrorReportingEnabled: False

  • Large Mail.que database in Exchange 2013

    [Background]
    Since Exchange 2013 is released, some user may come across the following situations:
    The space of disk C is used up.
    The transport service stops processing messages.
    The Mailbox server is crash.
    In this case, the issue can be resolved with checking with the mail.que file which is in the following path on the Mailbox server:
    C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue
    [Symptom]
    The Mail.que file on all Exchange 2013 servers grows very large and it’s even over 20 GB.
    [Cause]
    It’s a by design behavior.
    Different from the previous Exchange server, Safety Net which has the same function with the Transport dumpster in Exchange 2013 takes up the volume of the mail.que file and
    it’s the feature which is responsible for the large size of the mail.que in Exchange 2013.
     And here is a reference about the feature Safety Net in Exchange 2013:
    http://technet.microsoft.com/en-us/library/jj657495(v=exchg.150).aspx
    [Workarounds]
    1. Allocate large space for the Exchange 2013 installation or increase the volume for Exchange 2013.
    These articles will also provide further detail of size calculating:
    http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
    http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
    (See section: “Transport storage requirements”)
    2. Moved queue database to another drive by using
    Move-DatabasePath
    3. Reduce the SafetyNetHoldTime and MessageExpirationTimeouton values to one day (default values are 2 days). And these commands can be in use:
    Set-TransportConfig SafetyNetHoldTime 1.00:00:00
    Get-TransportService | Set-TransportService -MessageExpirationTimeout 1.00:00:00
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    [Background]
    Since Exchange 2013 is released, some user may come across the following situations:
    The space of disk C is used up.
    The transport service stops processing messages.
    The Mailbox server is crash.
    In this case, the issue can be resolved with checking with the mail.que file which is in the following path on the Mailbox server:
    C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue
    [Symptom]
    The Mail.que file on all Exchange 2013 servers grows very large and it’s even over 20 GB.
    [Cause]
    It’s a by design behavior.
    Different from the previous Exchange server, Safety Net which has the same function with the Transport dumpster in Exchange 2013 takes up the volume of the mail.que file and
    it’s the feature which is responsible for the large size of the mail.que in Exchange 2013.
     And here is a reference about the feature Safety Net in Exchange 2013:
    http://technet.microsoft.com/en-us/library/jj657495(v=exchg.150).aspx
    [Workarounds]
    1. Allocate large space for the Exchange 2013 installation or increase the volume for Exchange 2013.
    These articles will also provide further detail of size calculating:
    http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
    http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
    (See section: “Transport storage requirements”)
    2. Moved queue database to another drive by using
    Move-DatabasePath
    3. Reduce the SafetyNetHoldTime and MessageExpirationTimeouton values to one day (default values are 2 days). And these commands can be in use:
    Set-TransportConfig SafetyNetHoldTime 1.00:00:00
    Get-TransportService | Set-TransportService -MessageExpirationTimeout 1.00:00:00
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.
    You cant move the queue database with move-databasepath. You have to follow this method:
    http://technet.microsoft.com/en-us/library/bb125177(v=exchg.150).aspx
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Maybe you are looking for

  • How can I get imported Outlook email into folders in mail?

    I am a longtime PC user with email and calendar in MS Outlook (finally) converting to an iMac.  I used the Migration Assistant to transfer my old PC email to new iMAC running OSX Lion via ethernet.  On the old PC, I have ~15 years of stored emails in

  • How can I add XML metadata to simulate my application?

    I have a client application I support and I'm trying to use Dreamweaver as a tool to customize pages within the application. Each page, or report, consists of a HTM file with supporting CSS and Jscript used to render a view of data from the server th

  • Not all of the gestures work with my mid-2009 macbook's trackpad. How do I fix this?

    I recently upgraded to OS 10.7. I can make the two-finger scrolling work, but I can't make the mission control or zoom gestures work. How do I properly configure configure the built-in trackpad?

  • Illustrator and InDesign not responding

    Illustrator and InDesign keep shutting down or not responding. I am using large files(Im designing wallpaper for my final piece, i do it on Photoshop, then try and transfer parts to Illustartor to put it together and get it to line up at the edges et

  • IMac 27", Win7 x64

    I'm trying to list down specific problems regarding Windows 7 64-bit on a late 2009 27" iMac. I'm currently having the below problems: - Apple wireless keyboard only works on login screen - Magic mouse does not work at all - Graphic driver crashes re