# Windows Service Memory Limitations version 6.1.1

**URL:** <https://discuss.elastic.co/t/windows-service-memory-limitations-version-6-1-1/113351>\
**Category:** Elasticsearch\
**Created:** [December 27, 2017, 7:11pm UTC](https://discuss.elastic.co/t/windows-service-memory-limitations-version-6-1-1/113351 "2017-12-27T19:11:27Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![tiago.ramalho](https://avatars.discourse-cdn.com/v4/letter/t/4491bb/32.png) [@tiago.ramalho](https://discuss.elastic.co/u/tiago.ramalho)\
**Post date:** [December 27, 2017, 7:11pm UTC](https://discuss.elastic.co/t/windows-service-memory-limitations-version-6-1-1/113351/1 "2017-12-27T19:11:28Z")

</div>

Hi there,

The question is probably pretty obvious but I just can’t find it… After installing the windows service (both the msi and zip, via sc.exe) I can’t just the jvm.options to anything above -Xmx1G… If I do (-Xmx4G, for instance) the service will not start with an unhandled exception thing… What is happening here.

Tks in advance...

BR,  
T

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [December 27, 2017, 8:19pm UTC](https://discuss.elastic.co/t/windows-service-memory-limitations-version-6-1-1/113351/2 "2017-12-27T20:19:55Z")

</div>

Please post the error.

---

<div class="post-metadata">

**Author:** ![tiago.ramalho](https://avatars.discourse-cdn.com/v4/letter/t/4491bb/32.png) [@tiago.ramalho](https://discuss.elastic.co/u/tiago.ramalho)\
**Post date:** [December 28, 2017, 12:18am UTC](https://discuss.elastic.co/t/windows-service-memory-limitations-version-6-1-1/113351/3 "2017-12-28T00:18:10Z")

</div>

Fast reply 🙂 taken from event viewer...

"The Elasticsearch service terminated unexpectedly. "

"Faulting application name: elasticsearch.exe, version: 6.1.1.0, time stamp: 0x5a36e874  
Faulting module name: KERNELBASE.dll, version: 6.3.9600.18340, time stamp: 0x57366075  
Exception code: 0xe0434352  
Fault offset: 0x0000000000008a5c  
Faulting process id: 0x1470  
Faulting application start time: 0x01d37f710480462b  
Faulting application path: C:\Program Files\Elastic\Elasticsearch\6.1.1\bin\elasticsearch.exe  
Faulting module path: C:\Windows\system32\KERNELBASE.dll  
Report Id: 424bd642-eb64-11e7-80d0-000d3a26fdfc  
Faulting package full name:  
Faulting package-relative application ID: "

"Application: elasticsearch.exe  
Framework Version: v4.0.30319  
Description: The process was terminated due to an unhandled exception.  
Exception Info: Elastic.ProcessHosts.Process.StartupException  
at Elastic.ProcessHosts.Process.ProcessBase.HandleException(System.Exception)  
at System.Reactive.ObserverBase`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].OnError(System.Exception) at System.Reactive.Observer`1[[System.\_\_Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].OnError(System.Exception)  
at System.Reactive.Linq.ObservableImpl.AsObservable`1+_[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].OnError(System.Exception) at System.Reactive.AutoDetachObserver`1[[System.\_\_Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].OnErrorCore(System.Exception)  
at System.Reactive.ObserverBase`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].OnError(System.Exception) at Elastic.ProcessHosts.Process.ObservableProcess+<>c__DisplayClass22_0.<CreateProcessExitSubscription>b__0(System.Reactive.EventPattern`1\<System.Object\>)  
at System.Reactive.AnonymousSafeObserver`1[[System.\_\_Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].OnNext(System.\_\_Canon)  
at System.EventHandler.Invoke(System.Object, System.EventArgs)  
at System.Diagnostics.Process.OnExited()  
at System.Diagnostics.Process.RaiseOnExited()  
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)  
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)  
at System.Threading.\_ThreadPoolWaitOrTimerCallback.PerformWaitOrTimerCallback(System.Object, Boolean)"

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [December 28, 2017, 2:36am UTC](https://discuss.elastic.co/t/windows-service-memory-limitations-version-6-1-1/113351/4 "2017-12-28T02:36:40Z")

</div>

Is there anything in the Elasticsearch logs?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [December 28, 2017, 4:10am UTC](https://discuss.elastic.co/t/windows-service-memory-limitations-version-6-1-1/113351/5 "2017-12-28T04:10:17Z")

</div>

Are you using a 64-bit version of Windows?

---

<div class="post-metadata">

**Author:** ![tiago.ramalho](https://avatars.discourse-cdn.com/v4/letter/t/4491bb/32.png) [@tiago.ramalho](https://discuss.elastic.co/u/tiago.ramalho)\
**Post date:** [December 28, 2017, 11:16am UTC](https://discuss.elastic.co/t/windows-service-memory-limitations-version-6-1-1/113351/6 "2017-12-28T11:16:01Z")

</div>

Yes, 64 bit, a VM on Azure running Windows Server 2012 R2.  
The logs shows nothing relevant.  
"stopping ...  
stopped  
closing ...  
closed"

---

<div class="post-metadata">

**Author:** ![tiago.ramalho](https://avatars.discourse-cdn.com/v4/letter/t/4491bb/32.png) [@tiago.ramalho](https://discuss.elastic.co/u/tiago.ramalho)\
**Post date:** [January 11, 2018, 4:11pm UTC](https://discuss.elastic.co/t/windows-service-memory-limitations-version-6-1-1/113351/7 "2018-01-11T16:11:31Z")

</div>

I finally found the solution. It’s very simple, just install the Server JRE (Java SE Runtime Environment) and config your ES to use it. And that’s it.

---

<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 8, 2018, 4:11pm UTC](https://discuss.elastic.co/t/windows-service-memory-limitations-version-6-1-1/113351/8 "2018-02-08T16:11:46Z")

</div>

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