Having downloaded (saved) several Jan 2010 hot fix modules such as Payables 81B APHFP20100120, I'm getting the 404 install error that also indicates it cannot communicate with the server. It goes on after aborting to read that it cannot open the zip file on the local drive. Tried several sites, running on XP and 7, IE8 on the workstation. Tried running the install from the shared server drive and tried copying the install file to the local pc - same result.

Suggestions greatly appreciated.
Thanks

Are you sure you downloaded and saved the HotFix and didn't try and run it from the web? The 404 error normally occurs if you try and run the EXE directly off the internet.

Try downloading the hotfix again and see if the problem persists.

Well I kinda gave up on this which explains the long delay, but must now get it working. Got to get other hot fixes installed.

Yes I downloaded the HF to the server, tried running it from there, and also copying the file to the local drive of the workstation.

The actual message on every computer I try this on is an Install dialogue box "Could not communicate to the network server, error 3" "404 not found" with Abort and Retry as the options.

When aborting the message is "the file C:\documents and settings\%username%\local settings\Temp\TmpSsi\%hotfixname%.zip could not be opened.

This network is using a Sonicwall security appliance which I suspect is preventing communication on some port the Hot Fix needs, but I'm not sure about that. This is a Windows Server 2008 sever with WinXP and Win7 prof workstations environment. Tried disabling the local WS firewall to no avail.

What about the firewall port theory? Anyone else using a security appliance like the Sonic Wall TZ100 with Adagio?

Okay. I guess the long question didn't get a response, so here's the short version...

What causes the 404 error when when trying to install the hot fix on a LAN from local drives or server shares?

Hi Ed,

The only cause of this error that we know of is trying to run the EXE directly from the Internet using Internet Explorer, rather than downloading it to your local workstation and running the EXE from there. We have never seen this error under other circumstances.

Sorry.

"...could not be opened" Either this means what is says (user does not have rights to open the file) or you have not actually saved the file to your hard drive before running it.

If you are using a hardware firewall then you should not also be running a software firewall. Could the firewall be causing an issue? Possibly, but it would take someone with specific experience with this firewall to tell you if it is the cause of your problem. Could you temporarily remove it so that you are directly connected to the internet? If the Hot Fix does/does not install then you have at least eliminated/confirmed the firewall as the problem.

Hi Ed,

The Hot Fix has been superceded by a Service Pack. Could you try downloading and installing the service pack?

Finally figured this out. A case of mea culpa. I downloaded the hotfix and figured I would be cleaver and give it a longer friendlier name. Problem is, the name got too long for the environment. Went back to the short name Softrak gave the file and it worked. Human error strikes again. Yet another lesson learned, eh? Thanks for the input.

Thanks for letting us know that everything's ok.