←  AutoPatcher Bug Reports

AutoPatcher Forum

»

failed verification

leon's Photo leon 23 Oct 2010

Hi, Im a first timer to this forum. I ran the first tool, received a warning as per attachment (screen dump). Tried it 3 times, same message
Any idea how to fix ?
Cheers
Leon

Attached Files

Quote

Cristiano's Photo Cristiano 23 Oct 2010

no, unless you run autopatcher with the file "hit this..." and paste the log generated by that file in here

[]s
Quote

leon's Photo leon 23 Oct 2010

View PostCristiano, on 23 October 2010 - 10:38 AM, said:

no, unless you run autopatcher with the file "hit this..." and paste the log generated by that file in here

[]s


Cristiano,
thanks but what do you mean with "hit this ..."

Txs
Quote

_def_x_'s Photo _def_x_ 23 Oct 2010

Quote

thanks but what do you mean with "hit this ...
Cristiano needs to see an unedited log file to better be able to help you, the easiest way to create a log file is to double-click the hit_this...cmd file in your \apup folder. You will need to post the log file unedited using Spoiler code.

Here's more info on log files - link 1 - link 2
Quote

leon's Photo leon 24 Oct 2010

Guitar Mike, Cristiano,

thanks for the help. Log file attached. Appreciate any advice you may have

Cheers

Attached Files

Quote

_def_x_'s Photo _def_x_ 24 Oct 2010

@leon, I put your log file in spoiler code, much easier to read.

Spoiler
I seems you are having troubles finishing two downloads, WindowsXP-KB892130-ENU-x86.exe and WindowsXP-KB898461-x86-ENU.exe - are you having problems with your internet connection? If you've run APUP more than once and you can't get the files...,

Can you download directly - WindowsXP-KB892130-ENU-x86.exe & WindowsXP-KB898461-x86-ENU.exe. If you can get them by downloading directly, simply rename the files (you will see these files have a lot of extra digits), use the exact names from the script, and replace the incomplete files that are in the folders. You can find the folder locations using the log file or the script - here they are.

...WindowsXP-KB892130-ENU-x86.exe -->> \apup\modules\wga\wga_files\WindowsXP-KB892130-ENU-x86.exe
...WindowsXP-KB898461-x86-ENU.exe -->> \apup\modules\NonCritical\KB898461_xp_x86_enu.apm_files\WindowsXP-KB898461-x86-ENU.exe

It is a good idea to re run APUP again, selecting the same scripts giving you troubles and see if things get fixed. The releases should be Official. Post again if you are still having troubles.
Quote

ongagua's Photo ongagua 01 Dec 2010

I have this log. Could you help me?

Spoiler
Quote

Cristiano's Photo Cristiano 02 Dec 2010

please, can you move apup to an shorter path, like c:\apup and try again?

thanks

[]s
Quote

ongagua's Photo ongagua 03 Dec 2010

View PostCristiano, on 02 December 2010 - 11:20 PM, said:

please, can you move apup to an shorter path, like c:\apup and try again?

thanks

[]s

Done, but I have the same error.

Attached Files

Quote

_def_x_'s Photo _def_x_ 03 Dec 2010

I put your log in Spoiler - it's easier to read and you don't have to download it.

Spoiler
We need details about your setup, where you're running apup.exe from, security software, firewall, AV etc installed - something seems to be interferring with the download process.

Can you download these files... extract the contents (overwrite any files if you are prompted), re run APUP, selecting the same scripts.

extract to \apup ... http://www.autopatch...100_20100310.7z
extract to \tools ... http://www.autopatch...e/tools_0711.7z
extract to \translations ... http://www.autopatch...apengine_lng.7z

Are you having problems with a release (XP, Vista, 7), your log only shows 2 scripts and no release?
Quote

Moon's Photo Moon 05 Dec 2010

mmmm, well, i 've the same problem guys abt '' verification failed '' and i tried all wat u said up here and nothing solved :S

so 'll be galde if u tell me how can i fix this

thnx
Quote

_def_x_'s Photo _def_x_ 05 Dec 2010

@Moon

What's the problem release you downloaded, details please like - the XP SP3 release is unofficial, here's my log file. If there is an .md5 in the root folder did you run it, have you tried to update the release? If you have multiple releases in the same folder, to know what release is causing the problem - start AutoPatcher - click About - click Release Info - the release title in red needs fixin' :)

If you follow the above and all releases are True under Official this means you have a stray (extra) file that you need to remove - this can be more difficult to trace, not impossible.

You can start APUP w/ logging by running the 'hit_this...cmd' file, select the offending release(s) etc. Read this about logs, please one release / twice run logs - Logs - More Info! - simply means always run APUP at least twice before posting a log file (it keeps the logs smaller, easier to read) and post a log file of the problem release only, we don't need to read thru a log file with the contents of 11 scripts.

Read Here! - the last Note: about Spoiler code for the log file - it makes posting your log very easy.
Quote

Moon's Photo Moon 05 Dec 2010

oh sorry bro, u r right the problem was abt '' Xp Sp3 release wasnt official '' , i dont know how i didnt notice that :$ :S
any way the problem fixed and now Apup is working perfectly,

am sorry for disturbing and Thank you for helping n giving me ur time. :)
Quote

_def_x_'s Photo _def_x_ 05 Dec 2010

Quote

am sorry for disturbing and Thank you for helping n giving me ur time.
Not a problem at all, we're here trying to fix any issues that arise, we just need info, without it we have no where to begin :)

Anyway, what was the problem with your release and how did you fix it - just curious...
Quote

aha's Photo aha 16 Dec 2010

Hello Cristiano, please can you help me, thanks.

Spoiler

Edited by aha, 16 December 2010 - 01:23 AM.
Quote

Cristiano's Photo Cristiano 16 Dec 2010

that may be related with the wrong rti file at our servers. i've fixed the report about it, but to be sure that it worked, i have to download the whole release and this will take some time

sorry

[]s
Quote

_def_x_'s Photo _def_x_ 17 Dec 2010

Running APUP and updating XP SP3 should fix the problem.

There were 2 updates added since Dec. 14th (and an .apm edit), the release is Official (dated December 16, 2010) - click About // Release Info :)
Quote