RV 220W connect to exchange server 2013

Hello,
i want to send remote protocol to my own Exchange Server.
There is no working with "Login Plan" or "Cram-MD5".
Error:
[rv220w][System][PLATFORM] dbRecordValueGet failed for toAddr column
Is there a solution?
Thank you!

Similar Messages

Writing client app to connect to Exchange Server 2013 and set OOF for users on vacation

I am coding an C# app that should connect to Exchange Server 2013 on-premise (Servers Location is not in our Company). I`ve got an account (User and Pass) with readonly admin-rights for now and want to read and set OutOfOffice Objects for other users. I
decide to use EWS Managed API over Autodiscovery but I am bit confuse how
I tried to connect with "service.UseDefaultCredentials = true" and read contacts -> this code works:
try
            ExchangeService _service
= new ExchangeService(ExchangeVersion.Exchange2013_SP1);
            _service.Credentials
= new WebCredentials("service.exchange",
"1234", "domain");
            _service.TraceEnabled
= true;
            _service.TraceFlags
= TraceFlags.All; _service.UseDefaultCredentials
= true;
            _service.AutodiscoverUrl("[email protected]",
RedirectionUrlValidationCallback);
            foreach
(Contact contact in _service.FindItems(WellKnownFolderName.Contacts,
new ItemView(2)))
var test = contact;
        catch
(Exception exception)
            Console.WriteLine(exception);
After that I tried the same with _service.UseDefaultCredentials = false; got error -> "The Autodiscover service couldn't be located." I am not shure if this "direct log on" is the right way, On msdn I've read about "delegate access"
and "Impersonation" (NTLM and Basic Authentication) I'am a bit confused. Can anybody help me?

hi,
when you set a credential, you don't have to set the UseDefaultCredentials property (it is already updated).
For autodiscover, you should try to set the property EnableScpLookup to True if you are in the Exchange domain or it is known by the current domain.
Autodiscover uses a domain query (through Active Directory) and/or a dns query (this requires a DNS register for autodiscover.domain.net) to determine the access to the autodiscover service URI.
Regards,
Désiré GOVIN Refresh IT Solutions

Can ColdFusion 10 connects to Exchange Server 2013?

There are lots of forums and chats about ColdFusion 10 connecting to Exchange Server 2010. Does anybody knows whether ColdFusion 10 can connects to Exchange Server 2013. If you do know, what are the steps involved? I have tried all the tricks used in ColdFusion 10 connecting to Exchange Server 2010 and still cannot connect to Exchange Server 2013.

Found a solution. Yes you can connect ColdFusion 10 to Exchange Server 2013 but there is a slight twist to the solution if you want to use cfexchangeXXXXX functionalities.
1. Ensure that you have imported the Exchange Server 2013 certificate into ColdFusion 10 server.
2. When calling cfexchangeconnection, add:
serverversion="2010"
Protocol="https"
formbasedauthentication="TRUE"
formbasedauthenticationURL="XXXXXX"
If serverversion is missing, it will default to 2007 server.

Outlook 2013 not connect with Exchange server 2013 in internal network

Hello All,
I Have two Exchange server 2013 in our environment. Both server install mailbox and CAS role. After configure exchange server 2013, Outlook 2013 not connect in internal network. I have configure outlook manually. i tried by using the suggestion from blog
but not work. Outlook show that Server cannot connect/ server name could not be resolved. in outlook setting i also put exchange proxy setting. In exchange admin center i have changed the OWA, OAB, Auto discover name. But still not work.
I know that outlook can be connect from external by using ssl certificate and publish outlook anywhere but i did my configure from internal network.
Can you please suggest as soon as possible.
Thanks,
Parvez

Hi,
Firstly, I’d like to explain, same with external users, internal users use Outlook Anywhere to connect with Exchange server and use Autodiscover get all settings.
Thus, let’s try the following resolutions:
1. run the following command: get-clientaccessservice |fl autodiscoverserviceinternaluri
2. check if the host name in the above URL is in the DNS server and there is a DNS entry about the host name points to the proper IP address.
3. Check if the above host name is in your certificate.
Thanks,
Angela
Angela Shi
TechNet Community Support

Connecting to Exchange Server 2013 using IMAP command gives authenication error

Hello All,
My application (it is a C# code) connects to Microsoft exchange server 2013 using POP3 and IMAP, processes the emails, marks as read and move to particular folder if it is processed successfully else to an different folder. In this sometimes,
I am getting authentication failed error from IMAP however same mail is processed when it is executed next time. Few times it is processed with out error. I am not sure what is causing this issue.We are connecting to IMAP using tcpIMAP command.
This is the same application which we used with exchange server 2010 now we are upgrading to exchange server 2013. I have verified that the setting of exchange 2010 and 2013 are the same.
To verify the IMAP command I created a sample application using C# which will try to connect to IMAP service and log in to exchange server 2013; it fails to authenticate the user after connecting for few times and then it starts to authenticate
successfully then again fails for few times and then authenticates. I am not sure why this is happening.
Please suggest how can I resolve this.
Thank you, Santha

Since I've upgraded to Snow Leopard I've also moved from Entourage 2008 to Mail, iCal & Addressbook with the new Exchange support.
My company exchange server is Exchange 2007.
Mail works fine except the occasional Mail crash.
iCal worked fine the first two days and then it came with an error the it cannot connect to the Exchange server and asks me to type my email address again. Doesn't work so I need to put my exchange calendar in iCal in offline. But now there is no syncing with the Echange server.
This only occurs when I add a meeting request in iCal.
My Exchange administrator has reset my mailbox on the Exchange server.
This helped for about 4 hours. Now it's the same problem.
I have a feeling the when you setup your exchange account in Mail it uses different settings for Mail and iCal with the autoconfig.
Anybody has a solution? My Exchange admin cannot find any problems on his side. Do I need to make changes on my iCal client or do we need to wait for OS 10.6.1 ?

Exchange Server 2013 // MFCMAPI could connect with errors

While connecting with Exchange Server 2013 I have started facing problem with my application.
My application fails to connect to Exchange with below parameters, then i have tried using MFCMAPI to if everything is okay. MFCMAPI could connect with above errors.
And I have tried with program using below parameters, i still get network error from MAPI call. Can you kindly help, I can provide any additional
details needed.
___ props[prop_count].ulPropTag = PR_PROFILE_UNRESOLVED_NAME;
    props[prop_count].Value.lpszA   = <ProfileUnresolvedName>;
    prop_count++;
    props[prop_count].ulPropTag     = PR_PROFILE_UNRESOLVED_SERVER;
    props[prop_count].Value.lpszA   = <[email protected]>;
    prop_count++;
    // Setting this to TRUE causes OpenMsgStore() to fail with MAPI_E_UNCONFIGURED
    props[prop_count].ulPropTag      = PR_CONVERSION_PROHIBITED;
    props[prop_count].Value.b        = FALSE;
    prop_count++;
    props[prop_count].ulPropTag     = PR_PROFILE_CONFIG_FLAGS;
    props[prop_count].Value.l       = CONFIG_SERVICE /*| CONFIG_PROMPT_FOR_CREDENTIALS
| CONFIG_SHOW_CONNECT_UI */;
    prop_count++;
    props[prop_count].ulPropTag     = PR_DISPLAY_NAME;
    props[prop_count].Value.lpszA   = <Mailbox Profile Name>;
    prop_count++;
    //Above setting used to be sufficient to connect using RPC
    //Below parameters added to connect via HTTPS
    LPSTR pwszUser = "domain\\username"; //also tried
[email protected] AND username
    LPWSTR pwszPassword = L"paswword"; // Password has been encrypted using CryptProtectData
    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_W;
   props[prop_count].Value.lpszW = L"https://ProxyHostname.domain";
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_AUTH_PACKAGE;
    props[prop_count].Value.l = RPC_C_AUTHN_NONE;      // RPC_C_HTTP_AUTHN_SCHEME_NTLM,
RPC_C_HTTP_AUTHN_SCHEME_BASIC
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_FLAGS;
    props[prop_count].Value.l = PRXF_ENABLED | PRXF_SSL;// | PRXF_IGNORE_SEC_WARNING; // | PRXF_IGNORE_SEC_WARNING;
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_PRINCIPAL_W;
    props[prop_count].Value.lpszW = L"msstd:certificateserverhostname.domain";
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_AUTH_PACKAGE;
    props[prop_count].Value.l = RPC_C_AUTHN_GSS_NEGOTIATE;
// RPC_C_AUTHN_WINNT, RPC_C_AUTHN_GSS_NEGOTIATE, RPC_C_AUTHN_NONE
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_AUTH_USER_W;
    props[prop_count].Value.lpszA = pwszUser;
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_AUTH_PASSWORD;
    props[prop_count].Value.bin.lpb = dataBlobOut.pbData;
    props[prop_count].Value.bin.cb = dataBlobOut.cbData;
    prop_count++;
    DB( (DB_PR _T("ConfigureExchangeService() About to configureMsgService\r\n"),
this ) );
    hres = lpServiceAdmin->ConfigureMsgService( exchUID, 0, config_flags, prop_count, props
    I still get MAPI_E_NETWORK not found
Are there any configuration changes need to be done on Exchange Server?
Is there any mistake in above parameters?
Kindly suggest.

You can refer Dave's blog post @
http://blogs.msdn.com/b/dvespa/archive/2013/05/21/how-to-mfcmapi-create-mapi-profile-exchange-2013.aspx
DeVa, M.S., {MSFT} Please remember to mark the replies as answers if they help

External Clients cannot connect to Exchange Server

Hello all:
My external clients using outlook cannot connect to Exchange Server 2013. We have on-presmise version updated to Cu3 and after the Cu3 update we lost connectivity with Outlook clients. Many of the settings in IIS were changed after the Cu3 update,
I noticed after my http->https redirect was not applied anymore to the default website. Here is my Get-OutlookAnywhere results:
RunspaceId : 6379fab1-f692-484f-8118-99e48330d4c4
ServerName : EXCHSERV
SSLOffloading : True
ExternalHostname : mail.domain.com
InternalHostname : mail.domain.com
ExternalClientAuthenticationMethod : Negotiate
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic}
XropUrl :
ExternalClientsRequireSsl : True
InternalClientsRequireSsl : True
MetabasePath : IIS://EXCHSERV.domain.com/W3SVC/1/ROOT/Rpc
Path : D:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 15.0 (Build 775.38)
Server : EXCHSERV
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : Rpc (Default Web Site)
DistinguishedName : CN=Rpc (Default Web
Site),CN=HTTP,CN=Protocols,CN=EXCHSERV,CN=Servers,CN=Exchange Administrative
Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=domain,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domain,DC=com
Identity : EXCHSERV\Rpc (Default Web Site)
Guid : 596ed7a1-ceec-4a36-9cbc-617ac5214463
ObjectCategory : domain.com/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged : 12/23/2013 2:20:41 AM
WhenCreated : 11/25/2013 2:51:36 PM
WhenChangedUTC : 12/23/2013 7:20:41 AM
WhenCreatedUTC : 11/25/2013 7:51:36 PM
OrganizationId :
OriginatingServer : DOMAINCONTROLLER.domain.com
IsValid : True
ObjectState : Changed
Thanks in advance

Hi,
According to your description, users cannot connect to Exchange server 2013 both internal and external.
Please run Test E-mail AutoConfiguration in Outlook to check your autodiscover service. Also
reset your Exchange virtual directory to connect correctly. If the issue still continues after all configurations are setting properly, collect some Event logs would be helpful.
If there is any question, please post the results here for further analysis.
Thanks,
Winnie Liang
TechNet Community Support

Strange Exchange name when connecting with Outlook 2013 to Exchange server 2013 SP1

I've setup a test environment with Windows Server standard 2012 R2 and Exchange Server 2013 SP1...
In- and outbound SMTP works fine, as well as connecting with OWA and Mac Outlook client...
Oddly though when setting up an Outlook 2013 connection....it recognizes the email address correctly, but later on can't connect and shows a dialog to enter the server and email account manually....though the profiled fields show something like:
Exchange Server: [email protected]
Mailbox: =SMTP:[email protected]
When I fill in the right fields....it won't connect and falls back to the values above...
Something wrong in the Exchange setup?

Hmm...found aguide here:
http://enterpriseit.co/microsoft-exchange/2013/ssl-certificate-request/
Though it doesn't mention anything that with the self-signed certs it won't allow Outlook 2013 to connect...
So from my point of view Outlook 2013 should be able to connect anyway...as during the connect process you can install the self-signed cert.....so must be something else then...

Exchange Server 2013: Outook Clients and OWA keeps on disconnecting/connecting every 5-10 mins

We have a new exchange server 2013 installed but also has exchange 2007 up.
MX records are now pointing to the new exchange server, all were working ok after DNS records were changed but after the weekend it Outlook clients and OWA keeps on disconnecting and reconnecting from exchange.
Exchange 2013 CU6
Anybody else experienced the same?

hi Jheycie,
can you please check if you have .local and .com (different internal and external domain)
almost similar thread.. it worked for me
http://social.technet.microsoft.com/Forums/office/en-US/cc7d2300-0e1f-499f-a8f1-97f84687b6cc/emails-stuck-in-outlook-have-to-restart-transport-service?forum=exchangesvrgeneral
http://social.technet.microsoft.com/Forums/office/en-US/9b9bf607-f882-4f73-a7b2-611ace3f3115/users-unable-to-connect-to-exchange-unless-they-close-and-reopen-outlook?forum=exchangesvrgeneral
MARK AS USEFUL/ANSWER IF IT DID
Thanks
Happiness Always
Jatin

Exchange Server 2013 Service Pack Upgrade - Outlook connectivity issue

Hi,
After upgrading to Exchange Server 2013 service pack 1, we are unable to connect via Outlook 2010 or Outlook 2013. Outlook Web Access is working fine though. We have followed all the instructions, and have applied Outlook upgrades, but the issue remain the
same. Outlook was working fine before the upgrade.
Have we missed out something. I would highly appreciate if someone can help out? I'm not sure if this is the known issue as I can't seem to find anything on the internet.
Already applied the transport fix.
Thanks in advance!

Hi,
According to your description, your Outlook 2010 and Outlook 2013 come across the connectivity issue.
To narrow down the issue, I’d like to recommend the following troubleshooting:
1. Check if the issue happens on all Outlook users
2. Check the Outlook Anywhere connectivity by using ExRCA:
https://testconnectivity.microsoft.com/
Additionally, MAPI over HTTP is only supported when you use Outlook 2013 sp1 and Exchange 2013 sp1 at the same time. Since the issue also happens on Outlook 2010 client, we can firstly try the above troubleshooting.
If you have any question , please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Issues connecting Outlook 2011 for Mac to Exchange Server 2013

Could someone help me with the bellow please:
I have a Mac with outlook 2011 on it.
We have recently set up Exchange Server 2013, and all of the Windows Workstation just required the trusted root certificate to be installed and they were working.
However I have spent hours reading different forums trying to get this working on the Mac and no luck.
The auto discover does not work when setting up the exchange email, therefore I have also tried setting up manually but it still will not connect to the server.

Hi,
Please check if the links below help:
How the Autodiscover service works with Outlook for Mac 2011:
http://technet.microsoft.com/en-us/library/jj984202(v=office.14).aspx
A great tool for troubleshooting Autodiscover and Outlook 2011 for Mac connectivity issue:
http://blogs.technet.com/b/johnmak/archive/2012/04/01/a-great-tool-for-troubleshooting-autodiscover-and-outlook-2011-for-mac-connectivity-issue.aspx
Since this forum is for general questions and feedback related to Outlook for Windows, it's better to post your question to the forum for Exchange or for Mac:
Exchange forum:
http://social.technet.microsoft.com/Forums/exchange/en-US/home?category=exchangeserver
Office for Mac forum:
http://answers.microsoft.com/en-us/mac/forum/macoffice2011?tab=Threads
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly
can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Steve Fan
TechNet Community Support

Exchange Server 2013: Failed to connect. Winsock error code: 10060, Win32 error code: 10060.

Dear All,
I have exchange server 2013 running with windows server 2012.
My email server have been send and receive email with internal and external as normal.
Today, i got the problem the email cannot send out to external and get the error below:
Please comment.
BR,
Khemarin
[email protected]

Hi Khemarin,
If it is Smarthost, are you able to telnet your smarthost using 25 port number?
Also please check your Send Connector setting.
http://technet.microsoft.com/en-us/library/aa998662(v=exchg.150).aspx
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Outlook connection to exchange server problem

We have a new domain and an existing exchange server. The problem is if i log in with a local computer account i can autodiscover and connect in cached mode to exchange no problem. If i then login with a domain user account the same computer (tried on other
workstations) will fail to auto discover, fail to connect to exchange even with manual settings. I cant find anything obvious in Group policy.
The server is setup with the latest 2013 Group policy templates with office 2013 templates
Users not logged in with the new AD server can connect to exchange
Users not logged into the domain can access exchange server
My feeling is its a local setting that is missing or needs to be changed in Group Policy but i am at a loss as to what it could be
I have disabled roaming profiles too and it makes no difference.
Any help would be greatly appreciated.
Steve

Hi,
Sorry for my delay. According to your description, I summarize your issue to the following points:
1. No problem when the user logs in Outlook with a local computer account in Cached mode.
2. Can’t connect to Exchange from an cache mode enabled Outlook 2013 client when using a domain user account on the same computer automatically or manually.
3. Can connect to Exchange from an online mode enabled Outlook 2013 client when using a domain user account on the same computer automatically or manually.
It is right? If I misunderstand, please feel free to point it out. Additionally, I noticed that the server is setup with the latest 2013 Group policy templates with office 2013 templates. Please confirm
if the Outlook cache mode is disabled by OTC or GPO. If there is following registry key applied on the machine:
Software\Microsoft\Office\15.0\Outlook\Cached Mode
Meanwhile, please try to install an Outlook 2013 with a fresh ISO file(Don’t use any template such as OCT template), see if the Cached mode Outlook can connect to Exchange server.
Waiting for your updates.
Regards,
Winnie Liang
TechNet Community Support

Microsoft Exchange Server 2013 Cumulative Update 7 Setup - Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error - Set-SharedConfigDC

What am I trying to do?
I have tried installing Microsoft Exchange Server 2013 Cumulative Update 7 Setup on a fresh install of Windows Server 2012 R2 but it gets stuck when running the setup exe on Step 8 of 14 “Mailbox Transport Service” I have included full
error logs at the bottom of the page but the basics are in order it will throw which loop around are:
[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
Exchange is currently running in the envirmonet on 2010 Sp3 I am installing 2013 CU7 fresh so I can migrate the databases over.
What am I running?
2 X DC on domain and forest functional level 2008R2 both writable
1 X fresh install of Windows 2012 R2 which is domain joined
What have I tried?
Checked Ipv6 is enabled on all DC NICS and Existing Exchange Servers
Rebooted every server
Run setup as Administrator
My account is part of the domain Enterprise Admin group
Tried adding "Exchange Server" or "Exchange Enterprise Servers" to the group policy and doing the relevant gpupdate /force and reboot :
Computer Configuration Windows Settings
Security Settings + Local Policies
User Rights Assignment Mange auditing and security log
Turned off firewall on DC and Exchange Server even stopped the service
Turned off all AV on the DC and Exchange Server
Checked I could telnet to global catalog servers on port 3268 which I can
Checked the global catalog records existed in DNS which they all do
Done the obvious ping tests all round which confirms connectivity
Schema has been prepared using appropriate commands before running the setup exe
setup.exe /PrepareSchema /IacceptExchangeServerLicenseTerms
Making sure the following path has full permissions:
EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
Restarted Microsoft Exchange Active Directory Topology service
DcDiag all looks good
What have I noticed that is suspicious?
Microsoft Exchange Transport service will not start even though both of its dependences services have started:
Microsoft Filtering Management Service
Microsoft Exchange Active Directory Topology Service
It will eventually error with
“Windows could not start the Microsoft Exchange Transport Service on local computer
Error 1053: This Service did not respond to the start of control request in a timely fashion”
This error is from the GUI wizard itself:
Error:
The following error was generated when "$error.Clear();
$maxWait = New-TimeSpan -Minutes 8
$timeout = Get-Date;
$timeout = $timeout.Add($maxWait);
$currTime = Get-Date;
$successfullySetConfigDC = $false;
while($currTime -le $timeout)
$setSharedCDCErrors = @();
try
Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
$successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
if($successfullySetConfigDC)
break;
Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
catch
Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
Start-Sleep -Seconds 30;
$currTime = Get-Date;
if( -not $successfullySetConfigDC)
Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
" was run: "System.Exception: Unable to set shared config DC.
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Exchange logs which have been written:
**The error will loop around for 8 minutes on trying to set-sharedconfig DC whatever this is trying to do ??
[01/20/2015 17:13:20.0084] [2] Active Directory session settings for 'Set-SharedConfigDC' are: View Entire Forest: 'True', Configuration Domain Controller:mydomain.com', Preferred Global Catalog: 'mydomain.com', Preferred Domain Controllers:
'{ mydomain.com}'
[01/20/2015 17:13:20.0084] [2] User specified parameters:
-DomainController:mydomain.com' -ErrorVariable:'setSharedCDCErrors' -ErrorAction:'SilentlyContinue'
[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
[01/20/2015 17:13:20.0178] [2] Ending processing Set-SharedConfigDC
[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] An error ocurred while setting shared config DC. Error: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details
No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] Waiting 30 seconds before attempting again.
[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0195] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0288] [1] The following 1 error(s) occurred during task execution:
[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[01/20/2015 17:13:50.0288] [1] [ERROR] The following error was generated when "$error.Clear();
$maxWait = New-TimeSpan -Minutes 8
$timeout = Get-Date;
$timeout = $timeout.Add($maxWait);
$currTime = Get-Date;
$successfullySetConfigDC = $false;
while($currTime -le $timeout)
$setSharedCDCErrors = @();
try
Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
$successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
if($successfullySetConfigDC)
break;
Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
catch
Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
Start-Sleep -Seconds 30;
$currTime = Get-Date;
if( -not $successfullySetConfigDC)
Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
        " was run: "System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[01/20/2015 17:13:50.0288] [1] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___ee47ab1c06fb47919398e2e95ed99c6c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[01/20/2015 17:13:50.0288] [1] Setup is stopping now because of one or more critical errors.
[01/20/2015 17:13:50.0288] [1] Finished executing component tasks.
[01/20/2015 17:13:50.0304] [1] Ending processing Install-BridgeheadRole
Windows Event Viewer:
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=5276) Forest mydomain.com. Exchange Active Directory Provider couldn't find minimal required number of suitable Global Catalog servers
in either the local site 'Default-First-Site' or the following sites:

Hi apl228,
1. Please make sure the IPv6 is enabled.
2. Please make sure the account that install Exchange server has Administrator permission.
3. Please make sure DNS has been configured correctly.
Thanks
Mavis Huang
TechNet Community Support

Exchange Server 2013 - SChannel errors KB2992611

Hi,
At a customer we have Exchange 2013 setup on a Windows Server 2012 R2 virtual machine.
Last weekend we installed the latest patches and since then we are experiencing some errors regarding TLS. The System Eventlog is full of events from SChannel with ID 36887 saying: "A fatal alert received from the remote endpoint. The TLS Protocol defined
fatal alert code is 40."
When I search the internet I immediately found this topic: http://support2.microsoft.com/kb/2992611/en-us stating it had something to do with KB2992611 being installed.
This stated that I should download the update KB3018238. But I can't seem to download this KB for Windows Server 2012 R2. I searched the internet, the Microsoft Update Catalog, etc.
Any ideas on where I could find this KB for 2012 R2?
Many thanks in advance!
Best regards,
Bert

Hi,
Depending on my research, KB3018238 is for Windows Server 2008 R2 and Windows Server 2012. KB2992611 only add the new cipher suites to Windows Server 2008 R2 and Windows Server 2012. KB3018238 is used to remove the new cipher.
For your question, I want to double confirm whether client failed connect to Exchange server with error. Please post relevant error, it’s more helpful for further troubleshooting.
Please check if the cipher suits used by the server and client are matched. Besides, There have a few Schannel updates in the last couple months, for example KB3011780. We can install it in Windows Server 2012 R2 for test.
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

RV 220W connect to exchange server 2013

Similar Messages

Maybe you are looking for