none
Message routing problem. RRS feed

  • Question

  • I have two servers with Exchange 2007. Both of them are identical. Installed from one distributive, Exchange and OS. The first are virtual on HyperV, the second are phisical.

    First server has transport role, mailbox store role, client access role.

    Second has only mailbox store role.

    I have created mailbox on second server. But  i  can only recieve messages to this mailbox and can't send messages. The queue is empty. Message tracking can't find messages sent from this mailbox.

    In the event log:

    1009   MSExchangeMailSubmission

    The Microsoft Exchange Mail Send service is currently unable to contact the Hub Transport servers in the local Active Directory site. The servers may be busy and can not accept new connections.

    From Troubleshooting assistant:

    <Log Time = "10: 53: 56.991"> Error (The initializer of type "Microsoft.Exchange.Configuration.MonadDataProvider.ConnectionPool" threw an exception.) When trying to process the object get-ExchangeServer -Identity serv-mail -status -DomainController mail, object is skipped. </ Log>
    
    <Log Time = "10: 53: 59.335"> Error (The initializer of type "Microsoft.Exchange.Configuration.MonadDataProvider.ConnectionPool" threw an exception.) When an object is attempted to process the test-ServiceHealth -Server serv-mail object, the object is skipped. </ Log >
    
    <Log Time = "10: 53: 59.335"> Error (The initializer of type "Microsoft.Exchange.Configuration.MonadDataProvider.ConnectionPool" threw an exception.) When an object is attempted to handle the get-TransportConfig -DomainController mail object, the object is skipped. </ Log>
    
    <Log Time = "10: 53: 59.335"> Error (An initializer of the type "Microsoft.Exchange.Configuration.MonadDataProvider.ConnectionPool" issued an exception.) When an object is tried to process the get-ExchangeServer -Identity serv-mail -DomainController mail object, the object is skipped. </ Log>
    
    <Log Time = "10: 53: 59.335"> The Data acquisition phase has been completed. </ Log>
    
    <Log Time = "10: 54: 01.321"> Launching the Postprocessing phase of the rules. </ Log>
    
    <Log Time = "10: 54: 01.321"> The Postprocessing phase of the rules has been completed. </ Log>
    
    <Log Time = "10: 54: 01.337"> Run the Data Acquisition stage. </ Log>
    
    <Log Time = "10: 54: 01.399"> The Data acquisition phase has been completed. </ Log>
    
    <Log Time = "10: 54: 09.319"> Running the Postprocessing Rules step. </ Log>
    
    <Log Time = "10: 54: 09.319"> The Postprocessing phase of the rules has been completed. </ Log>
    
    <Log Time = "10: 54: 09.335"> Run the Data Acquisition stage. </ Log>
    
    <Log Time = "10: 54: 09.681"> Error (The initializer of the type "Microsoft.Exchange.Configuration.MonadDataProvider.ConnectionPool" issued an exception.) When trying to process the test-MapiConnectivity object -Server serv-mail -PerConnectionTimeout 120 -DomainController mail, the object is skipped. </ Log>
    
    <Log Time = "10: 54: 41.070"> Error (The initializer of type "Microsoft.Exchange.Configuration.MonadDataProvider.ConnectionPool" threw an exception.) When trying to process the object get-ExchangeServer -DomainController mail | where {$ _. IsHubTransportServer -and $ _. Site.ObjectGuid -eq '% varSiteGuid%'}, the object is skipped. </ Log>
    

    Tuesday, May 8, 2018 1:05 PM

