Listen port: An attempt was made to access a socket in a way

[Streamliner]

Hi,

I have a strange error when running Firefly under Windows 2003 SBS. It worked fine about a half a year ago, but now I get this message after uninstalling and reinstalling Firefly:

Log file: firefly.log

2007-01-26 00:45:21 (53b5fee7): Starting with debuglevel 0
2007-01-26 00:45:21 (53b5fee7): Starting rendezvous daemon
2007-01-26 00:45:21 (53b5fee7): Initializing database
2007-01-26 00:45:37 (53b5fee7): Starting web server from C:Program FilesFirefly Media Serveradmin-root on port 9999
2007-01-26 00:45:37 (53b5fee7): Listen port: An attempt was made to access a socket in a way forbidden by its access permissions.

2007-01-26 00:45:37 (53b5fee7): Error staring web server: An attempt was made to access a socket in a way forbidden by its access permissions.

2007-01-26 00:45:37: Aborting

Any help is greatly appreciated…..

Best Regards

Ryan

[rpedde]

@Streamliner wrote:

Hi,

I have a strange error when running Firefly under Windows 2003 SBS. It worked fine about a half a year ago, but now I get this message after uninstalling and reinstalling Firefly:

Log file: firefly.log

2007-01-26 00:45:21 (53b5fee7): Starting with debuglevel 0
2007-01-26 00:45:21 (53b5fee7): Starting rendezvous daemon
2007-01-26 00:45:21 (53b5fee7): Initializing database
2007-01-26 00:45:37 (53b5fee7): Starting web server from C:Program FilesFirefly Media Serveradmin-root on port 9999
2007-01-26 00:45:37 (53b5fee7): Listen port: An attempt was made to access a socket in a way forbidden by its access permissions.

2007-01-26 00:45:37 (53b5fee7): Error staring web server: An attempt was made to access a socket in a way forbidden by its access permissions.

2007-01-26 00:45:37: Aborting

Any help is greatly appreciated…..

Best Regards

Ryan

That’s WSAEACCESS:

Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4 SP4 or later), another application, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4 SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option.

Sounds like there is something else running on 9999. Maybe changing the port to something other than 9999 will help. Should be able to do that from the tray applet.

– Ron

[Streamliner]

Yup that did it. I assigned pot 9990 and everything works fine now… btw. I had Itunes running on one of the logged in users, which most probably blocked port 9999. I have uninstalled itunes…

Thank you verry much for your help

Ryan

[Author]

Posts