# 'A socket error occurred' on startup in 4.9.2

**URL:** <https://qa.fmod.com/t/a-socket-error-occurred-on-startup-in-4-9-2/12150>\
**Category:** Unreal Engine\
**Created:** [November 13, 2015, 9:23am UTC](https://qa.fmod.com/t/a-socket-error-occurred-on-startup-in-4-9-2/12150 "2015-11-13T09:23:02Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![geoff](https://avatars.discourse-cdn.com/v4/letter/g/a3d4f5/32.png) [@geoff](https://qa.fmod.com/u/geoff)\
**Post date:** [November 16, 2015, 12:51am UTC](https://qa.fmod.com/t/a-socket-error-occurred-on-startup-in-4-9-2/12150/2 "2015-11-16T00:51:41Z")

</div>

If you are running client and server at the same time the live update won’t be able to create a socket for live update. If you don’t have a separate client/server, you might still get the error if some other program is holding on to the same port that FMOD tries to use.

There are a few things you can do:

- Disable live update in the settings
- Add -noliveupdate or -nosound to the command line to disable either live update or the entire sound system.
- If the server is dedicated, it should already be running with the equivalent of -nosound so that should just work.
- You can tweak whether live update is enabled by changing ini files manually, for example if you are already changing ini file settings by hand.

---

_[View the full topic](https://qa.fmod.com/t/a-socket-error-occurred-on-startup-in-4-9-2/12150)._