Recently, I was installing/uninstalling too many programs on my machine that amazingly broke the Live Update feature of my Symantec Antivirus product. Here’s the error message I’ve received:

LU1805: LiveUpdate was unable to find any products to Update…

I just searched for the LU1805 on the net, and I found this article describing how to resolve the issue. I followed the instructions but unfortunately I received the same error message again. On the other hand, I’ve noticed that SQL Server 2005‘s “Copy Database Wizard” simply doesn’t work, giving me strange error messages over and over again. e..g, “Library not registered”, “QI for IEnumVARIANT failed” and the like.

The latter error message gave me a hint, that probably one of those programs I’ve already uninstalled has caused this problem. So I searched for the IEnumVARIANT definition on the registry, but I didn’t find any entry.

Thus, I created a text file named UpdateRegistry.reg, containing the following lines:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINESOFTWAREClassesInterface{00020404-0000-0000-C000-000000000046}]@="IEnumVARIANT"
[HKEY_LOCAL_MACHINESOFTWAREClassesInterface{00020404-0000-0000-C000-000000000046}NumMethods]@="7"
[HKEY_LOCAL_MACHINESOFTWAREClassesInterface{00020404-0000-0000-C000-000000000046}ProxyStubClsid]@="{00020421-0000-0000-C000-000000000046}"
[HKEY_LOCAL_MACHINESOFTWAREClassesInterface{00020404-0000-0000-C000-000000000046}ProxyStubClsid32]@="{00020421-0000-0000-C000-000000000046}"

Thereafter, I ran the file to attach those definitions to my registry settings. The good news, Norton Antivirus started to function. However, there was still one unresolved problem with SQL Server, the “Library not registered” on the “Copy Database Wizard”… I finally managed how to fix the problem. To do so, I registered the latest version of XML Parser already on my machine, say, msxml6.dll, using the following command entered in the “WindowsSystem32″ directory:

regsvr32 msxml6.dll

This amazingly, solved the issue.

 

10 Responses to LU1805, Library not registered and QI for IEnumVARIANT failed!

  1. This is amazing and it also works with Symantic Antivirus corporate edition 10.2

    Thanks Dude
    Uttam

  2. lautamas says:

    Incredible!! You are just so genius!! I have been looking for this unofficial patch for so long. Even after Endpoint Security MR1 (11.0.1000.1375) was released, Symantec never learns to patch this mistake. Again.>Thank you very much!

  3. Luke says:

    It worked for me too!!! Thanks man.

  4. Anonymous says:

    Thanks for the good work. You’ve saved me.

  5. Anonymous says:

    Amazing detective work!

    This worked for me for Symantec Corporate A/V 10.1.5.5000 which had begun failing LiveUpdate with LU1805 as well.

    Congratulations!
    -Bob R.

  6. Anonymous says:

    My SQL Server 2005 randomly started producing this error after some updates and I tried to run the Copy Database Wizard.

    I registered the msxml6.dll file as recommended and the problem disappeared.

    Many thanks for blog.

  7. Anonymous says:

    Many thanks – this worked for BackupExec 12.5 too…

    Why is the Symantec support site so useless? I guess it’s like the rest of the company.

  8. Anonymous says:

    So your Windows installation is corrupt to the point where Microsoft’s own SQL Server software doesn’t even work, and you’re blaming Symantec? I think you ought to be looking into what left your registry in a bad state in the first place, and complain to them to fix it. If IEnumVariant got clobbered, I can only wonder what other bizzare, hard to find issues you will have on that system.

  9. Anonymous says:

    Thanks that worked for me too!. Your notes:
    …one unresolved problem with SQL Server, the “Library not registered” on the “Copy Database Wizard”… I finally managed how to fix the problem. To do so, I registered the latest version of XML Parser already on my machine, say, msxml6.dll, using the following command entered in the “WindowsSystem32” directory:

    regsvr32 msxml6.dll

  10. Anonymous says:

    Thanks a lot… It saved me..

Leave a Reply

Your email address will not be published. Required fields are marked *

Recent Tweets

Rubber horse attack? Seriously? It's Rubber hose dudes! #security #fail

Sponsors