Exchange 2013 CU 19 - Transport Service Issue

markodenev
markodenev used Ask the Experts™
on
We decided to upgrade to Exchange 2013 CU 19 from our Exchange 2010 Environment and introduced 1st Exchange 2013 C19 into the environment. However , emails are not flowing between our two environments [ i.e. between exchange 2010 and 2013]. OWA 2013 will say you dont have permission to perform this action , when test mailbox user on exchange 2013 mailbox database tries to send an email.

[ Exchange 2010 version is SP3 Rollup 9 and Exchange 2013 version is CU 19]

Exchange 2013 is multirole server and having issues with its transport service and it wont start. Attempt to restart it also results in failure.



We see this event EVENT 16023.

Microsoft Exchange couldn’t start transport agents. The Microsoft Exchange Transport service will be stopped. Exception details: Failed to create type ‘Microsoft.Exchange.MessagingPolicies.TransportRuleAgent.TransportRuleAgentFactory’ from assembly ‘C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Rule\Microsoft.Exchange.MessagingPolicies.TransportRuleAgent.dll’ due to error ‘Agent Transport Rule couldn’t load the rule collection.’. : Microsoft.Exchange.Data.ExchangeConfigurationException: Failed to create type ‘Microsoft.Exchange.MessagingPolicies.TransportRuleAgent.TransportRuleAgentFactory’ from assembly ‘C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Rule\Microsoft.Exchange.MessagingPolicies.TransportRuleAgent.dll’ due to error ‘Agent Transport Rule couldn’t load the rule collection.’. —> Microsoft.Exchange.Data.ExchangeConfigurationException: Agent Transport Rule couldn’t load the rule collection.
at Microsoft.Exchange.MessagingPolicies.TransportRuleAgent.TransportRuleAgentFactory..ctor()
— End of inner exception stack trace —
at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable.CreateAgentFactory(AgentInfo agentInfo)
at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable..ctor(IEnumerable agents, FactoryInitializer factoryInitializer)
at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.RuntimeSettings..ctor(MExConfiguration config, String agentGroup, FactoryInitializer factoryInitializer)
at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExRuntime.Initialize(String configFile, String agentGroup, ProcessTransportRole processTransportRole, String installPath, FactoryInitializer factoryInitializer)
at Microsoft.Exchange.Transport.Categorizer.MExEvents.Initialize(String configFilePath)
at Microsoft.Exchange.Transport.Components.CategorizerMExRuntimeLoader.Load()

Additional error in Exchange logs

EVENT ID 1052 Source MSEXCHANGE Extensibility

Failed to create agent factory for the agent 'Transport Rule Agent' with error 'Failed to create type 'Microsoft.Exchange.MessagingPolicies.TransportRuleAgent.TransportRuleAgentFactory' from assembly 'C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Rule\Microsoft.Exchange.MessagingPolicies.TransportRuleAgent.dll' due to error 'Agent Transport Rule couldn't load the rule collection.'.'. Please verify the corresponding transport agent assembly and dependencies with correct version are installed.

Can you please advise ?




Can you please advise ?

Thanks very much,
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Author

Commented:
Update :

If I disable built-in Transport Agent from Microsoft called "Transport Rule Agent" [ which by default has priority of 1 ] , I can start the transport service with out any issues.

So , I am not sure why fresh Install of Exchange will have issue with built-in transport agent - "Transport Rule Agent".

Can you please advise ?

Thanks very much,
Update :

One of our transport rules which was in up and working in exchange 2010 broke the transport service in Exchange 2013 which we recently introduced in our exchange environment.  Because of this transport rule , Transport rule agent was not able to load all transport rules and which in turn was breaking our Transport Service.

We have to delete that transport rule and after that we were able to start transport services on Exchange 2013 environment without any issues.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial