# Import Dashboard: fail to set the mapping **URL:** \ **Category:** Beats\ **Tags:** winlogbeat\ **Created:** [February 16, 2017, 8:59pm UTC](https://discuss.elastic.co/t/import-dashboard-fail-to-set-the-mapping/75397 "2017-02-16T20:59:24Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![JB\_ELK](https://avatars.discourse-cdn.com/v4/letter/j/73ab20/32.png) [@JB\_ELK](https://discuss.elastic.co/u/JB_ELK)\ **Post date:** [February 16, 2017, 8:59pm UTC](https://discuss.elastic.co/t/import-dashboard-fail-to-set-the-mapping/75397/1 "2017-02-16T20:59:24Z")
I have an endpoint host OS running Winlogbeat and a VMworkstation hosting my ELK stack. I am testing and getting the dashboards is the last step I have. Need help with the script import. PS C:\Program Files\winlogbeat\> curl [http://192.168.124.128:9200/?pretty](http://192.168.124.128:9200/?pretty) { "name" : "Oneg the Prober", "cluster\_name" : "elasticsearch", "version" : { "number" : "2.3.5", "build\_hash" : "90f439ff60a3c0f497f91663701e64ccd01edbb4", "build\_timestamp" : "2016-07-27T10:36:52Z", "build\_snapshot" : false, "lucene\_version" : "5.5.0" }, "tagline" : "You Know, for Search" } PS C:\Program Files\winlogbeat\> PS C:\Program Files\winlogbeat\> PS C:\Program Files\winlogbeat\> scripts\import\_dashboards.exe -es [http://192.168.124.128:9200](http://192.168.124.128:9200) fail to set the mapping. Error: 400 Bad Request Create temporary directory C:\Users\jbanacj\AppData\Local\Temp\tmp660014183 Downloading [https://artifacts.elastic.co/downloads/beats/beats-dashboards/beats-dashboards-5.2.1.zip](https://artifacts.elastic.co/downloads/beats/beats-dashboards/beats-dashboards-5.2.1.zip) fail to download file: [https://artifacts.elastic.co/downloads/beats/beats-dashboards/beats-dashboards-5.2.1.zip](https://artifacts.elastic.co/downloads/beats/beats-dashboards/beats-dashboards-5.2.1.zip) PS C:\Program Files\winlogbeat\> Debug File: [2017-02-16 20:56:12,545][DEBUG][action.admin.indices.create] [Oneg the Prober] [winlogbeat-2017.02.16] failed to create MapperParsingException[Failed to parse mapping [_default_]: No handler for type [keyword] declared on field [related\_activity\_id]]; nested: MapperParsingException[No handler for type [keyword] declared on field [related\_activity\_id]]; at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService$1.execute(MetaDataCreateIndexService.java:320) at org.elasticsearch.cluster.ClusterStateUpdateTask.execute(ClusterStateUpdateTask.java:45) at org.elasticsearch.cluster.service.InternalClusterService.runTasksForExecutor(InternalClusterService.java:468) at org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.run(InternalClusterService.java:772) at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:231) at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:194) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: MapperParsingException[No handler for type [keyword] declared on field [related\_activity\_id]] at org.elasticsearch.index.mapper.object.ObjectMapper$TypeParser.parseProperties(ObjectMapper.java:303) at org.elasticsearch.index.mapper.object.ObjectMapper$TypeParser.parseObjectOrDocumentTypeProperties(ObjectMapper.java:218) at org.elasticsearch.index.mapper.object.RootObjectMapper$TypeParser.parse(RootObjectMapper.java:139) at org.elasticsearch.index.mapper.DocumentMapperParser.parse(DocumentMapperParser.java:118) at org.elasticsearch.index.mapper.DocumentMapperParser.parse(DocumentMapperParser.java:99) at org.elasticsearch.index.mapper.DocumentMapperParser.parse(DocumentMapperParser.java:85) at org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:269) at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService$1.execute(MetaDataCreateIndexService.java:317) ... 8 more ---
**Author:** ![JB\_ELK](https://avatars.discourse-cdn.com/v4/letter/j/73ab20/32.png) [@JB\_ELK](https://discuss.elastic.co/u/JB_ELK)\ **Post date:** [February 17, 2017, 4:08pm UTC](https://discuss.elastic.co/t/import-dashboard-fail-to-set-the-mapping/75397/2 "2017-02-17T16:08:50Z")
I found a work around by going to [https://github.com/elastic/beats-dashboards](https://github.com/elastic/beats-dashboards) and downloading dashboards and installing with, # Windows .\load.ps1 -url "[http://localhost:9200](http://localhost:9200)" method. > **[elastic/beats-dashboards](https://github.com/elastic/beats-dashboards)** > > beats-dashboards - DEPRECATED. Moved to https://github.com/elastic/beats. Please use the new repository to add new issues. Download Zip Installation To load the dashboards, execute the script pointing to the Elasticsearch HTTP URL: ``` # Unix ./load.sh -url "http://localhost:9200" # Windows .\load.ps1 -url "http://localhost:9200" ``` If you want to use HTTP authentication for Elasticsearch, you can specify the credentials as a second parameter: ``` # Unix ./load.sh -url "http://localhost:9200" -user "admin:secret" # Windows .\load.ps1 -url "http://localhost:9200" -user "admin:secret" ``` ---
**Author:** ![Exocomp](https://avatars.discourse-cdn.com/v4/letter/e/ea5d25/32.png) [@Exocomp](https://discuss.elastic.co/u/Exocomp)\ **Post date:** [March 12, 2017, 11:36pm UTC](https://discuss.elastic.co/t/import-dashboard-fail-to-set-the-mapping/75397/3 "2017-03-12T23:36:12Z")
I ran into the same issue, I filed a bug at [https://github.com/elastic/beats/issues/3740](https://github.com/elastic/beats/issues/3740) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 9, 2017, 11:36pm UTC](https://discuss.elastic.co/t/import-dashboard-fail-to-set-the-mapping/75397/4 "2017-04-09T23:36:34Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.