Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

i keep getting flancy.start() is being used by another process #42

Open
dotps1 opened this issue Aug 2, 2016 · 3 comments
Open

i keep getting flancy.start() is being used by another process #42

dotps1 opened this issue Aug 2, 2016 · 3 comments

Comments

@dotps1
Copy link

dotps1 commented Aug 2, 2016

this is super annoying everytime I try to use New-Flancy

The process cannot access the file because it is being used by another process
At C:\Users\dotps1\Documents\WindowsPowerShell\Modules\flancy\flancy.psm1:450 char:9
+         $flancy.start()
+         ~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], HttpListenerException
    + FullyQualifiedErrorId : HttpListenerException
@dotps1
Copy link
Author

dotps1 commented Aug 3, 2016

so, this seemed to be an issue with the example of port 8001, once I changed that, it works. Is there some way to maybe test for the port and if its use, throw a useful error, because a file in use error was not helpful lol.

@toenuff
Copy link
Owner

toenuff commented Aug 9, 2016

yeah poor error

@Tiberriver256
Copy link

@toenuff looks like you have this fixed in the devel branch? I'm getting this for the current error:

Failed to listen on prefix 'http://localhost:8001/' because it conflicts with an existing registration on the machine.
At C:\Users\tiber\Documents\GitHub\flancy\flancy.psm1:450 char:9
+         $flancy.start()
+         ~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], HttpListenerException
    + FullyQualifiedErrorId : HttpListenerException

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants