Can't get Flash Builder 4.6 debugger to run

12
votes

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.

Initial Error

Then often when I try again, I get this message

Unrecognized Windows Sockets error: 0: JVM_Bind

Secondary Error

Running the program without debugging works fine.

10
flashapache-flexdebuggingairflash-builder
Do you have a different version of the Java runtime in your path, ahead of Flash Builder's JVM? – Jason Sturges
Not really sure, I echo'd %path% and I have no jvm in there. Where should I be looking? – Dale Fraser
Silly question, but assuming you have the debug Flash player installed? :) – Sunil D.
I do, but perhaps I'll remove it and reinstall, I downloaded all the versions that made sense, though, its an AIR app so I wasnt clear which I needed. – Dale Fraser
Since this is an AIR App, you shouldn't need the Flash Player Debugger. I added the "AIR" tag tot his question. But, have no idea what the cause is; I've never had problems w/ AIR. – JeffryHouser

10 Answers

4
votes

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.

4
votes

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.
3
votes

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.

enter image description here

1
votes

EDIT:

I found something.

The guy at this link Unrecognized Windows Sockets error: 0: JVM_Bind in Flash Builder has a workaround. Problem is you have to do it everytime. He suggests using TCPView to see and close opened connections that are using the same port as the debugger.

People in this thread http://forums.adobe.com/message/653125 also notes that an old version of NOD32 was causing the problem.

ORIGNAL ANSWER :

The second error you get clearly indicate a problem with the Java Virutal Machine (JVM). I don't think it's project related at all.

Try checking out installed JREs (Java runtime environments) in Flash Builder.

Window -> Preferences -> Java - > Installed JREs

Check if there's anything strange here, like unknown JREs. You should use "Adobe Flash Builder 4.6", typically located at "C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6". If it's not here add it (Add, Next, paste corresponding path) and restart Flash Builder.

If it's already there, you might want to redownload Flex 4.6 SDK and replace your current one (typically located at "C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks").

It's unclear if you have uninstalled Flash Builder or not but if that's not the case and the above solutions doesn't work I'd considered reinstalling it from scratch.

1
votes

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.

1
votes

If your default browser is Chrome, you must set the default Flash plugin before debugger starts to work.

  • In Chrome goto address: chrome://plugins/
  • Click the [+]Details button at the right top side of the list.
  • Find the Adobe Flash Player from the plugins list and disable internal ones.
0
votes

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.

0
votes

I was going absolutely nuts dealing with this and what one of the members above said worked for me. Close FB, then set Firefox as your default browser open FB, change the debugger preferences to Default browser, then try debugging again, that did it for me. I'm running FB 4.6 with firefox 17.01

0
votes

I've closed chrome web browser. Then I can execute the debugger without that msg. I suspect some tab used that port.

0
votes

Happened to me just now, it happened after closing a debug Air app right after it launched. I had to restart the pc, problem solved.