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

Similar Messages

CAS restart and Mailbox database dismount unexpectedly somtimes

Hi all,
In my environment I have 2 Exchange server 2013 (CAS + Mailbox Role both) CU2 : EX01 & EX02 in DAG01. Sometimes CAS service is restarted or Mailbox Database copy on Exchange servers is dismounted unexpectedly. For example today:
I have "Mailbox Database 01" copies on EX01 & EX02
Get-MailboxDatabaseCopyStatus "Mailbox Database 01"
Name Status
Mailbox Database 01\EX01 Healthy
Mailbox Database 01\EX02 Mounted
"Mailbox Database 01" copy on EX02 is dismounted, of course the other copy on EX01 is mounted automatically
Log Name:      Application
Source:        MSExchangeRepl
Date:          4/3/2015 2:32:19 PM
Event ID:      2153
Task Category: Service
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EX02.mydomain.com
Description:
The log copier was unable to communicate with server 'EX01.mydomain.com'. The copy of database 'Mailbox Database 01\EX02' is in a disconnected state. The communication error was: An error occurred while communicating with server 'EX01'. Error: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine. The copier will automatically retry after a short delay.
CAS service on EX01 , The Microsoft Exchange Mailbox Assistants service on EX02 are restarted
Log Name: System
Source: Service Control Manager
Date: 4/3/2015 3:25:49 PM
Event ID: 7031
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: EX01.mydomain.com
Description:
The Microsoft Exchange RPC Client Access service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
Log Name: System
Source: Service Control Manager
Date: 4/3/2015 3:25:51 PM
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: EX01.mydomain.com
Description:
The Microsoft Exchange RPC Client Access service entered the running state.
Log Name: System
Source: Service Control Manager
Date: 4/3/2015 3:25:54 PM
Event ID: 7032
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: EX01.mydomain.com
Description:
The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Microsoft Exchange RPC Client Access service, but this action failed with the following error:
An instance of the service is already running.
Log Name: System
Source: Service Control Manager
Date: 4/3/2015 3:30:28 PM
Event ID: 7031
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: EX02.mydomain.com
Description:
The Microsoft Exchange Mailbox Assistants service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
Log Name: System
Source: Service Control Manager
Date: 4/3/2015 3:30:30 PM
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: EX02.mydomain.com
Description:
The Microsoft Exchange Mailbox Assistants service entered the running state.
Log Name: System
Source: Service Control Manager
Date: 4/3/2015 3:30:33 PM
Event ID: 7032
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: EX02.mydomain.com
Description:
The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Microsoft Exchange Mailbox Assistants service, but this action failed with the following error:
An instance of the service is already running.
On EX01 I can see many 1309 , 2009 , 6002 , 4999 in Event Viewer on both servers, and they just used half of RAM
I'm going to upgrade to SP1 this weekend but please help me to figure out really reason of this issue, limit of max connections on Exchange/Window server , or Disk IO or something ?
Thanks for your help.

