Sametime client install causes IE7 error - SPR# NRID7FXP9W
Victor Toal July 9 2008 09:36:38 AM
I just came across a new error that I have never seen in Sametime and thought I would just throw it up on my blog. There is an SPR in IBM out for it but I am not sure if anybody else has come across it as of now There is an internal technote on it but I have yet to find anything on IBM's support site.Here the issue:
- You have IE7 installed on a client machine
- You install the Sametime client (technote says 7.5.1 CF1 but we actually had it happen with ST Connect 8.0.1)
- After you install you try to use IE and it fails on many sites, due to scripting errors
What has happened:
The registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{EAB22AC0-30C1-11CF-A7EB-0000C05BAE0B}\1.1\0\win32]
was changed from
@="C:\\WINDOWS\\system32\\ieframe.dll"
to:
@="C:\\WINDOWS\\system32\\shdocvw.dll"
Solution:
Changing it back to the original entry fixes the issue.
The change seems to be done by InstallShield and it depends on the version of IS what it sets this to. Also, it only seems to happen IF there is a value set in that registry entry in the first place. I am trying to get a virgin install of IE to verify what value a "normal" IE7 installation would be set to.
My investigation:
How did we notice:
After the install, all users could suddenly not log-in to their secure websites using IE7 anymore. The client uses SiteMinder and allot of other security on the desktop so it was noticed right away.
I had a look and my machine (XP, ST8.0.1 AND ST 7.5.1 CF1 installed) has that registry key in it but it has no value set (my private machine that is). This is my private machine and my current client does have an entry there for some locations. The ieframe.dll is a MS file that is used for script injection. Not everybody uses this and even if this registry entry is changed, it does not always result in an error. It looks like to me that Is is only changing the value if there is an entry there in the first place. With my current client there are many departments that have this changed value and are not experiencing any issues whatsoever.
Here some helpful links and info:
Info on shdocvw.dll
http://www.auditmypc.com/process/shdocvw.asp
A security alert for ieframe.dll
http://www.securityfocus.com/bid/28581/info
A MS Forum discussion from 2006 that shows that there were some problems back then with VB scripts executing ... interesting for background info
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=843101&SiteID=1
Another MS forum thread from 2007 that shows some issues, and some of the solution there is to turn off the Phishing filter in IE7 ... we will have a look at this further down the line, right now we just change the registry entry back and it works.
http://www.technologyquestions.com/technology/internet-explorer/112882-windows-update-killed-ie7-navcancl-ieframe-dll-error.html?q=internet-explorer/112882-windows-update-killed-ie7-navcancl-ieframe-dll-error.html
- Comments [2]
