10 replies to this topic

[Bubba Gump]

James, on Sep 25 2008, 12:29 AM, said:

Thanks for letting us know. I really need to see a log-file to sort this out.
(There were other changes made to AutoPatcher's files at the same time.)

Could you please run apup /log selecting only Vista x86 (32-bit) and post the log-file here?

Then can you please do the same for Windows 2003?
(Please post that log-file in the Windows 2003 section)

--

I tried running "apup.exe /log" from Start, Run, Brouse to location of apup.exe, added " /log" and it sais it is not a valid file. Now what?

[Bubba Gump]

Bubba Gump, on Sep 25 2008, 04:09 PM, said:

I tried running "apup.exe /log" from Start, Run, Brouse to location of apup.exe, added " /log" and it sais it is not a valid file. Now what?

No suprise, but I have the same problem with (X64)

[Cristiano]

yours already tryed set the full patch for the folder, like:
D:\autopatcher\apup\apup.exe /log

or create an txt file, with:
apup.exe /log

save it and then rename it to test.cmd and double click it?

[]s

[Bubba Gump]

Cristiano, on Sep 25 2008, 04:16 PM, said:

yours already tryed set the full patch for the folder, like:
D:\autopatcher\apup\apup.exe /log

or create an txt file, with:
apup.exe /log

save it and then rename it to test.cmd and double click it?

[]s

I first get an error ~ "Error fetching release list!" from the AP Dialog Box
Here's what is in the resulting log file

APUP Has Started

Operating System: English (1033) Windows Vista Ultimate 64-bit
Current Locale: English - United States / Non-Unicode Default: English - United States
Starting APUP From: L:\Autopatcher
Date & Time: 26-Sep-2008 15:03 UTC Offset: -5

***Downloading/Processing Releases.list***

List file HTTP location: http://www.autopatch...m/releases.list
releases.list: The attempt to connect timed out

Edited by Bubba Gump, 26 September 2008 - 07:08 PM.

[James]

Bubba Gump

Thank you for posting your log-file.

The error message that you see means that APUP is unable to connect to the Internet.

This is usually because APUP is being blocked by your Firewall, by your Anti-Virus software or by your Anti-Spyware software. Make sure that you have allowed apup.exe to connect to the internet, the same as Internet Explorer.

--

[Bubba Gump]

James, on Sep 26 2008, 04:30 PM, said:

Bubba Gump

Thank you for posting your log-file.

The error message that you see means that APUP is unable to connect to the Internet.

This is usually because APUP is being blocked by your Firewall, by your Anti-Virus software or by your Anti-Spyware software. Make sure that you have allowed apup.exe to connect to the internet, the same as Internet Explorer.

--

I doubt it. I have an "always on" DSL connection, and had no trouble before or after this in downloading all other current AP updates. As for my Symantec EndPoint Protection (the Corporate version) firewall, I hit the internet dozens of times a day and I have never had a problem either inbound or outbound. The problem with this one patch is on the AP end ~ why else would EVERY other "K" download correctly ... except this one?
BTW, I download every version of AP (except Win 2000 and XP x64) for a total of 3 Gig, and this one patch is the only one thet bombs out of the hundreds I have downloaded.

Edited by Bubba Gump, 28 September 2008 - 04:14 AM.

[Cristiano]

> all other current AP updates
in the past days, we have updated apup. if your firewall is running properly, it will detect that the program has changed and will ask if you allow it to access internet. if you say "no", the software will go to the black list and will be unable to run. you can check this by:
1 - looking into the rules of your firewall to locked programs and unlock apup;
2 - disable your firewall to test if apup will be able to reach internet.

> this one patch
releases.list isn't a path. it is the very first file that apup need to download, in order to know what scripts are online. in a short term, is this file that you see when you run apup and see his first screen

[]s

[Bubba Gump]

Cristiano, on Sep 28 2008, 07:15 AM, said:

> all other current AP updates
in the past days, we have updated apup. if your firewall is running properly, it will detect that the program has changed and will ask if you allow it to access internet. if you say "no", the software will go to the black list and will be unable to run. you can check this by:
1 - looking into the rules of your firewall to locked programs and unlock apup;
2 - disable your firewall to test if apup will be able to reach internet.

> this one patch
releases.list isn't a path. it is the very first file that apup need to download, in order to know what scripts are online. in a short term, is this file that you see when you run apup and see his first screen

[]s

Now will you please look at this AP error? It is a Hash and file size problem ..............

APUP Has Started

Operating System: English (1033) Windows Vista Ultimate 64-bit
Current Locale: English - United States / Non-Unicode Default: English - United States
Starting APUP From: L:\Autopatcher
Date & Time: 28-Sep-2008 11:40 UTC Offset: -5

***Downloading/Processing Releases.list***

List file HTTP location: http://www.autopatch...m/releases.list

***Releases.list Processed: Waiting for User Input***

The Following Releases have been Picked:
autopatcher_vista_x64.script

***Running Any Pre-Cleanup Routines***


***Starting Detection Routine Phase***

Detection error for file L:\Autopatcher\modules\Critical\RootCert_files\rootsupd.exe
MD5 Hashes do NOT match. Expecting B0EF15FE19FB3AC9367B1FCFE6D473F3, but found b03d5926e946194b046dbb311baad15c!!!
Item rootsupd.exe failed detection. Adding its download to the queue.
--Adding http://download.windowsupdate.com/msdownlo.../rootsupd.exe--

***Downloading Releases***

Files to be Downloaded: 1

Download Error: L:\Autopatcher\modules\Critical\RootCert_files\rootsupd.exe
File size does NOT match. Expecting 302168, but found 303232!!!

***Processing Cleanup Routines***

Edited by Bubba Gump, 28 September 2008 - 03:46 PM.

[James]

Bubba Gump, on Sep 28 2008, 05:09 AM, said:

I doubt it. ...

I don't. Your log file is absolutely clear. On this one occasion you failed to connect to anywhere on the Internet.

Bubba Gump, on Sep 28 2008, 05:09 AM, said:

The problem with this one patch is on the AP end ...

There is no problem with this file. You cannot assert that there is a problem "on the AP end" when you didn't even reach the "AP end".

Now, as regards your second problem, (which is NOT the same problem NOR the same cause) what release did you download immediately before you downloaded the Vista 64-bit shown in you log-file?

--

[Bubba Gump]

James, on Sep 28 2008, 12:32 PM, said:

I don't. Your log file is absolutely clear. On this one occasion you failed to connect to anywhere on the Internet.


There is no problem with this file. You cannot assert that there is a problem "on the AP end" when you didn't even reach the "AP end".

Now, as regards your second problem, (which is NOT the same problem NOR the same cause) what release did you download immediately before you downloaded the Vista 64-bit shown in you log-file?

--

Apup = 1.0.5
AP Engine = 5.6.81
AP Vista (x64) = 10 Sept 2008
My Vista = Ultimate SP-1

BTW, what happened to the posts before 9/25 12:29AM?

[James]

I think you may have misunderstood my last question, so let me re-phrase it more clearly.

In your last log-file there are the lines:

Quote

The Following Releases have been Picked:
autopatcher_vista_x64.script

then the log-file reports an error involving rootsupd.exe.

This error only occurs if you download multiple Releases to the same folders. What I was asking was, when you ran APUP the previous time, what other Release did you download. Was it Windows XP? Or something else?

--