Software Update error -1001

I experience the very same behavior on all of our 10.4 machines as of today, but SU works fine with the 10.3 machines. I assume there is an error on Apple's side. Let's wait and see.

Having same problem. I am on an internal network and all of the machines with 10.3 can use Software Update, but the three machines with 10.4 can't and do get the same message that you got. They can all use the internet and Network Diagnostics says that there is no problem. I can ping IPs outside of our network just fine.

Add me to the list as well. The only way I've found to get it working is to enable my wireless connection (which I don't use that often) along with my ethernet connection.

Too strange.

After reading your message, I disabled my ethernet port connection and used a airport connection. It worked just fine. Maybe there is a fix in the Software Update that is being downloaded.

Charlie Havens

Nah. I downloaded that and it didn't change anything. However, I just got off the phone with AppleCare troubleshooting a problem with my Dock that seems to keep crashing after 10.4.3. He had me delete my ~/Library/Caches and /Library/Caches folders and reboot.

I have no idea if it fixed the Dock problem, as it is intermittent, but now Software Update is working again. Might be worth a shot for you, too.

That worked. Thanks so much!

Woohoo!!!! Hope others find it helpfull, too.

Hi all,

We had the same problem on all of our machines this morning.

About half an hour ago we tried again and Software Update worked fine. Must have been a problem on Apple's server.

Richard

Hi, folks!

Interesting thread. I empathize with the frustration — and feel glad for those who've resolved the problem. Curious, I tried to dig into this a bit in hopes of helping. But I'm happy no help seems to be needed at this point . . . (?)

Sometimes, common sense actually does work with log messages. Seems to me that Richard1's interpretation is correct for most cases.

Since I couldn't find specific reference to "error -1001" readily, I did a little more ADC searching. Components of the log entry are described pretty well in the "Constants" and "localizedDescription" sections of NSError (and to a lesser extent in Using NSURLConnection). But there's really no need to consult these references —

The bottom line seems to be that "timed out" is the essence of the situation. In cases where changing your method of Internet connection (or simply Netwrok Preferences) work, this may be a local situation; otherwise, it's probably Apple's server or some other aspect of connecting to it.

Personally, I was foolishly "ga•ga" enough to do the OS X 10.4.3 update Halloween evening, shortly after it was released. Naturally, I met up with server "time outs" on my first couple of tries, but eventually succeeded. I'm also fortunate to have cable Internet service — slow connections may suffer from "time-out"-related problems with some frequency. . .

Warm regards,
Dean

I have a similar problem, but wiping out ~/Library/Caches and /Library/Caches didn't fix the problem. My error is:

$ softwareupdate -l
Software Update Tool
Copyright 2002-2005 Apple

2005-11-16 10:33:48.347 softwareupdate[8495] loader:didFailWithError:NSError "timed out" Domain=NSURLErrorDomain Code=-1001 UserInfo={
NSErrorFailingURLKey = http://swscan.apple.com/content/catalogs/index-1.sucatalog;
NSErrorFailingURLStringKey = "http://swscan.apple.com/content/catalogs/index-1.sucatalog";
NSLocalizedDescription = "timed out";
}
timed out

I am running server 10.4.2 and would like to upgrade to 10.4.3. This system is trying to run software update for the first time, and getting the above error.

Hi, James —

A few thoughts in summary and addition to the suggestions presented here and in the other thread where you posted this query.

(1) You may find it beneficial to read and consider the troubleshooting info in these Apple KnowledgeBase Articles:

• 106692: Mac OS X: Troubleshooting installation and software updates

• 106695: Troubleshooting Automatic Software Update in Mac OS X

• 106704: Mac OS X: Updating your software

Please note that — both in these articles and the two threads — there are quite a few troubleshooting steps suggested beyond the one you've mentioned (cleaning caches). I won't reiterate them all here, but please do consider these issues, at a minimum:

(2) Your log has clearly indicated that the download process "timed out." Although I mentioned this in my previous message, I didn't discuss it in detail, because previous posters seemed to have resolved their issues.

"Timed-out" tends to imply one of two problems: ℹ an issue with the server you're connecting to for the download, or (ii) an issue with your connection itself.

In the first case, waiting a bit then trying again once or twice will usually solve this — or using an alternate ("mirror") site, if one's available.

In the latter case, many folks have found success by what I consider "kicking the tires" — e.g., checking Ethernet (or other) cable connections; changing AirPort channels; going to System Preferences »» Network and (a) changing the Location; (b) checking Network Status; or (c) as suggested in Article 106695, going to Show Network Port Configurations and selecting the Built-in Ethernet checkbox to enable the port. Then, click Apply Now. If Software Update now works, you can return to System Preferences »» Network and disable the built-in Ethernet port again, if you wish. In some cases where an ISP is the issue, you may need to use Show: Built-in Ethernet »» TCP/IP and check DHCP and other settings — or modify them, with the help of your ISP's tech. support.
James, I hope that one of these suggestions helps you to resolve the issue. I'd appreciate hearing back how things work out.
Good luck!
Dean
p.s. For future reference, it may help if you'd provide a specific summary of your Mac and its peripherals, etc. as a signature to your post (see My Settings). For example, replies might focus on AirPort if we knew that to be your method of connecting. Thanks!

Hi Dean. Thanks for your response. I only posted to various forums because all seemed old, and I didn't know if any were still being monitored.

