Quantcast
Channel: Exchange Server 2013 - Administration, Monitoring, and Performance forum
Viewing all 1453 articles
Browse latest View live

Getting location from custom transport agent

$
0
0

img

I am developing a custom transport agent. My OnEndOfData looks like following

privatevoidMazeMapAgent_OnEndOfData(ReceiveMessageEventSource source,EndOfDataEventArgs e){EmailMessage emailMessage = e.MailItem.Message;}

My question is how can I access The Location from EmailMessage object.


atish


MoveAllReplicas.ps1 not working at all

$
0
0

I created a new DAG, moved all mailboxes over and now I want to migrate the public folders.

I created a new PF Database on NEWSERVER then I tried to use 'MoveAllReplicas.ps1 -Server OLDSERVER -NewServer NEWSERVER'.  When I run 'Get-PublicFolder \ -Recurse -Server NEWSERVER' and 'Get-PublicFolderStatistics -Server NEWSERVER' I get no results. However, if I run 'Get-PublicFolder \ -Recurse -Server OLDSERVER | ft Name,ParentPath,Replicas' the results show all the folders and the Replicas column has the newly created PF Database.

I have increased the logging on OLDSERVER and NEWSERVER in the EMC by going to 'Server Configuration' -> 'Mailbox' then right-clicking each server, choosing 'Manage Diagnostic Logging Problems'.  From there I drill down to 'MSExchangeIS' -> '9001 Public' and change 'Replication Incoming Messages', 'Replication NDRs' and 'Replication Outgoing Messages' to 'Expert'.  I then re-ran the MoveAllReplicas.ps1 command again but didn't see anything new in the EventLogs (maybe I'm looking in the wrong place).

How can I further troubleshoot not being able to see the Public Folders on NEWSERVER? If I re-run in reverse MoveAllReplicas.ps1 -Server NEWSERVER -NewServer OLDSERVER' will I at least be able to view Public Folders on OLDSERVER again?  Currently I can't access those PFs.

Thanks for any insight in advance!

New-MailboxExportRequest -ContentFilter Received filter issue

$
0
0

I'm trying to search for key words in emails that were received after a certain date. When I run the script below, I get emails with the correct words, but it also exports all the ones from dates prior to what i'm requesting.

Any ideas? 

$username = "User"
$date ="06/01/2015"

((All -like "*Word*") -and (Received -ge $date)) -or ((Attachment -like "*Word*") -and (Received -ge $date)) -or
((All -like "*Word2*") -and (Received -ge $date)) -or ((Attachment -like "*Word2*") -and (Received -ge $date)) -or
((All -like "*Word3") -and (Received -ge $date)) -or ((Attachment -like "*Word3*") -and (Received -ge $date)) -or
((All -like "*Word4*") -and (Received -ge $date)) -or ((Attachment -like "*Word4*") -and (Received -ge $date)) -or
((All -like "*Word5*") -and (Received -ge $date)) -or ((Attachment -like "*Word5*") -and (Received -ge $date)) -or
((All -like "*Word6*") -and (Received -ge $date)) -or ((Attachment -like "*Word6*") -and (Received -ge $date)) -or
((All -like "*Word7*") -and (Received -ge $date)) -or ((Attachment -like "*Word7*") -and (Received -ge $date)) -or
((All -like "*Word8*") -and (Received -ge $date)) -or ((Attachment -like "*Word8*") -and (Received -ge $date)) -or
((All -like "*Word9*") -and (Received -ge $date)) -or ((Attachment -like "*Word9*") -and (Received -ge $date))} -FilePath \\XXXX\XXXX\$username.pst

NetworkAdapterRssMonitor Unhealthy

$
0
0

Hi All!!

I have a Exchange 2013 CU13 Russian.

SCOM show me what the Network\NetworkAdapterRssMonitor is in Unhealthy state.

