NServiceBus : Error messages does not appear in Error queue - ForwarderFaultManager does not start - ravendb

Question

I am running NServiceBus 5.2.14 with NServiceBus.Host 6.0.0
I am using MSMQ as transport and RavenDBPersistence.
All queues appear in computer management except for the error queue.
Everything functions fine for messages and endpoints. Errors are retried 5 times as they should. However after retrying 5 times they do not appear in the error queue.
I have specified the error queue in as such:
<MessageForwardingInCaseOfFaultConfig ErrorQueue="error" />
and included in configSections:
<section name="MessageForwardingInCaseOfFaultConfig" type="NServiceBus.Config.MessageForwardingInCaseOfFaultConfig, NServiceBus.Core" />
Edit1: app.config:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
<section name="UnicastBusConfig" type="NServiceBus.Config.UnicastBusConfig, NServiceBus.Core" />
<section name="TransportConfig" type="NServiceBus.Config.TransportConfig, NServiceBus.Core" />
<section name="MessageForwardingInCaseOfFaultConfig" type="NServiceBus.Config.MessageForwardingInCaseOfFaultConfig, NServiceBus.Core" />
</configSections>
<TransportConfig MaximumConcurrencyLevel="5" MaxRetries="5" />
<MessageForwardingInCaseOfFaultConfig ErrorQueue="error" />
<UnicastBusConfig ForwardReceivedMessagesTo="audit">
<MessageEndpointMappings>
...
</MessageEndpointMappings>
</UnicastBusConfig>
...
Edit2 : endpointconfig:
public class EndpointConfig : IConfigureThisEndpoint, AsA_Server
{
...
public void Customize(BusConfiguration busConfiguration)
{
...
var containerFactory = new ContainerFactory();
Container.InitializeContainer(containerFactory);
AutoMapperInitializer.Configure();
busConfiguration.AssembliesToScan(AllAssemblies.Matching("NServiceBus").And("OurProjectName."));
busConfiguration.UseTransport<MsmqTransport>();
busConfiguration.EndpointName(ConfigurationManager.AppSettings["InputQueueName"]);
busConfiguration.UseContainer<WindsorBuilder>(customizations => customizations.ExistingContainer(Container.Instance));
busConfiguration.UsePersistence<RavenDBPersistence>();
busConfiguration.EnableCriticalTimePerformanceCounter();
busConfiguration.RegisterComponents(components => { components.ConfigureComponent<UsernameForwarder>(DependencyLifecycle.InstancePerCall); });
...
}
}
I run the endpoints in self-hosting console. In the list of FEATURES I see this:
Name: ForwarderFaultManager
Version: 5.2.14
Enabled by Default: Yes
Status: Disabled
Deactivation reason: Did not meet one of the dependencies:
Name: InMemoryFaultManager
Version: 5.2.14
Enabled by Default: No
Status: Enabled
Dependencies: None
Startup Tasks: None
I suspect my problem is with the ForwarderFaultManager, however there is nothing listed in the missing dependencies list. What may I be missing? Where could I start looking?