RejectedSoftware Forums

Sign up

Can't build example

I am using Windows 7 (do not have admin rights if it's help)

After putting stuff in index.dt and app.d I am running DUB and get next errors: http://codepad.org/E2UBUI7S

Re: Can't build example

On Wed, 05 Feb 2014 13:10:45 GMT, Suliman wrote:

I am using Windows 7 (do not have admin rights if it's help)

After putting stuff in index.dt and app.d I am running DUB and get next errors: http://codepad.org/E2UBUI7S

Hm... look like issue was with missing package json.

Would server work without admin right?

I am getting error:
Running appname.exe
Failed to listen on :::8080
Failed to listen on 0.0.0.0:8080

Re: Can't build example

Am 05.02.2014 14:17, schrieb Suliman:

On Wed, 05 Feb 2014 13:10:45 GMT, Suliman wrote:

I am using Windows 7 (do not have admin rights if it's help)

After putting stuff in index.dt and app.d I am running DUB and get next errors: http://codepad.org/E2UBUI7S

Hm... look like issue was with missing package json.

Would server work without admin right?

I am getting error:
Running appname.exe
Failed to listen on :::8080
Failed to listen on 0.0.0.0:8080

It should be able to listen on ports >= 1024 without admin rights. Does
running netstat -an | findstr 8080 return anything that is already
listening on that port?

Re: Can't build example

It should be able to listen on ports >= 1024 without admin rights. Does
running netstat -an | findstr 8080 return anything that is already
listening on that port?

netstat -an | findstr 8080
TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING
TCP 192.168.1.120:51309 213.208.129.126:8080 ESTABLISHED
TCP [::]:8080 [::]:0 LISTENING

Re: Can't build example

On Thu, 06 Feb 2014 05:31:45 GMT, Suliman wrote:

It should be able to listen on ports >= 1024 without admin rights. Does
running netstat -an | findstr 8080 return anything that is already
listening on that port?

netstat -an | findstr 8080
TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING
TCP 192.168.1.120:51309 213.208.129.126:8080 ESTABLISHED
TCP [::]:8080 [::]:0 LISTENING

Okay so that means some process is already listening on that port, so either changing the port to somthing else or killing that process should make it work (netstat -anb | findstr 8080 run from an admin command prompt should show the process name).