# \[SOLVED\] New installation gives error
**URL:** https://discuss.elastic.co/t/solved-new-installation-gives-error/209220
**Category:** Beats
**Tags:** heartbeat
**Created:** [November 25, 2019, 5:14am UTC](https://discuss.elastic.co/t/solved-new-installation-gives-error/209220 "2019-11-25T05:14:51Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@ericv](https://discuss.elastic.co/u/ericv)
#### Post date: [November 25, 2019, 5:14am UTC](https://discuss.elastic.co/t/solved-new-installation-gives-error/209220/1 "2019-11-25T05:14:52Z")
Hi,
I just installed heartbeat-elastic on a Linux node, already have filebeat, metricbeat and packagebeat running on my entire cluster.
Heartbeat is throwing me, what I believe is an error, when I run 'heartbeat setup':
`Exiting: resource 'heartbeat-7.4.2' exists, but it is not an alias`
Now it seems that an index is created, but I don't see anything coming in on the Uptime board, no monitors are shown.
How can I either clean up everything and start from scratch to verify I did it all the correct way?
Or... How can I fix what's missing.
I would expect the heartbeat package to behave the same way as the other ones, but I don't have a dashboard created nor anything for example.
Any help is greatly appreciated.
BTW, I'm using ES Cloud.
Kind regards,
Eric V.
---
### Author:  [@ericv](https://discuss.elastic.co/u/ericv)
#### Post date: [November 25, 2019, 8:13am UTC](https://discuss.elastic.co/t/solved-new-installation-gives-error/209220/2 "2019-11-25T08:13:01Z")
Problem solved, I found to clean up everything on the cloud instance and restarted the service works.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 23, 2019, 8:13am UTC](https://discuss.elastic.co/t/solved-new-installation-gives-error/209220/3 "2019-12-23T08:13:07Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.