software update error (-1001)

Mike:

I suspect that this is connected to your other question about the airport card. Try a direct connection via the ethernet port and see if this helps.

😉 cornelius

I'm getting this error too, for some the Macs installed at our office. No firewall rules have changed, everyone's using an ethernet connection with static IPs and can access all other internet sites fine. Our internal DNS is solid (as far as I can tell, because my machine can get to software updates okay and it's using the same DNS server) and can resolve the Apple update site okay - and strangely it's affecting both Leopard installs (10.5.4) and Tiger (10.4.11).

I'm switching the last of our Macs to using our internal software update system today, so hopefully it won't matter anymore, but it's interesting.

I have observed this problem for at least two years and have investigated it extensively. I have determined:

* All of the following characteristics have been observed from MacOS 10.3 running on a G4, up to the latest OS and hardware. (I suspect the problem is even older)
* The problem happens most often on very popular downloads (iTunes updates being the most common)
* Once observed, it will happen consistently, but only for the one specific update file, not for others (for example, Software Update can successfully load other packages, but fail on the "problem" file)
* The download fails near the end, typically about 1 megabyte before the end.
* Failure manifests itself as a starvation timeout (HTTP server fails to send next block of data after repeated requests by client at other end of TCP connection)
* The timeout consistently happens at the same point in the transfer.
* Success downloading from the Apple Support website is unrelated to success/failure at downloading it through the Software Update program.
* If the URL is determined (by looking in the index catalog file) the transfer can be attempted with a command-line tool, or by pasting the URL into the Safari downloads window -- or even from a Windows computer. In all cases, the transfer proceeds to the same point and then times out.

And notably, I have found one workaround:

The file can usually be successfully downloaded from "another part of the internet". This might mean using another system located in your city but that gets its internet connection from another provider, or logging in to a system far away and downloading it there.

The nature of the workaround implies that the bug is caused by improper proxy cache server implementation. I suspect it is Akamai's responsibility.

- Robert Munafo

Here's what worked for me; unplugged the modem from the wireless router and plugged it directly into the iMac. Everything worked straight away and it works wirelessly too now. Might help a few others.

I just had this problem yesterday and it was driving me nuts. It appears that the solution ultimately resides with physiclaly re-setting your internet connection.

Here is how it happened for me.

1. I allowed an update to be installed for Firefox (gmail notifier). It failed. After that, I was unable to connect to any websites in Firefox. I was also unable to connect to any websites in Safari and IE. They would all time out.

The interesting part however is that I was still able to communicate on instant messenger. So I had an active working internet connection, it just would not work for the browsers.

2. I tried to download the software update and got the message from the title of this tread.

3. I tried to delete the software update and firefox update plist files as perscribed by some to fix the problem. This did not work.

4. I removed firefox and rebooted. This did not work.

5. Using my airport, I selected another network that was available in my building and then my internet access worked. So I knew it had nothing to do with any corrupt files, my connection itself was out of wack.

6. Tried logging in with another account on my same mac with my same connection via airport. This did not work.

7. Finally, I went to the the Windows PC where my cable modem and wireless router are actually connected. I pulled the power plug out of my wireless modem, thus causing a physical re-setting of my "network".

After doing this, my connection worked

Message was edited by: manoreza

Message was edited by: manoreza