Jump to content


Application Error -> Subscript out of range...


6 replies to this topic

#1 machinogodzilla

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 16 January 2009 - 11:57 AM

Hi!


I was trying to download:
- AutoPatcher Updater 1.0.5
- AutoPatcher Engine 5.6.81
- AutoPatcher for Windows Vista SP1/2008 (x86)

While downloading the progress bar was behaving in a bizarre way going back and forth, showing odd values, e.g. -907070 B/s.

At the end I got the following errors:

Application Error -> Subscript out of range in prjUpdater.mdlDownloader.processDownloadQueue at line 100

Verification Failed -> One or more files has failed verification. Please re-run AutPatcher Updater. If this problem persists, please report to the forums at AutoPatcher.com.

Re-running doesn't help.

#2 _def_x_

    audi 5k

  • Veterans
  • PipPipPipPipPipPip
  • 1,460 posts
  • Gender:Male

Posted 16 January 2009 - 12:22 PM

Hi machinogodzilla.

Check your firewall settings.

Have a look at this post.

Report back if you are still having problems.

Mike

#3 machinogodzilla

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 16 January 2009 - 01:07 PM

I added apup.exe to the exceptions of Windoze firewall but nothing changed.

Here is the log file:

apup.log

#4 _def_x_

    audi 5k

  • Veterans
  • PipPipPipPipPipPip
  • 1,460 posts
  • Gender:Male

Posted 16 January 2009 - 01:32 PM

You may want to clean up the path some, strange characters can be problematic
for APUP. -> @ ! # $ % & _ etc

Try changing this: -> D:\_System\apup

to This: -> D:\apup

and see if it helps:

APUP needs to be run from a system you have Full permissions on and unobstructed
internet access - double check and make sure.

Where is this D drive located - just curious?

Mike

#5 machinogodzilla

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 16 January 2009 - 02:31 PM

Changing the path didn't help.

Yep, full rights and no probs with internet access.

Here there is a video of that crazy progress bar: video

D is the third logical partition on the drive, after swap and C. All within the extended partition and all located on the same physical drive.

#6 _def_x_

    audi 5k

  • Veterans
  • PipPipPipPipPipPip
  • 1,460 posts
  • Gender:Male

Posted 16 January 2009 - 05:29 PM

Rerun apup.exe /log and uncheck the Vista release, only have AutoPatcher Updater
and AutoPatcher Engine selected - see if it completes and gives you a "Finish" tab.

Hopefully re-running APUP can fix this:
(_Download Error: D:\_System\apup\temp_bin\apengine_bin.7z
File size does NOT match. Expecting 1131928, but found 0!!!_)

I think this is the Junk Email Filter. It gets updated regularly and can become outdated fast
and give off a Verification error - the 0 bytes here is different but if you got everything else
in the Vista release you can still update using AutoPatcher - everything but the Junk Email Filter.
(_Download Error: D:\_System\apup\modules\NonCritical\KB905866_files\Windows6.0-KB905866-v26-x86.msu
File size does NOT match. Expecting 2375595, but found 0!!!_)

The strange speed issue has occurred before but is not a problem.

First things first - Re-run APUP with the 2 boxes only and report back.

Mike

#7 machinogodzilla

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 17 January 2009 - 11:24 AM

The first run without Vista release finished without any errors.

The second run with just Vista release resulted in the same behaviour as before.

Here is a piece of log from the second run:

***Downloading Releases***

Files to be Downloaded: 88
Windows6.0-KB905866-v26-x86.msu: 404 - File not found
Windows6.0-KB905866-v26-x86.msu: 404 - File not found

Download Error: D:\apup\modules\windows_critical.apm
	File size does NOT match. Expecting 1762, but found 0!!!

Download Error: D:\apup\modules\NonCritical\KB905866_files\Windows6.0-KB905866-v26-x86.msu
	File size does NOT match. Expecting 2375595, but found 0!!!


Download Error: D:\apup\modules\NonCritical\KB905866_files\Windows6.0-KB905866-v26-x86.msu
	File size does NOT match. Expecting 2375595, but found 0!!!

I unchecked the KB905866 update on the list and the autopatcher has done its work without any problems.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users