# Mapping Error in Kibana 5.6.x **URL:** \ **Category:** Kibana\ **Created:** [September 21, 2017, 2:48pm UTC](https://discuss.elastic.co/t/mapping-error-in-kibana-5-6-x/101356 "2017-09-21T14:48:14Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![RdrgPorto](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rdrgporto/32/13278_2.png) [@RdrgPorto](https://discuss.elastic.co/u/RdrgPorto)\ **Post date:** [September 21, 2017, 2:48pm UTC](https://discuss.elastic.co/t/mapping-error-in-kibana-5-6-x/101356/1 "2017-09-21T14:48:14Z")
Hi everyone, We have a problem after an upgrade from **Elasticsearch** and **Kibana 5.4.2** to **5.6.0**. We updated kibana index in order to have compatibility with **Elastic 6.x** by the new utility in **Kibana**. After that, we got the next exception: > [2017-09-21T16:37:07,992][DEBUG][o.e.a.a.i.m.p.TransportPutMappingAction] [name\_machine] failed to put mappings on indices [[[.kibana-6/txg1pewhRB-OTDp4\_c6Uew]]], type [url] > java.lang.IllegalArgumentException: [url] is defined as a field in mapping [url] but this name is already used for an object in other types We tried to upgrade **5.6.1** and the same problem happens. **Kibana** doesn't work however **Elastic** seems fine. ![Screenshot-2017-9-21 Kibana](https://us1.discourse-cdn.com/elastic/original/3X/9/e/9ed6fb83e3e03f7014b9e7f36fc594ca1f8f4702.png) Any idea? Thanks in advance ---
**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\ **Post date:** [September 21, 2017, 5:05pm UTC](https://discuss.elastic.co/t/mapping-error-in-kibana-5-6-x/101356/2 "2017-09-21T17:05:10Z")
There is an issue where the original Kibana index was created without dynamic mapping disabled. This breaks the compatibility fallback. We're currently working on a fix for this you would be able to run. Apologies for any inconvenience. ---
**Author:** ![RdrgPorto](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rdrgporto/32/13278_2.png) [@RdrgPorto](https://discuss.elastic.co/u/RdrgPorto)\ **Post date:** [September 21, 2017, 6:48pm UTC](https://discuss.elastic.co/t/mapping-error-in-kibana-5-6-x/101356/3 "2017-09-21T18:48:34Z")
Hi Tyler, Thanks for your answer 🙂. Is there any way to fix it easily? Thanks in advance, Regards ---
**Author:** ![1004lisa](https://avatars.discourse-cdn.com/v4/letter/1/2bfe46/32.png) [@1004lisa](https://discuss.elastic.co/u/1004lisa)\ **Post date:** [September 22, 2017, 6:29am UTC](https://discuss.elastic.co/t/mapping-error-in-kibana-5-6-x/101356/4 "2017-09-22T06:29:54Z")
I also occurred this error. you must upgrade to 5.6.1 and fix it refer below url > [@Upgrade issue with Elastic Stack 5.6.0, workaround option until fix is available](https://discuss.elastic.co/t/upgrade-issue-with-elastic-stack-5-6-0-workaround-option-until-fix-is-available/100595): > > Since the release of Elastic Stack 5.6.0, we’ve discovered an issue during the upgrade process to this version. Who is affected Anyone upgrading a cluster that has indexes created with Elasticsearch 2.x or prior. This does not affect users installing a fresh 5.6 cluster nor those who started their Elastic journey with the 5.x releases. Symptom The problem is most visible through Kibana. After attempting to login to Kibana post-upgrade, the following error appears: ---
**Author:** ![RdrgPorto](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rdrgporto/32/13278_2.png) [@RdrgPorto](https://discuss.elastic.co/u/RdrgPorto)\ **Post date:** [September 22, 2017, 6:43am UTC](https://discuss.elastic.co/t/mapping-error-in-kibana-5-6-x/101356/5 "2017-09-22T06:43:49Z")
Hi Park, We upgraded to **Elasticsearch** and **Kibana 5.6.1** and this kind of error continues. Moreover, in the post which you sent me, **Benpoizin** has the same error (at the end of the post). Regards ---
**Author:** ![benpolzin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benpolzin/32/12408_2.png) [@benpolzin](https://discuss.elastic.co/u/benpolzin)\ **Post date:** [September 22, 2017, 4:43pm UTC](https://discuss.elastic.co/t/mapping-error-in-kibana-5-6-x/101356/6 "2017-09-22T16:43:36Z")
Thanks, @RdrgPorto. My updated/detailed post is [over here.](https://discuss.elastic.co/t/kibana-5-6-1-remote-transport-exception/101408). But it's the exact same issue you describe in this thread. @tsmalley, any ETA on the fix? I'd like to get this in before the weekend. ---
**Author:** ![benpolzin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benpolzin/32/12408_2.png) [@benpolzin](https://discuss.elastic.co/u/benpolzin)\ **Post date:** [September 23, 2017, 1:26am UTC](https://discuss.elastic.co/t/mapping-error-in-kibana-5-6-x/101356/7 "2017-09-23T01:26:58Z")
Fixed mine using the instructions in [this thread](https://discuss.elastic.co/t/kibana-5-6-1-remote-transport-exception/101408/2?u=benpolzin). ---
**Author:** ![RdrgPorto](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rdrgporto/32/13278_2.png) [@RdrgPorto](https://discuss.elastic.co/u/RdrgPorto)\ **Post date:** [September 25, 2017, 6:18am UTC](https://discuss.elastic.co/t/mapping-error-in-kibana-5-6-x/101356/8 "2017-09-25T06:18:16Z")
Hi, Thanks Ben 😄 , Regards ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 23, 2017, 6:18am UTC](https://discuss.elastic.co/t/mapping-error-in-kibana-5-6-x/101356/9 "2017-10-23T06:18:52Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.