RunspaceId              : 2fe298c0-d62a-4fa4-a5ad-1f20c1515ba
Server                  : mailserver
CurrentHealthSetState   : NotApplicable
Name                    : NetworkAdapterRssMonitor
TargetResource          :
HealthSetName           : Network
HealthGroupName         : KeyDependencies
AlertValue              : Unhealthy
FirstAlertObservedTime  : 06.07.2016 0:51:52
Description             :
IsHaImpacting           : False
RecurranceInterval      : 600
DefinitionCreatedTime   : 06.07.2016 11:55:20
HealthSetDescription    :
ServerComponentName     : None
LastTransitionTime      : 06.07.2016 0:51:52
LastExecutionTime       : 12.07.2016 11:38:50
LastExecutionResult     : Succeeded
ResultId                : 105322716
WorkItemId              : 329
IsStale                 : False
Error                   :
Exception               :
IsNotified              : False
LastFailedProbeId       : 82
LastFailedProbeResultId : 57282586
ServicePriority         : 2
Identity                : Network\NetworkAdapterRssMonitor\
IsValid                 : True
ObjectState             : New


Every 4 hours in EventsLog appears this error:

HealthSet Network
Subject Состояние масштабирования сетевого адаптера на стороне приема не задано как "Включено" на сервере: MAILSERVER.

Message <b>Состояние масштабирования сетевого адаптера на стороне приема должно быть задано как "Включено". Включение RSS не устранило проблему. Сервер необходимо перезагрузить.</b> <hr /> <b>См.последнее сообщение об ошибке зонда:</b> {Последовательность не содержит элементов} <hr /> <b>Общее количество ошибок зонда сетевого адаптера за последние 20 минут:</b>{0} <hr />

Monitor NetworkAdapterRssMonitor 

This message tell me what the Receive Side Scaling is mast be Enable. But it is Enable already.