All replies

  • Are all the services running on the first server?  Have you tried rebooting that server?

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Tuesday, May 8, 2018 11:20 PM
    Moderator
  • All services are running. I have reloaded all servers and domain controller too. Also setup.com /ps generating error "file not found".

    part of  setup log:

    [08.05.2018 16:36:46] [1] Processing component 'Resource Property Schema Component' (Обновление схемы свойств ресурса.).
    [08.05.2018 16:36:46] [1] Executing 'if($RoleUpdateResourcePropertySchema -and !(test-path $RoleResourcePropertySchemaSaveFile)) { get-resourceconfig -DomainController $RoleDomainController | export-clixml $RoleResourcePropertySchemaSaveFile }', handleError = False
    [08.05.2018 16:36:46] [2] Launching sub-task '$error.Clear(); if($RoleUpdateResourcePropertySchema -and !(test-path $RoleResourcePropertySchemaSaveFile)) { get-resourceconfig -DomainController $RoleDomainController | export-clixml $RoleResourcePropertySchemaSaveFile }'.
    [08.05.2018 16:36:46] [1] Executing 'if($RoleUpdateResourcePropertySchema) { set-resourceconfig -ResourcePropertySchema $null -DomainController $RoleDomainController }', handleError = False
    [08.05.2018 16:36:46] [2] Launching sub-task '$error.Clear(); if($RoleUpdateResourcePropertySchema) { set-resourceconfig -ResourcePropertySchema $null -DomainController $RoleDomainController }'.
    [08.05.2018 16:36:46] [1] Executing 'if($RoleUpdateResourcePropertySchema) { Install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\update_ResourcePropertySchema.ldf") }', handleError = False
    [08.05.2018 16:36:46] [2] Launching sub-task '$error.Clear(); if($RoleUpdateResourcePropertySchema) { Install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\update_ResourcePropertySchema.ldf") }'.
    [08.05.2018 16:36:46] [1] Executing 'if(test-path $RoleResourcePropertySchemaSaveFile) { $value = import-clixml $RoleResourcePropertySchemaSaveFile; set-resourceconfig -resourcepropertyschema $value.ResourcePropertySchema -DomainController $RoleDomainController }', handleError = False
    [08.05.2018 16:36:46] [2] Launching sub-task '$error.Clear(); if(test-path $RoleResourcePropertySchemaSaveFile) { $value = import-clixml $RoleResourcePropertySchemaSaveFile; set-resourceconfig -resourcepropertyschema $value.ResourcePropertySchema -DomainController $RoleDomainController }'.
    [08.05.2018 16:36:46] [1] Executing 'Remove-SetupFile -FilePath $RoleResourcePropertySchemaSaveFile', handleError = False
    [08.05.2018 16:36:46] [2] Launching sub-task '$error.Clear(); Remove-SetupFile -FilePath $RoleResourcePropertySchemaSaveFile'.
    [08.05.2018 16:36:46] [2] Beginning processing.
    [08.05.2018 16:36:46] [2] Removing temporary file 'C:\ExchangeSetupLogs\ResourcePropertySchema.xml'.
    [08.05.2018 16:36:46] [2] Ending processing.
    [08.05.2018 16:36:46] [1] Processing component 'Active Directory Schema' (Обновление схемы Active Directory).
    [08.05.2018 16:36:46] [1] Executing 'install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix + "schema0.ldf")', handleError = False
    [08.05.2018 16:36:46] [2] Launching sub-task '$error.Clear(); install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix + "schema0.ldf")'.
    [08.05.2018 16:36:46] [2] Beginning processing.
    [08.05.2018 16:36:46] [2] Running <C:\Windows\system32\ldifde.exe> with arguments <-i -s "srv.domain.local" -f "F:\Setup\ServerRoles\Common\Setup\Data\PostExchange2003_schema0.ldf" -j "C:\Users\user\AppData\Local\Temp" -c "<SchemaContainerDN>" "CN=Schema,CN=Configuration,DC=domain,DC=local">.
    [08.05.2018 16:36:46] [2] [WARNING] An unexpected error has occurred and debug information is being generated: Не удается найти указанный файл
    [08.05.2018 16:36:46] [2] [ERROR] Не удается найти указанный файл
    [08.05.2018 16:36:46] [1] Exception : System.Management.Automation.CmdletInvocationException: Не удается найти указанный файл ---> System.ComponentModel.Win32Exception: Не удается найти указанный файл
       в System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
       в System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
       в Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.RunProcess(String fileName, String arguments, WriteVerboseHandler writeVerbose)
       в Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.ImportSchemaFile(String schemaMasterServer, String schemaFilePath, String macroName, String macroValue, WriteVerboseHandler writeVerbose)
       в Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.InternalProcessRecord()
       в Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
       в System.Management.Automation.CommandProcessor.ProcessRecord()
       --- Конец трассировки внутреннего стека исключений ---
       в System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
       в System.Management.Automation.PipelineNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
       в System.Management.Automation.StatementListNode.ExecuteStatement(ParseTreeNode statement, Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
    [08.05.2018 16:36:46] [1] [WARNING] An unexpected error has occurred and debug information is being generated: Не удается найти указанный файл
    [08.05.2018 16:36:46] [1] [ERROR] Не удается найти указанный файл
    [08.05.2018 16:36:46] [1] [ERROR] Не удается найти указанный файл
    [08.05.2018 16:36:46] [1] [ERROR] Не удается найти указанный файл
    [08.05.2018 16:36:46] [1] [ERROR] Не удается найти указанный файл



    • Edited by hogust Thursday, May 10, 2018 8:17 AM
    Thursday, May 10, 2018 8:11 AM