Having an issue after one of the servers in our DAG crashed this morning. 2 servers in DAG clients connect with outlook 2010 all clients are showing as disconnected, in Connection Status no servers are listed. I can create a new profile and autodiscover works, but when trying to open that new profile there is ano error opening (cannot read ost file) which i think means it cannot see the exchange. getting this in event viewer on one server: Microsoft Exchange could not find a certificate that contains the domain name mail.domain.co.uk in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector Internet Mail with a FQDN parameter of mail.domain.co.uk. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key. if i run that it says do i want to replace the certificate already assigned . . . would this be causing the issue? if not where can i look to solve this?

Hi The error you have found is unrelated to this issue. Is the RCPClientAccess service running on the mailbox servers? Do you load balance your MAPI connections, if so can you check that that mechanism is working correctly? Steve

I cant find that service listed in services.msc should it be there? I think that clients are directed using their local dns settings.

The full name of the service is Microsoft Exchange RPC Client Access and this should be on all servers with the CAS role installed. Do you have the CAS role installed on separate servers from your DAG members, if so how many CASs do you have?

we have 3 servers, 2 exchange in DAG and 1 sql server, as far as i can see none have the RPC client access on them

OK, could you paste these two commands into the Exchange Management Shell and reply with the output? Could you run the first one on both DAG members. Get-Service *rpc* Get-ExchangeServer | fl name,serverrole,admindisplayversion,edition

here is from one DAG member: [PS] C:\Windows\system32>Get-Service *rpc* Status Name DisplayName ------ ---- ----------- Running BackupExecRPCSe... Backup Exec Server Running MSExchangeRPC Microsoft Exchange RPC Client Access Running RpcEptMapper RPC Endpoint Mapper Stopped RPCHTTPLBS RPC/HTTP Load Balancing Service Stopped RpcLocator Remote Procedure Call (RPC) Locator Running RpcSs Remote Procedure Call (RPC) [PS] C:\Windows\system32>Get-ExchangeServer | fl name,serverrole,admindisplayversion,edition Name : MIDSERVER ServerRole : Mailbox, ClientAccess, HubTransport AdminDisplayVersion : Version 14.1 (Build 218.15) Edition : Standard Name : MAINSERVER ServerRole : Mailbox, ClientAccess, HubTransport AdminDisplayVersion : Version 14.1 (Build 218.15) Edition : Standard and from second DAG member: [PS] C:\Windows\system32>Get-Service *rpc* Status Name DisplayName ------ ---- ----------- Running BackupExecRPCSe... Backup Exec Server Stopped MSExchangeRPC Microsoft Exchange RPC Client Access Running RpcEptMapper RPC Endpoint Mapper Stopped RPCHTTPLBS RPC/HTTP Load Balancing Service Stopped RpcLocator Remote Procedure Call (RPC) Locator Running RpcSs Remote Procedure Call (RPC)

>> Stopped MSExchangeRPC Microsoft Exchange RPC Client Access That's on your second DAG member. Could you run this command on that server: Start-Service MSExchangeRPC -Verbose

sorry late answer, allaying managers fears. have run that command on server2

If that service started successfully does that allow your clients to connect now?

here is the output: [PS] C:\Windows\system32>Start-Service MSExchangeRPC -Verbose VERBOSE: Performing operation "Start-Service" on Target "Microsoft Exchange RPC Client Access (MSExchangeRPC)". WARNING: Waiting for service 'Microsoft Exchange RPC Client Access (MSExchangeRPC)' to finish starting... [PS] C:\Windows\system32>

and it has made the test pc i've been using showing as connected to exchange!! Will run a test on a selection of other machines and see how it looks!

Thanks Steve! saved my bacon! Very good to have you on hand for quick answers.

No worries, glad you got it working.