It does not "just get rid of the update". It replaces information that
/should/ have been there all along, but that "something" removed (and should
not have).

The update is a physical file stored in the filesystem.

This information tells the system how to find the ole32.dll file so that it
can, among other things, properly display ActiveX controls.

If the Brio is /not/ working after you insert this registry mod, then you
definitely need to have a heart-to-heart soapbox-standing discussion with Brio
as to why their client is incompatible with the standard configuration of the
operating system.

I'll repeat PA Bear's question, and add my own:
"Who is this 'Microsoft guy'"?
"Who is your "technical support microsoft contact".

And, next time you talk to them.. tell them to read KB909889, where this exact
fix is documented as the "official" Microsoft resolution for issues caused by
the installation of KB896688 on systems such as yours.


"Nikikelly" <Nikikelly@discussions.microsoft.com> wrote in message
news:9E23B786-9536-4032-BB1B-82066BDABDB2@microsoft.com...
> This is the one that everyone seems to be going with but my technical
> support
> microsoft contact says it just gets rid of the update:
>
> [HKEY_CLASSES_ROOT\CLSID\{0000031A-0000-0000-C000-000000000046}]
> @="ClassMoniker"
>
> [HKEY_CLASSES_ROOT\CLSID\{0000031A-0000-0000-C000-000000000046}\InprocServer32]
> @="ole32.dll"
>
> [HKEY_CLASSES_ROOT\CLSID\{0000031A-0000-0000-C000-000000000046}\ProgID]
> @="clsid"
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\CLSID]
> @="{0000031A-0000-0000-C000-000000000046}"
>
> So, what they are recommending is to recompile the activeX at the server
> level or make changes to your registry at the client level...since we need
> to
> make it at the server level and our activeX is part of Brio's enterprise
> solution, we're at their mercy for fixing the problem.
>
> "PA Bear" wrote:
>
>> To what "registry change...suggested here" are you referring?
>>
>> Who's this "Microsoft guy"?
>>
>> > So, my question now is, what is the CLSID of the control used by Brio?
>>
>> Have you asked Brio (now owned by Hyperion) Support?
>> http://www.brio.com/solutions/
>>
>> cf. http://support.microsoft.com/kb/909738 and
>> http://support.microsoft.com/?kbid=909889
>> --
>> ~Robear Dyer (PA Bear)
>> MS MVP-Windows (IE/OE, Shell/User, Security), AH-VSOP
>>
>>
>> Nikikelly wrote:
>> > I am running Brio Performance Suite 6.6 - ActiveX is not loading when
>> > document link is chosen from the Brio Documents Explorer. I checked with
>> > my Microsoft guy before implementing the registry change that is being
>> > suggested here and he says that's NOT the answer. The fix is to use one
>> > of the following registry values to mark the ActiveX control as safe for
>> > scripting and safe for initialization:
>> > â?¢ {7DD95801-9882-11CF-9FA9-00AA006C42C4}
>> > â?¢ {7DD95802-9882-11CF-9FA9-00AA006C42C4}
>> >
>> > For example, if the CLSID for the ActiveX control is
>> > {A697E83F-3B53-11D1-8AE4-006097ED2008}, you can add one of the following
>> > registry values to mark the ActiveX control as safe for scripting and
>> > safe
>> > for initialization:
>> >
>> > â?¢
>> > HKEY_CLASSES_ROOT\CLSID\{A697E83F-3B53-11D1-8AE4-006097ED2008}\Implemented
>> > Categories\{7DD95801-9882-11CF-9FA9-00AA006C42C4}
>> > â?¢
>> > HKEY_CLASSES_ROOT\CLSID\{A697E83F-3B53-11D1-8AE4-006097ED2008}\Implemented
>> > Categories\{7DD95802-9882-11CF-9FA9-00AA006C42C4}
>> >
>> > So, my question now is, what is the CLSID of the control used by Brio?
>> >
>> > Nicole
>> >
>> > "ybredybred" wrote:
>> >
>> > > Do you happen to be running Hyperion Financial Management software on
>> > > these machines? We are running into this problem in my company,
>> > > however the problem only appears to be on machines running HFM.
>> > >
>> > > Thanks
>>
>>