Application Error: Unable to listen on port 31234

[Chanz]

Hi Shane,

I've got a problem with the ID v1.3 BETA (build 91).
I'm using 2 Notebooks with Windows 7.
I got one new and installed a fresh Windows 7 Professional.
The old Notebook is using Windows 7 Home Premium OEM.
Both are using the ServicePack 1.
Latest updates etc.
I'm using the new notebook with Windows 7 Professional as slave.

Now when I start the Windows 7 Professional Notebook and login to
Windows, InputDirector starts and giving me the following Error
(screenshot on my server)
http://bcserv.eu/chanz/input%20director%20error.png

After shutting down InputDirector I can control my slave again or I
need to restart the slave then its working sometimes too.

Thanks for helping.

Regs,
Chanz

[Shane]

On May 20, 5:37 am, Chanz <gits2...@arcor.de> wrote:
> Hi Shane,
>
> I've got a problem with the ID v1.3 BETA (build 91).
> I'm using 2 Notebooks with Windows 7.
> I got one new and installed a fresh Windows 7 Professional.
> The old Notebook is using Windows 7 Home Premium OEM.
> Both are using the ServicePack 1.
> Latest updates etc.
> I'm using the new notebook with Windows 7 Professional as slave.
>
> Now when I start the Windows 7 Professional Notebook and login to
> Windows, InputDirector starts and giving me the following Error

> (screenshot on my server)http://bcserv.eu/chanz/input%20director%20error.png

>
> After shutting down InputDirector I can control my slave again or I
> need to restart the slave then its working sometimes too.
>

Hi Chanz,

If you change the port to a different number - does the error still
happen with the new number?

Regs,

Shane.

[Chanz]

Even with different ports this error shows up.
But restarting ID 3 times solves it somehow.
So the error shows up 2 times and the third time it just works.

I looked at netstat -ab while the error occur, but I can't find any
port that could have blocked ID from taking it.

[Shane]

On May 24, 8:12 pm, Chanz <gits2...@arcor.de> wrote:

>
> Even with different ports this error shows up.
> But restarting ID 3 times solves it somehow.
> So the error shows up 2 times and the third time it just works.
>
> I looked at netstat -ab while the error occur, but I can't find any
> port that could have blocked ID from taking it.

Hi Chanz,

Input Director swaps which process is listening on the port from its
service to the application during the startup process.

Can you have a look in the Windows Event log for Input Director errors
and see if its logging any?

Regs,

Shane.

[Chanz]

Hi Shane,

unfortunately there isn't anything in the windows logs.

I found out that when I transit with the mouse without the main ID is
running and then starting ID it kicks me once out, but then its
working.

Regs,
Chanz

[George Lewis]

I had a similar issue and ended up setting "Input Director Service" to Automatic-Delayed Start.   Then I removed the startup command "inputdirector.exe /hide" from my user's startup commands, and made it a task that triggers on login instead.   I have that task set to delay 60 seconds.   I never get the "Unable to listen on port 31234" error anymore.

This never used to happen on my PC before, but I'm guessing that either the SSD I added is causing services to start too fast for input director, or my cablecard tuner (which operates on it's own internal network) is causing some sort of confusion for the input director services.   Either way, I'm a happy camper now.

[Christopher Roge]

I only had to set the Input Director service to delayed-start as George says here, I did not need to make any other changes to clear the port 31234 error.

Chris