(07-20-2015, 09:23 AM)'parg' Wrote: So it looks as if something on your system is already listening on the port that Vuze uses to communicate with other instances of itself - are you sure there isn't a Vuze already running?
If you are sure that there isn't then please try starting Vuze in the same way but add the following BEFORE the org.gudy.azureus2.ui.swt.Main
-Dazureus.instance.port=<random number between 1025 and 65535>
that will cause Vuze to try and listen on another port.
Alternatively, do the same but instead of -Dazureus.instance.port-... use
-DMULTI_INSTANCE=true
Hi parg! Many, many thanks for your latest reply..... but.... my brain cell is not quite up to coping with the instructions you give. I am SO sorry to be a dunce! I have installed an alternative to Vuze as it just all ........ became......... too.... much! I HOPE you don't feel I have wasted your time and perhaps your advice may help others with the same problem I had. Many thanks once again.
07-20-2015, 02:01 PM (This post was last modified: 07-21-2015, 03:17 AM by warspite.)
sodam\ dateline='\'1437409893' Wrote:
parg\ dateline='\'1437409380' Wrote: So it looks as if something on your system is already listening on the port that Vuze uses to communicate with other instances of itself - are you sure there isn't a Vuze already running?
If you are sure that there isn't then please try starting Vuze in the same way but add the following BEFORE the org.gudy.azureus2.ui.swt.Main
-Dazureus.instance.port=<random number between 1025 and 65535>
that will cause Vuze to try and listen on another port.
Alternatively, do the same but instead of -Dazureus.instance.port-... use
-DMULTI_INSTANCE=true
Hi parg! Many, many thanks for your latest reply..... but.... my brain cell is not quite up to coping with the instructions you give. I am SO sorry to be a dunce! I have installed an alternative to Vuze as it just all ........ became......... too.... much! I HOPE you don't feel I have wasted your time and perhaps your advice may help others with the same problem I had. Many thanks once again.
You have to enter this code from Parg in CMD,
Code:
cd "C:\Program Files\Vuze"
and then use the code that he provided in his second reply.
Alternatively, you can paste both lines into notepad and save it as a .bat file, this file can then be used to start Vuze without the need of copy and pasting in CMD.
I just did this myself (I have the same problem as you), and it DID in fact start up now. (You WILL have to keep the CMD window open though, othwise Vuze will shut down)
Only problem is, that I can't just open a magnet link or torrent file, but have to use the "File>Open>Torrent file..." tab in Vuze.
For now, it's an okay emergency fix. But if anyone has a more permanet solution, please share it with us.
I have been following this post for the past couple days. Like Sodam - and, I am sure, others - I found that Vuze suddenly refused to open just after Windows 7 installed the last critical update. The logical conclusion would be that there was something in the last update that is now interfering with Vuze. Hopefully some enterprising techie will take that into account and look at producing a patch. In the meantime, does anyone have any idea what in the update has caused the issue and any suggestions on how to get around it?
I am on the verge of defecting to another torrent client myself, but I would like to give Vuze one more chance - it has always worked so well in the past. I would appreciate any help.
Ok, well I did as you suggested and more things happened but sadly not the loading of Vuze. Seems like progress though... hopefully getting closer to resolving this.
Two things stood out, the line 'This is BAD - fix me!' and an unsatisfied link error 'Cannot load 32-bit SWT libraries on 64-bit JVM. That last one is weird as I copied over the swt file with the 64 bit one from a link in an earlier suggestion.
I discovered Vuze Leap today and decided to try it. Interestingly, it worked perfectly well. Why would it work, while my old Vuze still refuses to open? Aside from the obvious bells & whistles that are missing from Leap, which is much more stripped down, what is different that allows it to open?
I ddi see that suggestion earlier in this thread, and I checked it immediately; both Vuze and Java were 64-bit versions. And, like others who have been writing about this issue, I also went through a series of uninstall-install of both Vuze and Java, each time ensuring that both were 64-bit. It still didn't help.
So, while I appreciate your suggestion, since that doesn't appear to have been the issue for a number of people who, like me, encountered this problem immediately after a Windows update, are any there any other new suggestions that might help - presumably ones that relate to what appears to be the cause of the problem: the last Windows update.
You could look for the swt.jar that is in the Vuze folder and open it using something like winzip or 7-zip (the .jar file format is basically a .zip file)
If you have a 64-bit swt.jar it will contain (amongst other things) a file called swt-win32-4508.dll with size 644,096 bytes.
For a 32-bit swt.jar the same file is 438,272 bytes
If it looks like you have a 64-bit swt.jar then perhaps you could delete the swt.jar and run Vuze to verify that it is actually that swt.jar file that is being used (i.e. deleting it should cause a different error message to be produced when Vuze fails)
I'm leaning towards it being another application taking over port 6880 (which is what Vuze uses to check if it's already running).
Try this instead
Code:
cd "C:\Program Files (x86)\Vuze"
azureus -console
or (cd "C:\Program Files\Vuze")
If it says "StartSocket: passing startup args to already-running Azureus java process listening on [127.0.0.1: 6880]" then it thinks vuze is already running.
To find out what's already using that port, use "Resource Monitor" (Start->type "Resource Monitor", run it), open the Network Tab, expand "Listening Ports", sort by Port and find the one that has 6880. Should look something like this:
Hopefully the name (Image column) will be helpful in determining what app to close.
-Tux
(07-21-2015, 12:06 PM)eam2 Wrote: No, that isn't the problem.
I ddi see that suggestion earlier in this thread, and I checked it immediately; both Vuze and Java were 64-bit versions. And, like others who have been writing about this issue, I also went through a series of uninstall-install of both Vuze and Java, each time ensuring that both were 64-bit. It still didn't help.
So, while I appreciate your suggestion, since that doesn't appear to have been the issue for a number of people who, like me, encountered this problem immediately after a Windows update, are any there any other new suggestions that might help - presumably ones that relate to what appears to be the cause of the problem: the last Windows update.
(07-22-2015, 10:19 PM)'ArronM' Wrote: I'm leaning towards it being another application taking over port 6880 (which is what Vuze uses to check if it's already running).
Try this instead
Code:
cd "C:\Program Files (x86)\Vuze"
azureus -console
or (cd "C:\Program Files\Vuze")
If it says "StartSocket: passing startup args to already-running Azureus java process listening on [127.0.0.1: 6880]" then it thinks vuze is already running.
To find out what's already using that port, use "Resource Monitor" (Start->type "Resource Monitor", run it), open the Network Tab, expand "Listening Ports", sort by Port and find the one that has 6880. Should look something like this:
Hopefully the name (Image column) will be helpful in determining what app to close.
-Tux
(07-21-2015, 12:06 PM)'eam2' Wrote: No, that isn't the problem.
I ddi see that suggestion earlier in this thread, and I checked it immediately; both Vuze and Java were 64-bit versions. And, like others who have been writing about this issue, I also went through a series of uninstall-install of both Vuze and Java, each time ensuring that both were 64-bit. It still didn't help.
So, while I appreciate your suggestion, since that doesn't appear to have been the issue for a number of people who, like me, encountered this problem immediately after a Windows update, are any there any other new suggestions that might help - presumably ones that relate to what appears to be the cause of the problem: the last Windows update.
Thanks for your help.
You ripper!
It was Hola runing on the same port that Vuze wanted. A swift uninstall of Hola and Vuze opens and runs perfectly fine. Many, many, many thanks to all of you who have offered up advice and guidance to resolve this for me (and hopefully others). Case closed.
WOW! You guys really are superstars. Seeing as I'm the one that started all this.... I thought I should let you know that I have been watching this thread even after I had given up all hope. I checked in today and saw the last post regarding Hola. I thought I'd give it a whirl and......... abracadabra! Fantastic. I have only one question left, now that I have my beloved Vuze up and running again.
Why, when I've been using both Hola and Vuze since Adam was a boy did it all go so suddenly wrong? A gold star and a smartie to the one who can answer that! And.... what would happen if (I am unlikely to start fiddling around again now, but one never knows!) I were to reinstall Hola?!!?
Anyway........ thank you all so much for your input and advice.
Hola was the culprit for me too. I've killed the processes and disabled switched hola off and BINGO, Vuze works! Exactly as it should. Pain and anguish has gone.
(07-23-2015, 01:34 AM)'sodam' Wrote: WOW! You guys really are superstars. Seeing as I'm the one that started all this.... I thought I should let you know that I have been watching this thread even after I had given up all hope. I checked in today and saw the last post regarding Hola. I thought I'd give it a whirl and......... abracadabra! Fantastic. I have only one question left, now that I have my beloved Vuze up and running again.
Why, when I've been using both Hola and Vuze since Adam was a boy did it all go so suddenly wrong? A gold star and a smartie to the one who can answer that! And.... what would happen if (I am unlikely to start fiddling around again now, but one never knows!) I were to reinstall Hola?!!?
Anyway........ thank you all so much for your input and advice.
I'm with Sodam on this one. I havent been at this for days, but hours yes(the usual, uninstall, 32/64 queries etc etc), and I was lucky to find this thread. After learning new fantasmagoricle things about command line, I got Vuze up and running albeit using a different port. GREAT suggestion by ArronM! I too found that Hola was hogging the port, and I have quoted Sodam because I have the same question, in that if I wanted to reinstall Hola, would it find itself another port to use, or would it push Vuze out of the way again? I think I might just never close Vuze again to be safe! ;P
same issue. tried in advanced mode to turn on internal browser and it keeps turning it back off. once in a while it will search internally for a second or two and if I hurry up and click mete search it will work briefly before the entire program shuts down. external search doesn't even work and just keeps displaying the loading circle endlessly. it was working about a week to two weeks ago when I was looking for a movie my girl wanted which I couldn't find, and two days ago when I got on two look for that movie it wouldn't start at all then after doing an update and then reinstall it runs but the internal search wont work. I am not adept at command programming so I and it seems many others would prefer to stay out of that until this is resolved. this has happened befor ,but always been fixed in a day or two btw.
