# MPI Integer Limit Error

**URL:** https://discourse.paraview.org/t/mpi-integer-limit-error/7709
**Category:** ParaView Support
**Created:** [July 28, 2021, 8:31am UTC](https://discourse.paraview.org/t/mpi-integer-limit-error/7709 "2021-07-28T08:31:08Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 6, 2021, 12:56pm UTC](https://discourse.paraview.org/t/mpi-integer-limit-error/7709/7 "2021-10-06T12:56:49Z")

</div>

> [@lockan](#):
>
> The latest release doesn’t even have AutoMPI enabled

The discussion about removal happened here:

> [@Remove AutoMPI?](https://discourse.paraview.org/t/remove-autompi/7952):
>
> AutoMPI is a boolean setting in ParaView that, when enabled, launches a server process with mpiexec when the ParaView client runs, then the client connects to that server. It was created as a convenient way to enable parallelism in ParaView back when most VTK algorithms were not multithreaded. These days, many VTK/ParaView filters are multithreaded to run on multiple cores, and this is usually faster than running separate MPI processes for parallelization of serial algorithms. Should we remove …

> Also in 5.9.1 and 5.10 when you try and set up a localhost client server you can’t enter a command into the server setup dialog without ParaView instantly crashing…on both Windows and Linux.

This issue has been fixed already in master and will not be present in ParaView 5.10

> I had to write an external batch/bash script to start a server and automatically connect to it. The files then read in successfully.

You can write a .pvsc file instead

---

_[View the full topic](https://discourse.paraview.org/t/mpi-integer-limit-error/7709)._