FAQ's - APPX Software, Inc.: Message; "can't bind local address"

APPX is the Premier Development and Runtime Environment for Business Application Software

	FAQ's - APPX Software, Inc. : APPX Utility : APPX Runtime Environment : Runtime Messages : Message; "can't bind local address"
	Something on your server already has the port you specified in the "-s=" argument, open. Causes: 1. A lingering copy of WinAppxD. Check to make sure no copies of WinAppxD are listed in Task Manager. This may occur if you Start and Stop the WinAppxD service using Control Panel, or if you run WinAppxD from the command line during troubleshooting. If you see any rogue WinAppxD's, kill them and try again. 2. Some other (non-APPX) application wants to use the port you specified in the "-s=" argument for WinAppxD during installation. There is no completely reliable way to detect this. If you are getting the "can't bind" error and are sure it's not due to an extra WinAppxD process running, this is probably what has happened. Since WinAppxD can't use a port claimed by another application, go back and edit the registry, choosing a different port number for the WinAppxD service. For example, try 8061 instead of 8060. Reboot, and try again.
	[Append to This Answer]
	2004-Apr-01 1:13pm

Previous:	Message; "can't open stream socket"
Next:	Message; "op_prt_buf, print new page failed"

	[Search]	[Appearance]
This is a Faq-O-Matic 2.719.