mailserver      NotApplicable       ActiveSync          Healthy
mailserver      NotApplicable       Compliance          Healthy
mailserver      NotApplicable       AMScanTimeout       Healthy
mailserver      NotApplicable       Autodiscover        Healthy
mailserver      NotApplicable       Autodiscover.Pro... Healthy
mailserver      NotApplicable       ActiveSync.Protocol Healthy
mailserver      NotApplicable       AMScanError         Healthy
mailserver      NotApplicable       AMMessagesDeferred  Healthy
mailserver      NotApplicable       AMADError           Healthy
mailserver      NotApplicable       AMTenantConfigError Healthy
mailserver      NotApplicable       AMService           Healthy
mailserver      Online              Autodiscover.Proxy  Healthy
mailserver      Online              ActiveSync.Proxy    Healthy
mailserver      NotApplicable       DLExpansion         Healthy
mailserver      Online              ECP.Proxy           Healthy
mailserver      NotApplicable       ECP                 Healthy
mailserver      NotApplicable       EDS                 Healthy
mailserver      NotApplicable       AD                  Healthy
mailserver      Online              EWS.Proxy           Healthy
mailserver      Online              OutlookMapiHttp.... Healthy
mailserver      Online              OAB.Proxy           Healthy
mailserver      Online              OWA.Proxy           Healthy
mailserver      Online              RPS.Proxy           Healthy
mailserver      Online              RWS.Proxy           Healthy
mailserver      Online              Outlook.Proxy       Healthy
mailserver      NotApplicable       EventAssistants     Healthy
mailserver      NotApplicable       AMScanners          Healthy
mailserver      NotApplicable       EWS.Protocol        Healthy
mailserver      Online              FrontendTransport   Healthy
mailserver      Online              HubTransport        Healthy
mailserver      NotApplicable       EWS                 Healthy
mailserver      NotApplicable       MailboxTransport    Healthy
mailserver      NotApplicable       AMEUS               Healthy
mailserver      NotApplicable       AMScannerCrash      Healthy
mailserver      NotApplicable       Monitoring          Healthy
mailserver      NotApplicable       DataProtection      Healthy
mailserver      NotApplicable       AMFMSService        Healthy
mailserver      NotApplicable       Clustering          Healthy
mailserver      NotApplicable       Search              Healthy
mailserver      Online              UM.CallRouter       Healthy
mailserver      NotApplicable       UM.Protocol         Healthy
mailserver      NotApplicable       OAB                 Healthy
mailserver      NotApplicable       EAS                 Healthy
mailserver      NotApplicable       Antimalware         Healthy
mailserver      NotApplicable       FreeBusy            Healthy
mailserver      NotApplicable       BitlockerDeployment Healthy
mailserver      NotApplicable       ClientAccess.Proxy  Healthy
mailserver      Online              Transport           Healthy
mailserver      NotApplicable       EmailManagement     Healthy
mailserver      NotApplicable       ExtendedReportWeb   Healthy
mailserver      NotApplicable       FEP                 Healthy
mailserver      NotApplicable       FfoRws              Healthy
mailserver      NotApplicable       Places              Healthy
mailserver      NotApplicable       FIPS                Healthy
mailserver      NotApplicable       RemoteMonitoring    Healthy
mailserver      NotApplicable       FfoCentralAdmin     Healthy
mailserver      NotApplicable       Inference           Healthy
mailserver      NotApplicable       OWA                 Healthy
mailserver      NotApplicable       FfoMonitoring       Healthy
mailserver      NotApplicable       OWA.Protocol.Dep    Healthy
mailserver      NotApplicable       JournalArchive      Healthy
mailserver      NotApplicable       MailboxSpace        Healthy
mailserver      NotApplicable       MailboxMigration    Healthy
mailserver      NotApplicable       Network             Unhealthy
mailserver      NotApplicable       OWA.Protocol        Healthy
mailserver      NotApplicable       Security            Healthy
mailserver      NotApplicable       UnifiedMailbox      Healthy
mailserver      NotApplicable       UnifiedGroups       Healthy
mailserver      NotApplicable       OWA.Attachments     Healthy
mailserver      NotApplicable       ProcessIsolation    Healthy
mailserver      NotApplicable       PeopleConnect       Healthy
mailserver      NotApplicable       OWA.WebServices     Healthy
mailserver      NotApplicable       HDPhoto             Healthy
mailserver      NotApplicable       HxService.Calendar  Healthy
mailserver      NotApplicable       HxService.Mail      Healthy
mailserver      NotApplicable       PublicFolders       Healthy
mailserver      NotApplicable       OWA.SuiteServices   Healthy
mailserver      NotApplicable       RemoteStore         Healthy
mailserver      NotApplicable       RPS                 Healthy
mailserver      NotApplicable       OutlookMapiHttp     Healthy
mailserver      NotApplicable       OutlookMapiHttp.... Healthy
mailserver      NotApplicable       Outlook.Protocol    Healthy
mailserver      NotApplicable       Outlook             Healthy
mailserver      NotApplicable       AntiSpam            Healthy
mailserver      NotApplicable       IMAP.Protocol       Healthy
mailserver      NotApplicable       CentralAdmin        Healthy
mailserver      NotApplicable       Datamining          Healthy
mailserver      NotApplicable       Store               Healthy
mailserver      NotApplicable       SiteMailbox         Healthy
mailserver      NotApplicable       Provisioning        Healthy
mailserver      NotApplicable       POP.Protocol        Healthy
mailserver      Online              SharedCache         Healthy
mailserver      NotApplicable       UserThrottling      Healthy
mailserver      NotApplicable       DAL                 Healthy
mailserver      NotApplicable       FfoUcc              Healthy
mailserver      NotApplicable       E4E                 Healthy
mailserver      NotApplicable       Calendaring         Healthy
mailserver      NotApplicable       Psws                Healthy
mailserver      NotApplicable       PushNotification... Healthy
mailserver      NotApplicable       MessageTracing      Healthy
mailserver      NotApplicable       MRS                 Healthy
mailserver      NotApplicable       OfficeGraph         Healthy
mailserver      NotApplicable       IMAP                Healthy
mailserver      NotApplicable       POP                 Healthy
mailserver      NotApplicable       PushNotifications   Healthy
mailserver      NotApplicable       StreamingOptics     Healthy
mailserver      NotApplicable       TimeBasedAssistants Healthy
mailserver      NotApplicable       TransportSync       Healthy
mailserver      NotApplicable       UnifiedPolicy       Healthy
mailserver      NotApplicable       FfoWebService       Healthy
mailserver      NotApplicable       FfoWebstore         Healthy
mailserver      Online              IMAP.Proxy          Healthy
mailserver      Online              POP.Proxy           Healthy

Get-ServerHealth mailserver | ?{$_.HealthSetName -eq "Network"} | ft Name, TargetResource, HealthSetName, AlertValue

