# Couldn't Start Elastic Search on a Remote Machine Windows-32 Bit

**URL:** <https://discuss.elastic.co/t/couldnt-start-elastic-search-on-a-remote-machine-windows-32-bit/71022>\
**Category:** Elasticsearch\
**Created:** [January 10, 2017, 5:42am UTC](https://discuss.elastic.co/t/couldnt-start-elastic-search-on-a-remote-machine-windows-32-bit/71022 "2017-01-10T05:42:39Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![prakash1243](https://avatars.discourse-cdn.com/v4/letter/p/35a633/32.png) [@prakash1243](https://discuss.elastic.co/u/prakash1243)\
**Post date:** [January 10, 2017, 5:42am UTC](https://discuss.elastic.co/t/couldnt-start-elastic-search-on-a-remote-machine-windows-32-bit/71022/1 "2017-01-10T05:42:39Z")

</div>

Hi-  
I wanted to host the Elastic Search on a Windows-7 machine which is installed with 32-bit.  
I could able to install the elastic search service, but when I start it, its throwing a error message. I've attached the screenshots below:

 ![](https://us1.discourse-cdn.com/elastic/original/2X/a/ae9130bccf166f330b3224accf7632fe2bda0505.png)

I've just noticed the logs, it has updated with "  
2017-01-10 07:13:27 Commons Daemon procrun stdout initialized  
Error occurred during initialization of VM  
Could not reserve enough space for 2097152KB object heap  
"

Please let me know, how do I resolve this issue. Thanks !

---

<div class="post-metadata">

**Author:** ![wenpos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wenpos/32/15326_2.png) [@wenpos](https://discuss.elastic.co/u/wenpos)\
**Post date:** [January 10, 2017, 8:14am UTC](https://discuss.elastic.co/t/couldnt-start-elastic-search-on-a-remote-machine-windows-32-bit/71022/2 "2017-01-10T08:14:49Z")

</div>

how about your machine system resource, CPUs or Memory,. the provided info indicates ES cannot allocate enough heap memory， while the default configuration are -Xms2g -Xmx2g. OR you may change this parameters to smaller.

---

<div class="post-metadata">

**Author:** ![prakash1243](https://avatars.discourse-cdn.com/v4/letter/p/35a633/32.png) [@prakash1243](https://discuss.elastic.co/u/prakash1243)\
**Post date:** [January 10, 2017, 9:00am UTC](https://discuss.elastic.co/t/couldnt-start-elastic-search-on-a-remote-machine-windows-32-bit/71022/3 "2017-01-10T09:00:45Z")

</div>

Hi @wenpos

Thanks for your reply.  
I've changed the Java Heap size in (Control Panel-\> Programe-\> Java) path as the default size and also tried increasing to -Xms512m and also with -Xms3072m, which didn't work out.

Could you please help me out.

My VM Windows Configuration Is:

Windows-7 32 Bit  
C: Driver of 80 GB  
RAM: 4GB

---

<div class="post-metadata">

**Author:** ![wenpos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wenpos/32/15326_2.png) [@wenpos](https://discuss.elastic.co/u/wenpos)\
**Post date:** [January 10, 2017, 9:17am UTC](https://discuss.elastic.co/t/couldnt-start-elastic-search-on-a-remote-machine-windows-32-bit/71022/4 "2017-01-10T09:17:30Z")

</div>

@prakash1243 change the ES JVM default configuration -Xms2g -Xmx2g to -Xms1g -Xmx1g ,or more smaller, have a try , the configuration file in $ES\_HOME/config/jvm.options

---

<div class="post-metadata">

**Author:** ![prakash1243](https://avatars.discourse-cdn.com/v4/letter/p/35a633/32.png) [@prakash1243](https://discuss.elastic.co/u/prakash1243)\
**Post date:** [January 10, 2017, 10:35am UTC](https://discuss.elastic.co/t/couldnt-start-elastic-search-on-a-remote-machine-windows-32-bit/71022/5 "2017-01-10T10:35:54Z")

</div>

Thank you very much, @wenpos

---

<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 7, 2017, 10:36am UTC](https://discuss.elastic.co/t/couldnt-start-elastic-search-on-a-remote-machine-windows-32-bit/71022/6 "2017-02-07T10:36:25Z")

</div>

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