I think this happened to me when there was something else running on the port. You can use netstat
to check what is running on ports in windows; follow this link for more on netstat. You will have to kill the process running on that port if it turns out to be the case.