That error makes it sound like something else is already running on tcp port 22022 on the server. On the server, go to a command line and run ' netstat -aon | find "":22022"" ', and the last column that spits out will be the PID of the task that's using that port. Then you can open Task Manager, Processes tab, click View \ Select Columns... and check PID (Process Identifier). Then you should be able to find the task that's blocking you.