Last night I tried reseed Mailbox Database 01\EX02 , about 8:15 PM
I checked event viewer, last 2153 event happened on 7:49 PM, check around :
Get-MailboxDatabaseCopyStatus -Server ex02 | fl name,*incoming*,*outgoing*
Name : Mailbox Database 07\EX02
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Name : Mailbox Database 01\EX02
IncomingLogCopyingNetwork : {EX01,ReplicationDagNetwork01,An error occurred while communicating with server
'EX01'. Error: Unable to write data to the transport connection: An established
connection was aborted by the software in your host machine.}
OutgoingConnections :
Name : Mailbox Database 99\EX02
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Get-MailboxDatabaseCopyStatus -Server ex01 | fl name,*incoming*,*outgoing*
Name : Mailbox Database 01\EX01
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Name : Mailbox Database 99\EX01
IncomingLogCopyingNetwork : {EX02,ReplicationDagNetwork01}
OutgoingConnections :
Name : Mailbox Database 07\EX01
IncomingLogCopyingNetwork : {EX02,ReplicationDagNetwork01}
OutgoingConnections :
Then I suspend and update Mailbox Database 01\EX02
Suspend-MailboxDatabaseCopy -Identity "Mailbox Database 01\EX02"
Update-MailboxDatabaseCopy -Identity "Mailbox Database 01\EX02" -Network "DAG01\ReplicationDagNetwork01"
Confirm
Are you sure you want to perform this action?
Seeding database copy "Mailbox Database 01\EX02".
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"):
The seeding operation failed. Error: An error occurred while running prerequisite checks. Error: Log files exist in
'D:\Exchange Mailbox Database\Mailbox Database 01'. You must remove them before database seeding or reseeding can be
performed. You can use the Update-MailboxDatabaseCopy cmdlet with the -DeleteExistingFiles or -SafeDeleteExistingFiles
parameter to do this. [Database: Mailbox Database 01, Server: EX02.mydomain.com]
+ CategoryInfo : InvalidOperation: (Mailbox Database 01:String) [Update-MailboxDatabaseCopy], SeedPrepare
Exception
+ FullyQualifiedErrorId : [Server=EX02,RequestId=56f71c07-6209-4aae-94cb-bf3cfc0a38fd,TimeStamp=4/22/2015 1:0
5:56 PM] [FailureCategory=Cmdlet-SeedPrepareException] 5F5B4C53,Microsoft.Exchange.Management.SystemConfigurationT
asks.UpdateDatabaseCopy
+ PSComputerName : ex02.mydomain.com
I want they use DAG01\ReplicationDagNetwork01 (1Gbps) for reseeding database, then I tried to add -SafeDeleteExistingFiles
Update-MailboxDatabaseCopy -Identity "Mailbox Database 01\EX02" -Network "DAG01\ReplicationDagNetwork01" -SafeDeleteExistingFiles
Confirm
Are you sure you want to perform this action?
Seeding database copy "Mailbox Database 01\EX02".
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"):
The seeding operation failed. Error: An error occurred while running prerequisite checks. Error: An error occurred
when trying to run the database redundancy validation checks for database 'Mailbox Database 01' due to
'SafeDeleteExistingFiles' being specified. Error: There were database redundancy check failures for database 'Mailbox
Database 01' that may be lowering its redundancy and putting the database at risk of data loss. Redundancy Count: 1.
Expected Redundancy Count: 2. Detailed error(s):
ex02:
Database 'Mailbox Database 01' does not have enough copies configured to meet the validation criteria.
[Database: Mailbox Database 01, Server: EX02.mydomain.com]
+ CategoryInfo : InvalidOperation: (Mailbox Database 01:String) [Update-MailboxDatabaseCopy], SeedPrepare
Exception
+ FullyQualifiedErrorId : [Server=EX02,RequestId=48374aa6-1198-4976-a435-3eb034dc5b58,TimeStamp=4/22/2015 1:0
8:44 PM] [FailureCategory=Cmdlet-SeedPrepareException] 458ED9A2,Microsoft.Exchange.Management.SystemConfigurationT
asks.UpdateDatabaseCopy
+ PSComputerName : ex02.mydomain.com
I think I should stop here, search more about -DeleteExistingFiles before continue. So I Resume-MailboxDatabaseCopy "Mailbox Database 01\EX02"
Everything is fine, I checked again
[PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus -Server ex02 | fl name,*incoming*,*outgoing*
Name : Mailbox Database 07\EX02
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Name : Mailbox Database 01\EX02
IncomingLogCopyingNetwork : {EX01,ReplicationDagNetwork01}
OutgoingConnections :
Name : Mailbox Database 99\EX02
IncomingLogCopyingNetwork :
OutgoingConnections : {}
[PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus -Server ex01 | fl name,*incoming*,*outgoing*
Name : Mailbox Database 01\EX01
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Name : Mailbox Database 99\EX01
IncomingLogCopyingNetwork : {EX02,ReplicationDagNetwork01}
OutgoingConnections :
Name : Mailbox Database 07\EX01
IncomingLogCopyingNetwork : {EX02,ReplicationDagNetwork01}
OutgoingConnections
What is going on :) ? IncomingLogCopyingNetwork for Mailbox Database 01\EX02 is fine :) til mid night
This morning I view events on EX02 and event 2153 appears again on 7:30 AM , I run command et-MailboxDatabaseCopyStatus again
Get-MailboxDatabaseCopyStatus -Server ex02 | fl name,*incoming*,*outgoing*
Name : Mailbox Database 07\EX02
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Name : Mailbox Database 01\EX02
IncomingLogCopyingNetwork : {EX01,ReplicationDagNetwork01,An error occurred while communicating with server
'EX01'. Error: Unable to write data to the transport connection: An established
connection was aborted by the software in your host machine.}
OutgoingConnections :
Name : Mailbox Database 99\EX02
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Get-MailboxDatabaseCopyStatus -Server ex01 | fl name,*incoming*,*outgoing*
Name : Mailbox Database 01\EX01
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Name : Mailbox Database 99\EX01
IncomingLogCopyingNetwork : {EX02,ReplicationDagNetwork01}
OutgoingConnections :
Name : Mailbox Database 07\EX01
IncomingLogCopyingNetwork : {EX02,ReplicationDagNetwork01}
OutgoingConnections :
Any suggest ?

Cannot Move Exchange 2013 Database "Object couldn't be found on" Error

Hello,
I am trying to move my exchange 2013 database to a different partition, when I enter the move-databasepath command, It says the operation couldn't be performed because object "databaseName" could not be found on "Southwestdc01"
My Exchange server name is SWPSExchange, I am in the exchange management shell on my exchange server, but it's as if it is looking for the database on my Active directory server. I have one DC, and an exchange server. Is there a way to specify
which server the database is on? If it would only look for the database on the SWPSExchange, it would work.
i verified the database name, the issue is when I run the move-database command, it is looking for the database on the wrong server.
Thanks for the help!

Here is all the info:
My Exchange 2013 server is SWPSExchange, My AD Server is Southwestdc01, I am logged into the exchange server management shell on SWPSExchange, below is what I get, as you can see it is trying to find the database on Southwestdc01 instead of SWPSExchange.
[PS] C:\Windows\system32>Get-MailboxDatabase
Name                           Server          Recovery
ReplicationType
Mailbox Database 1279379856    SWPSEXCHANGE    False           None
PS] C:\Windows\system32>Move-DatabasePath -Identity 1279379856 -EdbFilePath E:\ExchangeDatabase\1279379856.edb
The operation couldn't be performed because object '1279379856' couldn't be found on 'SOUTHWESTDC01.Southwest.local'.
    + CategoryInfo          : NotSpecified: (:) [Move-DatabasePath], ManagementObjectNotFoundException
    + FullyQualifiedErrorId : 3961D47F,Microsoft.Exchange.Management.SystemConfigurationTasks.MoveDatabasePath
    + PSComputerName        : swpsexchange.southwest.local

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 and Mailbox sizing configuration feedback?

Hello,
I am in the process of deploying Exchange 2013 in our environment, it will co-exist with Exchange 2010 until we move everyone over to the new server.
My question is regards to the disk storage design, we have a SAN that Exchange will share with the rest of our Virtual Machines. I plan to have 20 live databases and 20 archive databases so I can balance out mailboxes per database so that each db is roughly
100GB in size.
The goal is is to keep the size down so that any database specific maintenance can finish quicker and if I ever had to deal with db corruption it is faster to restore, backup, etc.
My question is, is there a lot of overhead I will be adding onto the Exchange server by having 40 databases mounted?
Currently 300 users, 3.5TB in exchange databases between live and archive mailboxes (no mailbox caps), with 40 databases (20/20) it spreads out nicely with roughly 15 users per db, and db size is roughly 100GB.
My concern is having 40 databases mounted on a single EXCH2013 multi-role server? We have no DAG, etc.
The machine is a 4vCPU/32GB and the disks are on a Compellent tiered SAN shared among other VMs.
Thanks.

Hi,
It depends on various things. I would suggest you to start with Server Role Requirement Calculator to see your hardware is sufficient to handle the load or not...
http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
http://gallery.technet.microsoft.com/Exchange-2013-Server-Role-f8a61780
Blog |
Get Your Exchange Powershell Tip of the Day from here

Exchange 2013 database unplaned to active on another mailbox server

we have to four mailbox servers, two in primary site, two in dr site. it happens an unplaned failover issue, all of database are actived on mailbox server1, but some hours later, these database are unplaned to active on another mailbox server2, it also happens
in mailbox server2. that's why? after check eventlog, I found below:
AppLogEventID: 3169
AppLogEventMessage:
(Active Manager) Database MDB00 was successfully moved from shmbx01.ebaotech.com to SHMBX02.ebaotech.com. Move comment: Managed availability system failover initiated by Responder=OutlookRpcDeepTestFailover Component=Outlook.
also check server health, found OutlookRpcDeepTestMonitor is degraded, OutlookRpcSelfTestMonitor  is unhealty
Server State         Name
TargetResource                             HealthSetName    AlertValue ServerComponent
shmbx01 NotApplicable OutlookRpcSelfTestMonitor
Outlook.Protocol Unhealthy None
shmbx01 NotApplicable OutlookRpcDeepTestMonitor
Outlook.Protocol Degraded   None
shmbx01 NotApplicable PrivateWorkingSetWarningThresholdExceeded.m.e.rpcclientaccess.service microsoft.exchange.rpcclientaccess.service Outlook.Protocol Healthy    None
shmbx01 NotApplicable ProcessProcessorTimeErrorThresholdExceeded.m.e.rpcclientaccess.service microsoft.exchange.rpcclientaccess.service Outlook.Protocol Healthy    None
shmbx01 NotApplicable ExchangeCrashEventErrorThresholdExceeded.m.e.rpcclientaccess.service   microsoft.exchange.rpcclientaccess.service Outlook.Protocol Healthy    None
shmbx01 NotApplicable OutlookMapiHttpSelfTestMonitor
Outlook.Protocol Healthy    None
shmbx01 NotApplicable OutlookMapiHttpDeepTestMonitor
Outlook.Protocol Healthy    None
I don't know what causes this issue, and how can I resovle it to prevent the database unplaned failover, please help to look into it. thanks.

Hi,
Based on my knowledge, this issue can be caused by the following reasons:
1. Antivirus software. Please disable the Antivirus software to see if it works.
2. LmCompatibilityLevel. For Windows server 2008 R2 or Windows server 2012, this value should be 3. I suggest you modify the value to 3 on all of your Exchange 2013 servers to check the result.
2. Outlook responders. Please try to disable the Outlook responders to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

How to Remove and Re-Attach Exchange 2013 Database?

A database is being copied from a location that is too small to external storage.
Due to management wishes to prevent administrative mistakes, a journal DB that we need to keep for compliance reasons needs to be removed from EAC access. I understand that the
Remove-MailboxDatabase command will accomplish this.
However, management also wants to be able to re-attach that database at a later date.
Can this database just be re-mounted, or is it necessary to create a NEW database and bring the mailbox info from the old DB to the new one?
Thank you.

