Exchange 2013 SP1 Health mailbox generating 4724 event on AD servers

I rebooted one of our Mailbox servers yesterday and ever since on our AD servers I'm getting an Event 4724- "An
attempt was made to reset an account's password" every three minutes."
I did find I had some health mailboxes corrupted and removed those from the OU in AD and restarted the health service again. The problem persisted. I then deleted the health mailbox causing the issue (which is on the rebooted server)- and restarted
the  Health Serice- and the issue started again from the recreated health mailbox.
The mailbox in question is for the DAG active copy on that server. The other two passive copies of that Database have health mailboxes with no issue
Exchange reports full health- no issues whatsover. Any idea what is causing this?

Hi Tony 
Try these suggestion too and i think you would be able to find the problem
First step is to run command "Get-MailboxServer | Get-Mailbox -Monitoring | FT Alias,ServerName" to see if there are any warnings related to health mailboxes. 
Also, you may want to check Managed availability with commands like : 
Get-HealthReport, Get-ServerHealth, Get-ServerComponentState and check Crimson logs found under Applications and Services Log\Microsoft\Exchange\ActiveMonitoring\ and
  Applications and Services Log\Microsoft\Exchange\ManagedAvailability\ 
And I would suggest to check password policy configured in your domain, values of attributes like Minimum/Maximum Password Length, Minimum/ Maximum Password Age. If
one mailbox server affected maybe you might need to run a gpupdate /force on that server
I think in your case the password policy is causing this trouble 
Let us know after  you check all the above 
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you

