Lauchpad crashes everytime I launch game

[Celestian_]

<p>Recently it's started but everytime I launch EQ2 the launchpad will crash just as EQ2 is starting. Game continues to start but this crash window is getting annoying.</p><p>I run win7, 64bit.</p>

[TSR-DanielH]

<p>Greetings,</p><p>This issue usually happens when a firewall blocks the voiceservice process that loads into the background as the game starts.  Are you using any type of firewall on that computer?  If so please open the exception list for your firewall and delete any entries that contain the words Everquest 2, EQ2, Launchpad, or Voiceservice.  Then rerun the patcher(right click an run as administrator if using Windows 7 or Vista).  Whenever prompted make sure to select 'allow'.  That should refresh the firewall entries and will correct the problem in most cases.</p>

[Celestian_]

<p>Nope, no firewall.</p><p>This recently started happening within the last week. Before that it didn't have any problems.</p><p>I've used the voice chat in the launcher and in game as well.</p>

[Celestian_]

<p>I checked my configuration and noticed it has EQII and EQII Trial both as listed games to patch. I unselected the trial and applied. Seems for whatever reason that stops it from crashing when I close the launcher after I launch EQ2.</p>

[Falcone01]

<p>Celestian where did you find it?</p>

[Inphina]

<p><cite>TSR-DanielH wrote:</cite></p><blockquote><p>Greetings,</p><p>This issue usually happens when a firewall blocks the voiceservice process that loads into the background as the game starts.  Are you using any type of firewall on that computer?  If so please open the exception list for your firewall and delete any entries that contain the words Everquest 2, EQ2, Launchpad, or Voiceservice.  Then rerun the patcher(right click an run as administrator if using Windows 7 or Vista).  Whenever prompted make sure to select 'allow'.  That should refresh the firewall entries and will correct the problem in most cases.</p></blockquote><p>In most cases it appears the fault is not in the firewall at all. I say this because deleting the .dll file worked fine for me, and I've read read most imaginative solutions to the problem from the numerous topics concerning this issue, none of them being related to firewall.</p>

[TSR-DanielH]

<p><cite>Inphina@Splitpaw wrote:</cite></p><blockquote><p>In most cases it appears the fault is not in the firewall at all. I say this because deleting the .dll file worked fine for me, and I've read read most imaginative solutions to the problem from the numerous topics concerning this issue, none of them being related to firewall.</p></blockquote><p>The issue you're referring to is different than the one being discussed in this thread.  The dll file issue was a bug that should be corrected at this point.  The issue in this thread has been happening for a while and tends to be a firewall problem in most of the cases I've been involved with.</p>