Recent IE security patch kills OLE DB calls - potential fix includ

Hi, after on of our customers installed the recent IE security fix on
17/12/2008 any OLE DB traffic to our SQL server(VB5 and 6 in our case) ceased
to work, it had removed the following reg key:
[HKEY_CLASSES_ROOT\CLSID\{2048EEE6-7FA2-11D0-9E6A-00A0C9138C29}\InprocServer32]
the microsoft roll back adds the following:
[HKEY_CLASSES_ROOT\CLSID\{2048EEE6-7FA2-11D0-9E6A-00A0C9138C29}\InprocServer32]
@="%Program Files%\\Common Files\\System\\Ole DB\\oledb32.dll"
"ThreadingModel"="Both"
unfortunatly whomever coded this added a space in %program files%, the
variable should be %programfiles% which would have worked. we rolled back and
compared the reg keys, originally it was:
[HKEY_CLASSES_ROOT\CLSID\{2048EEE6-7FA2-11D0-9E6A-00A0C9138C29}\InprocServer32]
@="C:\\Program Files\\Common Files\\System\\Ole DB\\oledb32.dll"
"ThreadingModel"="Both"
either rolling back using a restore point or changing the %program files% to
the correct %programfiles% fixes the issue.

I hope this helps anyone with the same issues and hope someone from
microsoft reads this and fixes the problem before it affects anyone else.

Regards
Richard Burnett

Start a free Windows Update support incident request:
https://support.microsoft.com/oas/de...spx?gprid=6527

For home users, no-charge support is available by calling 1-866-PCSAFETY in
the United States and in Canada or by contacting your local Microsoft
subsidiary. There is no-charge for support calls that are associated with
security updates. When you call, clearly state that your problem is related
to a Security Update and cite the update's KB number (e.g., KB960714).

Support for Windows Update:
http://support.microsoft.com/gp/wusupport

For more information about how to contact your local Microsoft subsidiary
for security update support issues, visit the International Support Web
site: http://support.microsoft.com/common/international.aspx

For enterprise customers, support for security updates is available through
your usual support contacts.
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin; DTS-L.net

Trickyburn wrote:
> Hi, after on of our customers installed the recent IE security fix on
> 17/12/2008 any OLE DB traffic to our SQL server(VB5 and 6 in our case)
> ceased to work, it had removed the following reg key:
> [HKEY_CLASSES_ROOT\CLSID\{2048EEE6-7FA2-11D0-9E6A-00A0C9138C29}\InprocServer32]
> the microsoft roll back adds the following:
> [HKEY_CLASSES_ROOT\CLSID\{2048EEE6-7FA2-11D0-9E6A-00A0C9138C29}\InprocServer32]
> @="%Program Files%\\Common Files\\System\\Ole DB\\oledb32.dll"
> "ThreadingModel"="Both"
> unfortunatly whomever coded this added a space in %program files%, the
> variable should be %programfiles% which would have worked. we rolled back
> and compared the reg keys, originally it was:
> [HKEY_CLASSES_ROOT\CLSID\{2048EEE6-7FA2-11D0-9E6A-00A0C9138C29}\InprocServer32]
> @="C:\\Program Files\\Common Files\\System\\Ole DB\\oledb32.dll"
> "ThreadingModel"="Both"
> either rolling back using a restore point or changing the %program files%
> to
> the correct %programfiles% fixes the issue.
>
> I hope this helps anyone with the same issues and hope someone from
> microsoft reads this and fixes the problem before it affects anyone else.
>
> Regards
> Richard Burnett