Similar Messages

  • Exchange 2013 Offline Address Book generat failure Event ID 17004

    Hello guys,
    i met the following event id when I tried to update the offline address book on my mailbox server (Exchange 2013),
    i have done the troubleshooting steps as below,
    1 Reboot the mailbox server
    2 restart the mailbox assistant service
    I'd like know what can i do  next step?
           Generation of OAB "\Default Offline Address Book" failed.       
    Dn: CN=Default Offline Address Book,CN=Offline Address Lists,CN=Address Lists Container,CN=zteservices,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=zteservices,DC=eu       
    ObjectGuid: a603acd4-ea74-47c3-88a5-ebf25cbc663a       
    Stats: S:OAB='\Default Offline Address Book';I32:Status=2147500037;Dt:StartTime=2014-02-04T14:50:14.9300281Z;Dt:EndTime=0001-01-01T00:00:00.0000000;S:DC=ztedomain01.zteservices.eu;I32:Total.Records=1908;Ti:TimeWritingFiles=00:00:04.7035164;S:Wasted=False;Ti:Al.Unsorted.LdapElapsedTime=00:00:04.6206741;Ti:MailboxDownload.StoreRpcLatency=00:00:00.0160000;I32:MailboxDownload.StoreRpcCount=6;Ti:MailboxDownload.CpuTime=00:00:00.0312500;Ti:MailboxDownload.ElapsedTime=00:00:00.0496183;I32:Template.FS.BytesRead=1499956;I32:Template.FS.BytesWritten=2216646;Ti:Template.FS.Reading.ElapsedTime=00:00:00.0077045;Ti:Template.FS.Writing.ElapsedTime=00:00:00.0285458;Ti:Template.CpuTime=00:00:03.2031250;Ti:Template.ElapsedTime=00:00:04.7140032;I32:AL.Unsorted.FS.BytesRead=0;I32:AL.Unsorted.FS.BytesWritten=1874031;Ti:AL.Unsorted.FS.Reading.ElapsedTime=00:00:00;Ti:AL.Unsorted.FS.Writing.ElapsedTime=00:00:00.0224695;Ti:AL.Unsorted.LdapLatency=00:00:14.1220000;I32:AL.Unsorted.LdapCount=4844;Ti:AL.Unsorted.CpuTime=00:00:09.8125000;Ti:AL.Unsorted.ElapsedTime=00:00:23.4694472;I32:AL.Sorted.FS.BytesRead=1866395;I32:AL.Sorted.FS.BytesWritten=1866419;Ti:AL.Sorted.FS.Reading.ElapsedTime=00:00:00.0157892;Ti:AL.Sorted.FS.Writing.ElapsedTime=00:00:00.0104285;Ti:AL.Sorted.CpuTime=00:00:00.0468750;Ti:AL.Sorted.ElapsedTime=00:00:00.0573755;I32:AL.Compress.FS.BytesRead=1866407;I32:AL.Compress.FS.BytesWritten=1866407;Ti:AL.Compress.FS.Reading.ElapsedTime=00:00:00.0009518;Ti:AL.Compress.FS.Writing.ElapsedTime=00:00:01.3330312;Ti:AL.Compress.CpuTime=00:00:01.3593750;Ti:AL.Compress.ElapsedTime=00:00:01.3756676;I32:DiffGen.FS.BytesRead=0;I32:DiffGen.FS.BytesWritten=0;Ti:DiffGen.FS.Reading.ElapsedTime=00:00:00;Ti:DiffGen.FS.Writing.ElapsedTime=00:00:00;Ti:DiffGen.CpuTime=00:00:00;Ti:DiffGen.ElapsedTime=00:00:00.0155622;Ti:AL.Total.CpuTime=00:00:11.2187500;Ti:AL.Total.ElapsedTime=00:00:24.9209864;Ti:Total.CpuTime=00:00:14.5468750;Ti:Total.ElapsedTime=00:00:29.8092411;;     
    System.NullReferenceException: Object reference not set to an instance of an object.
       at Microsoft.Exchange.OAB.BaseStream.Seek(Int64 offset, SeekOrigin origin)
       at Microsoft.Exchange.MailboxAssistants.Assistants.OABGenerator.DiffFileGenerator.ReadFileHeader(Stream stream, Byte[] buffer, Int32& numberOfBytesRead, UInt32& crc)
       at Microsoft.Exchange.MailboxAssistants.Assistants.OABGenerator.DiffFileGenerator.CreatePatch(Stream diffStream)
       at Microsoft.Exchange.MailboxAssistants.Assistants.OABGenerator.DiffFileGenerator.GenerateDiffFile(FileSet fileSet)
       at Microsoft.Exchange.MailboxAssistants.Assistants.OABGenerator.OABGenerator.GenerateDiffFile(OABFile addressListFile, OABFile oldFile)
       at Microsoft.Exchange.MailboxAssistants.Assistants.OABGenerator.OABGenerator.GenerateAddressListFiles(ADObjectId addressList, String habRootLegacyDN)
       at Microsoft.Exchange.MailboxAssistants.Assistants.OABGenerator.OABGenerator.Generate()
       at Microsoft.Exchange.MailboxAssistants.Assistants.OABGenerator.OABGeneratorAssistant.ProcessSingleOAB(MailboxSession mailboxSession, IConfigurationSession perOrgAdSystemConfigSession, OfflineAddressBook oab, SecurityIdentifier mailboxSid, String
    mailboxDomain)
    Exchange Lync Sharepoint

    Hi,
    Do you mean the new Offline Address Book has been set to default and can be updated successfully? And now, the new issue is that send/receive hang on "Offline address book Connecting to Microsoft Exchange" and will never finish. Is it right?
    The following link is a general discussion thread about the same issue. Please refer to it for more helpful suggestions or you can run Test E-mail AutoConfiguration tool and collect some error descriptions to open a new case
    for more troubleshooting.
    http://social.technet.microsoft.com/Forums/exchange/en-US/548f2ecc-faae-4744-8b33-7de536196d7d/sendreceive-hang-on-offline-address-book-connecting-to-microsoft-exchange-and-will-never-finish?forum=exchangesvrgenerallegacy
    Thanks,
    Winnie Liang
    TechNet Community Support

  • Seemingly successful install of Exchange 2013 SP1 turns into many errors in event logs after upgrade to CU7

    I have a new Exchange 2013 server with plans to migrate from my current Exchange 2007 Server. 
    I installed Exchange 2013 SP1 and the only errors I saw in the event log seemed to be long standing known issues that did not indicate an actual problem (based on what I read online). 
    I updated to CU7 and now lots of errors have appeared (although the old ones seem to have been fixed so I have that going for me). 
    Currently the Exchange 2013 server is not in use and clients are still hitting the 2007 server.
    Issue 1)
    After each reboot I get a Kernel-EventTracing 2 error.  I cannot find anything on this on the internet so I have no idea what it is.
    Session "FastDocTracingSession" failed to start with the following error: 0xC0000035
    I did read other accounts of this error with a different name in the quotes but still can’t tell what this is or where it is coming from.
    Issue 2)
    I am still getting 5 MSExchange Common 106 errors even after reregistering all of the perf counters per this page:
    https://support.microsoft.com/kb/2870416?wa=wsignin1.0
    One of the perf counters fails to register using the script from the link above.
    66 C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf\InfoWorkerMultiMailboxSearchPerformanceCounters.xml
    New-PerfCounters : The performance counter definition file is invalid.
    At C:\Users\administrator.<my domain>\Downloads\script\ReloadPerfCounters.ps1:19 char:4
    +    New-PerfCounters -DefinitionFileName $f
    +    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo         
    : InvalidData: (:) [New-PerfCounters], TaskException
        + FullyQualifiedErrorId : [Server=VALIS,RequestId=71b6bcde-d73e-4c14-9a32-03f06e3b2607,TimeStamp=12/18/2014 10:09:
       12 PM] [FailureCategory=Cmdlet-TaskException] 33EBD286,Microsoft.Exchange.Management.Tasks.NewPerfCounters
    But that one seems unrelated to the ones that still throw errors. 
    Three of the remaining five errors are (the forum is removing my spacing between the error text so it looks like a wall of text - sorry):
    Performance counter updating error. Counter name is Count Matched LowFidelity FingerPrint, but missed HighFidelity FingerPrint, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The
    exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
       at System.Diagnostics.PerformanceCounter.InitializeImpl()
       at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
    Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
       at System.Diagnostics.Process.GetProcessById(Int32 processId)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
    Performance counter updating error. Counter name is Number of items, item is matched with finger printing cache, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The exception thrown
    is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
       at System.Diagnostics.PerformanceCounter.InitializeImpl()
       at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
    Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
       at System.Diagnostics.Process.GetProcessById(Int32 processId)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
    Performance counter updating error. Counter name is Number of items in Malware Fingerprint cache, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The exception thrown is : System.InvalidOperationException:
    The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
       at System.Diagnostics.PerformanceCounter.InitializeImpl()
       at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
    Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
       at System.Diagnostics.Process.GetProcessById(Int32 processId)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
    Issue 3)
    I appear to have some issues related to the healthmailboxes. 
    I get MSExchangeTransport 1025 errors for multiple healthmailboxes.
    SMTP rejected a (P1) mail from 'HealthMailbox23b10b91745648819139ee691dc97eb6@<my domain>.local' with 'Client Proxy <my server>' connector and the user authenticated as 'HealthMailbox23b10b91745648819139ee691dc97eb6'. The Active Directory
    lookup for the sender address returned validation errors. Microsoft.Exchange.Data.ProviderError
    I reran setup /prepareAD to try and remedy this but I am still getting some.
    Issue 4)
    I am getting an MSExchange RBAC 74 error. 
    (Process w3wp.exe, PID 984) Connection leak detected for key <my domain>.local/Admins/Administrator in Microsoft.Exchange.Configuration.Authorization.WSManBudgetManager class. Leaked Value 1.
    Issue 5)
    I am getting MSExchange Assistants 9042 warnings on both databases.
    Service MSExchangeMailboxAssistants. Probe Time Based Assistant for database Database02 (c83dbd91-7cc4-4412-912e-1b87ca6eb0ab) is exiting a work cycle. No mailboxes were successfully processed. 2 mailboxes were skipped due to errors. 0 mailboxes were
    skipped due to failure to open a store session. 0 mailboxes were retried. There are 0 mailboxes in this database remaining to be processed.
    Some research suggested this may be related to deleted mailboxes however I have never had any actual user mailboxes on this server. 
    If they are healthmailboxes or arbitration mailboxes that might make sense but I am unsure of what to do on this.
    Issue 6)
    At boot I am getting an MSExchange ActiveSync warning 1033
    The setting SupportedIPMTypes in the Web.Config file was missing. 
    Using default value of System.Collections.Generic.List`1[System.String].
    I don't know why but this forum is removing some of my spacing that would make parts of this easier to read.

    Hi Eric
    Yes I have uninstalled and reinstalled Exchange 2013 CU7 for the 3<sup>rd</sup> time. 
    I realize you said one issue per forum thread but since I already started this thread with many issues I will at least post what I have discovered on them in case someone finds their way here from a web search.
    I have an existing Exchange 2007 server in the environment so I am unable to create email address policies that are defined by “recipient container”. 
    If I try and do so I get “You can't specify the recipient container because legacy servers are detected.”
     So I cannot create a normal email address policy and restrict it to an OU without resorting to some fancy filtering. 
    Instead what I have done is use PS to modify extensionAttribute1 (otherwise known as Custom Attribute 1 to exchange) for all of my users. 
    I then applied an address policy to them and gave it the highest priority. 
    Then I set a default email address policy for the entire organization. 
    After reinstalling Exchange all of my system mailboxes were created with the internal domain name. 
    So issue number 3 above has not come up. 
    For issue number one above I have created a new thread:
    https://social.technet.microsoft.com/Forums/office/en-US/7eb12b89-ae9b-46b2-bd34-e50cd52a4c15/microsoftwindowskerneleventtracing-error-2-happens-twice-at-boot-ex2013cu7?forum=exchangesvrdeploy
    For issue number four I have posted to this existing thread where there is so far no resolution:
    https://social.technet.microsoft.com/Forums/exchange/en-US/2343730c-7303-4067-ae1a-b106cffc3583/exchange-error-id-74-connection-leak-detected-for-key?forum=exchangesvradmin
    Issue number Five I have managed to recreate and get rid of in more than one way. 
    If I create a new database in ECP and set the database and log paths where I want, then this error will appear. 
    If I create the database in the default location and then use EMS to move it and set the log path, then the error will not appear. 
    The error will also appear (along with other errors) if I delete the health mailboxes and let them get recreated by restarting the server or the Health Manager service. 
    If I then go and set the retention period for deleted mailboxes to 0 days and wait a little while, these will all go away. 
    So my off hand guess is that these are caused by orphaned system mailboxes.
    For issue number six I have posted to this existing thread where there is so far no resolution:
    https://social.technet.microsoft.com/Forums/exchange/en-US/dff62411-fad8-4d0c-9bdb-037374644845/event-1033-msexchangeactivesync-warning?forum=exchangesvrmobility
    So for the remainder of this thread we can try and tackle issue number two which is the perf counters. 
    The exact same 5 perf counter were coming up and this had been true each time I have uninstalled and reinstalled Exchange 2013CU7. 
    Actually to be more accurate a LOT of perf counter errors come up after the initial install, but reloading the perf counters using the script I posted above reduces it to the same five. 
    Using all of your suggestions so far has not removed these 5 remaining errors either.  Since there is no discernible impact other than these errors at boot I am not seriously bothered by them but as will all event log errors, I would prefer
    to make them go away if possible.

  • In exchange 2013 sp1 SUBMITFAIL event id is happening

    Hi ,
    In exchange 2013 sp1 SUBMITFAIL event id is happening for some messages .But at the second time that the same message is delivered perfectly to the end users.
    My question is simple ,is this an bug in exchange 2013 sp1 if so on which CU it will be corrected ?We have to update to our customers so all of us please provide your suggestions as soon as possible.
    Thanks & Regards S.Nithyanandham

    Hi Allen Wang ,
    Thanks a lot for your response.
    Which version are you used? Is this issue arise after install update for Exchange server? 
    We are using exchange 2013 sp1 Ent edition.This issue is been existing in my environment when we start to use exchange 2013 and it is not from sp1 .
    Also, what your means of “second time”, server retry to send or send failed then user click to resend?
    When an user send an email for the first time to some of the recipient's it is reaching only to the few recipient's mailboxes and the email to the remaining recipients gets failed with the event ID "SUBMITFAIL" on the message tracking log.
    Same time if we forward that same message to the failed recipients it went and delivered successfully.
    Note : Apart from message tracking log i didn't found anything helpful in protocol and event viewer logs.
    Below link is for your Reference :
    https://social.technet.microsoft.com/Forums/fr-FR/ae61d80c-58da-4f47-b83c-66b123b2faf4/exchange-2013-mailflow-and-the-hosts-file?forum=exchangesvrgeneral
    Above is the link which is saying that this issue will be resolved in exchange 2013 sp1 and also it says it an bug in exchange 2013 CU3 .But still on my end the problems occurs in exchange 2013 CU3 as well as in exchange 2013 SP1.
    Please help me out yaar this issue is raising in my production environment.
    Thanks & Regards S.Nithyanandham

  • Error in moving exchange 2010 mailboxes to Exchange 2013 SP1 during migration

    Dear All,
    We were running Exchange 2010 SP3 with MBX/HT/CAS role in single server. Now we are migrating our exchange 2010 to Exchange 2013 SP1. After configuring co-existence and during the mailbox move from Exchange 2010 to Exchange 2013 SP1, we are facing below
    error. Please help to troubleshot. As per our search on net, people were suggesting that it can be due to not able to resolve NetBIOS name. We checked same and we are able to ping both servers by NetBIOS and FQDN names.
    [PS] C:\Windows\system32>New-MoveRequest -Identity
    '[email protected]' -TargetDatabase "CI-DB01"
    MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
    Diagnostic context:
        Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1722
        Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 323
        Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
        Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
        Lid: 62184
        Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
        Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
        Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
        Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
        Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1237
        Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 313
        Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
        Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
        Lid: 62184
        Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
        Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
        Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
        Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
        Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060
        Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 311
        Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
        Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 3
        Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 22964
        Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[1]: Pointer val: 0x0
        Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[2]: Pointer val: 0xFE01A8C000000000
        Lid: 62184
        Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
        Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
        Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
        Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
        Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060
        Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 318
        Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
        Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
        Lid: 53361   StoreEc: 0x977
        Lid: 51859
        Lid: 33649   StoreEc: 0x977
        Lid: 43315
        Lid: 58225   StoreEc: 0x977
        Lid: 39912   StoreEc: 0x977
        Lid: 54129   StoreEc: 0x977
        Lid: 50519
        Lid: 59735   StoreEc: 0x977
        Lid: 59199
        Lid: 27356   StoreEc: 0x977
        Lid: 65279
        Lid: 52465   StoreEc: 0x977
        Lid: 60065
        Lid: 33777   StoreEc: 0x977
        Lid: 59805
        Lid: 52487   StoreEc: 0x977
        Lid: 19778
        Lid: 27970   StoreEc: 0x977
        Lid: 17730
        Lid: 25922   StoreEc: 0x977
        + CategoryInfo          : NotSpecified: (:) [New-MoveRequest], RemoteTransientException
        + FullyQualifiedErrorId : [Server=Exch01,RequestId=f6886977-92f1-4148-991b-aa76b449aff5,TimeStamp=8/21/2014 9:1
       0:43 AM] [FailureCategory=Cmdlet-RemoteTransientException] 7FCC37,Microsoft.Exchange.Management.RecipientTasks.New
    MoveRequest
      + PSComputerName        : Exch01.domain.local
    Please help as we are stuck here!!
    Thanks in advance!!

    Can yo ping server by name not by FQDN? e.g. ping server1.
    Make sure firewall/antivirus not blocking communication. Disable antivirus and try
    Thanks,
    MAS
    Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Migrating a mailbox cross forest from exchange 2013 Sp1 to exchange 2010 SP2 Update rollup 8

    I can migrate a mailbox fine from exchange 2010 sp2 update rollup 8 to exchange 2013 sp1 or Cu2.
    I was testing today migrating cross forest from 2010 sp2 udpate rollup 8 back to exchange 2010 sp2 but I get the below error.  Is this even possible?  I cannot find any documentation on this scenario yet.
    VERBOSE: [21:52:47.622 GMT] New-MoveRequest : The remote server doesn't support client 'casservername.domain.com'
    version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
    VERBOSE: [21:52:47.637 GMT] New-MoveRequest : Admin Audit Log: Entered Handler:OnComplete.
    The remote server doesn't support client 'casservername.domain.com' version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
        + CategoryInfo          : NotSpecified: (0:Int32) [New-MoveRequest], RemotePermanentException
        + FullyQualifiedErrorId : 782D22F0,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest

    Hi Steve,
    I'm a little confused what you are saying. Here is my understanding:
    When you migrate mailboxes from Exchange 2013 back to Exchange 2007, the above error occurs.
    If I have misunderstood your concern, please let me know.
    For migrating mailboxes back to Exchange 2007, there is a simple and straightforward method. Please use the New-MailboxExportRequest cmdlet to convert all mailboxes into pst files. And then use the Import-Mailbox cmdlet to import all pst files into Exchange
    2007.
    Hope it helps.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • Exchange 2013 SP1 users not receiving quota warning email message

    Hi,
    We are on Exchange 2013 SP1 and Exchange 2010 SP3 co-existence mode and currently migrating users from Exchange 2010 to 2013.  We have noticed that users are not receiving email message when their mailbox quota warning when its near to maximum limit.
    If I log in via OWA it shows the notification (Pop up) that your mailbox is almost full but no message received in email.  Most of the users do not log into OWA but only uses Outlook.
    It looks like other people are also seeing this similar issue but I am unable to find any solution for it.
    How users will know if their mailbox is almost full if they are traveling and only using Mobile phone for emails to send and receive.
    Thanks,
    Raman

    Hi Thanks for your response. Our Quota is set on Database level. I am seeing these event ids as well.
    Log Name: Application Source: MSExchangeIS Date: 12/31/2014 10:07:12 PM Event ID: 1077 Task Category: MAPI Level: Warning Keywords: Classic User: N/A Computer: Exch2013mail01.company.com Description: The mailbox e3d48b23-0740-46ab-89f7-3b035dacf28f on database
    326f0997-4fe5-4b31-873b-6a3396e7a91c is approaching its storage limit. A notification has been sent to the user. This warning will not be sent again for at least twenty four hours.
    ========================
    Log Name: Application Source: MSExchange Store Driver Submission Date: 12/31/2014 10:07:12 PM Event ID: 1012 Task Category: MSExchangeStoreDriverSubmission Level: Error Keywords: Classic User: N/A Computer: Exch2013mail01.company.com Description: The store
    driver failed to submit event 8237691 mailbox e3d48b23-0740-46ab-89f7-3b035dacf28f MDB 326f0997-4fe5-4b31-873b-6a3396e7a91c and couldn't generate an NDR due to exception Microsoft.Exchange.MailboxTransport.StoreDriverCommon.InvalidSenderException at Microsoft.Exchange.MailboxTransport.Shared.SubmissionItem.SubmissionItemUtils.CopySenderTo(SubmissionItemBase
    submissionItem, TransportMailItem message) at Microsoft.Exchange.MailboxTransport.Submission.StoreDriverSubmission.MailItemSubmitter.GenerateNdrMailItem() at Microsoft.Exchange.MailboxTransport.Submission.StoreDriverSubmission.MailItemSubmitter.<>c__DisplayClass1.<SubmitNdrForFailedSubmission>b__0()
    at Microsoft.Exchange.MailboxTransport.StoreDriverCommon.StorageExceptionHandler.RunUnderTableBasedExceptionHandler(IMessageConverter converter, StoreDriverDelegate workerFunction).
    Raman

  • BSOD after upgrading to exchange 2013 SP1

    Hi,
    I Have 4 servers, x2 Mailbox and x2 CAS, all with 2008 r2 OS, Mailboxes with DAG. Problem started after I upgraded all servers from Exchange 2013 CU3 to Ex13 SP1. All Servers are in Vmware, same hardware.
    All servers getting BSOD, error is same as some other posts in Internet about:
    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa8007ab4890, Terminating object
    Arg3: fffffa8007ab4b70, Process image file name
    Arg4: fffff800019de7b0, Explanatory message (ascii)
    Debugging Details:
    PROCESS_OBJECT: fffffa8007ab4890
    IMAGE_NAME:  wininit.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    MODULE_NAME: wininit
    FAULTING_MODULE: 0000000000000000
    PROCESS_NAME:  MSExchangeHMWo
    BUGCHECK_STR:  0xF4_MSExchangeHMWo
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    CURRENT_IRQL:  0
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    LAST_CONTROL_TRANSFER:  from fffff80001a67ab2 to fffff800016d9bc0
    LOGS:
    RecoveryActionLogs: ForceReboot-ServerName -ActiveDirectoryConnectivityServerReboot: Throttling rejected the operation
    RecoveryActionLogs: ForceReboot-ServerName -ActiveDirectoryConnectivityConfigDCServerReboot: Throttling
    rejected the operation
    Recovery Action Failed. (ActionId=RestartService, ResourceName=ServerName.contoso.com, Requester=ActiveDirectoryConnectivityRestart,
    InstanceId=140408.062707.65292.001, ActualStartTime=2014-04-08T15:27:07.6529270Z, ActualEndTime=2014-04-08T15:27:07.7777262Z, ErrorMessage=Service ServerName.contoso.com was not found on computer '.'.)
    when Server restarts, logs show 
    Bugcheck action reported by server 'ServerName' initiated by responder 'ActiveDirectoryConnectivityServerReboot'
    Recovery Action Started. (ActionId=ForceReboot, ResourceName=ServerName, Requester=ActiveDirectoryConnectivityServerReboot, InstanceId=140408.063307.93261.004, ExpectedToFinishAt=2014-04-08T15:38:07.9326175Z
    Recovery Action Succeeded. (ActionId=ForceReboot, ResourceName=ServerName, Requester=ActiveDirectoryConnectivityServerReboot, InstanceId=140408.063307.93261.004, ActualStartTime=2014-04-08T15:33:07.9326175Z, ActualEndTime=2014-04-08T15:35:07.0828500Z)
    I found that it could restart like many times in a day, but
    Throttling does not let it, just one restart per day.
    I already spent four days trying to find problem but no luck.
    Try'ed to add override
    Add-GlobalMonitoringOverride
    -Identity Exchange\ActiveDirectoryConnectivityConfigDCServerReboot  -ItemType Responder -PropertyName Enabled -PropertyValue 0 -Duration 60.00:00:00
    but
    after 
    (Get-WinEvent
    -LogName Microsoft-Exchange-ActiveMonitoring/responderdefinition | % {[XML]$_.toXml()}).event.userData.eventXml | ?{$_.Name -like “ActiveDirectoryConnectivityConfigDCServerReboot"} | ft name,enabled
    still shows propertyValue 1, and servers are restarting no matter what, I just dont want to disable HealtManager
    Service.
    Try'ed to recreate all performance counters, did'nt worked
    Try'ed to create prefered domain controller, did'nt worked
    Try'ed to play with healthSet 'AD', but there is almost no information about it in TechNet, so I just looked which services are unhealthy, sometimes it shows ActiveDirectoryConnectivityServer
    or ActiveDirectoryConnectivityConfigDCServer as unhealthy, but after few minutes it goes to
    healthy, problem that Exchange could already restart the server
    mainly reason I think is: 
    The AD Health Set has detected a problem with Server.contoso.com at 2014.04.09 06:33:11. The Health Manager is reporting that ActiveDirectoryConnectivityProbe/Server.contoso.com
    Failed with Error message:  Search took 1518 ms. Threshold 800 ms. Attempts to auto-recover from this condition have failed and requires Administrator attention. Exception Details: System.Exception:  Search took 1518 ms. Threshold 800 ms
    I really need some new ideas...
    EDIT: Exchange 2013 sp1 works perfectly in test lab, there are  cloned machines from production, the only difference is DomainController, there is just one (server), no replications, and no subdomains (production domain have subdomain). 
    Running DCDiag shows no errors

    Hello Everyone,
    We have 2 CAS and 4 Mailbox server that were installed from SP1 and seeing the same issue.  This is a clean install still with no mailboxes migrated over as of yet.  Opened a case with MS.  also ran:
    Add-GlobalMonitoringOverride
    -Identity Exchange\ActiveDirectoryConnectivityConfigDCServerReboot  -ItemType Responder -PropertyName Enabled -PropertyValue 0 -Duration 60.00:00:00
    Waiting
    for MS to get back and to see how this workaround does.  Seems like the original issue was not resolved completely?
    Will
    post back when we get an update.  Changing the DirectoryActiveMonitoringContext.xml and the above workaround do not seem suitable for us.  We would like to see a complete resolution for this.
    Good
    luck!

  • What happend New-MailboxExportRequest cmdlet in exchange 2013 SP1 is missing?

    Cmdlet New-MailboxExportRequest is not recognize cmdlet in Exchange 2013 SP1
    How can i do export mailbox to pst file in exchange 2013 SP1?

    You might be facing this issue because of not having the rights to execute the New-MailboxExportRequest CMDLET.
    Follow the steps given below in order to export the mailboxes into PST file
    1. Open the Exchange Console and run:
    New-ManagementRoleAssignment -Name "Import Export PST" -SecurityGroup "Organization Management" -Role “Mailbox Import Export"
    This will generate a new role group called Import Export PST to the Oranization Management group with the role Mailbox Import Export.
    You should Close and Restart the Exchange Management System again so that the changes made will get reflected in the settings, otherwise you will still get the same erroriIf not
    restarted. Now move to the next steps.
    2. Assign “Mailbox Import Export” role to it.
    3.  Add Desired Users to Role Group
    4.  Create Network Share ( Exchange Trusted Subsystem group has read/write permission to NTFS Permissions)
    5. Run PS New-MailboxExportRequest
    6. Monitor New-MailboxExportRequest
    Verify PST File has been created on the network Share and you are done.
    If you get the same error again, then there will be some hardware or software issues due to which you are not able to export mailboxes into PST files. In that case, you can make
    use of any third party tool like Stellar Phoenix EDB To PST converter, which will help you to export your exchange database files to PST files easily and quickly. You can try this software by downloading its demo directly from their site http://www.stellarinfo.com/email-repair/edb-pst-converter.php

  • Exchange 2013 SP1 | Another HTTP 500.0.0 Error

    Help!
    We are in the middle of migrating from Exchange 2010 SP3 to Exchange 2013 SP1 and we are being plagued with HTTP 500 errors on every Exchange 2013 server now.
    I have two Client Access servers installed (EXCHFE01 & EXCHFE02) and one backend mailbox server (EXCHMB03) with the Client Access role also installed (for troubleshooting purposes). Once I get everything working I'll install two backend 2013 servers
    with the mailbox role only for production (load-balanced, clustered, etc). I still have two Exchange 2010 mailbox servers left since one has a single large mailbox left on it and the other hosts public folders. I'll get to migrating those later. All Exchange
    2013 servers are running Windows Server 2012. All are on the same LAN and no firewalls are between them.
    On all three 2013 servers (EXCHFE01, EXCHFE02, EXCHMB03) I'm getting the dreaded HTTP 500 error whether I try to get to OWA or ECP. This did work at one point where I could at least login to the mailbox server (EXCHMB03) and migrate all my mailboxes over
    to it. Sometime this morning after the two Client Access servers were installed the mailbox server stopped working (HTTP 500 errors). This is very frustrating because I can't even login to a console to manage Exchange from any server at this point.
    Both Client Access servers aren't really showing anything of value in the event logs or the IIS logs. The mailbox server (EXCHMB03) does show the following event 3002:
    Protocol /Microsoft-Server-ActiveSync failed to process request from identity NT AUTHORITY\SYSTEM. Exception: Microsoft.Exchange.Security.Authentication.BackendRehydrationException: Rehydration failed. Reason: Source server 'NT AUTHORITY\SYSTEM' does not have token serialization permission.
    at Microsoft.Exchange.Security.Authentication.BackendRehydrationModule.ProcessRequest(HttpContext httpContext)
    at Microsoft.Exchange.Security.Authentication.BackendRehydrationModule.OnAuthenticateRequest(Object source, EventArgs args).
    ...and I get the following when I run the Exchange Management Shell tool on the same mailbox server (along with lots of other red HTML text):
    More Information:
    This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.
    The Client Access servers show the following errors:
    Performance counter updating error. Counter name is Location cache update time, category name is MSExchange Active Manager Client. Optional code: 3. Exception: The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
    at System.Diagnostics.PerformanceCounter.InitializeImpl()
    at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
    at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
    Last worker process info : System.ArgumentException: Process with an Id of 4040 is not running.
    at System.Diagnostics.Process.GetProcessById(Int32 processId)
    at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
    Processes running while Performance counter failed to update:
    888 svchost
    264 smss
    532 conhost
    2576 Microsoft.Exchange.UM.CallRouter
    1596 WMSvc
    3932 dllhost
    4020 svchost
    2308 dwm
    5060 taskhostex
    844 svchost
    1972 Microsoft.Exchange.Directory.TopologyService
    1228 inetinfo
    1316 vmtoolsd
    3896 svchost
    780 svchost
    1580 rundll32
    1668 mqsvc
    816 dwm
    3840 slui
    3532 rdpclip
    3980 WmiPrvSE
    4200 SppExtComObj
    4288 winlogon
    2140 SMSvcHost
    676 svchost
    1564 svchost
    1296 Microsoft.Exchange.Diagnostics.Service
    1472 Microsoft.Exchange.ServiceHost
    1204 svchost
    1292 ServerManagerLauncher
    488 winlogon
    664 svchost
    572 lsass
    3236 dllhost
    2972 WmiPrvSE
    4484 w3wp
    388 csrss
    1600 rundll32
    564 services
    1260 msdtc
    5032 sppsvc
    1448 MSExchangeHMHost
    824 LogonUI
    4204 VSSVC
    2524 userinit
    2700 MSExchangeFrontendTransport
    1708 SMSvcHost
    728 svchost
    460 wininit
    904 svchost
    992 svchost
    4996 TSTheme
    4240 slui
    4904 taskhost
    452 csrss
    4340 csrss
    4 System
    1164 spoolsv
    1988 slClient
    2760 MSExchangeHMWorker
    0 Idle
    Performance Counters Layout information: FileMappingNotFoundException for category MSExchange Active Manager Client : Microsoft.Exchange.Diagnostics.FileMappingNotFoundException: Cound not open File mapping for name Global\netfxcustomperfcounters.1.0msexchange active manager client. Error Details: 2
    at Microsoft.Exchange.Diagnostics.FileMapping.OpenFileMapping(String name, Boolean writable)
    at Microsoft.Exchange.Diagnostics.PerformanceCounterMemoryMappedFile.Initialize(String fileMappingName, Boolean writable)
    at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetAllInstancesLayout(String categoryName)
    ... and...
    A transient failure has occurred. The problem may resolve itself. Diagnostic information:
    Microsoft.Exchange.Data.DataSourceOperationException: The request failed. The remote server returned an error: (503) Server Unavailable. ---> Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. The remote server returned an error: (503) Server Unavailable. ---> System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
    at System.Net.HttpWebRequest.GetResponse()
    at Microsoft.Exchange.WebServices.Data.EwsHttpWebRequest.Microsoft.Exchange.WebServices.Data.IEwsHttpWebRequest.GetResponse()
    at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
    --- End of inner exception stack trace ---
    at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
    at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request)
    at Microsoft.Exchange.WebServices.Data.ExchangeService.InternalFindFolders(IEnumerable`1 parentFolderIds, SearchFilter searchFilter, FolderView view, ServiceErrorHandling errorHandlingMode)
    at Microsoft.Exchange.WebServices.Data.ExchangeService.FindFolders(FolderId parentFolderId, SearchFilter searchFilter, FolderView view)
    at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
    --- End of inner exception stack trace ---
    at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
    at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.GetOrCreateFolderCore(String folderName, FolderId parentFolder, Func`1 creator)
    at Microsoft.Exchange.Data.Storage.Management.AsyncOperationNotificationDataProvider.GetDefaultFolder()
    at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.<>c__DisplayClass1b`1.<InternalFindPaged>b__13()
    at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
    at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.<InternalFindPaged>d__21`1.MoveNext()
    at Microsoft.Exchange.Data.Storage.Management.AsyncOperationNotificationDataProvider.<GetNotificationDetails>d__4.MoveNext()
    at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
    at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.RemoveAllNotification()
    at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.UpdateDataInMbx(List`1 certificates)
    at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.Work()
    I've tried all sorts of recommended fixes but none have worked so far:
    ADSIEdit and remove msExchCanaryData0 data
    Reinstall Exchange multiple times
    Rebooted multiple times
    This article: http://social.technet.microsoft.com/Forums/exchange/en-US/08d3777c-dc03-4411-8c87-7db37d2f406a/exchange-2013-owa-login-error-http-500?forum=exchangesvrclients
    Rebooted DCs multiple times (no exchange servers are DCs)
    I'm sure I've left out a few troubleshooting steps since I've been working at this for two days. Can anybody offer any advice? I'm at my wits end here...

    Hi,
    Please check whether the mail.mydomain.com is pointed to your Exchange 2010 or Exchange 2013. Please run the following command to check your OWA virtual directores and ECP virtual directories:
    Get-OwaVirtualDirectory -ShowMailboxVirtualDirectories | Select Identity,name,Internalurl,ExternalUrl,*auth*
    Get-EcpVirtualDirectory -ShowMailboxVirtualDirectories | Select Identity,name,Internalurl,ExternalUrl,*auth*
    In IIS manager > Default Web Site, please make sure Anonymous Authentication is Enabled in Authentication. Confirm that "Require SSL" is checked on the SSL Settings of the default web site.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 SP1 on Windows Server 2008 R2 Enterprise - BSOD after DAG creation

    Hi,
    We are running Exchange 2007 SP3 RU13 on Windows 2003 R2 with SP2 in a 2003 native AD environment and recently decided to upgrade to Exchange 2013. We installed a pair of new DELL R420 servers running Windows 2008 R2 Enterprise then threw Exchange 2013 SP1
    onto them. This all went fine and the servers are running stable.
    We connected the second NIC of each server to the other via a separate switch, the second NIC has Client for MS Networks and File/Printer Sharing disabled plus a totally separate subnet with no DNS or GW address assigned. DAG setup was run and completed
    OK. I created the DAG network in Exchange and enabled replication, I also left replication enabled across the production LAN. Finally, I went into the advanced network settings and made sure the replication network was below the production network in the binding
    order.
    After an hour or two the BSOD's started.. both servers would crash within a few minutes of each other and reboot with a Kernel Panic. I have attached the contents of the dump file below. This seems to happen every few hours and it always seems to be the
    server hosting the passive DB copies crashes first, followed by the server hosting the active copies. Note that if we disable the replication NIC on both servers they do not crash.
    I got the impression from somewhere that perhaps the servers had mixed up the binding order and were trying to use the replication network as primary, losing access to AD and rebooting (which I have read is the behaviour for Exchange now). It appears the
    Exchange Health service has killed WININIT which causes the crash.
    Thanks!!!
    The crash dump text is below:
    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa80192ebb30, Terminating object
    Arg3: fffffa80192ebe10, Process image file name
    Arg4: fffff80001dc37b0, Explanatory message (ascii)
    Debugging Details:
    PROCESS_OBJECT: fffffa80192ebb30
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    MODULE_NAME: wininit
    FAULTING_MODULE: 0000000000000000
    PROCESS_NAME:  MSExchangeHMWo
    BUGCHECK_STR:  0xF4_MSExchangeHMWo
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff80001e4cab2 to fffff80001abebc0
    STACK_TEXT:  
    fffff880`0d7f39c8 fffff800`01e4cab2 : 00000000`000000f4 00000000`00000003 fffffa80`192ebb30 fffffa80`192ebe10 : nt!KeBugCheckEx
    fffff880`0d7f39d0 fffff800`01df7abb : ffffffff`ffffffff fffffa80`1bcf3060 fffffa80`192ebb30 fffffa80`383ea060 : nt!PspCatchCriticalBreak+0x92
    fffff880`0d7f3a10 fffff800`01d77674 : ffffffff`ffffffff 00000000`00000001 fffffa80`192ebb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
    fffff880`0d7f3a60 fffff800`01abde53 : fffffa80`192ebb30 fffff880`ffffffff fffffa80`1bcf3060 00000000`00000000 : nt!NtTerminateProcess+0xf4
    fffff880`0d7f3ae0 00000000`7772157a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`34eed638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7772157a
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    IMAGE_NAME:  wininit.exe
    FAILURE_BUCKET_ID:  X64_0xF4_MSExchangeHMWo_IMAGE_wininit.exe
    BUCKET_ID:  X64_0xF4_MSExchangeHMWo_IMAGE_wininit.exe
    Followup: MachineOwner

    Hi Darrkon,
    I suggest checking the status of the HealthMailbox on each of servers.
    Also try to re-create the mailbox. You can safely delete and recreate health mailboxes.
    Be aware that any local Managed Availability probes that are using the these mailboxes will fail until the Microsoft Exchange Health Manager is restarted.  Once that service is restarted, it will recreate any mailboxes that it needs. 
    More details in the following similar thread, just for your reference:
    BSOD after creating DAG
    http://social.technet.microsoft.com/Forums/exchange/en-US/44d1cd98-cba1-4ed0-b0e7-8aa76ee3eabc/bsod-after-creating-dag
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange 2013 SP1 and SCOM 2012 R2

    Hi there, 
    Hopefully someone can assist me with this issue, if it is one... 
    I am halfway through an Exchange migration, from Exchange 2010 SP3 on Server 2008 R2 to Exchange 2013 SP1 on Server 2012 R2.
    76 users in total, roughly 80GB of Public Folders.
    I have configured the 2013 environment with a cross datacenter DAG, also increased all of the timeouts of the cluster to take this into consideration, and everything appears to function as expected. 
    Added both 2013 machines to SCOM 2012 R2 for at least a week with no active users on it, and all monitoring reported ok, no issues. 
    Exchange 2010 is configured to use webmail.company.com for RPC over HTTP, which is what I have configured 2013 to use as well. 
    Implemented Microsoft ARR for client access to Exchange 2013, as opposed to ISA we've used for Exchange 2010. 
    A week ago, changed the DNS records for webmail.company.com from ISA to ARR, and all clients connected perfect. 
    Thought, ok, now we can start the migration. So far everything "seems" to be going perfect with the mailbox moves, however, SCOM is really noisy. 
    Attempted to reran the probe for EWS and got the error below:
    Is there perhaps anyone that can assist me with these errors?
    Cheers

    FYI... IIS ARR is not supported for Exchange Server.
    Check in event log if you are getting anything related to the issue.
    About Outlook POP UP to end users. Check the event log on 2010/2013 for MRS events.
    Are those mailboxes still moving or in move request?
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.com    Twitter:
      LinkedIn:
       Check out CodeTwo’s tools for Exchange admins
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2013 SP1 and CUCM 9.1.2 - Exch not recognizing called extension

    I think I'm almost there in getting Exchange 2013 SP1 UM working with CUCM 9.1.2...I've got two issues at the moment that I need a little help with.
    1) When I dial my VM pilot (6040) from a UM enabled extension it prompts to enter an extension. When I dial the same extension and let it ring to VM, Exchange picks up and says "the person you are trying to reach does not have a valid voice mail box
    on our system".
    2) This just started happening this afternoon, when I dial my VM pilot (6040) exch3 picks up as thats what I have my route pattern pointing to. If I enter the extension of a mailbox on exch2, I get stuck in a endless loop.
    I've followed this post as a guide but it hasn't resolved my issue.
    https://supportforums.cisco.com/discussion/11914031/exchange-2013-um-and-cucm-86
    My Exchange environment looks like this:
    Site 1:
    exch1 - CAS/Mailbox, used for mainly utility type work, journal, dedicated SMTP flows etc
    exch2 - CAS/Mailbox, part DAG13
    exch3 - CAS/Mailbox, part of DAG13
    Site 2:
    exch2dr - CAS/Mailbox, part of DAG13
    exch3dr - CAS/Mailbox, part of DAG13
    DAG13 is stretched between two sites, there are no users at our DR site so CUCM is pointing to Site 1 for UM. Each site has an internet facing CAS-only server for OWA/EAS etc.
    Any help is greatly appreciated. I'd love to get rid of Unity. 
    EDIT:
    I just found this event in the event logs:
    The Microsoft Exchange Unified Messaging service on the Mailbox server received a diverted call with ID "d51600-3a3140c5-9b8-c1414ac@EXCH3-IPADDR" for extension "4099" on UM dial plan "CUCM" from UM IP gateway "CUCM IP",
    but no UM-enabled mailbox for the corresponding extension could be found. Please check the extension and make sure that the corresponding mailbox is enabled for UM and associated with the correct UM dial plan.

    9.1.2 I think it is, we upgraded to avoid the known DNS bug
    I cant see how to PM you either
    The crux of it was outlined below with some tweaks
    http://blogs.technet.com/b/canitpro/archive/2014/04/30/step-by-step-integration-between-exchange-2013-um-and-cisco-unified-communication-manager.aspx
    As we have multiple combined role servers, our trunks are set up as follows:
    1. 1 x CAS Trunk - contains all CAS Servers on port 5060
    2. 4 x MBX Trunks - contains Maibox Server with ports 5062-5068
    On top of that, we had to Allow "Redirecting Diversion Header Delivery - Inbound (and Outbound)" on the CAS Trunk but DISABLE it on the Mailbox Trunks
    Also, make sure that you are using Telephone Extension Dial plans in Exchange 2013 (Despite them being unable to be associated with a 13 Server - EX13 answers for all calls anyway)
    Lastly, the MS documentation is a little strange - it says that as your last step of UM migration, you should point your Call Manager to 2013 - I don't agree with that statement, EX13 routes calls back to 2010 UM Servers perfectly fine, so treat it the same
    as any other CAS based service - point to 2013, and it will handle the rest

  • Exchange 2013 SP1 CU8 installation stuck

    Good Morning,
    I'm just installing CU8 for Exchange 2013 on a DAG Member (only mailbox role installed), and setup is stuck at 49% of "Mailbox Role: Client Access service" for more than 2 hours now.
    The ExchangeSetup logfile says:
    [04/15/2015 06:44:20.0582] [2] Active Directory session settings for 'New-PerfCounters' are: View Entire Forest: 'True', Configuration Domain Controller: 'srv-dc02.oostvogels.com', Preferred Global Catalog: 'dc02.contoso.com', Preferred Domain Controllers: '{ dc02.contoso.com }'
    [04/15/2015 06:44:20.0582] [2] User specified parameters: -DefinitionFileName:'ServiceProxyPoolCounters.xml'
    [04/15/2015 06:44:20.0582] [2] Beginning processing new-PerfCounters
    [04/15/2015 06:44:20.0582] [2] Processing file: C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf\ServiceProxyPoolCounters.xml
    [04/15/2015 06:44:20.0582] [2] Performance counter name is Proxy Instance Count, type is NumberOfItems32.
    [04/15/2015 06:44:20.0582] [2] Performance counter name is Current Outstanding Calls, type is NumberOfItems32.
    [04/15/2015 06:44:20.0582] [2] Performance counter name is Total Number of Calls, type is NumberOfItems32.
    [04/15/2015 06:44:20.0582] [2] Performance counter name is Calls/sec, type is RateOfCountsPerSecond32.
    [04/15/2015 06:44:20.0582] [2] Performance counter name is Average Latency, type is AverageCount64.
    [04/15/2015 06:44:20.0582] [2] Performance counter name is Base for Average Latency, type is AverageBase.
    [04/15/2015 06:44:20.0582] [2] Performance counter category name is 'MSExchange ServiceProxyPool'.
    [04/15/2015 06:44:20.0738] [2] Performance counter category name is 'MSExchange ServiceProxyPool'.
    [04/15/2015 06:44:22.0255] [2] Ending processing new-PerfCounters
    Does anyone have any suggestions or did you experience a similar issue?
    I also can see some events like this:
    Cmdlet failed. Cmdlet New-PerfCounters, parameters -DefinitionFileName "ADDriverCachePerformanceCounters.xml".
    Thanks and best regards,
    Sebastian

    Hi,
    According to your post, I understand that install Exchange 2013 SP1 CU8 in a DAG with MBX role failed with error “Cmdlet failed. Cmdlet New-PerfCounters, parameters -DefinitionFileName ‘ADDriverCachePerformanceCounters.xml’”.
    If I misunderstand your concern, please do not hesitate to let me know.
    I want to double confirm whether you deploy clean install or implement upgrade an existing Exchange Server 2013 installation to Cumulative Update 8.
    To rebuild all Performance counters including extensible and third-party counters, type the following commands at an Administrative command prompt. Press ENTER after each command:
    1. Rebuilding the counters:
        cd c:\windows\system32
        lodctr /R
    2. Resyncing the counters with Windows Management Instrumentation (WMI):
        WINMGMT.EXE /RESYNCPERF
    3. Stop and restart the Performance Logs and Alerts service.
    4. Stop and restart the Windows Management Instrumentation service.
    If the issue persists, please run to reload all the perf counters. For your reference:
    http://blogs.technet.com/b/mikelag/archive/2010/09/10/how-to-unload-reload-performance-counters-on-exchange-2010.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

  • Exchange 2013 SP1 - healthsets failing

    Hi,
    I have recently installed two Exchange 2013 SP1 servers in different environments and are experiencing issues on both. Issues that I haven't seen on Exchange 2013 without SP1.
    I have 6 healthsets which are unhealthy. 
    Autodiscover...
    ActiveSync.P...
    EWS.Proxy
    OAB.Proxy
    Outlook.Proxy
    OutlookMapiH...
    I found this article: 
    http://technet.microsoft.com/en-us/library/ms.exch.scom.ecp.proxy(v=exchg.150).aspx
    Which describes, that try to restart the app pool, then an iisreset - and lastly reboot the server. Tried all and none of them helped.
    But then I found this error in the Exchang event log:
    RecycleApplicationPool-MSExchangePowerShellAppPool-RpsDeepTestPSProxyRestart: Throttling rejected the operation
    Which fails almost every minute.
    And I guess that this could be the issue. But I can't figure out which throttling that is causing this.
    Any one else with this issue on Exchange 2013 SP1?
    Thanks in advance.
    /Kim

    Hi,
    I have seen a lot of similar issues with health manager service. For IIS services, we can safely ignore these warnings. Personal experience, we just need to monitor whether there are related
    error reports in event log.
    Thanks,
    Simon Wu
    TechNet Community Support

Maybe you are looking for

  • Satellite A100-795 - Hard disk replacement

    Hi, I have a Satellite A100-795 (model: PSAANE-02D00JBT). HD = Toshiba MK1237GSX HD can only be partly read with recovery software (Active@undelete) and makes bad noises too. Wich SATA harddisk are possible and supported by the bios? I want to avoid

  • Exporting From Final Cut Pro 5.0

    Hello, I need to export my work from Final Cut Pro 5.0 to a Quicktime Movie with the following settings - Compression: H.264 Frame Rate: 15fps Bit Rate: 200k Is this posible without loosing the quality of the video footage? The footage was capture fr

  • Connecting PowerBook to PowerMac

    I've heard there is a procedure for connecting a PowerBook to a PowerMac so that basically the PowerBook is an external hard drive for the PowerMac. What all is involved besides just hooking the firewire cable to each computer? TIA for your help.

  • Apple works opening an old file

    trying to open a file get a window : An I/o error occurred. any clues how to open

  • WD Raptor 8M cache or 16 MB cache?

    Hello, I have a Mac G5 Dual 2.0 GHz and I want to buy one of this drive but I'm not sure about the compatibility with my system. If I use these drives on a firewire 800 external case I don't know if they're going to perform as well as internal. Thank