DnsHostRecordMonitor                 Network             Healthy
NetworkAdapterMonitor                Network             Healthy
NetworkAdapterRssMonitor             Network             Unhealthy
MaintenanceFailureMonitor....        Network             Healthy
MaintenanceTimeoutMonitor....        Network             Healthy



Invoke-MonitoringProbe Network\NetworkAdapterRssProbe -server mailserver | fl
ПРЕДУПРЕЖДЕНИЕ: PopulateDefinition is not implemented for WorkItem 'Microsoft.Exchange.Monitoring.ActiveMonitoring.Local.Components.Network.Probes.NetworkAdapterRssProbe'



In EventLog I found this error:

ResultId 57327801    ServiceName Network    IsNotified 0    ResultName NetworkAdapterRssProbe    WorkItemId 82    DeploymentId 0    MachineName MAILSERVER    Error Последовательность не содержит элементов
    Exception System.InvalidOperationException: Последовательность не содержит элементов в System.Linq.Enumerable.First[TSource](IEnumerable`1 source) в Microsoft.Exchange.Monitoring.ActiveMonitoring.Local.Components.Network.Probes.NetworkAdapterRssProbe.DoWork(CancellationToken
 cancellationToken) в Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken) в Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0() в System.Threading.Tasks.Task.Execute()

    RetryCount 0    StateAttribute1 TCP Global Parameters could be obtained successfully. Запрос активного состояния... <br /> <br /> Глобальные параметры TCP <br /> ---------------------------------------------- <br /> Состояние масштабирования
 на стороне приема: enabled <br /> Состояние разгрузки Chimney: disabled <br /> Состояние NetDMA: disabled <br /> Прямой доступ к кэшу (DCA): disabled <br /> Уровень автонастройки окна получения: normal <br /> Поставщик
 дополнительного компонента контроля перегрузки: none <br /> Мощность ECN: enabled <br /> Метки времени RFC 1323: disabled <br /> Начальное RTO: 3000 <br /> Состояние объединения сегментов приема: enabled <br
 /> Устойчивость RTT без SACK: disabled <br /> Максимум повторных передач SYN: 2 <br /> <br /> <br />     StateAttribute2 [null]    StateAttribute3 [null]    StateAttribute4 [null]    StateAttribute5 [null]    StateAttribute6 0    StateAttribute7 0    StateAttribute8 0    StateAttribute9 0    StateAttribute10 0    StateAttribute11 [null]    StateAttribute12 [null]    StateAttribute13 [null]    StateAttribute14 [null]    StateAttribute15 [null]    StateAttribute16 0    StateAttribute17 0    StateAttribute18 0    StateAttribute19 0    StateAttribute20 0    StateAttribute21 [null]    StateAttribute22 [null]    StateAttribute23 [null]    StateAttribute24 [null]    StateAttribute25 [null]    ResultType 4    ExecutionId 30609216    ExecutionStartTime 2016-07-12T09:08:54.4738454Z    ExecutionEndTime 2016-07-12T09:08:54.5207054Z    PoisonedCount 0    ExtensionXml [null]    SampleValue 0    ExecutionContext [null]    FailureContext [null]    FailureCategory -1    ScopeName [null]    ScopeType [null]    HealthSetName [null]    Data [null]    Version 65536 



Error: Sequence contains no elements

StateAttribute1 is a output of netsh command:

netsh interface tcp show global
Querying active state...

TCP Global Parameters
----------------------------------------------
Receive-Side Scaling State          : enabled
Chimney Offload State               : disabled
NetDMA State                        : disabled
Direct Cache Access (DCA)           : disabled
Receive Window Auto-Tuning Level    : normal
Add-On Congestion Control Provider  : none
ECN Capability                      : enabled
RFC 1323 Timestamps                 : disabled
Initial RTO                         : 3000
Receive Segment Coalescing State    : enabled
Non Sack Rtt Resiliency             : disabled
Max SYN Retransmissions             : 2






Need Help to prepare professinal email disclaimr usning html program

$
0
0

Dear Members,

                      ima unable to change the font  and text   after  copying the text  for  email disclaimer in exchange server 2013.

please  advise  for best  practice  to  prepare  Email disclaimer  through crating  diclaimers.

Regards

Altaf


Mohammed Altaf Ahmed

Transport Rule Incident Report and AcceptMessagesOnlyFrom Mailbox property

$
0
0

I’m trying to configure a Mailbox to only accept system-generated messages.  It’s being used to collect Exchange Transport Rule generated Incident Reports.

Based on the Set-Mailbox documentation it should work via either the AcceptMessagesOnlyFrom orAcceptMessagesOnlyFromSendersOrMembers Mailbox properties but it’s not working.  The Incident Reports aren’t making it into the Mailbox.

This is the output from the Set-Mailbox and subsequent Get-Mailbox cmdlets.

[PS] C:\Windows\system32>Set-Mailbox “MyMailbox” -AcceptMessagesOnlyFromSendersOrMembers 'Microsoft Outlook' [PS] C:\Windows\system32>Get-Mailbox "MyMailbox" | Format-List *accept* AcceptMessagesOnlyFrom                 : {MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e} AcceptMessagesOnlyFromDLMembers        : {}

AcceptMessagesOnlyFromSendersOrMembers : {MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e}


From the documentation:
https://technet.microsoft.com/en-us/library/bb123981(v=exchg.150).aspx

AcceptMessagesOnlyFrom
The AcceptMessagesOnlyFrom parameter specifies the mailbox users, mail users, and mail contacts that can send email messages to this mailbox. You can also specify Exchange as a valid recipient for this parameter.If you configure a mailbox to accept messages only from the Exchange recipient, the mailbox receives only system-generated messages.


AcceptMessagesOnlyFromSendersOrMembers
The AcceptMessagesOnlyFromSendersOrMembers parameter specifies the recipients who can send email messages to this mailbox. You can specify users, contacts, or distribution groups. If you specify a distribution group, messages are accepted from all recipients that are members of that distribution group. You can also specify Exchange as a valid recipient for this parameter. If you configure a distribution group to accept messages only from the Exchange recipient, the distribution group only receives system-generated messages.





Exchange 2013 EAC only has tools option

$
0
0

This is a 2013 server that was installed in a separate domain but never deployed beyond that.  I need to uninstall, remove this machine from the domain, then we're going to deploy 2016 on a different domain.  Uninstall fails because it says a mailbox still exists, but I have disabled that mailbox as per instructions and it still fails.  But I have no options in the EAC except tools and the only options there are "checks", which only has a best practices analyzer.  

I'm using explorer on the local server with a URL of https://<FQDN>/ecp and I don't get any errors on login, but I can't do anything.  Did my best to search the forums but the closest I found was a recommendation to run install-rbacroles and install-rbacrole... something.  Why can't I manage my server?

HubTransport and FrontendTransport marked as Unhealthy. How to diagnose and resolve?

$
0
0

I am trying to do an Exchange 2007 to 2013 migration.  Before doing all the final repointing of DNS and proxying clients, I just want to make sure that the new Exchange 2013 is healthy.  So I run a Get-HealthReport and it shows both the Online states of HubTransport and FrontendTransport as Unhealthy.

In the event logs under Microsoft>Exchange>ManagedAvailability>Monitoring I see Error events for them about the client submission probe failed x times over 15 minutes.  No connection because the target machine actively refused it 127.0.0.1:587. There was also another one that said Unable to relay.  For the Hub Transport it does not give as detailed information.  It just says The HubAvailibilityProbe has failed 5 or more times in 15 minutes.  Last failing server: ".

So it would sound like a connectivity problem, so with TELNET I tried to connect to port 25 and I get this:

telnet 127.0.0.1 25

421 4.3.2 Service not available

BUT if I put the hostname instead of 127.0.0.1, I get the 220 EMAIL.domain.com Microsoft ESMTP MAIL Service ready.

I tried temporarily disabling the windows firewall and its the same problem.  I know SMTP is running because from another machine I can telnet to the mail server on port 25 and I get the SMTP banner.

So for me it seems like the Managed Availability is trying to use the IP address of 127.0.0.1 and that fails fundamentally for me when I try that in the command line, so no wonder why its marking the FrontendTransport as unhealthy.  How can I resolve this?  I would think a resolution would be either somehow allow 127.0.0.1 access to relay which I DID put in my Frontend Transport receive connector, but it made no difference.  Or the other option is somehow  configure the probe to use the hostname instead of 127.0.0.1.  

As far as the HubTransport being unhealthy, I have a feeling its the same type of issue, but I am not seeing as detailed information in this path of the Event Viewer.


Exchange Transport rule - all external senders - does not match

$
0
0

Dear all,

my customer uses Exchange Serevr 2013 using the current CU. I created a Transport rule like that

1. if External sender then bcc mail to bccmailbox

2. stop processing other rules

for the vast majority of mail that is working fine.

Sometimes the rule does not match, so the mail is still delivered, but the rule above looks to be not applied. I inserted some header tagging, and we can find that for those mails the header is also not present, so even though a mail is external (sender like yahoo, others) the rule sometimes looks to be not applied.

It does not depend on specific senders, as I can see the rule is applied / not applied to the same sender in Different cases. Up to now I'm not able to describe the dependency on when it is not applied. It does not depend on header / envelope from.

When I had a look to the message Tracking I can see the Agentinfo contains an entry like that:

{[AMA, SUM|v=0|action=|error=|atch=8], [AMA, EV|engine=M|v=0|sig=1.223.2953.0|name=|file=], [CompCost, |AMA=0|ETR=0],

[DeliveryPriority, Normal], [AccountForest, maildomain.local]}

if the rule is applied, it looks like [AMA, SUM|v=0|action=|error=|atch=0] , when it's not applied it looks like [AMA, SUM|v=0|action=|error=|atch=8]. I'm not clear about that log entry.
What does it mean? Is that the place to check? How do I debug errors like that?

Please advise. Thanks.
Martin

how to grant Admistrators and NetworkService full access to ContentSubmitters group ?

$
0
0

Hello Everyone, I am trying to follow this guide here :

http://support.microsoft.com/kb/2807668?wa=wsignin1.0

how can I grant Admistrators and NetworkService full access to the group?

the group is on Active Directory , NetworkService I assume is a local exchange server account ?

I am missing something here ..please help... Thanks.

=======

Method 1

  1. Create a new Active Directory group that is named "ContentSubmitters," and then grant Admistrators and NetworkService full access to the group. This is a dummy group and should be used as a placeholder only. You might want to add a description so that the group is not removed. 
  2. Force or wait for Active Directory replication.
  3. Restart the following services:
    • Microsoft Exchange Search 
    • Microsoft Exchange Search Host Controller

OWA not working - OWA-Error: SDServerErr;System.Xml.XmlException

$
0
0

Hi everyone,

for a couple of days users receive the following error when they try to connect to OWA.

The error occured suddenly, nothing was changed at the configuration.

its Exchange 2013 with CU10 and Windows 2012 R2 Servers.

2 CAS and 2 Mailbox Servers within a DAG.


X-ClientId: KQYO - LXOX - ESTK - YVPBVMLG X-OWA-Error: SDServerErr;System.Xml.XmlException X-OWA-Version: 15.0.1130.7 X-FEServer: *Server* X-BEServer: *Server* Date: 18.01.2016 10:06:35

*url*owa/auth/errorfe.aspx?owaError=SDServerErr;System.Xml.XmlException&owaVer=15.0.1130.7&be=*server*&msg=ErrorUnexpectedFailure

I tried it already with deleting canary data values in the AD. Did not helped.

I have no more ideas for solving this issue. Maybe somebody here could help me.

Thanks.


Exchange 2013 server reboot automataclly

$
0
0

Hi All,

we have coexistance with Exchange 2010 and Exchange 2013.

My all exchange 2013 SP1 Cu13 server reboot automatically with below bug event.

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ef (0xffffe000db5c2900, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 072416-168109-01.



Exchange 2013 - Event ID 4999 MS Exchange Common - Watson report about to be sent for process id: 5816

$
0
0

Hi,

We have a single Exchange 2013 server and are getting this error many times in a day.  I haven't been able to find a solution and was wondering if anyone came across this error or have any suggestions.

Edition             : Standard
AdminDisplayVersion : Version 15.0 (Build 913.22)


Watson report about to be sent for process id: 5816, with parameters: E12IIS, c-RTL-AMD64, 15.00.0913.022, M.Exchange.Imap4, M.Exchange.Net, M.E.N.NetworkConnection.BeginNegotiateTlsAsClient, System.InvalidOperationException, 99a4, 15.00.0913.007.
ErrorReportingEnabled: True 

Thanks

Amit

Exchange 2013 Management from Powershell Web Access (PSWA).

$
0
0

Hi Scripting guy,

I'm trying to manage Exchange 2013 from powershell web access (PSWA) on Win2012R2.

Both components reside on the same server. If I try from a different server it works fine but not on the same. Is it possible?

Thank you!

I.H.

Exchange Server 2013 - Std - Database Size

$
0
0

Hi guys

I have a situation where the size of the Exchange Database (500GB) is on 40GB free at the moment.

Amount of mailboxes are not that high, which seems impossible to have 30 users deplete this size of database.

I've done investigation and even though archiving is done, and shows 300MB as example on the local drive of an mailbox, it still remains over 2GB on the Server Data Tab. How do you decrease this number on the server, seeing that if you look at the mailbox folder size overall, it states being 300MB?

Would appreciate any adivse.

Regards



Exchange 2013 DAG Failover

$
0
0

Dear Team,

While doing Exchange 2013 DAG failover, There is any way to set Database to mount same server once server came up after some time.

Thanks

Dravil

OWA not working - OWA-Error: SDServerErr;System.Xml.XmlException

$
0
0

Hi everyone,

for a couple of days users receive the following error when they try to connect to OWA.

The error occured suddenly, nothing was changed at the configuration.

its Exchange 2013 with CU10 and Windows 2012 R2 Servers.

2 CAS and 2 Mailbox Servers within a DAG.


X-ClientId: KQYO - LXOX - ESTK - YVPBVMLG X-OWA-Error: SDServerErr;System.Xml.XmlException X-OWA-Version: 15.0.1130.7 X-FEServer: *Server* X-BEServer: *Server* Date: 18.01.2016 10:06:35

*url*owa/auth/errorfe.aspx?owaError=SDServerErr;System.Xml.XmlException&owaVer=15.0.1130.7&be=*server*&msg=ErrorUnexpectedFailure

I tried it already with deleting canary data values in the AD. Did not helped.

I have no more ideas for solving this issue. Maybe somebody here could help me.

Thanks.


Mailbox migration reports it completed, ecp shows 0 mailboxes have moved and the mailbox does not move

$
0
0

I am migrating 1600 mailboxes from Exchange 2007 to Exchange 2013, over 700 have moved fine, but 1 mailbox fails repeatedly. 

When I run the migration in ecp it says the migration status is complete, but it also says that 0 mailboxes were synced, 0 were finalized and 0 failed. I also receive an email saying it completed successfully. The only thing, apart from the fact it says it worked when it didn't, is that the Total column changes from 1 to 0 while it is in Syncing status.

I'm confused, why is this not working? What do I need to do to fix it?


UnhealthyMailboxDeliveryAvailabilityMonitor

$
0
0

Hello

In our Exchange 2013 deployment I can see on all Mailbox servers MailboxDeliveryAvailabilityMonitor reported as unhealthy

Name                    : MailboxDeliveryAvailabilityMonitor
TargetResource          :
HealthSetName           : MailboxTransport
HealthGroupName         : ServiceComponents
AlertValue              : Unhealthy

In the event log under Active Monitoring -> Probe Results are the visible errors like this:

   ResultId 117170212
 
   ServiceName MailboxTransport
 
   ResultName MailboxDeliveryInstanceAvailabilityProbe/MBX200-02
 
   WorkItemId 884
 
   MachineName XXXXX
 
   Error A TLS API failure occurred. Error = 0x80090301
 
   Exception Microsoft.Exchange.Net.ExSmtpClient.TlsApiFailureException: A TLS API failure occurred. Error = 0x80090301 at Microsoft.Exchange.Net.ExSmtpClient.SmtpSslStream.SmtpSslHelper.Encrypt(Byte[] bytesToEncrypt, Int32 offset, Int32 numberOfBytesToEncrypt) at Microsoft.Exchange.Net.ExSmtpClient.SmtpSslStream.SmtpSslHelper.Encrypt(Byte[] bytesToEncrypt) at Microsoft.Exchange.Net.ExSmtpClient.SmtpSslStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.IO.Stream.<BeginWriteInternal>b__11(Object param0) at System.Threading.Tasks.Task`1.InnerInvoke() at System.Threading.Tasks.Task.Execute() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.IO.Stream.EndWrite(IAsyncResult asyncResult) at System.IO.Stream.<BeginEndWriteAsync>b__17(Stream stream, IAsyncResult asyncResult) at System.Threading.Tasks.TaskFactory`1.FromAsyncTrimPromise`1.Complete(TInstance thisRef, Func`3 endMethod, IAsyncResult asyncResult, Boolean requiresSynchronization)
 
   StateAttribute11 127.0.0.1
 
   StateAttribute12 2 latencies were above the standard deviation. Mean: 0 Standard Deviation: 1. STARTTLS (2, Two) BeforeConnect (1, One)  
 
   StateAttribute13 BeforeConnect=1;Connect=0;EHLO=0;STARTTLS=2;EHLO=0
 
   StateAttribute14 XXXXX.DOMAIN
 
   StateAttribute15 220 XXXXX.DOMAIN Microsoft ESMTP MAIL Service ready at Wed, 17 Feb 2016 15:20:44 +0100EHLO XXXXX.DOMAIN 250-XXXXX.DOMAIN Hello [127.0.0.1]X-ANONYMOUSTLS 220 2.0.0 SMTP server readyEHLO XXXXX.DOMAIN  
 
   StateAttribute16 475
 
   StateAttribute17 2
 
   StateAttribute21 System.Exception
 
   StateAttribute22 220 2.0.0 SMTP server ready  

   ResultType 4
 
   ExecutionId 54194945
 
   ExecutionStartTime 2016-02-17T14:20:45.0533096Z
 
   ExecutionEndTime 2016-02-17T14:20:45.0583101Z

   ExtensionXml [null]
 
   SampleValue 4.0004
 
   ExecutionContext [null]
 
   FailureContext Server 127.0.0.1 on port 475 did not respond with expected response (OK). The actual response was: 220 2.0.0 SMTP server ready .
 
   FailureCategory -1

This error is logged several times per minute.

Any idea?

Thanks

MailboxTransport health set unhealthy (MailboxDeliveryAvailabilityMonitor)

$
0
0

Hi,

I'm getting the following error:

MailboxTransport health set unhealthy (MailboxDeliveryAvailabilityMonitor) - The mail delivery smtp probe failed 5 times over 15 minutes.

I have checked server health and indeed one Probe/Monitor is unhealthy:

CurrentHealthSetState   : NotApplicable
Name                    : MailboxDeliveryAvailabilityMonitor
TargetResource          : 
HealthSetName           : MailboxTransport
HealthGroupName         : ServiceComponents
AlertValue              : Unhealthy
FirstAlertObservedTime  : 9/08/2016 16:05:16
Description             : 
IsHaImpacting           : False
RecurranceInterval      : 0
DefinitionCreatedTime   : 10/08/2016 16:21:05
HealthSetDescription    : 
ServerComponentName     : None
LastTransitionTime      : 9/08/2016 16:21:55
LastExecutionTime       : 10/08/2016 16:24:07
LastExecutionResult     : Succeeded
ResultId                : 231615357
WorkItemId              : 374
IsStale                 : False
Error                   : 
Exception               : 
IsNotified              : False
LastFailedProbeId       : 87
LastFailedProbeResultId : 338511671
ServicePriority         : 0
Identity                : MailboxTransport\MailboxDeliveryAvailabilityMonitor\
IsValid                 : True
ObjectState             : New

I have tried the following command:

Invoke-MonitoringProbe MailboxTransport\MailboxDeliveryAvailability -Server mailbox1.contoso.com | Format-List
As stipulated in the article "Troubleshooting MailboxTransport Health Set"

But it returns an error:

WARNING: Failed to find the probe result for invoke now request id 9c486bb5336b4b06bb11cf2071dbac48 and probe
workdefinition id 423.

I have restarted the Health Manager service but this didn't help.

I'm running Exchange 2013 CU8

I read in this article that the MailboxDeliveryAvailability probe is now obsolete. Does it mean I can safely create a monitoring override? 

Many thanks for the help already.

Greetings,

Adriaan

Viewing all 1453 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>