Error Code: 0xD: Type mismatch
Posted 28 July 2010 - 11:16 PM
It appears that the error occured while AutoPatcher was trying to determine if a module's property is compatible with the running component.
Error Code: 0xD: Type mismatch
Attempting to initialize common controls.
AutoPatcher 5.6 loaded the filesystem.
Italian (1040) Windows XP Professional Service Pack 3
Internet Explorer: 8.0.6001.18928
Windows Media Player: 184.108.40.20607
.NET Framework: 1.1.4322|1.1SP1|2.0.50727.3053|2.0SP2|3.2.30729.01|3.2SP2|3.5|3.5SP1|4|4SP0|4.0|4.0SP0
Windows Installer: 4.5.6001.22159
Microsoft Word: 11.0.8169.0
Microsoft Excel: 11.0.8169.0
Microsoft PowerPoint: 11.0.8169.0
Microsoft Outlook: 11.0.8169.0
Microsoft Access: 11.0.8166.0
Microsoft Publisher: 11.0.8166.0
Microsoft FrontPage: 11.0.5516.0
Microsoft InfoPath: 11.0.8169.0
Microsoft SharePoint Designer:
Module 'KB968930_xp_x86_ita.apm' uses an unknown/unsupported property called 'DotNetFramework>'. Please make sure this is not a mis-spelling!
Module 'K:\apup\modules\Components\__msxml\MSXML4SP2_x86_enu.apm' EXPLICITLY refers to its module folder as 'K:\apup\modules\Components\__msxml\MSXML4SP2_x86_files'. However, such folder does not exist!
Module 'K:\apup\modules\Components\__msxml\MSXML6SP1_x86_enu.apm' EXPLICITLY refers to its module folder as 'K:\apup\modules\Components\__msxml\MSXML6SP1_x86_files'. However, such folder does not exist!
Module 'K:\apup\modules\Critical\KB928366_DN11SP1_x86_enu.apm' EXPLICITLY refers to its module folder as 'K:\apup\modules\Critical\KB928366_files'. However, such folder does not exist!
Posted 29 July 2010 - 05:49 AM
You dont mention much in your post, what all releases you have in the same folder, are they Official. I would delete the 3 .apm files listed, rerun APUP and update the releases you are having troubles with. If the .apm files are needed they will re download. If the messages persist, post exactly the scripts you are running, are the packages Official or not. The scripts have been cleaned recently, if you haven't updated lately a few files may have been left behind.
If you have multiple releases in the same \modules folder you can determine what releases are failing by - running AutoPatcher - click 'About' - click 'Release Info' - the 'Title' in Red and False under "Official' is your problem. It wouldnt hurt to post an APUP log of the failing script as well. Also, this really is a script issue not an AutoPatcher or APUP bug. It helps to locate the failing script by following the guidelines I offered and then provide a log file of the offending script and post in the appropriate forum - for next time.
Posted 29 July 2010 - 10:44 AM
Posted 29 July 2010 - 12:40 PM
I would keep an eye on this thread, when Domenico posts 'fixed' you will need to run APUP so the new script can make the needed corrections. You will want to delete the 3 apm files mentioned in post #2 second "quote" also.
When patches become outdated and get replaced the script will get new commands to remove these files/folders - but the commands get removed at some point in time (months later) otherwise the scripts would be huge, if you wait too long these stray files can cause problems and make a release Unofficial.
So the moral of the story is - if you want AutoPatcher/APUP to work reliably for you it is best to run APUP at least 2 or 3 times a month - the big one is a few days after 'Patch Tuesday' (second Tuesday of every month), this will get the new patches and remove the old ones. The 1 or 2 additional times is to catch the typos that can show up in a script - this is part of being human, making mistakes.
You can always look at the 'Release Info' to check the date of your releases, a few expect to be old - DirectX (doesn't get updated every month), AutoPatcher (same), but XP, Vista, 7, Office - if the date is getting old you may be better off downloading from scratch or find out if a release has been abandoned.
Posted 01 August 2010 - 01:45 PM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users