←  AutoPatcher Bug Reports

AutoPatcher Forum

»

Application Error

Black Ghost's Photo Black Ghost 06 Mar 2013

Got this when I ran the AutoPatcher Updater.

Invalid procedure or argument in prjUdater.mdDownloader.processDownloadQueue at line 170

I am running Windows 7.
Quote

ViroMan's Photo ViroMan 07 Mar 2013

what a strange place to have an error.

Can you repeat it? What are the steps if so.
Quote

Black Ghost's Photo Black Ghost 07 Mar 2013

I have only gotten it twice. Now I just got another error.

Permission denied in prjUpdater.frmMain.Form_Unload at line 106.
Quote

ViroMan's Photo ViroMan 08 Mar 2013

What version of AP are you using so I know if something that changed caused it?
Quote

Black Ghost's Photo Black Ghost 08 Mar 2013

I am using version 1.4.11.
Quote

ViroMan's Photo ViroMan 10 Mar 2013

Did anyone notice I managed to revert the code to display script sizes for the latest version?(I just now put it back in)

Quote

Permission denied in prjUpdater.frmMain.Form_Unload at line 106.
As far as I know that line is perfect. It has to do with deleting the temp_bin that is created. It won't work though if it doesn't have delete permissions(hence why it said permission denied). That line also won't execute if the dir doesn't exist since there is a check for it just above that line. I will change how it reads the variable but, it "shouldn't" make a difference.

Quote

Invalid procedure or argument in prjUdater.mdDownloader.processDownloadQueue at line 170
looking into that now but, like I said... weird place to have an error. It just removes the queue item that was just used from the list.(I have done some testing and I can't seem to replicate the problem.)

edit: I threw in some more error code for that area... in the next version if you get the same error(for the error above) I will have some more information to go on.
also... Show the log so I can see what you were doing. The error should be listed there as well.
Edited by ViroMan, 10 March 2013 - 08:40 PM.
Quote

Black Ghost's Photo Black Ghost 10 Mar 2013

It could be a random error. It is not doing it now. Grrrrrrrr.........
Quote