This is an update to a previous Post  SharePoint, public website and name.dll ActiveX yellow bar.

Here is the fix

Open the init.js file (make a backup copy first)

Note The Init.js file is located in the %Program Files%\Common Files\Microsoft Shared\Web server extensions\12\Template\Layouts\1033 folder.

At the end of the file, find the following function

   1:  function ProcessDefaultOnLoad(onLoadFunctionNames)

   2:  {

   3:        ProcessPNGImages();

   4:        UpdateAccessibilityUI();

   5:        ProcessImn();

   6:        for (var i=0; i < onLoadFunctionNames.length; i++)

and modify it to be

   1:  function ProcessDefaultOnLoad(onLoadFunctionNames)

   2:  {

   3:        ProcessPNGImages();

   4:        UpdateAccessibilityUI();

   5:        //ProcessImn();

   6:        for (var i=0; i < onLoadFunctionNames.length; i++)

Save the file

Run IISRESET

Here is the story of how I found the fix,

So here I am again with the name.dll and my new SharePoint public web site.  First a minor rant, I have to pull up my laptop to test whether my website is asking for the name dll; Why you ask do I need to go to my laptop? well you see on my dev machine I Authorized the name.dll “for all websites”, and so far my abilities of Abduction (second usage) on Google have not helped me to find the answer of how I can rescind that permission (without having to buy someone else tool).  So I have to go to my laptop where I have not yet granted name.dll any permissions (and never well).

Well in my earlier post I thought I had solved the problem, and I had, for pages on my main home site in sharepoint that I have added and that use the default.master in the master catalog directory.  But for System Pages it still shows up, and I wasn’t aware of that until I tried to make some modifications to my site settings on my laptop and bamm! There is the Name ActiveX control warning againg. No big problem, only I can get into the setup pages, so I didn’t worry about it.  Then I decided to make a sub-site to host these development related blogs.

Five days after I have my new blog up and running (and that will be its own blog entry about the SharePoint Community Toolkit) I surf into my blog site from my laptop to post a thought, and DAMN there is that stupid name.dll activex warning DOH!

So here I go trying different fixes on the website (because the one detailed in the early post isn’t working), but that requires me to make a modification, switch to my laptop and test, my modification didn’t work, back to my dev machine, rinse – repeat. That switching back and forth gets old, so of course I have been sidetracked trying to figure out where in the registry IE stores the permissions for usage of ActiveX dlls on website(s).  I don’t mind a bug, what I get impatient about is when I need to solve stumbling blocks, that while not directly related to the real issue are interfering with my progress: I find my equanimity is severely compromised.

Putting aside for the moment the issue with finding out how to rescind a permission to an ActiveX dll in IE (see this blog entry for my solution for that problem). Let’s get back to stopping the warning in my blog.

What have I found out about this issue

• It is used by SharePoint in Intranets to allow the User Presence web part to operate and tell you, and others about your status on the SharePoint Site
• It is turned on during the PageInit JavaScript deeply embedded in core of shadowfax
• There is no way in configuration or thru site settings to disable it for a particular page or for the whole site
• Following the instructions in Fixing the name.dll ActiveX Problem the Mossman Way does not solve the issue for entire site.
• The “official” KB article from MS on this issue http://support.microsoft.com/kb/931509 has issues with it, and for many people doesn’t work.

Things just got a lot more “odd” for me.  I was trying to implement the exact steps as detailed on official 931509 KB article from MS when I hit the step that asks you change

<SharePoint:ScriptLink language="javascript" name="init.js" runat="server"/>

in the master page for the site to

<SharePoint:ScriptLink language="javascript" name="initNoPresence.js" runat="server"/>

but when I went into the master page, I couldn’t find the specified line ANYWHERE on the website.  It seemed to have just disappeared, but I was definitely getting an error.

So in desperation, I went into the init.js file and directly modified it in a hail mary pass.  and that fixed.  I can’t determine what is calling the init.js, but if I modify it directly my problem goes away.

Good enough

Back to the true issue