←  AutoPatcher Bug Reports

AutoPatcher Forum

»

Confused Autopatcher

aleatorul's Photo aleatorul 19 Apr 2010

I've used Autopatcher successfully last time 2/3 months ago. Decided today to update it.

Apup run fine, all updateds donwloaded. Pressed Finish.

Autopatcher.exe however pops up a "Yikes! Confused.." error with these details:
"It appears that the error occurred while AutoPatcher was trying to get commandline arguments.
Where: mdlInitialization.Main()
Error code: File not found"

Great! Only way to go further was to press the close button.

The log:
Attempting to initialize common controls.
Accessing filesystem...
AutoPatcher 5.6 loaded the filesystem.

Detected 
English (1033) Windows XP Professional Service Pack 3
System Components:
	Internet Explorer: 6.0.2900.5921
	Windows Media Player: 9.0.0.4507
	.NET Framework: 1.1.4322|1.1SP1|2.0.50727.3053|2.0SP2|3.2.30729.01|3.2SP2|3.5|3.5SP1
	Windows Installer: 4.5.6001.22159
	DirectX: 4.09.00.0904
	MSN/Live Messenger: 

Office Components:
	Microsoft Word: 10.0.6850.0
	Microsoft Excel: 10.0.6850.0
	Microsoft PowerPoint: 
	Microsoft Outlook: 
	Microsoft Access: 
	Microsoft Project: 
	Microsoft Publisher: 
	Microsoft OneNote: 
	Microsoft FrontPage: 
	Microsoft InfoPath: 
	Microsoft Visio: 
	Microsoft SharePoint Designer: 
	Microsoft Groove: 


Looking around for others with similar problems, I saw their log went further than "Microsoft Groove:". So... I have no idea what went wrong.

Restarted, created a new folder, downloaded a fresh apup from here, used it to update only the updater and the engine, no other modules. Download successful, finish... same error!

Disabled antivirus/firewall... no luck.
Edited by aleatorul, 19 April 2010 - 01:09 AM.
Quote

Cristiano's Photo Cristiano 19 Apr 2010

well, "file not found" us to mean that some of the files that are in the bin folders are missing or the system has an version that doesn't match with the expected one. but to be sure, we may require certain details from your system, like the firewall and anti-virus version and name. also, do you have any kind of anti-spyware software?

thanks

[]s
Quote

aleatorul's Photo aleatorul 19 Apr 2010

View PostCristiano, on 19 April 2010 - 01:24 AM, said:

but to be sure, we may require certain details from your system, like the firewall and anti-virus version and name. also, do you have any kind of anti-spyware software?

XP sp3 Eng (regional settings: RO)
Avast Free 5.0.507
Look n Stop 2.06p3
Spybot 1.6.2.46 (just immunization, resident just SDHelper)

Thanks.
Quote

Cristiano's Photo Cristiano 19 Apr 2010

there's an know issue regarding certain languages, like Romanian. i'm unsure if it affects also the way that autopatcher runs, but it's an possible issue. can you please change the Non-Unicode Default to english? there's an tutorial about it in here. also, with non-english systems, there's another know issue: the patch name. certain characters in the patch does autopatcher have an unexpected behavior. just as an test, can you please move autopatcher to an short path, like c:\apup, where none non-english characters are present?

also, the issue may be related to Look n Stop, but certain softwares aren't fully disabled when you just stop them.

of course, "file not found", issues also may related to any of those files missing:
http://www.autopatch...apengine.script

can you please check that?

thanks

[]s
Quote

aleatorul's Photo aleatorul 19 Apr 2010

Changed everything to EN-US and no change. So far I've used autopatcher on other systems with RO set as non-unicode lang. and no problem.
The previous install was in C:\apup The new instance (the clean one) is in C:\AutoPatcher
I never use other chars in filenames/folders except standard En.
Like I said, I've tried disabling the firewall (both the application filtering and packet filtering). No change. I'm familiar enough with LnS to believe it's not its fault (when disabled, the rules certainly don't apply anymore and programs are wild and free).
As far as I can tell, the files in the script match what I have (also the checksums). I also have the apup_bin folder which doesn't appear in that script.


Other things that come to mind: I have DEP only for windows programs and services... I don't have stateful packet inspection enabled in the firewall...


Is there a way to downgrade/download an older version of autopatcher.exe ?
Quote

Cristiano's Photo Cristiano 19 Apr 2010

> Is there a way to downgrade/download an older version of autopatcher.exe ?
the old version is still online, but i don't remember the download link. i can take that from home, at night. in meantime, i will ask to our developers take a look on this

thanks

[]s
Quote

Antony's Photo Antony 19 Apr 2010

Ok, - I've added few log messages in code for understanding on which file this error is raising...
Let's try this one for now...

EDITED: not his one but another - see next post
Quote

Antony's Photo Antony 19 Apr 2010

ooops, sorry - not that file but this one:
Attached File  autopatcherLOG.zip (169.27K)
downloads: 11
Quote

aleatorul's Photo aleatorul 19 Apr 2010

View PostAntony, on 19 April 2010 - 08:06 PM, said:

ooops, sorry - not that file but this one:
Attachment autopatcherLOG.zip

With this one the log goes a little more further:

Spoiler
Quote

Antony's Photo Antony 20 Apr 2010

a little more further and with the same "Yikes!" report after all?
Quote

aleatorul's Photo aleatorul 20 Apr 2010

View PostAntony, on 20 April 2010 - 07:22 AM, said:

a little more further and with the same "Yikes!" report after all?

The Yikes is kinda the same:
It appears the error occurred while AutoPatcher was trying to check existing of all needed spec.files.
Where: mdlInitialization.Main()
Error code: 0x35 File not found.
Quote

Antony's Photo Antony 20 Apr 2010

Ok, another version of tool with added LOG's.
Attached File  autopatcherLOG.zip (169.42K)
downloads: 12

btw/ can you try to run this code in folder were AutopatcherLOG.exe is locating?
regsvr32.exe .\bin\SSubTmr6.dll
succeeded? failed?
Quote

aleatorul's Photo aleatorul 20 Apr 2010

View PostAntony, on 20 April 2010 - 12:03 PM, said:

btw/ can you try to run this code in folder were AutopatcherLOG.exe is locating?
regsvr32.exe .\bin\SSubTmr6.dll

Apparently this was the problem... 'cause for some reason, regsvr32 was missing from my windows\system32

As soon as I extracted it from the install disk and put it there, all versions (original, LOGs) of autopatcher launched successfully.

So this could've been the file the ap didn't find? A more descriptive error msg should say something about "can't register my dlls or something" :)

Thank you all, now I should do some patching.
Quote

Antony's Photo Antony 21 Apr 2010

yep, that's was exactly "that file" which "was not found".
Regarding more logical msg. you are right - I will add it..
Quote