Del via


Hotfix - After installing MS07-045 Cumulative Security Update for Internet Explorer - CreateObject call fails with 8000ffff

I had reported an issue which happens after installing MS07-045 IE security update.
"After installing MS07-045 Cumulative Security Update for Internet Explorer - CreateObject call fails with 8000ffff "

We have a hotfix available for the same and it's KB 945701. KB is not yet available (as of today) and it might take a while to be public.

If you are struggling with this issue you can call PSS and request for the hotfix. It should be publically available during next IE patch schedule.

Comments

  • Anonymous
    December 23, 2007
    PingBack from http://internet-explorer-update.blogyblog.info/?p=170

  • Anonymous
    April 14, 2008
    We are currently running a Digital Asset Management web application called MediaBin.  The supplier is Interwoven.  MediaBin periodically runs slow and I have to restart IIS to get it to run normal.  I was told by Interwoven that the Hotfix will resolve the problem.  Can you tell me how I could get a copy of the Hotfix?

  • Anonymous
    April 14, 2008
    I'm not sure if this hotfix would resolve your performance problem. Please call Microsoft PSS to get the hotfix which should be free.

  • Anonymous
    April 21, 2008
    The comment has been removed

  • Anonymous
    April 26, 2008
    That message "The file does not begin with PDF%" sounds like a custom error message from some application. I don't see any relation with that error message and the hotfix!

  • Anonymous
    May 06, 2008
    Apparently the core problem is that IUSR loses read permissions to a registry key. Details (enough to fix without obtaining the hotfix) here: http://weblog.ikvm.net/PermaLink.aspx?guid=9bdc9af1-7f46-482e-bd5a-aed5fe82a2f5

  • Anonymous
    May 06, 2008
    I have already mentioned workaround in my previous post here http://blogs.msdn.com/sukeshak/archive/2007/09/18/installing-ms07-045-cumulative-security-update-for-internet-explorer-createobject-call-fails-with-8000ffff.aspx I guess the patch also includes a registry key addition to make sure it's restricted to w3wp.exe. Downloading a patch from an unknown site might get you into trouble. The correct way to fix the issue is to install the patch related to the KB mentioned above.