Destroying/removing the fact that the Exchange Journal DB ever existed on the server is a drastic way to go if you still want to access the data in the future. However if you wanted to do that then you would recover the data via RDB method and you
can see more on that here
http://technet.microsoft.com/en-us/library/ee332351%28v=exchg.150%29.aspx
The only other methods to gain access to that EDB in the future would be to
1. Move it then dismount it so that its not taking up any resources and can also be backed up as a flat file. Then when needed just remount the DB, do you work and dismount again.
2. Or use a 3rd party utility like DigiScope that can open the offline EDB without needing to be on an Exchange server.
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 Size didn't reduction after user move another DB.

Hi, I have two Exchange Server Ex01, Ex02 and two database DB1 and DB2. Already we move few user DB1 to DB2 but DB1 database size didn't reduction after move user.
Md. Ramin Hossain

Hi ,
If you delete or move a mailbox from a database will not create a free space on that database.Instead a white-space will be created on that database during the online defragmentation and that will not make any changes on the physical size of the database
.Then that white-space will be used when a new mailbox is created on that same database.
In case if you wanted to convert those white space to free space then you need to do an offline defragmentaion and that will make the physical change in the size of the database
Note : For offline defragmentation we should have the database to be in a dismounted state.
Command for offline defragmentation :
eseutil /d "path of the edb file"
But my suggestion would be to move the mailboxes to the newly created database instead of doing the offline defragmentation to attain the free space .Because it would take too much of time for the large databases to get completed.
Reference link for offline defragmentation :
http://exchangeserverpro.com/defrag-exchange-2010-mailbox-database/
Command to see the white space on the mailbox database :
ESEUTIL /MS "path of the edb file"
To execute the above we need the database to be in a dismounted state.
Reference Link :
https://social.technet.microsoft.com/Forums/office/en-US/4059c686-7c02-483b-9b15-891ca55295fe/running-the-eseutil-command-on-each-exchange-database-to-verify-database-whitespace?forum=exchangesvrgeneral
Please reply me if anything is unclear.
Thanks & Regards S.Nithyanandham

Exchange 2013 ECP "500 Unexpected Error" after Updates

Hi *,
after installing the latest Server 2012 Updates, i get the error "500 Unexpected Error" when i try to Login to the Exchange ECP. There wer no changes to the URL or front-/backend.
I also tried the Workaround focussed over here: http://social.technet.microsoft.com/Forums/exchange/en-US/777b51ee-330d-43cc-a56e-4614d44aed7b/unable-to-access-owa-or-ecp-something-went-wrong-or-500-unexpected-error?forum=exchangesvrclientsentries but
there were no entries like CN=Services at the ADSI edit.
Best Regards
Max @ Magelan Support

Hi Max,
Please double check the port bindings are correct.
Please try to run lodctr /r and reset IIS as administrator.
Found a similar thread for your reference:
Unable to access ECP. - "500 unexpected error"
http://social.technet.microsoft.com/Forums/en-US/b4b7c47e-cde4-4c62-8bb1-91a5430d4814/unable-to-access-ecp-500-unexpected-error?forum=exchangesvrclients
Thanks
Mavis
Mavis Huang
TechNet Community Support

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

What is the best practice on mailbox database size in exchange 2013

Hi,
does anybody have any links to good sites that gives some pros/cons when it comes to the mailbox database sizes in exchange 2013? I've tried to google it - but hasn't found any good answers. I would like to know if I really need more than 5 mailbox databases
or not on my exchange environment.

Hi
As far as I know, 2TB is recommended maximum database size for Exchange 2013 databases.
If you have any feedback on our support, please click
here
Terence Yu
TechNet Community Support

"The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook" in Exchange 2013

