Microsoft Windows Vista Community Forums - Vistaheads
Recommended Download



Welcome to the Microsoft Windows Vista Community Forums - Vistaheads, YOUR Largest Resource for Windows Vista related information.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so , join our community today!

If you have any problems with the registration process or your account login, please contact us.

Driver Scanner

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

microsoft.public.internetexplorer.general






Speedup My PC
Reply
  #1 (permalink)  
Old 12-19-2008
Trickyburn
 

Posts: n/a
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
Reply With Quote
Sponsored Links
  #2 (permalink)  
Old 12-19-2008
PA Bear [MS MVP]
 

Posts: n/a
Re: Recent IE security patch kills OLE DB calls - potential fix includ
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


Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
RSS feeds: unspecified potential security risk Ildhund microsoft.public.internetexplorer.general 6 11-24-2008 19:37
Security experts warn of potential malicious AIR code Steve Security News 0 02-27-2008 03:20
Researcher sees potential iPhone security problems Steve Security News 0 09-21-2007 13:51
Security World: Bank changes its name, phishers smell the potential Steve Security News 0 08-09-2007 20:25
Security Audit Reveals Threat Potential Paul Security News 0 05-01-2007 14:49




All times are GMT +1. The time now is 17:44.




Driver Scanner - Free Scan Now

Vistaheads.com is part of the Heads Network. See also XPHeads.com , Win7Heads.com and Win8Heads.com.


Design by Vjacheslav Trushkin for phpBBStyles.com.
Powered by vBulletin® Version 3.6.7
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.6.0 RC 2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120