# Couldn't create report for search

**URL:** <https://discuss.elastic.co/t/couldnt-create-report-for-search/164486>\
**Category:** Kibana\
**Tags:** elastic-stack-reporting\
**Created:** [January 16, 2019, 2:53pm UTC](https://discuss.elastic.co/t/couldnt-create-report-for-search/164486 "2019-01-16T14:53:39Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [January 16, 2019, 2:53pm UTC](https://discuss.elastic.co/t/couldnt-create-report-for-search/164486/1 "2019-01-16T14:53:39Z")

</div>

Hello,

I followed [X-Pack reporting settings in Kibana | Kibana User Guide [6.5] | Elastic](https://www.elastic.co/guide/en/kibana/current/reporting-settings-kb.html), yet while trying to generate report, I get following message:

> "Couldn't create report for search 'test'"
> 
> Error: Failed to decrypt report job data.  
> Please ensure that xpack.reporting.encryptionKey is set and re-generate this report.

`xpack.reporting.encryptionKey` _IS_ set:

```
sh-4.2$ export | egrep 'XPACK_REPORTING'
export XPACK_REPORTING_ENABLED="true"
export XPACK_REPORTING_ENCRYPTIONKEY="X"
sh-4.2$ 

```

Please advise.

---

<div class="post-metadata">

**Author:** ![timroes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timroes/32/19712_2.png) [@timroes](https://discuss.elastic.co/u/timroes)\
**Post date:** [January 16, 2019, 3:20pm UTC](https://discuss.elastic.co/t/couldnt-create-report-for-search/164486/2 "2019-01-16T15:20:52Z")

</div>

@tsullivan or @joelgriffith could one of you help out on this? Thanks.

---

<div class="post-metadata">

**Author:** ![joelgriffith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joelgriffith/32/53738_2.png) [@joelgriffith](https://discuss.elastic.co/u/joelgriffith)\
**Post date:** [January 16, 2019, 6:34pm UTC](https://discuss.elastic.co/t/couldnt-create-report-for-search/164486/3 "2019-01-16T18:34:55Z")

</div>

@alexus do you happen to know if the instances share the same reporting index? We've found that if all kibana instances use different indexes there can be issues with how reporting works:

**Multiple `kibana.index` settings across Kibana instances** : if each instance a unique `kibana.index` setting but has the _same_ xpack.reporting.index setting, it's possible that workers can claim a job that they aren't able to fulfill. The job will contain references to saved objects that the instance doesn't have in its own `kibana.index` .

- _Solution_ : With different `kibana.index` settings across Kibana instances connected to the same Elasticsearch cluster, you _must_ also configure a different `xpack.reporting.index` setting per each unique `kibana.index`

This assumes you have a few instances running (which I'm not sure if you do). It'd also be good to see your other env variables just to know more about the environment itself.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 13, 2019, 6:35pm UTC](https://discuss.elastic.co/t/couldnt-create-report-for-search/164486/4 "2019-02-13T18:35:15Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.