AutoPatcher Forum

.NET Framework 4.0 beta 1 has been released.

I know you don't add betas to AutoPatcher but I figured I'd better mention that after I installed it AutoPatcher would not start. Got a Yikes! AutoPatcher is confused, here's part of 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.5764
Windows Media Player: 11.0.5721.5260
.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

Figured I'd mention it as I expect others may run into problems too.

More info:

Ran APUP to see if anything had been updated/changed - no difference when AutoPatcher was run; same error message

Turned on my #2 system, installed .NET Framework 4.0 beta 1 - same results, same error message.

So, I would say that anyone that installed the new .NET Framework will not have success with AutoPatcher.

This might be another issue only Antonis can address by updating the code in AutoPatcher. I'm sure Cristiano
will know if this is code related, or maybe just a beta bug?

Mike

yep, that is another issue that only can be solved by updating autopatcher.exe code. and worst, this situation is worst than the one with windows live messenger 14

of course, this could be an beta bug too, but i'm thinking more about it also an code issue than an beta bug

i will wait for antonis at msn, but reach him is a problem, due our timezone

[]s

i was forgetting to report... antonis was warned about the issue with .net 4 and also about the issue with windows live messenger 14. but there's another big issue, that he also was warned about: windows seven. i have an hd running seven rc1 at home and i did some testes with it. autopatcher runs ok, but can't detect the OS, meaning that autopatcher.exe needs to be updated in order to work ok with seven. also, i've taken the main registry detections for seven and i've sent to him.

in our talk at msn, he said that will investigate all those issues and fix the code soon

again, thanks for your report

[]s

Houston, we have a problem... i've talked with antonis a few minutes ago. he said this:

Quote

it may not be fully related to .net 4 beta 1, but more tests will be required. i will try the same test tonight, in my english xp vm, that has all current updates applied.

in mean time, more details about the issue are welcome, like any custom module that may be at autopatcher folder and/or any other possible hint that may help to track the issue in any way is welcome

[]s

DesertJerry, my friend, we really will require more info about your system. i've installed .net 4 sp1 into my english vm, fully updated. it worked. the first log was taken before .net 4:

AutoPatcher 5.6 loaded the filesystem.

Detected English (1033) Windows XP Professional Service Pack 3

System Components:
	Internet Explorer: 8.0.6001.18702
	Windows Media Player: 11.0.5721.5260
	.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: 
	Microsoft Excel: 
	Microsoft PowerPoint: 
	Microsoft Outlook: 
	Microsoft Access: 
	Microsoft Project: 
	Microsoft Publisher: 
	Microsoft OneNote: 
	Microsoft FrontPage: 
	Microsoft InfoPath: 
	Microsoft Visio: 
	Microsoft SharePoint Designer: 
	Microsoft Groove:

this 2nd log was taken after .net 4:

AutoPatcher 5.6 loaded the filesystem.

Detected English (1033) Windows XP Professional Service Pack 3

System Components:
	Internet Explorer: 8.0.6001.18702
	Windows Media Player: 11.0.5721.5260
	.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
	DirectX: 4.09.00.0904
	MSN/Live Messenger: 

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

so, i'm unable to duplicate the issue in here too. but you may have found one, so we really will need more infos about your system and installed software

thanks in advance

[]s

Cristiano,

Ran APUP a few minutes ago, updates were mainly AutoPatcher Office 2007 SP2 items, from what I could tell.

Started AutoPatcher, same yikes!, error log follows:

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.5764
Windows Media Player: 11.0.5721.5260
.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
DirectX: 4.09.00.0904
MSN/Live Messenger: 6.1.0.207

Office Components:
Microsoft Word: 11.0.8237.0
Microsoft Excel: 11.0.8302.0
Microsoft PowerPoint: 11.0.8307.0
Microsoft Outlook: 11.0.8217.0
Microsoft Access: 11.0.8166.0
Microsoft Project:
Microsoft Publisher: 11.0.8212.0
Microsoft OneNote:
Microsoft FrontPage:
Microsoft InfoPath: 11.0.8307.0
Microsoft Visio:
Microsoft SharePoint Designer:
Microsoft Groove:


So, what other info is it you need? Hardware, software, etc?

Another item,

I had the same error on both of my systems, which do not have the same hardware so that cannot or should not be an issue.

The other main difference betwen them is #1 has Office Pro 2003 and #2 has Office Pro XP, so that would introduce differences between them also.

DesertJerry, if i'm not mistaken, when yikes happen, there's an button or something that returns an extra info, but i'm not sure (i don't see that screen since long ago). also, if possible, can you sent me all the .apm files that you have in any of those machines (compressed, of course)? my email is at your pms. it may be nothing, but there's certain mistakes in the .apm files that can do that too

thanks in advance

[]s

Cristiano, on May 26 2009, 11:22 AM, said:

Yikes! (at top) includes the statement 'press ctrl+c to copy to clipboard'
I did that and got this:

What AutoPatcher was trying to do
It appears that the error occured while AutoPatcher was trying to determine if a module's property is compatible with the running component.

Where: mdlModuleLoading.isPropertyCompatible()
Error Code: 0xD: Type mismatch

Below that are two buttons: Show Log and Quit.

Clicking Show Log got me:
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.5764
Windows Media Player: 11.0.5721.5260
.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
DirectX: 4.09.00.0904
MSN/Live Messenger: 6.1.0.207

Office Components:
Microsoft Word: 11.0.8237.0
Microsoft Excel: 11.0.8302.0
Microsoft PowerPoint: 11.0.8307.0
Microsoft Outlook: 11.0.8217.0
Microsoft Access: 11.0.8166.0
Microsoft Project:
Microsoft Publisher: 11.0.8212.0
Microsoft OneNote:
Microsoft FrontPage:
Microsoft InfoPath: 11.0.8307.0
Microsoft Visio:
Microsoft SharePoint Designer:
Microsoft Groove:

which is the same info as yesterday.

Select Quit and AutoPatcher ends/exits.

ALL the .APM files? Really? I checked using search, there are 432 files (838,621 bytes)

OK - they are on the way - APMFiles.zip 478,501

size isn't a problem, but i will be able to run my enu vm just in 18h from now. it's almost 2am in here

[]s

the issue seems be pointing to some .apm issues. we will investigate this deeper.

[]s

An update on this issue:

Both Cristiano and I have spent considerable time looking at this problem. There is a problem with AutoPatcher.exe itself, which we cannot fix in the short-term.

However, it has emerged that there are major problems with the .NET 4 Beta 1, reported by Microsoft, including an incompatibility with Office 2007 (you have to UNinstall BOTH products to fix this). Also, if you install .NET 4 Beta 1 on Vista you CANNOT upgrade to Windows 7.

My recommendation: UNinstall .NET 4 Beta 1, ASAP.
(By the time Microsoft have their bugs ironed out, we might have fixed AutoPatcher, too!)

==
Edited by James, 15 August 2009 - 07:34 AM.

Cristiano and I did some troubleshooting and the issue was with some APMs - these at first:
clip_enu.apm
gsexcel07_enu.apm
gspowerpoint07_enu.apm
gsword07_enu.apm
offaddons_clip_enu.apm

As of ten minutes ago running APUP and AutoPatcher the yikes is gone and .NET 4 beta is still installed.

DesertJerry, on 16 August 2009 - 04:18 AM, said:

Yes, I am aware of that.

Actually the issue is with AutoPatcher.exe, not with the APM's. Cristiano has "fixed" the APMs to stop the Yikes error, but the issue is still there.

==