Autopatcher is confused (bug report)
Posted 01 January 2010 - 12:52 PM
While installing the final update on my PC today, Autopatcher crashed. It asked me to provide an error log.
Here it is in the attachments:
The error text from the crash: Autopatcher is confused.txt 15.62K 10 downloads
The apup.log file when I ran APUP earlier today:
By the way, Autopatcher was showing "Unofficial/Unsupported Release", even though I downloaded APUP from this website just this morning (about 11AM, Australian Eastern Daylight Savings time (+11)).
Let me know if I can provide any more useful information!
By the way, thanks for the awesome software.
Posted 01 January 2010 - 02:53 PM
Edited by mbonwick, 01 January 2010 - 02:53 PM.
Posted 01 January 2010 - 07:49 PM
There is really only one person that offers support in the forums, the rest of us come in from time to time to offer a bit of advice so
I would suggest reading -> Log Files, the important part is running APUP twice and only selecting ONE main release - the one you
are having troubles with, this is all to keep the log file small and easily readable. Also, the forum software has changed so instead of
codebox for the log use spoiler. Please post each log in their given forum - XP errors in the XP forums etc.
As has been stated already, you should rerun APUP and get those incomplete releases finished, you have alot of releases crammed
into one main "\modules" folder so the easiest way to determine what releases didn't finish (are Unofficial) is to look at the release info...
...Start AutoPatcher - Click About - Click Release Info, under Official, the releases that are labeled False (Unofficial) need to be rerun
in APUP and Finish (get completed). You can't miss them they will be in red.
Your log shows 300+ files missing, you could have tried to install an incomplete file from your disconnect or you may have overwhelmed
AutoPatcher by trying to install too many updates simultaneously - you don't mention what you were updating (or how many updates were
selected for installation) when the crash occurred. I would seriously avoid trying to update critical features as DotNet, DirectX, any new
version of Internet Explorer, or too many Office updates -> All At The Same Time.
I would start with getting your release package(s) Official and then updating a few things at a time and not all at once.
This should be fixed...properly spelled -> SharePoint Designer.
Module 'KB955655_vis_enu.apm' uses an unknown/unsupported property called 'SharePointDesginer'. Please make sure this is not a mis-spelling!
This issue is in my AutoPatcher log as well
Module 'Update for Windows Media Player 9 or 10 (KB895181)' (unique id: 'KB895181_WMP10_X86_ENU') reports 'WMP10_NONCRITICAL_PARENT' as its parent, but such module does not exist or is not loaded in the right order.
Edited by gUiTaR_mIkE, 01 January 2010 - 07:50 PM.
Posted 02 January 2010 - 08:55 PM
i don't know about the office scripts, but i will take a look anyway, just to check
ok. i will take a look on that by tomorrow (i'm not in home right now...
by the way: happy new year
Posted 03 January 2010 - 05:24 AM
I'm embarrassed that I skipped the General Support forum! I foolishly assumed that everything was fine (and that the error was just something cosmetic at the end, after everything was installed). But I see now I have made about 100 common errors!
I'll take into account the info in the General Support forum, run APUP a couple more times, and let you know how I go.
Posted 03 January 2010 - 01:58 PM
as for WMP10_NONCRITICAL_PARENT, there's 6 modules asking for this one. it's weird that just one is pointing this file as missing. this file should be this one:
Item=WMP 10 NonCritical Parent Module
and it is in the script. so please, take a look
as for KB955655, this one should be calling for SharePointDesigner=ANY. in fact, this was an mis-spelling
also, KB95636 was forgot into the modules download (it was removed some time ago). this issue was created by an wrong typo for the module removal. now it shall be ok
now, download test...
Posted 03 January 2010 - 11:03 PM
Also, I checked the information supplied concerning "__WMP10_noncritical.apm", the size and hash match.
In my opinion the WMP section is confusing, here's what I mean...if interested.
With regard to KB895181 there might be 2 ways to deal with the problem. Since this update applies to both WMP 9 and 10 (the other 5 only WMP10), you
could move the update up one level and put it in "\__WMP_noncritical", like the multi version WMP Critical updates, or, and I think this removed the error but
not sure if it affects installation, change [SystemComponents] to read like this...
Posted 04 January 2010 - 10:48 AM
about the wmp updates, the best way to deal with that is just remove the wmp10 updates and keep only the wmp11 updates, but then some guys will complain about that... at least, in the way that is right now the user can select only the required updates and deploy them faster than before. but you are right, that empty folder shouldn't be in there
this doesn't work. it has to be (or should be) WindowsMediaPlayer=9,10
oh well, i will try keep awake...
Posted 13 January 2010 - 06:41 AM
I have tried some more things, but AutoPatcher still says that my installation is unofficial.
I followed gUiTaR_mIkE's advice and looked at which module was unofficial. It was Office 2003 that was unofficial.
I ran hkSFV on "md5_checksum_for_office2003_ENU.md5" and discovered that I was missing "modules\Office2003\KB95636_view_enu.apm".
I had run APUP several times, including twice with just Office 2003. But I was still missing this file.
I decided to poke around manually. I downloaded "http://www.autopatcher.com/releases/office/2k3/old/office_critical_03_enu_20091115.7z" using Firefox, and extracted "KB95636_view_enu.apm" to "modules\Office2003\KB95636_view_enu.apm". hkSFV then reported that my files match the MD5 file.
Then, next time I ran AutoPatcher, the file "KB95636_view_enu.apm" disappeared. I think AutoPatcher deleted it in accordance with the script ("office/2k3/autopatcher_off_03_enu_20100103.script" on the web server).
Office 2003 was still marked Unofficial in AutoPatcher. I have attached a screenshot of the Release Information screen:
(Only Office 2003 is marked "False".)
I am not sure what to try next.
My latest apup.log is:
APUP Has Started Version: 1.2 Operating System: English (1033) Windows XP Professional Service Pack 3 Current Locale: English - Australia / Non-Unicode Default: English - Australia Starting APUP From: C:\AP Date & Time: 13-Jan-2010 17:30 UTC Offset: 10 ***Downloading/Processing Releases.list*** List file HTTP location: http://www.autopatcher.com/releases.list Download queue processed. Proceeding to next phase. ***Releases.list Processed: Waiting for User Input*** The Following Releases have been Picked: office/2k3/autopatcher_off_03_enu_20100103.script ***Running Any Pre-Cleanup Routines*** Download queue processed. Proceeding to next phase. Executing shell command: xcopy /y /e /i C:\AP\modules\Office2003\KB973866_enu.apm_files modules\Office2003\KB973866_view_enu.apm_files Executing shell command: rmdir /S /Q "C:\AP\modules\Office2003\KB973866_enu.apm_files" ***Starting Detection Routine Phase*** ***Downloading Releases*** Files to be Downloaded: 0 Download queue processed. Proceeding to next phase. ***Processing Cleanup Routines***
Thanks and warm regards,
Posted 13 January 2010 - 02:08 PM
that's the reason why you are getting issues. the old folder is where we put the obsolete releases. if you take any file from there, then you will make your folder unofficial, due the presence of "not should be in there" files. anyway, i will do an download test just to be sure, after update the main scripts
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users