Can't get Flash Builder 4.6 debugger to run

Question

I've tried everything, firewalls, reinstalling etc etc. I can't get the debugger to connect no matter what I do.

I'm just writing a simple Air application, with Flex and Actionscript. But any type of debugging on any type of application doesn't work. I get this message

The Flash Builder debugger failed to connect to the running application.

Then often when I try again, I get this message

Unrecognized Windows Sockets error: 0: JVM_Bind

Running the program without debugging works fine.

Solution 1

After spending way too much time on this and trying everything suggested and more, the solution unfortunately was to reformat the laptop and try again.

Thanks for everyone for their responses and efforts.

Solution 2

I believe this indicates that the tcp connection between ADL and Flash Builder could not be established using port 7935 because the socket is in use.

Use netstat to assure the port is not in use.

Solution 3

I hit the same situation, and resolve it with http://therush.wordpress.com/2008/03/11/resolved-flex-builder-3-debugger-stopped-working/

It seems a very strange bug. I solve it with:

1. Close FB4.6
2. Launch a Web Application HTML with Flash content (content must have been built with debug enabled)
3. Right click, select Debugger, Select "Localhost" (or "Other Machine", input 127.0.0.1), click Connect
4. Needn't care about if the connection is successful.
5. Close Browser, re-launch FB4.6, open your AIR application, Debug, -- the problem is gone.

Solution 4

I recently encountered the same issue in OSX. I resolved it by reinstalling the debugger version of flash player for mac, and changing the flash player browser to Safari in the Flex preferences.

Solution 5

I had the same issue. I'm using Google Chrome as my default browser, and although I had flash debugger installed (both IE and the "other browsers" version), I got this error.

I opened mozilla firefox and set that as default browser. Now I re-opened FB, and the error was gone.

I think this has to do with Google Chrome having flash build internally which might be slightly off.

View more solutions