It is expected as per your configuration.  Have aem configured with context root then have SetHandler dispatcher-handler configured to that path rather than route.

You can't change & even if you do so upgrade or sp or hotfix installation overwrites it.  Instead create your own bundle & don;t interfere with OOB.  If you have requirements to use same selector etc then still create your own bundle and  make use of service ranking to get your implementation called...

http://docs.adobe.com/docs/en/aem/6-0/administer/integration/marketing-cloud/campaign.html

Unfortunately have to uninstall one by one. In case you have organized well & to clean folder use crx explorer or crxde to delete parent node. You can use automaize using curl.  In any case file a daycare request so that enhancement request can be tracked.

Randy Thomas wrote... Sham HC wrote... Make sure in dispatcher.any form section1)    Renderers are defined2)    The value in rendere section are valid.  Especially if server has multiple ip & host.3)    Firewalls rules for connection between dispatcher & publishers.   This is all on a one test...

Make sure in dispatcher.any form section1)    Renderers are defined2)    The value in rendere section are valid.  Especially if server has multiple ip & host.3)    Firewalls rules for connection between dispatcher & publishers.

Sounds like you have higher version of oak installed prior to sp2. Need some history of instance. File daycare with all the logs & list of hotfix installed prior to sp2. ALso mention if you are using nosample content.  If qualified will file bug & get it fixed.

Verify the pom.xml import package.

remove-type launcher rules should support for nt:file & not seen any issue reported so far.  File a support case to investigate and as an workaround you can implement listeners.

error indicates a overload or slow-repository.  Don't think it is related to live copy. File an official support request to investigate