Send connector created on exchange 2013 with 2010 coexistence does not function (Network Steve Forum)

Send connector created on exchange 2013 with 2010 coexistence does not function

I need to know what happened with this connector, i put all the permissions on my smart host same as MBX 2010, but not function.

i prove sending with a telnet through Exchange MBX and result message is:

451 4.7.0 Temporary server error. Please try again later. PRX1

March 17th, 2015 8:27am

If the 2013 server is reporting that error, check available disk space, all exch services are running ( test-servicehealth) and 2013 server components are all active ( get-servercomponentstate <server>)

Free Windows Admin Tool Kit Click here and download it now

March 17th, 2015 8:47am

>get-servercomponentstate EXCH01.contoso.com

Server Component State
------ --------- -----
EXCH01.contoso.com ServerWideOffline Inactive
EXCH01.contoso.com HubTransport Inactive
EXCH01.contoso.com FrontendTransport Inactive
EXCH01.contoso.com Monitoring Inactive
EXCH01.contoso.com RecoveryActionsEnabled Inactive
EXCH01.contoso.com AutoDiscoverProxy Inactive
EXCH01.contoso.com ActiveSyncProxy Inactive
EXCH01.contoso.com EcpProxy Inactive
EXCH01.contoso.com EwsProxy Inactive
EXCH01.contoso.com ImapProxy Inactive
EXCH01.contoso.com OabProxy Inactive
EXCH01.contoso.com OwaProxy Inactive
EXCH01.contoso.com PopProxy Inactive
EXCH01.contoso.com PushNotificationsProxy Inactive
EXCH01.contoso.com RpsProxy Inactive
EXCH01.contoso.com RwsProxy Inactive
EXCH01.contoso.com RpcProxy Inactive
EXCH01.contoso.com UMCallRouter Inactive
EXCH01.contoso.com XropProxy Inactive
EXCH01.contoso.com HttpProxyAvailabilityGroup Inactive
EXCH01.contoso.com ForwardSyncDaemon Inactive
EXCH01.contoso.com ProvisioningRps Inactive
EXCH01.contoso.com MapiProxy Inactive
EXCH01.contoso.com EdgeTransport Inactive

[PS] C:\Windows\system32>test-servicehealth

Role : Mailbox Server Role
RequiredServicesRunning : True
ServicesRunning : {IISAdmin, MSExchangeADTopology, MSExchangeDelivery, MSExchangeIS,
MSExchangeMailboxAssistants, MSExchangeRepl, MSExchangeRPC, MSExchangeServiceHost,
MSExchangeSubmission, MSExchangeThrottling, MSExchangeTransportLogSearch, W3Svc, WinRM}
ServicesNotRunning : {}

Role : Client Access Server Role
RequiredServicesRunning : True
ServicesRunning : {IISAdmin, MSExchangeADTopology, MSExchangeMailboxReplication, MSExchangeRPC,
MSExchangeServiceHost, W3Svc, WinRM}
ServicesNotRunning : {}

Role : Unified Messaging Server Role
RequiredServicesRunning : True
ServicesRunning : {IISAdmin, MSExchangeADTopology, MSExchangeServiceHost, MSExchangeUM, W3Svc, WinRM}
ServicesNotRunning : {}

Role : Hub Transport Server Role
RequiredServicesRunning : True
ServicesRunning : {IISAdmin, MSExchangeADTopology, MSExchangeEdgeSync, MSExchangeServiceHost,
MSExchangeTransport, MSExchangeTransportLogSearch, W3Svc, WinRM}
ServicesNotRunning : {}

Edited by DavDove 17 hours 55 minutes ago

March 17th, 2015 9:14am

>get-servercomponentstate EXCH01.contoso.com

Edited by DavDove Tuesday, March 17, 2015 1:27 PM

Free Windows Admin Tool Kit Click here and download it now

March 17th, 2015 1:12pm

Looks like this server has a bunch disabled. Specifically for this issue:

EXCH01.contoso.com HubTransport Inactive
EXCH01.contoso.com FrontendTransport Inactive

See about enabling those:

http://blogs.technet.com/b/exchange/archive/2013/09/26/server-component-states-in-exchange-2013.aspx

If all else fails you can delete the registry entries as described in the article above.

March 17th, 2015 7:00pm

Hi,

As Andy suggested, please use the cmdlet below to set the Server Components to an active state and check the result.

Set-ServerComponentState -Component xxx -Identity EXCH01.contoso.com -State Active

For your reference:

https://technet.microsoft.com/en-us/library/jj218699%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

Hope this can be helpful to you.

Best regards,

Free Windows Admin Tool Kit Click here and download it now

March 18th, 2015 3:05am

Both of you help me,

doing this:

the Get-ServerComponentState cmdlet from the Shell to retrieve these settings:

$scs = Get-ServerComponentState -Identity SERVERNAME -component ServerWideOffline

$scs.Localstates

then this command to activate

Set-ServerComponentState -Identity SERVERNAME -component ServerWideOffline -State Active -Requeter functional

thanks

Let me know , why this happens because i have had installed exchange 2013 for new.

Edited by DavDove 9 hours 1 minutes ago

March 19th, 2015 6:25pm

This topic is archived. No further replies will be accepted.