Tuesday, 27 April 2010

Element not found error

Back in the office after SPEVO and found I was getting javascript errors accessing our MOSS 2007 Intranet. Error:

 

Element not found

_layouts/1033/init.js?rev=ICv7xM5bvv5kFLfurJciEg%3D%3D

After working out that the init.js probably related to presence I re-installed the Office Communicator R2 client, no dice, then repaired Office 2010 (RC). All sorted now…

15 comments:

  1. Well I'll be damned. Spent ages chasing this red herring and trying to fix javascript issues. Followed your fix thinking it'll never work and it did just the trick...

    ReplyDelete
  2. The presence status was causing the error, given the new 'business card' that you get with Office 2010 installed I thought I may have to live with it until RTM, but a quick repair sorted it ;)

    Glad the post was useful to you!

    ReplyDelete
  3. Hi. Thank for the advice because i've encountered the same error too, and now i'm ok. Previously i've also tried to debug the init.js and all i could see is that it might be something with the conditional compilation of javascript in ie. In fact this was the function that threw an exception in my case:

    function EnsureIMNControl()
    {
    if (!bIMNControlInited)
    {
    if (browseris.ie5up && browseris.win32)
    {
    //@cc_on
    //@if (@_jscript_version >=5)
    //@ try
    //@ {
    //@ IMNControlObj=new ActiveXObject("Name.NameCtrl.1");
    //@ } catch(e)
    //@ {
    //@
    //@ };
    //@else
    //@end
    }
    bIMNControlInited=true;
    if (IMNControlObj)
    {
    IMNControlObj.OnStatusChange=IMNOnStatusChange;
    }
    }
    return IMNControlObj;
    }

    Without the repair of office 2010 installation the browser didn't run the code inside the comment.

    Marco

    ReplyDelete
  4. The same happened to me today. I've fixed the same way. Thanks for showing the way... :-)

    ReplyDelete
  5. Someone should really give you a big hug. I too spend a lot of time trying to solve this error message, figuring that it would be connected to either IE or Java installation. No luck until I read this blog. A simple repair of the office 2010 installation solved the issue.

    ReplyDelete
  6. Thanks for your kind comments everyone, especially Erik, although I'm not sure about the hugging ;)

    ReplyDelete
  7. Matt, awesome, luckily yours was the first article that I've come across ... hug is warranted :)

    ReplyDelete
  8. Amazing. Worked like a charm. Many thanks!

    ReplyDelete
  9. A colleague and I have been chasing the same problem today - we were focusing on IE8 and Java. After finding your post a quick repair to Office 2007 did the trick. Thanks!

    ReplyDelete
  10. When you say repair MS Office, what does that mean? Diagnostics Tool? re-install? Something else? Thanks!

    ReplyDelete
  11. I mean insert DVD (or ISO, etc) and when setup runs, select "repair" (I think you can do the same from add/remove programs).
    HTH

    ReplyDelete
  12. Thank you so much!! We've been chasing this issue for weeks.

    This was very useful.

    ReplyDelete
  13. Thanks much! It worked for me also. Strange in IE 9 and IE 8 this was a problem with the 32 bit version but not the 64 bit version. I guess its because I have 32 bit Office 2007/2010 installed??

    ReplyDelete
  14. Hello,
    The same for me, Office 2010 installed on my PC, and when viewing MOSS 2007 pages, then I got the same error message, and now after a repair, all's good, thank you.

    ReplyDelete

Please feel free to comment on this post, I want to hear your feedback!