Unable to start the IP server

Have an idea for a new feature? Voice your opinion here.
Post Reply
lewelby
Member
Posts: 4
Joined: Wed Sep 29, 2004 1:36 pm

Unable to start the IP server

Post by lewelby »

Hi,

Ive just downloaded and installed meedio Housebot.

But each time i tried to launch HouseBot it failed with the following error message.

"Assertion Failed

Trace Section 'System Monitor' generated an assertion, File:........

Unable to start the IP Server."



Marc
ScottBot
Site Admin
Posts: 2790
Joined: Thu Feb 13, 2003 6:46 pm
Location: Georgia (USA)
Contact:

Post by ScottBot »

What OS and version are you running it on?
Scott
lewelby
Member
Posts: 4
Joined: Wed Sep 29, 2004 1:36 pm

unable to start ip server

Post by lewelby »

OS: WinXP SP2

HouseBot version: 2.20



On the flash screen displaying all the initialisation step.

...

initializing devices

starting server

bin() failed with error 10048
ScottBot
Site Admin
Posts: 2790
Joined: Thu Feb 13, 2003 6:46 pm
Location: Georgia (USA)
Contact:

Post by ScottBot »

I've seen this problem when I have the "Application Layer Gateway Service" enabled. For me HouseBot would startup fine after a reboot, but then fail with the 10048 error. I disabled the Application Layer Gateway Service and it worked fine. I never did figure out exactly what the conflict was.



Check to see if you have that service running. If you have no need for it, just disable it.
Scott
lewelby
Member
Posts: 4
Joined: Wed Sep 29, 2004 1:36 pm

Post by lewelby »

I've stopped the service but problem is still here



10048 means Adr already in use but i have no server running on my machine except the windows default port.



:(
ScottBot
Site Admin
Posts: 2790
Joined: Thu Feb 13, 2003 6:46 pm
Location: Georgia (USA)
Contact:

Post by ScottBot »

Maybe another application is using the same port. The default port that is used between the HouseBot server and the Software Remote clients is 5009. You can specify a different port through Registry settings on the server and the SW Remotes. Search for "Software Remote Connection Port" in the online help and it will give you info on how to change it. Start with just changing the server port and see if that allows the server to start.
Scott
lewelby
Member
Posts: 4
Joined: Wed Sep 29, 2004 1:36 pm

Post by lewelby »

Ok, adding the registry entries and change default port to 9999 solve the problem



thks.
ScottBot
Site Admin
Posts: 2790
Joined: Thu Feb 13, 2003 6:46 pm
Location: Georgia (USA)
Contact:

Post by ScottBot »

I thought 5009 was an odd enough port number. I guess not anymore.



Don't forget that you will need to make the changes on any machines that are running the SWRemote also.
Scott
Post Reply