|
|
|
Rank: Member
Groups: Registered
Joined: 2/12/2014
Posts: 3
|
Hi All,
We are having rapidspell spellchecker for web in our application. There are some users facing issue of empty popup.
When they click on spellcheck, the pop window shows up as blank and says done.
Is this a known issue?
Looking forward to any suggestion to triage further...
Thank,
Jaydip
|
|
|
|
Rank: Member
Groups: Registered
Joined: 4/22/2006
Posts: 216
|
Hi Jaydip, the only way I've seen that before is with cross domain issues - such as if you specify document.domain, but this typically affects everyone. Have you found anything in common with the affected users, such as browser version? Or location (eg off site)? Are there any Javascript errors? Regards, -Harry -Harry
|
|
|
|
Rank: Member
Groups: Registered
Joined: 2/12/2014
Posts: 3
|
Hi Harry,
I found that only few users at one location are getting this error(it works for some users at same location too). They are having IE8.
Yes, there is a JS error on rapidspelllauncher.js.
Message: The tag is invalid.
Line: 157
Char: 5
Code: 0
The line#157 is inside function RS_writeDoc(toWindow){
toWindow.document.open();
any clue?
~Jaydip
|
|
|
|
Rank: Member
Groups: Registered
Joined: 4/22/2006
Posts: 216
|
Hi Jaydip, please see http://social.msdn.micro...?forum=iewebdevelopment
Specifically the last 3 posts quote:
Question
Vote as helpful
0
Vote
DOCOBJ.DLL that comes with older MS Office programs (97) has the same handler as IEPROXY.DLL does. When you install Office 97 after IE 8 is installed then DOCOBJ.dll gets registered and breaks document.open() code. Close your browsers, unregister C:\Windows\SYSWOW64\DOCOBJ.DLL as the local admin and then register "C:\Program Files (x86)\Internet Explorer\IEPROXY.DLL". That fixes it for us.
Proposed as answer by Tundra Tuesday, February 08, 2011 4:12 PM
Thursday, January 06, 2011 8:00 PM
Reply | Quote |
Report as abuse
Avatar of TEK Man
TEK Man0 Points
Question
Vote as helpful
1
Vote
Unregistering the docobj.ll and reregistering the ieproxy.dll is the answer to this problem. I've spent many days on this attempting many code changes to one of our applications but to no avail. It doesn't appear that unregistering docobj.dll hurts anything. Use "regsvr32 docobj.dll -u" to unregister in the directory that contains it, and then go to the Internet Explorer directory (as mentioned above) and re-register ieproxy.com with "regsvr32 ieproxy.dll".
This also fixed any other application that is broken because of the Window.Open being used. The fix is completely unrelated to the problem so I'm amazed anyone figured it out.
The reason that reformatting or reimaging you drive fixes it is because you've deleted the problem dll.
Tuesday, February 08, 2011 4:18 PM
Reply | Quote | Propose as answer |
Report as abuse
Avatar of Tundra
Tundra5 Points
Question
Vote as helpful
0
Vote
When I did this register and unregister the machine crashed.
--Lesson Learned - This will happen if the correct DLL is not registered. Older version of the dll was registered and that caused this issue. Otherwise the fix seems to work correctly.
Thanks
MM
Looks like you have to do some work on those client machines to repair them. -Harry -Harry
|
|
|
|
Rank: Member
Groups: Registered
Joined: 2/12/2014
Posts: 3
|
Thanks a bunch Harry!!
This will be really useful..I am gonna try re-installing IE itself..
|
|
|
