Recipient verification on Exchange 2013 SP1

Hello,
we use 3rd party tool for antispam and I'm unable to configure recipient verification on Exchange 2013 with SP1.
Basically i have done all steps described in article http://technet.microsoft.com/en-us/library/bb125187.aspx and still i am able to send mail to non existent users (Exchange sends NDR)
My recipient filter config looks like this:
RunspaceId                 : a4ec4d9b-a68d-43e2-beb9-c397505d1321
Name                       : RecipientFilterConfig
BlockedRecipients          : {}
RecipientValidationEnabled : True
BlockListEnabled           : True
Enabled                    : True
ExternalMailEnabled        : True
InternalMailEnabled        : True
AdminDisplayName           :
ExchangeVersion            : 0.1 (8.0.535.0)
DistinguishedName          : CN=RecipientFilterConfig,CN=Message Hygiene,CN=Transport
                             Settings,CN=secureemail,CN=Microsoft
                             Exchange,CN=Services,CN=Configuration,DC=domain,DC=priv
Identity                   : RecipientFilterConfig
Guid                       : d34e78fa-bc92-44db-80bb-85e300135422
ObjectCategory             : domain.priv/Configuration/Schema/ms-Exch-Message-Hygiene-Recipient-Filter-Config
ObjectClass                : {top, msExchAgent, msExchMessageHygieneRecipientFilterConfig}
WhenChanged                : 30/04/2014 10:29:43 AM
WhenCreated                : 01/10/2011 12:34:08 PM
WhenChangedUTC             : 30/04/2014 2:29:43 PM
WhenCreatedUTC             : 01/10/2011 4:34:08 PM
OrganizationId             :
OriginatingServer          : server01.domain.priv
IsValid                    : True
ObjectState                : Unchanged
I have allowed anonymous connection on default connector.
Also, transport agent is enabled.
My problem is that mail gets in queue even i don't wanna this to happen.
Any advice is more then welcome.
Thanks,
Ivica

Hello,
well, we don't use Edge transport, we use 3rd party tool.
here is link from them:
http://helpdesk.spamtitan.com/support/articles/95349-recipient
important part:
"Once Recipient Filtering is enabled log on to the SpamTitan web interface. Browse to System Setup->Mail Relay->Domains.  Edit a domain and select "Dynamic Verification" and enter your mail server IP as the Verification Server.
This will allow SpamTitan to verify the recipient addresses of all incoming mail. 
Any mail addresses to invalid addresses will be dropped.  This will aid the spam block rate and keep your daily license usage count accurate."
But here is not issue with Spamtitan, it is with Exchange itself because i try to make it work via telnet session. 
I'm using scripts:
Set-RecipientFilterConfig -Enabled $trueSet-RecipientFilterConfig -BlockListEnabled $trueSet-RecipientFilterConfig -RecipientValidationEnabled $true

