Exchange 2013 Availability monitoring
Hi All,
I'm sort of stuck on the Exchange 2013 Probe Monitors, Monitors such as Imap, ActiveSync, Pop3 and FrontEndTransport keep failing. To fix/check the issue I'm following the below links:
http://technet.microsoft.com/en-us/library/ms.exch.scom.activesync(v=exchg.150).aspx
http://technet.microsoft.com/en-us/library/ms.exch.scom.imap(v=exchg.150).aspx
For example typing in Invoke-MonitoringProbe ActiveSync\ActiveSyncCTPProbe -Server server1.contoso.com | Format-List
I will get the following error:
WARNING: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
Not sure why I'm getting this error.
For Imap testing i.e. typing in Invoke-MonitoringProbe IMAP\ImapCTPProbe -Server server1.contoso.com | Format-List
I will get the following error:
WARNING: No mailboxes were found to use in the CTP probe.
I'm absolutely stumped on why I'm getting these errors.
I'm running my Exchange servers on Hyper-V 2012 (My Hyper-V 2012 is clustered and managed by VMM 2012 SP1)
I have 8 Exchange 2013 Enterprise CU6 nodes, with 2 DAGS
Each Exchange server is running 4 cores of Processor and 24Gig of Ram (Not using Dynamic Memory)
If someon can shed some light on this issue it would be most appreciated.
Regards
Mike
Hi,
Thanks for your update.
Based on my research, I notice that most of this issue occur on the code level.
Some threads that I've refered:
1.
https://social.msdn.microsoft.com/Forums/en-US/b4d46d2b-ed00-45ce-82ce-1a23790e52d5/index-was-out-of-range-must-be-nonnegative-and-less-than-the-size-of-the-collection-parameter?forum=csharplanguage
2.
http://stackoverflow.com/questions/19162248/index-was-out-of-range-must-be-non-negative-and-less-than-the-size-of-the-colle
Disclaimer: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information
found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
I suggest ask Exchange Development Forum to double confirm this issue. For your convenience:
https://social.technet.microsoft.com/Forums/office/en-US/home?forum=exchangesvrdevelopment
Thanks
Mavis Huang
TechNet Community Support
Similar Messages
-
Exchange 2013 Performance Monitor Data Collector Sets
I've noticed that the Exchange 2013 install created two data collector sets within Performance Monitor:
ExchangeDiagnosticsDailyPerformanceLog
ExchangeDiagnosticsPerformanceLog
These sets are creating daily log files saved in C:\Program Files\Microsoft\Exchange Server\V15\Logging\Diagnostics\DailyPerformanceLogs that are about 500MB in size, which are filling up our system volume.
I've tried stopping them, but they get restarted automatically. I also tried deleting them, but they get recreated automatically. Is there a way to disable these? We have a 3rd party tool that we use for performance monitoring and would like to avoid having
to delete these log files on a regular basis to keep our system volume from filling up.
As a workaround, I've changed the path where the log files get saved to a non existent drive letter, but would still like to disable the Data Collector Sets completely.
Thanks,
-CoryDo note,
These performance counters only take up 1 week and not more so it will be about 3-5 GB if you can`t spare this on you c disk you have not implemented any best practise exchange design.
specialy with todays JBOD SATA design your c disk will be 1TB +. Review your designs to match MS advise.
MCTS-MCITP exchange 2010 | MCTS-MCITP Exchange: 2007 | MCSA Messaging: 2003 | MCP windows 2000
Hello Martin,
Many of us are implementing exchange in a virtual environment, where disk is at a premium. Spending money on a 1 TB system drive is not a reasonable expectation. Even if that is best practice, there should be a way to manage the location and
size of these log files.
The inability to manage the location of log/performance data for centralization, or other reasons, is one more example of the disconnect between MS and their customer's use cases in regards to 2013.
These are the requirements for 2013 from MS:
At least 30 GB on the drive on which you install Exchange
An additional 500 MB of available disk space for each Unified Messaging (UM) language pack that you plan to install
200 MB of available disk space on the system drive
A hard disk that stores the message queue database on with at least 500 MB of free space.
So your statement is invalid as 30 GB is not even close to deal with the amount of log and performance data that we cannot modify in any way. -
Tuning Exchange 2013 HealthSet Monitors (example: MailboxTransport - Mapi.Submit.Monitor)
Hello everyone,
I was hoping some of you could help me out a bit with the new monitors in Exchange 2013.
Especially after updating to CU6 we are getting a lot of warnings from SCOM with different HealthSets that show as unhealthy. These are usually “OK” again when we log on to the server and run Get-ServerHealth or Get-HealthReport. The most common healthset is
Compliance, but also get warnings from MailboxTransport and ActiveSync.
If we do manage to log on before the healthset returns to healthy again, like in the example below, we can drill down a bit. We are however very unsure about what to do with this information. Perhaps we should change the threshold, but how do we find out exactly
what this monitor is reporting on? We know it has something to do with Mapi Submit, and that the threshold is 8, but not much more than that?
Get-ServerHealth SERVER | where {($_.healthsetname -eq "mailboxtransport") -and ($_.alertvalue -eq "unhealthy")} | ft name,alertvalue -auto
Name AlertValue
Mapi.Submit.Monitor Unhealthy
(Get-WinEvent -LogName Microsoft-Exchange-ActiveMonitoring/MonitorDefinition | % {[XML]$_.toXml()}).event.userData.eventXml | ?{$_.Name -like "Mapi.Submit.Monitor"}
auto-ns2 : http://schemas.microsoft.com/win/2004/08/events
xmlns : myNs
Id : 266
AssemblyPath : D:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Office.Datacenter.ActiveMonitoringLocal.dll
TypeName : Microsoft.Office.Datacenter.ActiveMonitoring.OverallXFailuresMonitor
Name : Mapi.Submit.Monitor
WorkItemVersion : [null]
ServiceName : MailboxTransport
DeploymentId : 0
ExecutionLocation : [null]
CreatedTime : 2014-11-20T08:51:03.5576888Z
Enabled : 1
TargetPartition : [null]
TargetGroup : [null]
TargetResource : MailboxTransport
TargetExtension : [null]
TargetVersion : [null]
RecurrenceIntervalSeconds : 0
TimeoutSeconds : 30
StartTime : 2014-11-20T08:51:03.5576888Z
UpdateTime : 2014-11-20T08:42:58.9416436Z
MaxRetryAttempts : 0
ExtensionAttributes : [null]
SampleMask : Mapi.Submit.Probe
MonitoringIntervalSeconds : 3600
MinimumErrorCount : 0
MonitoringThreshold : 8
SecondaryMonitoringThreshold : 0
MonitoringSamplesThreshold : 100
ServicePriority : 2
ServiceSeverity : 0
IsHaImpacting : 0
CreatedById : 57
InsufficientSamplesIntervalSeconds : 28800
StateAttribute1Mask : [null]
FailureCategoryMask : 0
ComponentName : ServiceComponents/MailboxTransport/High
StateTransitionsXml : <StateTransitions>
<Transition ToState="Unrecoverable" TimeoutInSeconds="0" />
</StateTransitions>
AllowCorrelationToMonitor : 0
ScenarioDescription : [null]
SourceScope : [null]
TargetScopes : [null]
HaScope : Server
Version : 65536
We have an Exchange 2007 server coexisting in the environment, but it is not in use and will be decommissioned.
ServerRole Edition AdminDisplayVersion
Mailbox, ClientAccess, HubTransport Standard Version 8.3 (Build 83.6)
Mailbox, ClientAccess Enterprise Version 15.0 (Build 995.29)
Mailbox, ClientAccess Enterprise Version 15.0 (Build 995.29)Thanks Belinda.
We had a look in the log you mentioned, and found some events that appear to be related.
Mailbox Transport Submission - the verification that the probe messages were successfully submitted within 5 minutes to HUB has failed.
This could indicate that the mailbox submissions are taking too long or not progressing at all.
SequenceNumber: 635515592255510017
Error: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
FailureContext: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
ExecutionContext: MapiSubmitLAMProbe started. This performs - 1. Submits a new message to Store 2. Checks results from previous Send Mail operation. Sequence # = 635515592255510017. First Run? = False. Previous mail submission to store
was successful. Results - # of previous results: 0. Could Not Find stages that ran. Previous SendMail failure - Mail submitted to Store during the previous run never reached SendAsCheck.
This may indicate a latency from Store to Submission Service. Investigating. Found lower SA latency. Indicates an issue in Submission service.
Investigate. In SendMail - NotificationID=00000044-0000-0000-0000-0000659c9601 Sending mail. SendMail finished. MapiSubmitLAMProbe finished with CheckPreviousMail
failure.
CheckPreviousRunMail exception details:
Current SendMail exception details:
MailWasSentInLastRun (0(no)/1(yes)): 1
CheckMailSuccess(0(no)/1(yes)): 0
SendMailSuccess(0(no)/1(yes)/2(no-noMDBs)/3(no-noActiveMDBs)/4(no-ignorableException)): 1
PreviousMailLatencies: <[email protected]>,,2014-11-20T08:37:58.817Z;LSRV=SERVER001.DOMAIN.locale:TOTAL=0.811|SA=0.343|MTSSDMO=0.426|MTSSDPL=0.002|MTSSDSS=0.008|MTSSDS=0.031|MTSS=0.466;;<[email protected]>,,2014-11-20T08:32:58.772Z;LSRV=SERVER001.DOMAIN.locale:TOTAL=0.702|SA=0.203|MTSSDMO=0.451|MTSSDPL=0.003|MTSSDSS=0.007|MTSSDS=0.047|MTSS=0.500;;<[email protected]>,,2014-11-20T08:27:58.664Z;LSRV=SERVER001.DOMAIN.locale:TOTAL=1.170|SA=0.530|MTSSDMO=0.548|MTSSDPL=0.002|MTSSDSS=0.035|MTSSDS=0.078|MTSS=0.647;;
GetPreviousMailLatencyFailures:
(The following are applicable if the mail was actually sent)
MailSentAt: 20.11.2014 08:42:58
TimeInSendingToStore: 62,3989
Sent Mail Result Details:
(InternetMessageId:<[email protected]>;
ItemEntryId:0 0 0 0 2E 57 BD C1 1C 4B 5C 47 9E 54 6E B8 B2 C5 75 38 7 0 FA 78 3 5 D1 D4 6 48 B2 FF B 4 D7 25 55 92 0 0 0 0 1 B 0 0 FA 78 3 5 D1 D4 6 48 B2 FF B 4 D7 25 55 92 0 0 18 1A CD F1 0 0 )
Properties of Sending mail
(Subject:00000044-0000-0000-0000-0000659c9601-MapiSubmitLAMProbe;
Sender:[email protected];
MbxGuid:340b204b-c716-4dfe-bbe1-cf09b5c73934;
MdbGuid:2a6b9801-1647-4378-bc11-6ff342d22fcf;
Recipient:[email protected];
Body and MessageClass:MessageClass:IPM.Note.MapiSubmitLAMProbe;MessageBody:This is a Probe Mapi message that's Submitted from Store to Mailbox transport Submission service to Hub transport service;
DoNotDeliver, DropMessageInHub and DeleteAfterSent:DoNotDeliver:True;DropMessageInHub:True;DeleteAfterSubmit:True;)
Probe Exception: 'System.ApplicationException: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.PerformProbeFinalAction(Boolean potentialForAlertBasedOnPreviousRun, Boolean potentialForAlertBasedOnCurrentRun, Exception previousRunVerificationException,
Exception currentRunException, DateTime timeMessageSentToStore)
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.DoWorkInternal(CancellationToken cancellationToken)
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.DoWork(CancellationToken cancellationToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
at System.Threading.Tasks.Task.Execute()'
Probe Result Name: 'Mapi.Submit.Probe'
Probe Result Type: 'Failed'
Monitor Total Value: '0'
Monitor Total Sample Count: '12'
Monitor Total Failed Count: '12'
Monitor Poisoned Count: '0'
Monitor First Alert Observed Time: '16.11.2014 21:40:10' -
Hello,
I'm getting several times per day the following alert in the Event Viewer of both my Mailbox Role servers which then raise an alert in SCOM 2012:
Log Name: Microsoft-Exchange-ManagedAvailability/Monitoring
Source: ManagedAvailability
Event ID: 4
Mean Scan Time has been greater than 60 seconds for the last 15 mins. Please investigate.
I'm not able to find information about what is being monitored and how to get rid of this events.
Any help appreciated.
Thank you in advance.
Raffaele ZamunerHi Amit,
here's the output from the EMS and the Event Viewer:
[PS] C:\Windows\system32>Get-ServerHealth [ServerName] | ?{$_.alertvalue -ne "Healthy" -and $_.alertvalue -ne "Disabled"}
Server State Name TargetResource
HealthSetName AlertValue ServerComp
onent
[ServerName] NotApplicable ScanTimeMeanMonitor FIPS
Unhealthy None
[ServerName] NotApplicable MaintenanceFailur... DAL
Unknown None
[ServerName] NotApplicable DatabaseLogicalPh... FINIT MailboxSpace Repairing None
[ServerName] NotApplicable DatabaseLogicalPh... MailboxSpace
Unhealthy None
[ServerName] Online Total.Shadow.Queu...
HubTransport Unhealthy HubTran...
[ServerName] NotApplicable MailboxDeliveryAv... MailboxTrans... Unhealthy
None
[ServerName] NotApplicable DatabaseLogicalPh... DB1 MailboxSpace Repairing None
[ServerName] NotApplicable DatabaseLogicalPh... MCS1 MailboxSpace Repairing None
[PS] C:\Windows\system32>get-serverhealth -Server [ServerName] -HealthSet AMScanTimeou
[PS] C:\Windows\system32>
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Exchange-ManagedAvailability" Guid="{C424A887-A89F-455F-8319-960917152221}" />
<EventID>4</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-06-03T07:23:16.626852900Z" />
<EventRecordID>1753</EventRecordID>
<Correlation />
<Execution ProcessID="1860" ThreadID="21496" />
<Channel>Microsoft-Exchange-ManagedAvailability/Monitoring</Channel>
<Computer>[ServerName].finit.local</Computer>
<Security UserID="S-1-5-18" />
</System>
- <UserData>
- <EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
<HealthSet>FIPS</HealthSet>
<Subject>FIPS health set unhealthy (ScanTimeMeanMonitor) - High Mean Scan Time</Subject>
<Message>Mean Scan Time has been greater than 60 seconds for the last 15 mins. Please investigate. ------------------------------------------------------------------------------- States of all monitors within the health set: Note: Data may be stale.
To get current data, run: Get-ServerHealth -Identity '[ServerName]' -HealthSet 'FIPS' State Name TargetResource HealthSet AlertValue ServerComponent ----- ---- -------------- --------- ---------- --------------- NotApplicable ScanProcessesRunningMonitor FIPS
Healthy None NotApplicable ScanProcessBelowMinimumMonitor FIPS Healthy None NotApplicable ScanRequestsTimedOutMonitor FIPS Healthy None NotApplicable ScanRequestsTimedOutUrgentMonitor FIPS Healthy None NotApplicable ScanRequestQueueTimeoutUrgentMonitor FIPS
Healthy None NotApplicable RecoveryQueueTimeoutUrgentMonitor FIPS Healthy None NotApplicable ScanTimeMeanMonitor FIPS Healthy None NotApplicable ScanRequestErrorRatioMonitor FIPS Healthy None NotApplicable ScanRequestErrorsMonitor FIPS Healthy None NotApplicable
TextExtractionErrorsMonitor FIPS Healthy None NotApplicable ObsoleteEngineInUseEventMonitor FIPS FIPS Healthy None NotApplicable MaintenanceFailureMonitor.FIPS FIPS Healthy None NotApplicable EngineNotEnabledForUpdatesEventMonitor FIPS FIPS Healthy None NotApplicable
EUSTerminationEventMonitor FIPS FIPS Healthy None NotApplicable EUSUnableToStartEventMonitor FIPS FIPS Healthy None NotApplicable ADFilteringSettingsWatcherStartFaile... FIPS FIPS Healthy None NotApplicable ScanningProcessRepeatedlyCrashingMon... FIPS FIPS
Healthy None NotApplicable FilteringManagementServiceDownMonitor FIPS Healthy None NotApplicable PrivateWorkingSetWarning.fms fms FIPS Healthy None NotApplicable PrivateWorkingSetError.fms fms FIPS Healthy None NotApplicable ProcessProcessorTimeWarning.fms
fms FIPS Healthy None NotApplicable ProcessProcessorTimeError.fms fms FIPS Healthy None NotApplicable ExchangeCrashEventError.fms fms FIPS Healthy None NotApplicable LongRunningWatsonWarning.fms fms FIPS Healthy None NotApplicable LongRunningWerMgrWarning.fms
fms FIPS Healthy None NotApplicable MicrosoftFailedUpdatesMonitor FIPS Healthy None NotApplicable MicrosoftEngineErrorsMonitor FIPS Healthy None NotApplicable MSClassificationEngineErrorsMonitor FIPS Healthy None States of all health sets: Note: Data may be
stale. To get current data, run: Get-HealthReport -Identity '[ServerName]' State HealthSet AlertValue LastTransitionTime MonitorCount ----- --------- ---------- ------------------ ------------ NotApplicable ActiveSync.Protocol Healthy 03/06/2014 05.04.35 9
NotApplicable Autodiscover.Protocol Healthy 03/06/2014 01.18.16 9 NotApplicable ActiveSync Healthy 03/06/2014 08.24.19 1 NotApplicable Antimalware Unhealthy 03/06/2014 09.18.14 11 NotApplicable ECP Healthy 03/06/2014 08.40.07 5 NotApplicable Ediscovery.Protocol
Healthy 03/06/2014 08.55.21 1 NotApplicable AD Healthy 03/06/2014 07.46.15 19 NotApplicable EDS Healthy 03/06/2014 08.52.30 90 NotApplicable EventAssistants Healthy 03/06/2014 09.21.03 15 NotApplicable EWS.Protocol Healthy 03/06/2014 09.15.04 11 NotApplicable
FEP Healthy 02/06/2014 09.04.40 2 NotApplicable FIPS Healthy 03/06/2014 09.15.34 28 NotApplicable Monitoring Healthy 03/06/2014 07.53.12 17 NotApplicable MailboxMigration Healthy 02/06/2014 14.03.19 3 Online UM.CallRouter Healthy 03/06/2014 04.44.11 8 NotApplicable
UM.Protocol Healthy 03/06/2014 05.05.45 22 NotApplicable OAB Healthy 03/06/2014 09.22.26 8 Online HubTransport Unhealthy 03/06/2014 09.22.35 133 NotApplicable EAS Healthy 02/05/2014 10.33.27 1 NotApplicable Autodiscover Healthy 03/06/2014 05.56.59 1 NotApplicable
DataProtection Healthy 03/06/2014 09.18.11 66 NotApplicable FreeBusy Healthy 02/05/2014 10.30.56 1 NotApplicable Clustering Healthy 03/06/2014 08.21.27 5 NotApplicable BitlockerDeployment Healthy 02/06/2014 22.00.36 1 NotApplicable ClientAccess.Proxy Healthy
02/06/2014 14.20.31 1 NotApplicable Compliance Healthy 02/05/2014 10.29.01 1 NotApplicable EWS Healthy 01/06/2014 12.57.38 1 NotApplicable FfoRws Healthy 01/06/2014 09.15.31 1 NotApplicable Places Healthy 03/06/2014 01.16.29 1 Online Transport Healthy 03/06/2014
08.23.33 10 NotApplicable RemoteMonitoring Healthy 02/06/2014 15.11.34 4 NotApplicable Search Healthy 03/06/2014 07.04.56 140 NotApplicable Inference Healthy 01/06/2014 23.57.09 1 NotApplicable OWA Healthy 03/06/2014 09.16.39 2 NotApplicable MailboxSpace Repairing
03/06/2014 09.22.02 17 NotApplicable MRS Healthy 03/06/2014 09.20.58 19 NotApplicable MessageTracing Healthy 03/06/2014 07.03.30 8 NotApplicable Network Healthy 03/06/2014 09.09.30 2 NotApplicable Calendaring Healthy 03/06/2014 09.19.16 8 NotApplicable PeopleConnect
Healthy 02/06/2014 14.10.08 1 NotApplicable IMAP Healthy 03/06/2014 08.10.29 1 NotApplicable POP Healthy 03/06/2014 05.54.04 1 NotApplicable ProcessIsolation Healthy 03/06/2014 07.39.59 22 NotApplicable Provisioning Healthy 03/06/2014 08.35.16 8 NotApplicable
Psws Healthy 03/06/2014 08.51.44 15 NotApplicable PublicFolders Healthy 03/06/2014 09.21.54 5 NotApplicable Outlook Healthy 03/06/2014 05.56.00 1 NotApplicable RPS Healthy 03/06/2014 08.22.48 1 NotApplicable RWS Healthy 03/06/2014 08.11.44 2 NotApplicable
Security Healthy 03/06/2014 08.11.33 8 NotApplicable SiteMailbox Healthy 03/06/2014 09.07.10 4 NotApplicable Store Healthy 03/06/2014 09.19.09 110 NotApplicable TransportSync Healthy 03/06/2014 08.11.56 8 NotApplicable UserThrottling Healthy 03/06/2014 09.21.49
8 NotApplicable FfoWebService Healthy 03/06/2014 07.07.43 1 NotApplicable DAL Healthy 03/06/2014 08.08.02 12 NotApplicable FfoWebstore Healthy 03/06/2014 07.07.33 1 NotApplicable AntiSpam Healthy 03/06/2014 06.02.52 8 NotApplicable OWA.Protocol.Dep Healthy
30/05/2014 17.45.35 1 NotApplicable MigrationMonitor Healthy 03/06/2014 08.33.07 3 NotApplicable MailboxTransport Unhealthy 03/06/2014 09.05.01 63 NotApplicable MSExchangeCertificateDeplo... Disabled 01/01/0001 01.00.00 2 NotApplicable OWA.Protocol Healthy
03/06/2014 07.33.09 9 NotApplicable Outlook.Protocol Healthy 02/06/2014 18.07.34 11 NotApplicable RPS.Protocol Healthy 02/05/2014 10.33.10 2 NotApplicable IMAP.Protocol Healthy 03/06/2014 07.31.55 7 NotApplicable Datamining Healthy 03/06/2014 05.06.42 7 NotApplicable
POP.Protocol Healthy 01/06/2014 19.02.12 7 Online FrontendTransport Healthy 02/06/2014 09.06.30 7 NotApplicable CentralAdmin Healthy 03/06/2014 07.37.18 7 Online ECP.Proxy Healthy 03/06/2014 06.30.43 7 Online RPS.Proxy Healthy 03/06/2014 09.22.16 28 NotApplicable
PushNotifications.Protocol Healthy 03/06/2014 08.34.46 7 Online RWS.Proxy Healthy 02/06/2014 22.55.09 7 Online Outlook.Proxy Healthy 03/06/2014 07.51.37 7 Online OutlookMapi.Proxy Healthy 03/06/2014 08.09.14 7 Note: Subsequent detected alerts are suppressed
until the health set is healthy again.</Message>
<Monitor>ScanTimeMeanMonitor</Monitor>
</EventXML>
</UserData>
</Event>
Raffaele Zamuner -
BPA for Exchange 2013 still in beta!?
Exchange 2013 is over 2 years old.
Is Microsoft ever going to release a BPA for their flagship messaging platform that's NOT in beta?Hi,
At present, there is only a beta of Best Practices Analyzer for Exchange 2013 available. If you want to get the latest information about it, please pay attention to the Exchange blog.
For your convenience:
http://blogs.technet.com/b/exchange/
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support -
Exchange 2013 Monitoring Mailboxes
I'm running exchange 2013 and it seems to have problems with health mailboxes (monitoring mailboxes). I have 5 mailbox databases on this server, DB1, DB2, DB3, DB4 and DB5.
I know there are 2 health mailboxes per mailbox database.
The command `Get-Mailbox -monitoring | Get-MailBoxStatistics` shows that several of these have not been accessed since December, even though they are in mounted Databases and powershell shows they are healthy.
There is also 2 health mailboxes that are missing from the below output because I got warninings saying these mailboxes have not been logged into yet.
[PS] C:\windows\system32> Get-Mailbox -monitoring | Get-MailBoxStatistics
DisplayName : HealthMailbox98fb2dc7692341ad8a3325ea2b14bbcc
ItemCount : 17426
LastLogonTime : 12/8/2012 3:28:04 PM
Database : DB1
DisplayName : HealthMailboxe27d88df28ae4d53af620604a83aca4d
ItemCount : 12386
LastLogonTime : 2/4/2013 3:29:46 PM
Database : DB1
DisplayName : HealthMailbox815f0ff077a342f7889a53ef38e40256
ItemCount : 291
LastLogonTime : 12/8/2012 3:26:43 PM
Database : DB3
DisplayName : HealthMailboxbca2f3409f1d4ae99098f48b574fc36d
ItemCount : 579
LastLogonTime : 12/8/2012 3:26:05 PM
Database : DB2
DisplayName : HealthMailbox2412e1a0e5d9415b8328f653b2e42efe
ItemCount : 209
LastLogonTime : 2/3/2013 6:08:41 PM
Database : DB3
DisplayName : HealthMailbox594b739a129941e688eafee6bbdfece6
ItemCount : 209
LastLogonTime : 2/3/2013 6:09:52 PM
Database : DB2
DisplayName : HealthMailboxc401cae2a70d4d659f5758908582406e
ItemCount : 210
LastLogonTime : 2/4/2013 3:28:59 PM
Database : DB4
DisplayName : HealthMailbox4b81211d555c4accad1f61a98700382e
ItemCount : 212
LastLogonTime : 2/3/2013 6:09:46 PM
Database : DB5
Warning: The user hasn't logged onto mailbox `<AD Domain>/users/HealthMailbox2c62876ca1bb45849c0daf2ecee6d715`, so there is no data to return. After the user logs on, this warning will no longer appear.
Warning: The user hasn't logged onto mailbox `<AD Domain>/users/HealthMailbox4399c592609a464d95c993ecee46f671`, so there is no data to return. After the user logs on, this warning will no longer appear.
I am also getting a lot of queued messages in the inboundproxy.com queue that have the subject line "Undelieverable: Inbound Proxy Probe". I dont know how to get these to stop. I just have to clean out the queue once a day to prevent it from getting
to large.
The last thing I notice is that I get a lot of audit errors in the event log when the system is trying to login to these mailboxes. That might be what is causing the issue. Here is one of the messages:
An account failed to log on.
Subject:
Security ID:
SYSTEM
Account Name:
<computer name here>$
Account Domain:
<AD DOMAIN>
Logon ID:
0x3E7
Logon Type: 8
Account For Which Logon Failed:
Security ID:
NULL SID
Account Name:
HealthMailboxbca2f3409f1d4ae99098f48b574fc36d@<domain.tld>
Account Domain:
Failure Information:
Failure Reason:
Unknown user name or bad password.
Status:
0xC000006D
Sub Status:
0xC0000064
Process Information:
Caller Process ID:
0x1265c
Caller Process Name:
C:\Windows\System32\inetsrv\w3wp.exe
Network Information:
Workstation Name:
<computer name here>
Source Network Address:
::1
Source Port:
34602
Detailed Authentication Information:
Logon Process:
Advapi
Authentication Package:
Negotiate
Transited Services:
Package Name (NTLM only):
Key Length:
0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
As you can see, the system can not login to to this health mailbox account. The one in my example one of the mailboxes that has not been logged into since december.
Is there anywhere to troubleshoot these? or possibly rebuild them? The is a huge lack of documentation on these mailboxes from microsoft, I can not find any commands to interact with these other then 'get-mailbox -monitoring'Because I KNOW it can lead to problems and do NOT know whether it can ever help me or not.
Here is one example of why I don't want it enabled:
http://social.technet.microsoft.com/Forums/exchange/en-US/7ed96489-92dd-441a-93e0-3d805b807dc3/maildeliveryprobemaildeliveryprobecom-and-inboundproxyinboundproxycom-in-the-logs
In my opinion there's one more strangeness about Managed Availability in Exchange 2013:
http://blogs.technet.com/b/exchange/archive/2012/09/21/lessons-from-the-datacenter-managed-availability.aspx
"When something is unhealthy its first action is to attempt to recover that component. Managed Availability provides multi-stage recovery actions – the first attempt might be to restart the application pool, the second attempt might
be to restart service, the third attempt might be to restart the server, and
the final attempt may be to offline the server so that it no longer accepts traffic.
If these attempts fail, managed availability
then escalates the issue to a human through event log notification."
...am I getting it right that Managed Availability is not going to alert an administrator BEFORE restarting/taking the server offline...just AFTER and in case it was unable to fix the issue??????!!!!! -
Exchange 2013 Untrusted Cross-Forest Availability Intermittently Working
Goal:
I’m attempting to configure cross-forest availability for Exchange 2013 using the instructions here:
http://technet.microsoft.com/en-us/library/bb125182%28v=exchg.150%29.aspx
At the very bottom of the page are three different methods. I have tried the first (per-user) and the third (untrusted) methods, with identical results. For various unfortunate reasons, I am unable to use the Microsoft Federated Gateway for availability
information (although that is configured in the production domain and I would use it if it were possible).
Situation:
When attempting to view availability information in either OWA or Outlook, the free/busy information typically isn’t visible. If you open and close Outlook a few times, creating meetings with the users in other domains, sometimes the other user’s information
will be visible, and sometimes it will not. When it is not, the area is filled with diagonal lines and hovering over it says “No Information”. The situation is the same in both Adatum trying to access Contoso, and in Contoso trying to access either
Adatum or Fabrikam.
I’m currently close to finishing up my third week with Microsoft Support on this issue, and am starting over with a third first level support person. They are quickly eroding what little confidence I had in them already. I’m posting here because
I’m desperate, and web searches for my errors turn up zero results. I fear this method of availability sharing doesn’t actually work correctly in Exchange 2013 as Microsoft is pushing organizations to use the Microsoft Federated Gateway, but I’d love
to heave about anyone getting this to work, or not.
Setup:
There are three separate domains I am working with (names changed to protect the innocent). Contoso.local is the production domain, containing Exchange 2007 and Exchange 2013 SP1 servers. Adatum.local is a test domain set up fresh with Exchange
2013 SP1. Fabrikam.com is a remote Exchange system that I others are connecting to without issue using Exchange 2010.
The Contoso and Adatum domain controllers are running Windows Server 2008 R2 SP1 and are running at a 2008 R2 functional levels. The Exchange 2013 servers are all at SP1 (results were the same prior to SP1), and the OS is Windows Server 2012.
Contoso has two sites, connected via 10Gbps links, and ~10ms latency, with Exchange 2013 CAS and mailbox servers in both sites. Adatum has a single site, and has two CAS and two mailbox servers. Fabrikam has one internet facing server to connect
to. A handful of contacts have been created in both Contoso and Adatum for the other domains, to select to view availability.
Contoso and Adatum domains sit on different subnets, but there is no firewall or filtering between their subnets. Routing between them is completely unimpeded. The Fabrikam server sits on another network across the internet, but firewalls have
been configured and I can browse the availability website from the Contoso CAS servers.
The CAS servers were originally set up to be load balanced, but working with Microsoft they’ve had me specify a single CAS server for autodiscover/EWS/ECP/OWA/etc in both Contoso and Adatum. The number of actual users on Exchange 2013 in Contoso is
~10. In Adatum, there are only a handful of mailboxes configured. The Exchange 2007 servers in Contoso are using Public Folders for free/busy replication for other domains right now, and we don’t care at the moment if they can use the 2013 availability.
None of our testing/configurations have involved the Exchange 2007 servers. There are no SPNs configured for the other domains in AD.
Errors:
There are three basic errors that are returned in Outlook diagnostics. The first is the timeout error. For a given mailbox server, the first time it is queried for availability information for a remote domain (after some amount of time of being
idle) it might not respond for 70 seconds (actually somewhere between 69 and 70 seconds each time when viewing the IIS logs), and eventually fails with the timeout error. If it doesn’t timeout, then it will respond with the Correct Response.
Once a particular mailbox server has timed out, it will typically immediately return the first Availability Error for all subsequent calls. Less frequently, it will return Availability Error 2. If a mailbox server returns the first Availability
Error, then it will continue to return that error until it times out again or starts working. Similarly, if a mailbox server returns the second Availability Error, then it will continue to return that error until it times out again or starts working.
If an IISRESET is performed on a mailbox server, then it will either timeout at the next cross-forest availability request, or work. There is never an issue accessing availability information for users in the same domain as the request.
If the remote Exchange is in an errored state, then the response includes the error. For example, if the mailbox servers in the remote domain are turned off, and the local mailbox server that you are querying happens to be responding correctly
for the remote domain, then it will return an error about how no mailbox servers are available in adatum.local to service the request.
There are no Event Log errors that correspond to failed requests of any type. IIS logs don’t show anything beyond what is shown in the Outlook diagnostics. There are no DNS or Active Directory Replication errors in the Event Logs.
Timeout error:
CalendarEvents : {}
ViewType : None
MergedFreeBusyStatus : {}
WorkingHours :
Result : Error
ErrorCode : ErrorTimeoutExpired
ErrorMessage : Microsoft.Exchange.InfoWorker.Common.Availability.TimeoutExpiredException: Request could not be processed in time. Timeout occurred during 'LookupRecipientsBatchBegin'.
. Name of the server where exception originated: Mailbox01
ErrorDetails : {}
ErrorProperties : {}
Availability Error:
CalendarEvents : {}
ViewType : None
MergedFreeBusyStatus : {}
WorkingHours :
Result : Error
ErrorCode : ErrorProxyRequestProcessingFailed
ErrorMessage : Unable to send cross-forest request for mailbox <Free BusyTest>SMTP:[email protected] because of invalid configuration., inner exception: Microsoft.Exchange.InfoWorker.Common.Availability.AutoDiscoverFailedException:
AvailabilityAddressSpace 'adatum.local' couldn't be used because the Autodiscover endpoint couldn't be discovered.
. Name of the server where exception originated: Mailbox01
ErrorDetails : {}
ErrorProperties : {}
Availability Error 2:
CalendarEvents : {}
ViewType : None
MergedFreeBusyStatus : {}
WorkingHours :
Result : Error
ErrorCode : ErrorProxyRequestProcessingFailed
ErrorMessage : Unable to send cross-forest request for mailbox <Free BusyTest>SMTP:[email protected] because of invalid configuration., inner exception: Microsoft.Exchange.InfoWorker.Common.Availability.AddressSpaceNotFoundException:
Configuration information for forest/domain swelab.wayad.corp.wayport.net could not be found in Active Directory.
at Microsoft.Exchange.InfoWorker.Common.Availability.TargetForestConfigurationCache.FindByDomain(OrganizationId
organizationId, String domainName)
at Microsoft.Exchange.InfoWorker.Common.Availability.QueryGenerator.GetTargetForestConfiguration(EmailAddress
emailAddress)
. Name of the server where exception originated: Mailbox02
ErrorDetails : {}
ErrorProperties : {}
Working:
CalendarEvents : {Microsoft.Exchange.WebServices.Data.CalendarEvent}
ViewType : FreeBusyMerged
MergedFreeBusyStatus : {Free, Free, Free, Free...}
WorkingHours : Microsoft.Exchange.WebServices.Data.WorkingHours
Result : Success
ErrorCode : NoError
ErrorMessage :
ErrorDetails : {}
ErrorProperties : {}
Start : 04/09/2014 00:00:00
End : 04/12/2014 00:00:00
Subject :
Location :
Testing Methodologies:
While it is possible to dig through Outlook diagnostics and OWA, we ended up scripting out these requests to save time. Microsoft support refuses to use the scripts, but they produce the same output that it takes them days to find in the logs, so I’ll
post them here to help anyone in the future.
Through reading the documentation and experimenting, it appears that the Exchange 2013 CAS servers really do just proxy availability requests from the client to the mailbox servers. At least by default, it seems to pick a mailbox server in the same
site, but which mailbox server in the site appears to be random. It will typically pick the same one repeatedly for a while.
The first script uses the Microsoft Exchange Web Services Managed API 2.1.
http://www.microsoft.com/en-us/download/details.aspx?id=42022
You specify a source email address, and a target address in the remote domain, and it creates a SOAP request that it sends to a CAS server of the source email address. The CAS proxies the request to the mailbox server which either responds with a failure
or the free/busy data.
The second script takes the XML SOAP request generated by the first script, and uses that to query a mailbox server directly. That allows you to test specific mailbox servers that are working or failing, instead of randomly using whichever mailbox
server the CAS happens to select. I generated a SOAP request with the first script that I knew had some data, and then copy/pasted it into the second script to verify if data was being returned.
I’ve deleted and recreated the availability address spaces in Contoso and Adatum for each other and Fabrikam multiple times. I’ve reset the password in the OrgWideAccount in both Adatum and Contoso, and viewed the lastBadPassword attribute in both
ADs to verify it wasn’t failing authentication. (A failed authentication also generates a 401 error that is returned to the client.) I can access the availability site of the other domain using the credentials of the OrgWideAccount without any
errors ever.
First Script:
# Import the Exchange Web Services module
Import-Module -Name "C:\Program Files (x86)\Microsoft\Exchange\Web Services\2.1\Microsoft.Exchange.WebServices.dll"
# Create the services object used to connect to Exchange
# You can specify a specific Exchange version, which I had to do to connect to 2007
# Exchange2007_SP1
# Exchange2010
# Exchange2010_SP1
# Exchange2010_SP2
# Exchange2013
# $ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2007_SP1
# $Service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)
$Service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService
$Service.UseDefaultCredentials = $true
# Specify an SMTP address. The autodiscover URL from the associated mailbox will be used to connect to Exchange
# This is used to distinguish resolving from the 2007 server versus 2013
#$Service.AutodiscoverUrl("[email protected]") # For Exchange 2007
$Service.AutodiscoverUrl("[email protected]") # For Exchange 2013
# Increase the amount output at the end to include the SOAP commands
$Service.TraceEnabled = $true
# Specify time frame to get free/busy for
$StartTime = [DateTime]::Parse([DateTime]::Now.ToString("yyyy-MM-dd 0:00"))
$EndTime = $StartTime.AddDays(7)
# Create the various objects needed to perform the EWS request
$drDuration = new-object Microsoft.Exchange.WebServices.Data.TimeWindow($StartTime,$EndTime)
$AvailabilityOptions = new-object Microsoft.Exchange.WebServices.Data.AvailabilityOptions
$AvailabilityOptions.RequestedFreeBusyView = [Microsoft.Exchange.WebServices.Data.FreeBusyViewType]::DetailedMerged
$Attendeesbatch = New-Object "System.Collections.Generic.List[Microsoft.Exchange.WebServices.Data.AttendeeInfo]"
$attendee = New-Object Microsoft.Exchange.WebServices.Data.AttendeeInfo($userSMTPAddress)
# Specify SMTP addresses of accounts to request availability for
#$Attendeesbatch.Add("[email protected]")
$Attendeesbatch.Add("[email protected]")
#$Attendeesbatch.Add("[email protected]")
#$Attendeesbatch.Add("[email protected]")
# Clear out old results so that a failed request doesn't show information still
$availresponse = ""
# Request the availability information from Exchange
$availresponse = $service.GetUserAvailability($Attendeesbatch,$drDuration,[Microsoft.Exchange.WebServices.Data.AvailabilityData]::FreeBusy,$AvailabilityOptions)
# Show summary information that would include errors
$availresponse.AttendeesAvailability
# Show all of the appointments in the requested time period
foreach($avail in $availresponse.AttendeesAvailability){
foreach($cvtEnt in $avail.CalendarEvents){
"Start : " + $cvtEnt.StartTime
"End : " + $cvtEnt.EndTime
"Subject : " + $cvtEnt.Details.Subject
"Location : " + $cvtEnt.Details.Location
Second Script:
# Change the server in this URL to specify which mailbox server to access
$url = 'https://mailbox01.contoso.local:444/EWS/Exchange.asmx'
# Uncomment the below lines if you want to query EWS using credentials other than
# the ones used to run the script.
#If(!(Test-Path variable:global:cred))
# $cred = Get-Credential
function Execute-SOAPRequest
[Xml] $SOAPRequest,
[String] $URL
write-host "Sending SOAP Request To Server: $URL"
$soapWebRequest = [System.Net.WebRequest]::Create($URL)
# These appear to be the only things needed in the headers when making the request
$soapWebRequest.ContentType = 'text/xml;charset="utf-8"'
$soapWebRequest.Accept = "text/xml"
$soapWebRequest.Method = "POST"
If(Test-Path variable:global:cred)
$soapWebRequest.Credentials = $cred
Else
$soapWebRequest.UseDefaultCredentials = $true
write-host "Initiating Send."
$requestStream = $soapWebRequest.GetRequestStream()
$SOAPRequest.Save($requestStream)
$requestStream.Close()
write-host "Send Complete, Waiting For Response."
$resp = $soapWebRequest.GetResponse()
$responseStream = $resp.GetResponseStream()
$soapReader = [System.IO.StreamReader]($responseStream)
$ReturnXml = [Xml] $soapReader.ReadToEnd()
$responseStream.Close()
write-host "Response Received."
return $ReturnXml
# The specing and line returns in the below variable are important for some reason
# For example, there must be a line return after the @' on the first line, or it's invalid...
# Change the line with this:
# <t:Address>[email protected]</t:Address>
# to the email address in the domain you want to query
$soap = [xml]@'
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<t:RequestServerVersion Version="Exchange2013_SP1" />
<t:TimeZoneContext>
<t:TimeZoneDefinition Name="(UTC-06:00) Central Time (US & Canada)" Id="Central Standard Time">
<t:Periods>
<t:Period Bias="P0DT6H0M0.0S" Name="Standard" Id="Std" />
<t:Period Bias="P0DT5H0M0.0S" Name="Daylight" Id="Dlt/1" />
<t:Period Bias="P0DT5H0M0.0S" Name="Daylight" Id="Dlt/2007" />
</t:Periods>
<t:TransitionsGroups>
<t:TransitionsGroup Id="0">
<t:RecurringDayTransition>
<t:To Kind="Period">Dlt/1</t:To>
<t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
<t:Month>4</t:Month>
<t:DayOfWeek>Sunday</t:DayOfWeek>
<t:Occurrence>1</t:Occurrence>
</t:RecurringDayTransition>
<t:RecurringDayTransition>
<t:To Kind="Period">Std</t:To>
<t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
<t:Month>10</t:Month>
<t:DayOfWeek>Sunday</t:DayOfWeek>
<t:Occurrence>-1</t:Occurrence>
</t:RecurringDayTransition>
</t:TransitionsGroup>
<t:TransitionsGroup Id="1">
<t:RecurringDayTransition>
<t:To Kind="Period">Dlt/2007</t:To>
<t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
<t:Month>3</t:Month>
<t:DayOfWeek>Sunday</t:DayOfWeek>
<t:Occurrence>2</t:Occurrence>
</t:RecurringDayTransition>
<t:RecurringDayTransition>
<t:To Kind="Period">Std</t:To>
<t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
<t:Month>11</t:Month>
<t:DayOfWeek>Sunday</t:DayOfWeek>
<t:Occurrence>1</t:Occurrence>
</t:RecurringDayTransition>
</t:TransitionsGroup>
</t:TransitionsGroups>
<t:Transitions>
<t:Transition>
<t:To Kind="Group">0</t:To>
</t:Transition>
<t:AbsoluteDateTransition>
<t:To Kind="Group">1</t:To>
<t:DateTime>2007-01-01T06:00:00.000Z</t:DateTime>
</t:AbsoluteDateTransition>
</t:Transitions>
</t:TimeZoneDefinition>
</t:TimeZoneContext>
</soap:Header>
<soap:Body>
<m:GetUserAvailabilityRequest>
<m:MailboxDataArray>
<t:MailboxData>
<t:Email>
<t:Address>[email protected]</t:Address>
</t:Email>
<t:AttendeeType>Required</t:AttendeeType>
<t:ExcludeConflicts>false</t:ExcludeConflicts>
</t:MailboxData>
</m:MailboxDataArray>
<t:FreeBusyViewOptions>
<t:TimeWindow>
<t:StartTime>2014-04-03T00:00:00</t:StartTime>
<t:EndTime>2014-04-10T00:00:00</t:EndTime>
</t:TimeWindow>
<t:MergedFreeBusyIntervalInMinutes>30</t:MergedFreeBusyIntervalInMinutes>
<t:RequestedView>DetailedMerged</t:RequestedView>
</t:FreeBusyViewOptions>
</m:GetUserAvailabilityRequest>
</soap:Body>
</soap:Envelope>
$ret = Execute-SOAPRequest $soap $url
# Uncomment out one of the below two lines to get output in different alternative formats
#$ret | Export-Clixml c:\temp\1.xml;Get-Content c:\temp\1.xml
#$ret.InnerXml
# If the request is successful, show the appointments, otherwise show the failure message
If ($ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.ResponseMessage.ResponseClass -eq 'Success')
$ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.FreeBusyView.CalendarEventArray.CalendarEvent
Else
$ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.ResponseMessageIn this case, the SMTP domain is the same as the AD domain. If the wrong domain were configured then the connection would never work, as opposed to sometimes work.
RunspaceId : abb30c12-c578-4770-987f-41fe6206a463
ForestName : adatum.local
UserName : adatum\availtest
UseServiceAccount : False
AccessMethod : OrgWideFB
ProxyUrl :
TargetAutodiscoverEpr :
ParentPathId : CN=Availability Configuration
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : adatum.local
DistinguishedName : CN=adatum.local,CN=Availability Configuration,CN=Wayport,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=contoso,DC=local
Identity : adatum.local
Guid : 3e0ebc2c-0ebc-4be8-83d2-077746180d66
ObjectCategory : contoso.local/Configuration/Schema/ms-Exch-Availability-Address-Space
ObjectClass : {top, msExchAvailabilityAddressSpace}
WhenChanged : 4/15/2014 12:33:53 PM
WhenCreated : 4/15/2014 12:33:35 PM
WhenChangedUTC : 4/15/2014 5:33:53 PM
WhenCreatedUTC : 4/15/2014 5:33:35 PM
OrganizationId :
OriginatingServer : dc01.contoso.local
IsValid : True
ObjectState : Unchanged -
Hi,
I currently have a single Exchange 2010 Server that has all the roles supporting about 500 users. I plan to upgrade to 2013 and move to a four server HA Exchange setup (a CAS array with 2 Server as CAS servers and one DAG with 2 mailbox Servers). My
goal is to plan out the transition in steps with no downtime. Email is most critical with my company.
Exchange 2010 is running SP3 on a Windows Server 2010 and a Separate Server as archive. In the new setup, rather than having a separate server for archiving, I am just going to put that on a separate partition.
Here is what I have planned so far.
1. Build out four Servers. 2 CAS and 2 Mailbox Servers. Mailbox Servers have 4 partitions each. One for OS. Second for DB. Third for Logs and Fourth for Archives.
2. Prepare AD for exchange 2013.
3. Install Exchange roles. CAS on two servers and mailbox on 2 servers. Add a DAG. Someone had suggested to me to use an odd number so 3 or 5. Is that a requirement?
4. I am using a third party load balancer for CAS array instead of NLB so I will be setting up that.
5. Do post install to ready up the new CAS. While doing this, can i use the same parameters as assigned on exchange 2010 like can i use the webmail URL for outlook anywhere, OAB etc.
6. Once this is done. I plan to move a few mailboxes as test to the new mailbox servers or DAG.
7. Testing outlook setups on new servers. inbound and outbound email tests.
once this is done, I can migrate over and point all my MX records to the new servers.
Please let me know your thoughts and what am I missing. I like to solidify a flowchart of all steps that I need to do before I start the migration.
thank you for your help in advanceHi,
okay, you can use 4 virtual servers. But there is no need to deploy dedicated server roles (CAS + MBX). It is better to deploy multi-role Exchange servers, also virtual! You could install 2 multi-role servers and if the company growths, install another multi-role,
and so on. It's much more simpler, better and less expensive.
CAS-Array is only an Active Directory object, nothing more. The load balancer controls the sessions on which CAS the user will terminate. You can read more at
http://blogs.technet.com/b/exchange/archive/2014/03/05/load-balancing-in-exchange-2013.aspx Also there is no session affinity required.
First, build the complete Exchange 2013 architecture. High availability for your data is a DAG and for your CAS you use a load balancer.
On channel 9 there is many stuff from MEC:
http://channel9.msdn.com/search?term=exchange+2013
Migration:
http://geekswithblogs.net/marcde/archive/2013/08/02/migrating-from-microsoft-exchange-2010-to-exchange-2013.aspx
Additional informations:
http://exchangeserverpro.com/upgrading-to-exchange-server-2013/
Hope this helps :-) -
Monitoring for Users Exchange 2013
Hi All,
How to find out which mailbox is generating high number of logs in Exchange 2013 ..............?Hi,
You can monitor Exchange 2013 with SCOM 2012
Refer from:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/monitoring-operations/monitoring-exchange-2013-scom-2012-part1.html
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please
make sure that you completely understand the risk before retrieving any suggestions from the above link.
Best Regards. -
Exchange 2013 Apps - "Office Store isn't available or is offline" Error
Hi there,
I have a problem with exchange apps. I want to add new app to my company exchange but I got an error which is "Office Store is not available". I tried to download some other apps but I see following error again.
I am using Exchange 2013 SP1 .Hi,
According your post, I notice that you cannot add app for Exchange 2013 with error “Office Store isn't available or is offline”.
If I misunderstand your concern, please do not hesitate to let me know.
How about add app from a URL or file location? We can try to add app for Outlook client or Word for testing:
https://store.office.com/appshome.aspx?legRedir=true&CorrelationId=83275012-a3a9-4bee-b761-96e1e38c957d&ui=pt-BR&rs=pt-BR&ad=BR&productgroup=Outlook
Access to the Office Store isn’t supported for mailboxes or organizations in specific regions. For more information, we need contact service provider to double confirm.
More details about Install or remove apps for Outlook for your organization, please refer to:
https://technet.microsoft.com/en-us/library/jj943752(v=exchg.150).aspx
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support -
EXMON "exchange server user monitor" for Exchange 2013?
Hello,
it Looks like EXMON is not supported for Exchange 2013. Is this correct or can i use it with Server 2012 R2 and Exchange 2013 (CU6++) ?
Is there any alternative to check high log growth rate to see which user is responsable for this?
Thanks for Feedback.
best,
MartinHi Martin,
Yes, ExMon is not supported for exchange 2013.
Except the suggestion above, here is an exclusive application for you reference, it could retrieve statistics for all or selected mailboxes in a specified database and server, it may give you some help:
Exchange Server Mailbox Statistics Tool - v1.6.2
The tool retrieves mailbox statistics which includes Folder Count, Total Items, Associated Items, Deleted Items, Total Items Size, Deleted Items Size, Oldest Item Date, Newest Item Date, Items Age, Mailbox Age and Quota details. It also includes an additional
option named "Archive Statistics Planner" which will let you search mailboxes and provide statistics report with specific dates.
Best regards,
Niko Cheng
TechNet Community Support -
How to enable health monitor on exchange 2013.
Dear All,
I ran the BPA for exchange 2013 on one of our CAS servers and received the below event, I need to enable the 'MessageCountMonitor' on exchange server. I have other counters that I need to enable but I'll start with this and apply for the rest.
Event:
The health alert value of 'MessageCountMonitor' on exchange server 'server_name' is 'Disabled', that may cause some special unhealthy state of the server. Run 'Get-ServerHealth' to get the detail information.
Learn more.Hello,
Yes, you can safely ignore this information reports.
Thanks,
Simon Wu
TechNet Community Support -
Exchange 2013 SP1 setup fails at prerequisite Analysis
I installed a completely new server network with Hyper-v 2012R2
I installed two virtual 2012R2 servers: DC01 as the Domain Controller of "testdomain.local" and EX01 as the Exchange server.
EX01 is joined the domain "testdomain" from DC01
I log in on EX01 with an in AD created testdomain\exadmin account who is member of domain admins, enterprise admins, schema admins, administrators and group policy creator owners.
I have run the command Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience,
NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing,
Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression,
Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation, Telnet-Client, RSAT-ADDS
on EX01
I have installed the Microsoft Unified Communications Managed API 4.0
Then I run the Exchange 2013 SP1 setup and the prerequisite check gives the following errors:
Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
Error:
Setup encountered a problem while validating the state of Active Directory: Active Directory server is not available. Error message: Active directory response: The LDAP server is unavailable. See the Exchange setup log for more information on this
error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
I can connect with the Active Directory Sites and Domains and other applets to the AD. So Why these errors???
HELP!
Regards, Manu
Manu van WinkelHi, thanks for the answer.
I restarted the server and did the "run as administrator": same result.
The first errormessage in the exchangesetup.log is:
[ERROR] Setup encountered a problem while validating the state of Active Directory: Active Directory server is not available. Error message: Active directory response: The LDAP server is unavailable. See the Exchange setup log for more information
on this error.
When I run dcdiag /s:DC01 from EX01 it passes all tests except:
DFSREvent "The RPC server is unavailable"
KccEvent "The RPC server is unavailable."
SystemLog "The RPC server is unavailable."
Could these be of any influence?
Running dcdiag on DC01 passes all tests.
The only thing I changed after setting up DC01, was changing the fixed IP-adres from 192.168.25.3 to 192.168.25.2, but I ran ipconfig /flushdns and ipconfig /registerdns and dcdiag /fix afterwards.
The only roles installed on DC01 are AD DS (I tried installing exchange before and after adding the AD DS role), AD, DNS, DHCP and Fileservices
I don't know where to look anymore....
Manu van Winkel -
Exchange 2013 SP1 OWA something went wrong
Hi,
I have a three node exchange 2013 DAG cluster that I upgraded to SP1 three days ago. All email flows currently work and ECP is available on all node on all browsers for all users. OWA was working on 2013 CU3. After
the upgrade to SP1 and I confirmed that all email flows were working, I did change the administrators username. I noticed OWA problems after that, but they would have happened before the administrator rename. I have confirmed
certificates and binding are correct on all three nodes. I did rebuild the OWA directory on one node with no success.
However OWA is only available using Firefox (tested on several users on several machines) . Logging on to ECP using IE 11 works fine (multiple users) Logging on to OWA using IE 11 give me the error. This is happening on
all three nodes using IE 11 but not Firefox 27
something went wrong
Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk.
X-OWA-Error: ClientError;exMsg='_u' is undefined;file=ReferenceError: '_u' is undefined at $LE (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:155) at Anonymous function (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:305913) at $8J (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:60172) at $E (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:59789) at $4pj (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:57814) at $6JC (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:58302) at Anonymous function (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:306768) at $8J (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:60172) at $E (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:59789) at $4pj (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:57814):406
X-OWA-Version: 15.0.847.32
X-FEServer: EXCH02
X-BEServer: null
Date: 1/2/1601 2:43:20 PM
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 3/13/2014 11:45:50 PM
Event ID: 10028
Task Category: None
Level: Error
Keywords: Classic
User: SYSTEM
Computer: exch01.loran3.net
Description:
DCOM was unable to communicate with the computer EXCH02.loran3.net using any of the configured protocols; requested by PID 115c (c:\windows\system32\inetsrv\w3wp.exe).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10028</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2014-03-14T05:45:50.109325400Z" />
<EventRecordID>12481</EventRecordID>
<Correlation />
<Execution ProcessID="596" ThreadID="1372" />
<Channel>System</Channel>
<Computer>exch01.loran3.net</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="param1">EXCH02.loran3.net</Data>
<Data Name="param2"> 115c</Data>
<Data Name="param3">c:\windows\system32\inetsrv\w3wp.exe</Data>
<Binary>3C5265636F726423313A20436F6D70757465723D286E756C6C293B5069643D3539363B332F31342F3230313420353A34353A35303A3130393B5374617475733D313832353B47656E636F6D703D323B4465746C6F633D313436313B466C6167733D303B506172616D733D303B3E3C5265636F726423323A20436F6D70757465723D286E756C6C293B5069643D3539363B332F31342F3230313420353A34353A35303A3130393B5374617475733D313832353B47656E636F6D703D323B4465746C6F633D3135333B466C6167733D303B506172616D733D343B7B506172616D23303A2D323134363839333030367D7B506172616D23313A347D7B506172616D23323A36383132367D7B506172616D23333A317D3E</Binary>
</EventData>
</Event> --------------------- I am also getting
the following error
Log Name: Application
Source: ASP.NET 4.0.30319.0
Date: 3/14/2014 12:46:26 AM
Event ID: 1309
Task Category: Web Event
Level: Warning
Keywords: Classic
User: N/A
Computer: exch01.loran3.net
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 3/14/2014 12:46:26 AM
Event time (UTC): 3/14/2014 6:46:26 AM
Event ID: 7741cd563e154a14a0ba52343b4e30ee
Event sequence: 328
Event occurrence: 87
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/2/ROOT/owa-1-130392504882416692
Trust level: Full
Application Virtual Path: /owa
Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\
Machine name: EXCH01
Process information:
Process ID: 8756
Process name: w3wp.exe
Account name: NT AUTHORITY\SYSTEM
Exception information:
Exception type: MapiExceptionIllegalCrossServerConnection
Exception message: MapiExceptionIllegalCrossServerConnection: Monitoring mailbox [] with application ID [Client=OWA] is not allowed to make cross-server calls from [EXCH01.loran3.net] to [EXCH03.loran3.net]
at Microsoft.Mapi.CrossServerDiagnostics.BlockCrossServerCall(ExRpcConnectionInfo connectionInfo, String mailboxDescription)
at Microsoft.Mapi.CrossServerConnectionPolicy.CheckAndBlockMonitoringMailboxes(ExRpcConnectionInfo connectionInfo)
at Microsoft.Mapi.CrossServerConnectionPolicy.Apply(ExRpcConnectionInfo connectionInfo)
at Microsoft.Mapi.ExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, Boolean unifiedLogon, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout,
TimeSpan callTimeout, Byte[] tenantHint)
at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, ClientIdentityInfo
clientIdentity, String applicationId, Byte[] tenantPartitionHint, Boolean unifiedLogon)
at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore, Boolean unifiedSession)
Request information:
Request URL:
https://localhost:444/owa/proxylogon.owa
Request path: /owa/proxylogon.owa
User host address: 127.0.0.1
User: LORAN3\SM_ae42d22c64ff48a5a
Is authenticated: True
Authentication Type: Kerberos
Thread account name: NT AUTHORITY\SYSTEM
Thread information:
Thread ID: 39
Thread account name: NT AUTHORITY\SYSTEM
Is impersonating: False
Stack trace: at Microsoft.Mapi.CrossServerDiagnostics.BlockCrossServerCall(ExRpcConnectionInfo connectionInfo, String mailboxDescription)
at Microsoft.Mapi.CrossServerConnectionPolicy.CheckAndBlockMonitoringMailboxes(ExRpcConnectionInfo connectionInfo)
at Microsoft.Mapi.CrossServerConnectionPolicy.Apply(ExRpcConnectionInfo connectionInfo)
at Microsoft.Mapi.ExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, Boolean unifiedLogon, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout,
TimeSpan callTimeout, Byte[] tenantHint)
at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, ClientIdentityInfo
clientIdentity, String applicationId, Byte[] tenantPartitionHint, Boolean unifiedLogon)
at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore, Boolean unifiedSession)
Custom event details:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="ASP.NET 4.0.30319.0" />
<EventID Qualifiers="32768">1309</EventID>
<Level>3</Level>
<Task>3</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-03-14T06:46:26.000000000Z" />
<EventRecordID>115079</EventRecordID>
<Channel>Application</Channel>
<Computer>exch01.loran3.net</Computer>
<Security />
</System>
<EventData>
<Data>3005</Data>
<Data>An unhandled exception has occurred.</Data>
<Data>3/14/2014 12:46:26 AM</Data>
<Data>3/14/2014 6:46:26 AM</Data>
<Data>7741cd563e154a14a0ba52343b4e30ee</Data>
<Data>328</Data>
<Data>87</Data>
<Data>0</Data>
<Data>/LM/W3SVC/2/ROOT/owa-1-130392504882416692</Data>
<Data>Full</Data>
<Data>/owa</Data>
<Data>C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\</Data>
<Data>EXCH01</Data>
<Data>
</Data>
<Data>8756</Data>
<Data>w3wp.exe</Data>
<Data>NT AUTHORITY\SYSTEM</Data>
<Data>MapiExceptionIllegalCrossServerConnection</Data>
<Data>MapiExceptionIllegalCrossServerConnection: Monitoring mailbox [] with application ID [Client=OWA] is not allowed to make cross-server calls from [EXCH01.loran3.net] to [EXCH03.loran3.net]
at Microsoft.Mapi.CrossServerDiagnostics.BlockCrossServerCall(ExRpcConnectionInfo connectionInfo, String mailboxDescription)
at Microsoft.Mapi.CrossServerConnectionPolicy.CheckAndBlockMonitoringMailboxes(ExRpcConnectionInfo connectionInfo)
at Microsoft.Mapi.CrossServerConnectionPolicy.Apply(ExRpcConnectionInfo connectionInfo)
at Microsoft.Mapi.ExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, Boolean unifiedLogon, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout,
TimeSpan callTimeout, Byte[] tenantHint)
at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, ClientIdentityInfo
clientIdentity, String applicationId, Byte[] tenantPartitionHint, Boolean unifiedLogon)
at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore, Boolean unifiedSession)
</Data>
<Data>https://localhost:444/owa/proxylogon.owa</Data>
<Data>/owa/proxylogon.owa</Data>
<Data>127.0.0.1</Data>
<Data>LORAN3\SM_ae42d22c64ff48a5a</Data>
<Data>True</Data>
<Data>Kerberos</Data>
<Data>NT AUTHORITY\SYSTEM</Data>
<Data>39</Data>
<Data>NT AUTHORITY\SYSTEM</Data>
<Data>False</Data>
<Data> at Microsoft.Mapi.CrossServerDiagnostics.BlockCrossServerCall(ExRpcConnectionInfo connectionInfo, String mailboxDescription)
at Microsoft.Mapi.CrossServerConnectionPolicy.CheckAndBlockMonitoringMailboxes(ExRpcConnectionInfo connectionInfo)
at Microsoft.Mapi.CrossServerConnectionPolicy.Apply(ExRpcConnectionInfo connectionInfo)
at Microsoft.Mapi.ExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, Boolean unifiedLogon, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout,
TimeSpan callTimeout, Byte[] tenantHint)
at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, ClientIdentityInfo
clientIdentity, String applicationId, Byte[] tenantPartitionHint, Boolean unifiedLogon)
at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore, Boolean unifiedSession)
</Data>
</EventData>
</Event>Thanks
I have three servers exch01,exch02,and exch03. All three have both CAS and mailbox server roles. This problem does not occur using firefox (OWA and ECP are available) but the problem occurs with IE 11 and safari (ECP
work, OWA dos not) I have tried this from different machines and different users. I have cleared the browser's cache and have even reloaded the client machines. The problem occurs across all three exchange servers.
I have used iis manager to confirm the binding are correct. (works on Firefox)
From the local server , If I browse to
https://localhost/ecp I get my ecp page. If I browse to
https://localhost/owaI get the something went wrong page (X-OWA-Error: ClientError;exMsg='_u' is undefined;file=ReferenceError: '_u' is undefined)
If I try to browse to https://localhost:444/owa/proxylogon.owa I get the error page "this page cannot be displayed"
I confirmed port 444 bindings are correct -
Exchange 2013 CU7 server performance/outage issues.
Hi Forum,
We are constantly faced with incidents from users that the connections are lost with the exchange server. As a result, we hired a consultant to install an new Exchange 2013 environment based on the Microsoft, VM-Ware and NetApp best practices.
We are still having problems with performance issues. From the client prospective, the performance has not changed, weekly hangs are still happening and I’m at my wits end.
This is our configuration:
2 Windows Server 2012 R2 CAS and DB
VM with 4 vCpu, 16GB, 1 Vmxnet3, IPv6 disabled (the Microsoft way)
VM Ware 5.1 U1
Cluster without AAP
DB1 active on Server 1 (Datacenter 1 with 3 host cluster)
DB2 active on Server 2 (Datacenter 2 with 3 host cluster)
Veeam 8 Backup (Move-ActiveMailboxDatabase DB2 -ActivateOnServer Server1 , backup server 2 then Move-ActiveMailboxDatabase back to
Server2.
Exchange is in Online-Mode due to Citrix XD VDI clients.
1300 Mailboxes and 750 users.
NetApp with SATA disks. (1.5TB E: Vol for DB1/1.5TB F: Vol for DB2)
No archiving
Unlimited mailbox sizes.
The problems are:
If we migrate a non-Exchange VM in the same cluster or to\from the same host, this results in a 30 second to 5 min Outlook outage;
If we make both DB’s active on mail server 1 and reboot server 2, this results in a 30 second to 5 min Outlook outage;
If we make both DB’s active on mail server 1 and do a Veeam backup of server 2, sometimes one of the DB’s go back to server 1, on its own;
While monitoring we see that the w3wp.exe and the Microsoft.Exchange.Store.worker.exe are consuming most of the cpu and memory;
What can I do to solve the outages?
Tnx. Timotatty.
Exchange server performance issues.
Hi Forum,
We are constantly faced with incidents from users that the connections are lost with the exchange server. As a result, we hired a consultant to install an new Exchange 2013 environment based on the Microsoft, VM-Ware and NetApp best practices.
We are still having problems with performance issues. From the client prospective, the performance has not changed, weekly hangs are still happening and I’m at my wits end.
This is our configuration:
2 Windows Server 2012 R2 CAS and DB
VM with 4 vCpu, 16GB, 1 Vmxnet3, IPv6 disabled (the Microsoft way)
VM Ware 5.1 U1
Cluster without AAP
DB1 active on Server 1 (Datacenter 1 with 3 host cluster)
DB2 active on Server 2 (Datacenter 2 with 3 host cluster)
Veeam 8 Backup (Move-ActiveMailboxDatabase DB2 -ActivateOnServer Server1 , backup server 2 then Move-ActiveMailboxDatabase back to
Server2.
Exchange is in Online-Mode due to Citrix XD VDI clients.
1300 Mailboxes and 750 users.
NetApp with SATA disks. (1.5TB E: Vol for DB1/1.5TB F: Vol for DB2)
No archiving
Unlimited mailbox sizes.
The problems are:
If we migrate a non-Exchange VM in the same cluster or to\from the same host, this results in a 30 second to 5 min Outlook outage;
If we make both DB’s active on mail server 1 and reboot server 2, this results in a 30 second to 5 min Outlook outage;
If we make both DB’s active on mail server 1 and do a Veeam backup of server 2, sometimes one of the DB’s go back to server 1, on its own;
While monitoring we see that the w3wp.exe and the Microsoft.Exchange.Store.worker.exe are consuming most of the cpu and memory;
What can I do to solve the outages?
Tnx. Timotatty.Hi Simon,<o:p></o:p>
Apparently we are using basic authentication which result in a FailingCode=401 as seen in the Event Log under Active Monitoring --> Probe Results from ECP and others. This
became apparent after reading this blog:
http://blogs.technet.com/b/ehlro/archive/2014/02/20/exchange-2013-managed-availability-healthset-troubleshooting.aspx<o:p></o:p>
We are now overriding some of the monitors which require Forms Based Authentication.<o:p></o:p>
Regarding the other 2 issues we have changed the licensing model for Veeam 8 to allow full throughput which will reduce the backup time and add compression.
The KEMP support team helped us by deselecting Use HTTP/1.1 under View/Modify Services --> ECP –> Modify --> Real Servers. This
now only flags a service (ECP or ActiveSync or OWA) as being down instead of an etire server should one component fail.<o:p></o:p>
I am satisfied but still not happy with the steps required to troubleshoot an Unhealthy Health Sets:<o:p></o:p>
Invoke-MonitoringProbe always returns with: WARNING: Could not find assembly or object type associated with monitor identity '<Healthe Set >\< Probe >'. Please ensure
that the given monitor identity exists on the server.
This makes it very difficult to troubleshoot
Unhealthy Health Sets.
Regards,
Timotatty
Maybe you are looking for
-
Hi, I am doing a small java project and I am expected to code all the GUI I need in just one class file. Can someone help me? My GUI consists of 2 JButtons, 2 JLabels and 1 JTextField. Also I need to have ActionListener for both of the buttons all in
-
URGENT........ACTIVITY TYPE AND THEIR ASSIGNEMENT TO WORK CENTER!!!!!!!!!!!
Hi Friends, I have A REAL URGENT REQUIREMENT as far as activity type and assignment to Work Center is concerned. I work for a client who is a manufacturer of Paint equipment. I'm responsible for capturing the cost of an assembly activity of spray gun
-
TS1717 Why Won't My iTunes won't upload CDs?
Any idea why my iTunes doesn't automatically begin uploading my CDs when I insert them into he CPU?
-
PROBLEMAS RECUPERAR/INSTALAR WINDOWS 8
Muy buenas, Hace año y medio, adquirí un Lenovo Z500 el cuál venía con Windows 8 preinstalado en su disco duro HDD interno. Bien, decidí adquirir un disco SSD, intalar Windows 7 y sustituirlo por el HDD de la casa. Mantengo el HDD con el WINDOWS 8 en
-
OIM 11g Pre Process event handler
Hi All, I had built a pre process event handler to generate userid and it was working fine. But i had slight modifications in the code. When i unregistered the old event handler and registered a new one, oim was still picking the old event handler. S