In Exchange 2013, Outlook finds a new connection point made up of the user’s mailbox GUID + @ + the domain portion of the user’s primary SMTP address. This change makes
it much less likely that users will see the dreaded message “Your administrator has made a change to your mailbox.”
http://technet.microsoft.com/en-us/library/dd298114(v=exchg.150).aspx
Although the error message in the topic has been already improved a lot in Exchange 2013, the users may still encounter them in some specific scenarios. We have collected them and let’s discuss them in this thread.
Symptom
=======================================
Consider the following scenario:
Exchange 2013 was installed for a migration from Exchange 2007/2010.
The legacy Exchange server is removed after successful migration.
Exchange 2013 may be updated to Exchange 2013 SP1.
Some users were being randomly prompted with a popup in their outlook client with the following message when connecting with Exchange 2013 server:
“The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook”
Cause
=======================================
The issue may be caused due to Public Folders.
The msExchHomePublicMDB attribute on Exchange 2013 databases was set to deleted legacy public folder object.
Solution
=======================================
Removed the Public Folder from all the Exchange
2013 Databases. To do it, we can use ADSIedit.msc and remove the arrtibute - msExchHomePublicMDB from all the Databases:
1. Open ADSIEdit.
2. Connect to the Configuration container.3.
Expand Configuration, expand CN=Configuration,DC=Domain,DC=com.4. Expand CN=Services -> CN=Microsoft Exchange -> CN=Domain -> CN=Administrative Groups -> CN=Exchange
Administrative Group -> CN=Databases.5. In the right hand pane you will see a list of databases.6.
Right-click the listed database object -> Properties.7. Check whether the msExchHomePublicMDB value is set to an unavailable value. If you see reference to the old database,
please clear the value.8. Click OK.9. Check the rest of the databases to make sure
that they are not populated in the same way.
References:
https://social.technet.microsoft.com/Forums/en-US/2f736bdd-1c00-4a22-97a5-95faeadf1495/exchange-2013-sp1-users-randomly-prompted-with-the-microsoft-exchange-administrator-has-made-a?forum=exchange2010
https://social.technet.microsoft.com/Forums/lync/en-US/7a7b3cf8-8761-421c-9d55-6c84e05531c0/the-administrator-has-made-a-change?forum=exchangesvrclients
https://social.technet.microsoft.com/Forums/en-US/0d71c843-b662-493c-ab6e-30708929ef18/2013-sp1-problem-the-microsoft-exchange-administrator-has-made-a-change-that-requires-you-quit-and?forum=exchangesvrdeploy
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

This one? http://support.microsoft.com/kb/2934750

Mailboxes migrated to Exchange 2013 - some Outlook profiles do not auto-update

** EDIT WITH SIMPLIFIED QUESTION:
Should I be able to manually create a profile in my Exchange 2013 environment without knowing the
GUID@DOMAIN server name? When I specify the Ex2010 server name and Outlook Anywhere settings, the server name does not auto-resolve to the GUID as other threads suggest. I am curious whether others are able to manually
create a profile without knowing the GUID@domain.
Hi all,
Our computers have Outlook configured to automatically configure a profile without any intervention. The profile is pointing to Exchange 2010, which is still running in our environment with Exchange 2013. When a user logs into a computer and
launches Outlook for the first time, Outlook fails to connect and a "Cannot open your default-email folders" error occurs.
I have verified that the Outlook Anywhere settings are configured correctly.
If I delete the profile and create a new one using Autodiscover, everything works fine.
Occurs on all clients - 2007, 2010, 2013, fully patched).
To troubleshoot, I attempted to manually create a new profile. I supplied the Exchange 2010 server name, and configured Outlook Anywhere. When hitting "Check Name", the server name stays to Exchange 2010 (does not switch to
[email protected]). When I launch Outlook, the connection fails. Again, an autodiscovery succeeds.
From my reading, it appears that Outlook should be updating the profile with the new GUID server name when it attempts to connect. The RPCClientAccessServer setting on the Exchange 2013 databases points to the Exchange 2010 CAS Array names.
Any ideas?
Thanks for your hel

Thanks for the reply .
AutodiscoverInternalURI is pointing to the Exchange 2013 environment, and is working fine when auto creating the profile. The Test Autodiscover function returns the correct URL for the mailboxes. The problem comes when manually creating
a profile. Other threads indicate that a manually created profile should auto change the server name when the Check Name option is selected, but mine remains with the Ex2010 cas name listed on the database, and the creation fails.
However, if the user had previously connected to Ex2010 prior to the mailbox move, the profile successfully changes to Ex2013. Only during manual creation does it fail, which is a problem because our existing PCs are configured to create
profiles without autodiscover.

Outlook 2007-2013 doesn't connect in non-cached mode to Exchange 2013.

Hello!
I have organization Exchange 2010 + Exchange 2013 in one AD site (hybrid organization)
Mailboxes based on Exchange 2010 servers work fine. But after moving one of mailboxes to
Exchange 2013 database, Outlook doesn't connect to mailbox in
non-cached mode. If I turn on cached mode this mailbox is connecting perfectly (OAB, Folders, PublicFolders, Addresslists).
I cleaned parameter "PublicFolderDatabase" for Exchange 2013 database, but the problem didn't solve.
In CAS
RpcHttp
log:
2015-01-22T12:08:12.720Z,MBXDB13,RpcHttp,S:Stage=BeginRequest;S:AuthType=Negotiate;S:HttpVerb=RPC_IN_DATA;S:UriQueryString=?MBXDB13.DOMAIN.local:6001;S:RpcHttpUserName=DOMAIN\USER;S:ServerTarget=[email protected];S:RequestId=267b0bf2-4361-4efb-9865-7f8d664b6e00;S:ClientIp=10.10.10.111
2015-01-22T12:08:12.720Z,MBXDB13,RpcHttp,S:Stage=PostAuthorizeRequest;S:UserName=DOMAIN\MBXDB13.domain.local:6001;S:RpcHttpUserName=DOMAIN\USER;S:ServerTarget=[email protected];S:RequestId=267b0bf2-4361-4efb-9865-7f8d664b6e00;S:ClientIp=10.10.10.111
Exchange Server 2013 Cumulative Update 7 (CU7)
are installed.

Hi Allen!
Thank you for reply!
Outlook cannot connect to all mailboxes on Exchange 2013 server.
>Get-OutlookAnywhere | FL Name,*auth*,*host*Name : Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic}
ExternalHostname : exchange2010.contoso.com
InternalHostname :
Name : Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic}
ExternalHostname : exchange2010.contoso.com
InternalHostname :
Name : Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic}
ExternalHostname : exchange2013.contoso.com
InternalHostname : cas1302.domain.local
Name : Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic}
ExternalHostname : exchange2013.contoso.com
InternalHostname : cas1301.domain.local
Outlook error message:
"Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The attempt log on to Microsoft Exchange has failed."
This error reproduced even in new profile. Repair does not help.

Enable legacy public folders for Exchange 2013 prior to migration?

We're about ready to migrate to Exchange 2013 from 2010. We have a public folder database on 2010 that users can't see once migrated to 2013. If I run through the commands according to the technet article "Configure legacy public folders where user
mailboxes are on Exchange 2013 servers" (https://technet.microsoft.com/en-us/library/dn690134(v=exchg.150).aspx), will users who's mailboxes are still on Exchange 2010 be able to see these public folders?

I know they've made alot of changes recently in how legacy public folders are handled in Exchange 2013 (mostly CU7), but I haven't had to do anything more than just setting the proper public folder database on the Exchange 2013 databases.
That being said, looking over the article you are not doing any moves, and it looks eerily similar to this blog post:
http://blogs.technet.com/b/exchange/archive/2014/11/07/on-premises-legacy-public-folder-coexistence-for-exchange-2013-cumulative-update-7-and-beyond.aspx
So I don't think this would hurt Public Folder access for your users in your legacy environment.
Did you deploy CU7? If so, then do what both articles say. If not try using Set-MailboxDatabase -Identity <2013 db name> -PublicFolderDatabase <PF DB NAME>
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

Exchange 2013 database dismounts unexpectedly

Similar Messages

Maybe you are looking for