Error updating wyBuild from 2.6.3.1 to 2.6.4

I received the following error when I tried to update:

Unable to cast COM object of type 'wyUpdate.ShellLink' to interface type 'wyUpdate.IPersistFile'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{0000010B-0000-0000-C000-000000000046}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

I've had issues updating in the past, even downloading the newest wyBuild-setup.exe. Something is funny about our firewall (Astaro), and it (the firewall) often says "unsupported archive format encountered" when I try to download wyBuild-setup.exe directly. For some reason, it had no problem with directly downloading 2.6.3.1 earlier this week, but it doesn't like 2.6.4 again. That might be why the update failed.

So if this is purely a firewall issue, feel free to ignore it. I don't know enough about COM to tell whether the issue is on my end or yours.

I'll check into it. But I've never seen these errors before - and we haven't changed anything with shortcut creation in the last year (that's what the COM exception is complaining about). Also, I've just checked our wybuild-setup.exe and it validates as still being signed:

[attachment=0]Digital Signature Details.png[/attachment]

If you right click the setup, and it shows it's no longer signed, then something corrupted it along the way.

I've checked updating from 2.6.3.1 to 2.6.4 and it works fine for me. Also, what OS (Windows 7 x64?) are you running?

I tried downloading the full setup again, and this time it came in fine. For clarification, the error about the archive format occurs on the dedicated firewall hardware we have, so all I see is an error page -- I'm not allowed to download the file. But then I tried updating through wyBuild, and I received the same COM error as before. So, I have 2.6.4 available now, but not through an update. I still think it's possibly a firewall issue, but I don't have the means to look at the logs to verify that.

I'm running Windows XP 32-bit.

On a side note, where has Wyatt been? Don't get me wrong, Sam, you're very helpful on your own -- I was just curious as to why he hasn't been on the forums for what seems like several weeks now.

On a side note, where has Wyatt been? Don't get me wrong, Sam, you're very helpful on your own -- I was just curious as to why he hasn't been on the forums for what seems like several weeks now.

I'm still here.

I'll try to reproduce your errors on our XP machines - there's no reason a firewall would interfere with COM operations. Either it's a bug or an agressive anti-virus program is interfering.

Unable to cast COM object of type 'wyUpdate.ShellLink' to interface type 'wyUpdate.IPersistFile'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{0000010B-0000-0000-C000-000000000046}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

OK, I've looked into this. These COM interfaces have existed since before Windows 2000. And I've even tried multiple ways of reproducing this when upgrading from 2.6.3.1 to 2.6.4 - and every time the update succeeds perfectly (testing on XP x86, XP x64, Vista x86/x64, and Windows 7 x86/x64).

Also, we're creating the COM objects correctly (we're not using any hacky coding tricks).

Were you, by any chance, in the middle of a Windows Update (during install, or after install but before restart)? The reason I ask is that I'm looking for ways your system might be in an unstable state where a call to a common interface "IPersistFile" fails.

I'll continue looking for ways to reproduce this.

As far as I'm aware, there were no pending Windows updates at the time. But I can't be 100% sure about it.

Reply
Discard post