(1) I read a number of KnowledgeBase articles before I posted, but none seemed to describe my problem. I did try a number of other suggestions in these posts, but none helped. These included erasing com.apple.SoftwareUpdate.plist and erasing the cache files. As for changing the Language preference to English, I couldn't find anywhere how to do that using command line administration. As for turning off the Ethernet port, I can't do that because I only have an Ethernet port and do not have an Airport. There is no ~/Library/Logs and /Library/Logs/Console/501/console.log hasn't been updated since Sept. 26. /var/logs/system.log shows no entries at the time of the error. I wouldn't know what other logs to look at.

(2) I have an Ethernet connection to a T-1 line. I have no time-outs accessing any other service, and have no problems accessing the server using AFP and retrieving large files. The only thing which times out is the Software Update function. It is hard to believe that the Apple server is consistently having problems only at the exact moments I am trying to update Mac OSX Server. I can update my desktop systems (running plain old Mac OSX) with no problem. The problem, therefore, would seem to be a bug in the Mac OSX Server Software Update function (and, given the number of similar reports here, that seemed like a good bet) or the network configuration of the system but only in a way that Software Update experiences the problem. As I said, no other service on this computer is affected by whatever it is that is hosing Software Update.

The system is a brand new Mac Mini, 512 MB, running a brand new Mac OSX Server 10.4.2. The install (upgrade, really) of Mac OSX Server 10.4.2 on top of the 10.4.2 which came with the Mac Mini went flawlessly. We bought the thing to be a file server, and it is doing that job marvelously. Really the only problem is updating the software to 10.4.3. It is sitting in the file server room with all the (ug!) Windows file servers. I have access to it through command line adminstration, but I guess I could carry in a monitor and hook that up if I really had to change the language to English... or whatever it is in Software Update which isn't working.

I only posted here hoping that someone had identified something besides erasing the cache files that might fix this problem.

Hi again, James —

Thanks for your detailed reply.

I've noted your posts in threads A and B — in addition to this one.

I didn't realize that you were running Mac OS X 10.4.2 Server — and must admit that I'm over my head when it comes to the server side of things. Dog-paddling for a moment . . .

In an effort to be helpful, I did root around a bit — and will offer a few thoughts, for whatever they're worth —>

(a) Have you considered searching &/or posting in the Mac OS X Server forum? I presume that's the correct folder; if not, there are other server-related forums linked from the new Apple Discussions homepage. Seems to me that folks also running the Server software would be most able to help.

(b) I surfed quickly at AFP548.com. I didn't find too much beyond refs to Apple's About the Mac OS X Server 10.4.3 Update and Xsan 1.2: How to use the Xsan 1.2 Updates — if those are relevant. The former does note improvements have been made to Software Update Server, among many others. From your most recent comments, may I presume that you can download and install the stand-alone 10.4.3 Server Combo Updater — just not utilizing Software Update? If so, perhaps the improvements will help to ameliorate the current problem.

(c) AFP548.com also brought to mind that — if the appropriate Apple Discussions forums' folks (I'm thinking again of participants with more server experience than I) aren't able to help, there are some Mac OS X Server mail lists that may prove invaluable to you. If it's comparable to others I've visited, Apple's mac-os-x-server list may be very good. AFP548 also suggests MacOSX-admin and macenterprise.org's list.

= = = = =
Sorry, it wasn't my intent to imply a scolding tone about posting more than once; rather, I was trying to provide a cross-reference link. Although "cross-posting" is generally viewed as a "no-no", I don't think it should be emphasized at a time like this transition from old-to-new Apple Discussions. Many a thread have undoubtedly lost momentum under the circumstances — and I agree that you've a particularly frustrating situation, to the extent I understand it. Personally, I do appreciate text links between/among threads as a means to minimize redundancy in replies — so, when I don't see 'em, I tend to mention it and add same. Again, I'm sorry if by so doing I caused you any discomfort — 'twas unintended.

And in this instance, I'm sorry to see that — as of my drafting this preliminary reply — you've received a dearth of other responses . . . I ask that you trust in the generosity and resourcefulness of folks here — "the cavalry" usually does eventually find its way over the horizon. (That's intended as a wry reference.)

I hope something here helps you toward resolving the problem . . .

Warm regards,
Dean

Hi Dean,

I've got this dreaded 1001 Software Update error message myself and have read all the thread ooking for a solution but nothing works.

Until a week ago I was running 10.3.9 with no problems - I then purchased 10.4.3 from Apple and installed the new system - that's when the troubles started.

Firstly, the machine would stall about 15 seconds after waking from Sleep (No problems with Software Update as that ran perfectly OK). After a week of frustration trying all suggestions to fix this, I re-installed 10.4.3 earlier today and that solved the Sleep Problem !!! but ........ then tried running Software Update and that no longer connected to the Internet (Time Out error 1001) hence my reading this thread and trying all suggestions but to no avail.

Taking a simple view, I suspect that each time if I re-installed again then I'd have a new Problem next time.

I'm now 1 year into the MacWorld after 20 years of MS-DOS & Windows but I never had problems like these before - I still don't regret the change but Apple needs to sort out it's pre-release testing of OS software and not get the users to do it.

Have you got any other ideas ? ----- thanks

Hi, Tony - See Fumiaki Kawashima's post, here:

http://discussions.apple.com/thread.jspa?messageID=1382171&tstart=0#1382171

Good luck!

Tuttle



1603/8311