OK, I've lived with this for years but am really starting to get annoyed. Am I the only one that has a problem with Autoupdate in that if you forget to click on the 'Programming Complete without Error' dialog and another window covers it, then you try another Autoupdate later, you get a dialog stating that Autoupdate is already running, and to close that instance before trying again. When I do what it asks and then try again, I continue to get the same dialog, even though Autoupdate IS closed, and DOESN'T show up in Task Manager (either as an Application or a process). My only recourse is to reboot the computer. I can't tell you how many times this has happened to me since I started working with Netburner modules.
The 'Programming Complete without Error' dialog is completely useless. Why can't the program just end upon a successful programming session???!!! And why does the program think it's running when it's not?
Autoupdate is already running (even when it's not)
Re: Autoupdate is already running (even when it's not)
That has never happened to me. What OS are you using? Network sockets are involved, could an antivirus or firewall be messing things up? Could try disabling them and test to see if that's the case.
Re: Autoupdate is already running (even when it's not)
Are you running IPSetup at the same time? Basically there's some port grabbing/forwarding that went wrong a while ago, that I thought we fixed that relates to this.
If you encounter this and do have IPSetup open, and you close IPSetup, does the issue go away? Basically this issue is either: a) the port we need is in use by another process (i.e. IPSetup) and Autoupdate cannot bind to it to perform the update (this is usually due to AutoUpdate already running, hence the message), b) the operating system isn't cleaning up/releasing the port for rebinding properly (this seems less likely, but not impossible), or c) the os simply isn't letting us bind to the port (could be user permissions insufficient to fully kill a hung bind, or a firewall issue, seems the more likely OS issue).
-Dan
If you encounter this and do have IPSetup open, and you close IPSetup, does the issue go away? Basically this issue is either: a) the port we need is in use by another process (i.e. IPSetup) and Autoupdate cannot bind to it to perform the update (this is usually due to AutoUpdate already running, hence the message), b) the operating system isn't cleaning up/releasing the port for rebinding properly (this seems less likely, but not impossible), or c) the os simply isn't letting us bind to the port (could be user permissions insufficient to fully kill a hung bind, or a firewall issue, seems the more likely OS issue).
-Dan
Dan Ciliske
Project Engineer
Netburner, Inc
Project Engineer
Netburner, Inc
Re: Autoupdate is already running (even when it's not)
Don't laugh, Dan, but I'm on Vista 32-bit.
Can the problem be related to having Eclipse open but using the separate Autoupdate utility instead of the Autoupdate button in Eclipse?
It seems that sometimes I have this problem and sometimes I don't, i.e. there are times when I can close out the completion dialog and it runs OK when I start it again, and other times when I keep getting the error message. Could it have anything to do with how long that completion dialog is displayed? Not sure this is always true, but it seems like I almost always have the problem when the completion dialog has been up for a while (minutes) before I do another update.
Can the problem be related to having Eclipse open but using the separate Autoupdate utility instead of the Autoupdate button in Eclipse?
It seems that sometimes I have this problem and sometimes I don't, i.e. there are times when I can close out the completion dialog and it runs OK when I start it again, and other times when I keep getting the error message. Could it have anything to do with how long that completion dialog is displayed? Not sure this is always true, but it seems like I almost always have the problem when the completion dialog has been up for a while (minutes) before I do another update.
Closing MTTY worked.
So I left the completion dialog up again by accident, and after closing it was still getting the 'another instance is already running'. I closed Eclipse, and I still got the problem when I then tried to run the Autoupdate utility instead of using the button in Eclipse. I was about to reboot, when I decided to try closing MTTY first and see if that helped. After closing it, I was able to run AutoUpdate. Hope this provides useful data.