Similar Messages

  • 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

  • Cannot write email body in OWA with Exchange 2013 SP1 CU6

    Hi,
    I have a problem with Exchange 2013 SP1 with CU6.
    All of OWA user cannot write in the body of email. They can write the Object and the recipient but they cannot select body and write the body message. We have try with multiple Web brother and desactivate all Add-on but the problem still there...
    The only way that works is to respond to an email, and in that case, it's working, we can write normally in the body of email.
    Have you an idea ?
    Thanks in advance!
    Sebastien

    Hi, 
    After contacting Microsoft support, we have found the solution.
    The problem appear after we have recently install the patch described in this KB 2997209:
    https://support.microsoft.com/kb/2997209?wa=wsignin1.0
    But on 2013 Mailbox Server, Echange is not installed in the default path C:\ but on D:\
    So we have to manually copy the content of folder D:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\prem\15.0.995.29 in the folder 15.0.995.31 (MAKE a BACKUP of FOLDER BEFORE!)
    No need to reboot, or restart IIS, it's working after that!
    @+
    Sébastien

  • New DAG - 2012R2 & Exchange 2013 SP1

    Hi there,
    Setting up a test platform running on 2012R2 with Exchange 2013SP1, and whilst all looks ok I simply cannot add any server to a new DAG, I can create the dag without any issues and tried using DAG with an IP, and a simplified DAG without IP however simply
    cannot add any of my 2 member servers with the following error;
    Exchange 2013 SP1 A server-side administrative operation has failed. 'GetNetworkConfig' failed on the server. Error: The NEtworkManager has not yet initialized.
    LAN - 10.21.129.111 & 112 / 24
    REPLICATION - 192.168.129.111 & 112 / 24
    I've checked everything! All sits on vCloud, removed ALL NICs and replaced, removed Symantec, no loss between REPL NICs, all seems fine.  Not a lot in the logs other than these last results;
    [2014-03-05T12:51:10] Updating 'MDB001'.MasterServerOrAvailabilityGroup to 'DAG001.
    [2014-03-05T12:51:10] database[ 0 ] (MBDB01)'s MsOrDag=DAG001.
    [2014-03-05T12:51:10] database[ 1 ] (MDB001)'s MsOrDag=DAG001.
    [2014-03-05T12:51:10] Updated Progress 'Successfully updated the membership of server 'SRV111' in Active Directory group 'DAG001'.' 18%.
    [2014-03-05T12:51:10] Working
    I'm at the end of the road and cannot find anything to help me ;(

    HI Jared,
    I agree, have a feeling it's that bit but not sure how to check if working or re-install perhaps.
    Copy status is ALL ok;
    CopyQueueLength - 0
    ReplayQueueLEnght - 0
    ContentIndexState - Healthy
    This is without DAG.  For replication Health fails on last 2 points on both VMs, could it be missed failover cluster bit or didn't install correctly?
    DatabaseRedundancy
    DatabaseAvailability
    RunspaceId       : d4597641-ae09-4687-8e66-cfbef67bc31f
    Server           : SRV111
    Check            : DatabaseRedundancy
    CheckDescription : Verifies that databases have sufficient redundancy. If this check fails, it means that some
                       databases are at risk of losing data.
    Result           : *FAILED*
    Error            : Failures:
                           There were database redundancy check failures for database 'MBDB01' that may be lowering its
                       redundancy and putting the database at risk of data loss. Redundancy Count: 1. Expected Redundancy
                       Count: 2. Detailed error(s):
                               SRV111:
                               Database 'MBDB01' does not have enough copies configured to meet the validation criteria.
                           There were database redundancy check failures for database 'MDB001' that may be
                       lowering its redundancy and putting the database at risk of data loss. Redundancy Count: 1.
                       Expected Redundancy Count: 2. Detailed error(s):
                               SRV111:
                               Database 'MDB001' does not have enough copies configured to meet the validation
                       criteria.
    Identity         :
    IsValid          : True
    ObjectState      : New
    RunspaceId       : d4597641-ae09-4687-8e66-cfbef67bc31f
    Server           : SRV111
    Check            : DatabaseAvailability
    CheckDescription : Verifies that databases have sufficient availability. If this check fails, it means that some
                       databases are at risk of losing service.
    Result           : *FAILED*
    Error            : Failures:
                           There were database availability check failures for database 'MBDB01' that may be lowering its
                       availability. Availability Count: 0. Expected Availability Count: 2. Detailed error(s):
                               SRV111:
                               Couldn't read the database availability group for server
                       'SRV111.ad.totalitycloud.com' from Active Directory. Error: Could not find the database
                       availability group object for server SRV111 in Active Directory.
                           There were database availability check failures for database 'MDB001' that may be
                       lowering its availability. Availability Count: 0. Expected Availability Count: 2. Detailed
                       error(s):
                               SRV111:
                               Couldn't read the database availability group for server
                       'SRV111.ad.totalitycloud.com' from Active Directory. Error: Could not find the database
                       availability group object for server SRV111 in Active Directory.
    Identity         :
    IsValid          : True
    ObjectState      : New

  • 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

  • Error while adding member to the dag in exchange 2013 sp1

    I have Windows Server 2012 Std Edition with Exchange 2013 SP1 and get the following error while adding member to the dag either i do it using EAC or the powershell
    Senior Technical Consultant, MDS Computers

    When running set-databaseavailabilitygroup Exchange-dag without parameters, it crashes again:
    [PS] C:\Windows\system32>Set-DatabaseAvailabilityGroup exchange-dag
    WARNING: An unexpected error has occurred and a Watson dump is being generated: Some or all identity references could not be translated. Some or all identity references could not be translated.
        + CategoryInfo          : NotSpecified: (:) [Set-DatabaseAvailabilityGroup], IdentityNotMappedException
        + FullyQualifiedErrorId : System.Security.Principal.IdentityNotMappedException,Microsoft.Exchange.Management.Syste
       mConfigurationTasks.SetDatabaseAvailabilityGroup
        + PSComputerName        : <server>
    Also, this is logged in the eventlog:
    Watson report about to be sent for process id: 7424, with parameters: E12, c-RTL-AMD64, 15.00.0847.032, w3wp#MSExchangePowerShellAppPool, M.Exchange.Management, M.E.M.C.FileShareWitness.Create, S.S.Principal.IdentityNotMappedException, 3e5c, 15.00.0847.031.
    ErrorReportingEnabled: True 
    Definitely looks like a problem creating the filewitness share.
    Frank.

  • Upgrade of Integation Services (Windows 2012 R2) on Windows 2008 R2 with Exchange 2013 SP1 DAG fails

    Here is the scenario:
    Legacy Host: Windows 2008 R2
    Guest VM: Windows 2008 R2 with Exchange 2013 SP1 DAG cluster.
    After importing the VM (2008 R2 and Exchange 2013 DAG) into a 2012 R2 host (Cluster).  (copy VM files to new 2012 R2host) Everything works fine.
    Then upgrading "Installation Services" (for Windows 2012 R2 host) on the imported VM runs fine with no errors to the "Restart" prompt. VM than shows: "Configuring Windows updates 32% complete. Do not turn
    of your computer." Hangs there for about 20 minutes until is says "shutting down". Hangs there for 20 minutes until power off. Restart to normal start; "Preparing to configure Windows. Do not turnoff your computer." proceeds slowly
    to "Configuring Windows updates 32% complete. Do not turn of your computer." hangs there again indefinite. Sometime hangs at shutdown cycle and "Configuring Windows updates 32% complete. Do not turn of your computer." indefinitely.
    I moved 20 other machines from a 2008 R2 host to new Windows 2012 R2 hosts all of these machines install the 2012 R2 Integration services just fine on the 2008 R2 VM. Just the 2008 R2 VMs clustered (DAG) and Exchange 2013 SP1 do not take the Integration
    Services upgrade.
    Any advise from Microsoft? I know I could decommission the DAG and Exchange machines and install Integration services on the native box before Exchange and DAG and that would sure work, but I'd rather avoid that amount of work for a simple integration layer
    upgrade.
    Thanks
    Gerhard Waterkamp ACSLA Inc.

    Hi,
    Could you try use the following method to fix this issue first?
    1. Run the System Update Readiness Tool, then check if there is any error in the Checksur.log and checksur.persist.log.
     1. Please run the System Update Readiness Tool on this affected server. Please download this tool from the following Microsoft article:
     Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, and for Windows 7
     http://support.microsoft.com/kb/947821/en-us
    2. The System Update Readiness Tool creates the log files that captures any issues that the tool found or fixed. The log files are located at the following location:
    %SYSTEMROOT%\Logs\CBS\
    3. Please paste the checksur.log here for analysis.
    If there is no error found, please try the following step.
    ==================================
    2. Use Fix it tool to reset the Windows Update components.
     1. Open the following link.
     http://support.microsoft.com/kb/971058/en-nz
     2. Select Windows 8.1, Windows 8 and Windows 7 in the product selection box.
     3. Click “Run Now” to reset the Windows Update components.
    Note: We can reset the Windows Updates manually by following the steps in the KB above.
    3. Use the System File Checker tool to repair missing or corrupted system files
     1. Open the command promote with Administrators.
     2. At the command prompt, type the following command, and then press ENTER:
         sfc /scannow
    Any errors are found in the steps above, please let me know.
    Hope this helpful.
    Best Regards,
    Jason Zeng
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Exchange 2013 SP1 setup fails at prerequisite Analysis

    I installed a completely new server network with Hyper-v 2012R2
    I installed two virtual 2012R2 servers: DC01 as the Domain Controller of "testdomain.local" and EX01 as the Exchange server.
    EX01 is joined the domain "testdomain" from DC01
    I log in on EX01 with an in AD created testdomain\exadmin account who is member of domain admins, enterprise admins, schema admins, administrators and group policy creator owners.
    I have run the command Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience,
    NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing,
    Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression,
    Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation, Telnet-Client, RSAT-ADDS
    on EX01
    I have installed the Microsoft Unified Communications Managed API 4.0
    Then I run the Exchange 2013 SP1 setup and the prerequisite check gives the following errors:
    Error:
    You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
    Error:
    Setup encountered a problem while validating the state of Active Directory: Active Directory server  is not available. Error message: Active directory response: The LDAP server is unavailable.  See the Exchange setup log for more information on this
    error.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
    Error:
    Either Active Directory doesn't exist, or it can't be contacted.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
    I can connect with the Active Directory Sites and Domains and other applets to the AD. So Why these errors???
    HELP!
    Regards, Manu
    Manu van Winkel

    Hi, thanks for the answer.
    I restarted the server and did the "run as administrator": same result.
    The first errormessage in the exchangesetup.log is:
    [ERROR] Setup encountered a problem while validating the state of Active Directory: Active Directory server  is not available. Error message: Active directory response: The LDAP server is unavailable.  See the Exchange setup log for more information
    on this error.
    When I run dcdiag /s:DC01 from EX01 it passes all tests except:
    DFSREvent "The RPC server is unavailable"
    KccEvent "The RPC server is unavailable."
    SystemLog  "The RPC server is unavailable."
    Could these be of any influence?
    Running dcdiag on DC01 passes all tests.
    The only thing I changed after setting up DC01, was changing the fixed IP-adres from 192.168.25.3 to 192.168.25.2, but I ran ipconfig /flushdns and ipconfig /registerdns and dcdiag /fix afterwards.
    The only roles installed on DC01 are AD DS (I tried installing exchange before and after adding the AD DS role), AD, DNS, DHCP and Fileservices
    I don't know where to look anymore....
    Manu van Winkel

  • Exchange 2013 SP1 Installation Errors I Cannot Resolve

    Good Afternoon All -
    Note:  I updated this post an hour after posting.  Still no solution, but please see updated info at end of this post)
    I'm trying to introduce Exchange into an existing, small environment.  The server I'm trying to install it onto is an SBS 2011 server (single server.)  Even though SBS comes with Exchange, I found out that it's installation was corrupted and someone
    had attempted to uninstall it before.  Yes, it's being installed onto a server with a DC.  I considered creating a Hyper-V VM on the server for Exchange, but thought it may be better to try to install directly onto server instead.
    Before I started, I made sure all Exchange data had been removed.  I checked for and deleted (if present) all Exchange-related objects in ADSI, ADU&C, files, and registry entries.
    When I try to install Exchange 2013 SP1, I get the below errors.  I know that some are easily resolved by installing pre-requisites - however - others aren't - especially the pending reboot one.  I've restarted the server many times when making
    changes or applying various updates and still get flagged to restart during installation.  I've tried the SBS 2011 repair disc as well, but had many issues with it.  In all honesty, the whole server needs to be wiped and re-installed, but
    cannot do at this point.
    Besides the errors below, I've zipped up the ExchangeSetupLogs folder and placed them in the link below.  Also below are system specs.  The only edit I made in them is a find/replace for server and domain name.
    ExchangeSetupLogs Folder
    System Specs
    Xeon E31270 3.4Ghz
    16gb RAM
    Windows Server 2011 SBS x64 (Domain Controller Role Installed & Used)
    C:\ - RAID 1 = 500gb
    D:\ - SATA HDD = 320gb
    E:\ - SATA HDD = 320GB
    Should I perhaps try to install to a VM on the server or think that would use too many unnecessary resources?
    Any help would be appreciated - Thanks!
    Error:
    This computer requires the update described in Microsoft Knowledge Base article KB2619234 (http://go.microsoft.com/fwlink/?LinkId=262359).
    Without this update, the Outlook Anywhere feature may not work reliably.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.Win7RpcHttpAssocCookieGuidUpdateNotInstalled.aspx
    Error:
    There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then
    run Setup again.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindowsComponents.aspx
    Error:
    The Windows component RSAT-Clustering isn't installed on this computer and needs to be installed before Exchange Setup can begin.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RsatClusteringInstalled.aspx
    Error:
    This computer requires the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit. Please install the software from
    http://go.microsoft.com/fwlink/?LinkId=260990.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UcmaRedistMsi.aspx
    Error:
    An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
    Windows Server 2008 R2 SP1 or later and Windows Server 2012.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
    Warning:
    Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected
    in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected
    in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
    Ben K.
    UPDATE
    I just tried fixing a few things and tried again.  Still no luck.  Below is what I changed as well as the errors received.  Only option was Retry.  Can I just not install it onto this environment?
    What I Changed
    Installed Unified Comm Managed API 4.0 (Required Uninstalling Speech Analysis app before it would install)
    Installed KB2619234 for Outlook Anywhere
    Installed 12 updates - Server fully patched
    Exchange Setup Errors
    Error:
    An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
    Windows Server 2008 R2 SP1 or later and Windows Server 2012.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
    Warning:
    Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected
    in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected
    in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
    Thanks Guys -

    Hi,
    Agree. Windows Server 2011 SBS x64 can be the problem.
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • 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 Object is corrupted and inconsistent state after Lync 2013 Installation

    Hi Fellows,
    I am facing an issue with Exchange 2013 SP1 (5.0.847.32)
    environment. I recently installed Lync 2013 (version: 5.0.8308.0) a week ago and just recently start getting the below error when configuring delegation or modifying the users/groups from Exchange Control Panel:
    "The Object <object DN> has been corrupted, and it's in an inconsistent state. The following validation errors happened:
    The access control defines the ObjectType <object guid> that can't be resolved.."
    I can see some forum threads with same issue (links given below) but unable to find if this is a known issue and how to get it resolved. Need assistance if anyone has faced same and could help me out to figure it.
    http://social.technet.microsoft.com/Forums/exchange/en-US/72310530-d1de-4b39-a0fb-1592247df03f/access-control-entry-issue-after-installing-lync-2013-into-the-forest?forum=exchangesvrdeploy
     http://www.networksteve.com/exchange/topic.php/Issue_with_exchange_2013_lync_2013_intergration/?TopicId=37192&Posts=2
    J.A

    Hi
    Usually the affected SID objects are referring to deleted objects.
    Use the PsGetSid tool to try to resolve them.

  • Exchange 2013 SP1 readiness check failing

    Trying to install our first Exchange 2013 SP1 server on Windows 2012 R2 in our datacentre, the readiness check fails with:
    Error:
    The Active Directory schema isn't up-to-date, and this user account isn't a member of the 'Schema Admins' and/or 'Enterprise Admins' groups.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.SchemaUpdateRequired.aspx
    There are many more errors relating to Enterprise admin rights etc.
    Please note that:
    My account is Domain admin, Schema admin and Enterprise admin member, it always has been.
    I tried the built-in AD Administrator which of course is part of the groups as well, no difference.
    Active Directory is at 2008 R2 for domain and forest functional levels.
    I tried rejoining the new Exchange designated server to the domain
    I've installed RSAT-ADDS, the Managed API 4.0 and all the other windows roles via powershell
    There is a local domain controller that is a global catalog server on the new Exchange server subnet
    I tried running the Exchange Setup on a different server on the same subnet as where the active 2010 Exchange server resides as well as the FSMO AD role holder resides, this works fine. I even did the AD prep from there no problem, that made no difference
    on the datacentre server
    AD replicates fine between the FSMO role holder and the Datacentre (no errors in dcdiag or repadmin /showrepl)
    This error is in the event log:
    The description for Event ID 4027 from source MSExchange ADAccess cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    ExSetupUI.exe
    6724
    Get Servers for domain.local
    TopologyClientTcpEndpoint (localhost)
    3
    System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:02.0475315. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:890. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890
    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
    at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
    at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
    --- End of inner exception stack trace ---
    Server stack trace:
    at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
    at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
    at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
    at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
    at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
    Exception rethrown at [0]:
    at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
    at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
    at System.ServiceModel.ICommunicationObject.Open()
    at Microsoft.Exchange.Net.ServiceProxyPool`1.GetClient(Boolean useCache)
    at Microsoft.Exchange.Net.ServiceProxyPool`1.TryCallServiceWithRetry(Action`1 action, String debugMessage, WCFConnectionStateTuple proxyToUse, Int32 numberOfRetries, Boolean doNotReturnProxyOnSuccess, Exception& exception)
    the message resource is present but the message is not found in the string/message table

    So I decided to re-install the OS, worked perfectly now. Only difference from before would be:
    SCCM hasn't pushed SCEP 2012 to the new build of the same server yet
    The original server was installed in a different AD site and then it was physically mode and reassigned to an new AD site and subnet
    I might have installed the pre-reqs in a slightly different order (RSAT-ADDS, all the IIS etc things via powershell
    and then the UCM API 4.0. (saw few comments that the order of how you install them matters in other forums).
    10 or so Microsoft Windows updates haven't installed on the new OS build yet.
    Other than that, its identical. But if its not broken don't fix it, perhaps the above can help someone else though. 

  • Exchange 2013 sp1 move databases

    Hello all
    I am running Exchange 2013 sp1 in a two node DAG. Originally the DAG  had two under powered servers, i built two new more powerful servers added the servers to the DAG, then i moved database copies to the new servers, removed the copies from the original
    servers and then removed the original servers from the DAG. The two original servers are multi role (CAS Mailbox) and currently they are still in the org. My confusion is around this. When i run get-mailbox -identity <name>. The output from the command
    shows the mailbox is on oldserver.  Again oldserver was removed from the DAG and no databases exist on the server. I want to remove the two old servers from the org, but i am hesitant on doing this because all mailboxes seem to think they exist on oldserver 
    Thanks for any help
    Bulls on Parade

    You can ignore that:
    http://blogs.technet.com/b/timmcmic/archive/2011/09/26/exchange-2010-homemta-and-msexchhomeservername-are-not-updated-on-mailboxes.aspx
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2013 SP1 & Custom OWA Theme

    On Friday of last week we updated from Exchange 2013 CU2 to Exchange 2013 SP1. Since updating our custom OWA theme no longer works. We configured it according to the following guide:
    http://technet.microsoft.com/en-us/library/bb201700(v=exchg.150).aspx
    The theme we customized was stored in the following location:
    \Client Access\OWA\version\Owa2\resources\themes\"title of our theme"
    Themes no longer appear to be stored in this location and I am uncertain as to where they have moved and how to apply them. Has anyone else run into this issue?

    Hi,
    Can we try to re-importing the theme again?
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

Maybe you are looking for