KB891781 DHTML edit update - no such interface supported - microsoft.public.inetsdk.programming.dhtml_editing

Message from discussion KB891781 DHTML edit update - no such interface supported

David Alison

View profile

More options Feb 15 2005, 8:53 am

Newsgroups: microsoft.public.inetsdk.programming.dhtml_editing

From: "David Alison" <no_spam_drali...@hotmail.com>

Date: Tue, 15 Feb 2005 08:53:16 -0500

Local: Tues, Feb 15 2005 8:53 am

Subject: Re: KB891781 DHTML edit update - no such interface supported

  Reply to author
  |
  Forward
  | Print
  | View thread
  | Show original
  | Report this message
  | Find messages by this author
  

Hi Pat,

You are not the only one. There are a huge number of products that now do
not work as a result of KB891781 being installed. We have had to resort to
uninstalling the patch before our application starts using the following
call:

%windir%\$NtUninstallKB891781$\spuninst\spuninst.exe /quiet

The vendor of the DHTML editing control I use in Delphi (Profgrid) has told
us that Microsoft eliminated documented interfaces in this control throught
that patch. I believe that this problem will become significantly larger in
the days ahead as people begin to apply the windows patches and realize that
some of their applications do not work.

Microsoft needs to address this ASAP.

--David

"Pat Magnan" <p...@sluggo.org> wrote in message

news:a8b73b06.0502141643.242011b7@posting.google.com...

> Hi All:

> I haven't seen this exact issue posted here, but apologize if this has
> been replied to previously.

> The company I work for uses the MS DHTML edit control as our primary
> editor in our software product. Since the release of this hotfix, we
> have only developed one solution, which is to remove the update, then
> try to coerce our customer's corporate IT people to hold off deploying
> it.

> We did a little research with the DHTML edit control, and it would
> appear that many of the interfaces it exports return NULL pointers,
> specifically any interface which would return a reference to the DOM
> document. We access the object through the OCX, in a Delphi
> application, so perhaps there is a solution available to a C++
> developer that we don't currently have available.

> I know of a handful of other applications that are similarly broken,
> is there documentation available on a new method of using the
> control(s)? Is there a way to instantiate it that is 'safe' such that
> we can again access the DOM object? Running it in our application on
> the local machine doesn't seem like it should relate to 'cross site
> scripting' which is what was apparently resolved...

Reply to author Forward