SharePoint Products > SharePoint Products and Technologies Forums > SharePoint - General Question and Answers and Discussion (pre-SharePoint 2010) > For a WSS 2.0 site, the Edit DropDown menu doesn't appear on the Shared Documents page
Ask a questionAsk a question
 

AnswerFor a WSS 2.0 site, the Edit DropDown menu doesn't appear on the Shared Documents page

  • Thursday, July 23, 2009 4:52 PMRKHenry Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I'm getting reports from some users that the dropdown menu for each item in the "name" column in the Shared Documents page doesn't appear. This is the menu that lists options "View Properties," "Edit Properties," "Edit in Word," etc. A grey box appears around the item and a button appears, but no dropdown menu appears.

    • For affected users, the Internet Explorer Status Bar displays "errors on page" and the error is "Object Required" on "Allitems.aspx" on line 12129
    • We've tried clearing browser caches and history -- no effect.
    • One user downgraded from IE8 back to IE7 -- no effect.
    • Not all users are affected. My own machine / IE browser displays the page correctly -- I can't duplicate the error.
    • One user's machine used to display the menu correctly but now does not. I haven't been able to identify changes that might have caused it.
    • Affected users have the same problem with other sites on the same server.
    • One affected user demonstrated that he could connect to a similar SharePoint site on another server and that it properly displayed the dropdown menus on that site.
    • While the menu in the "name" column doesn't appear for affected users, the menu for user names in the "modified" column does appear.
    • The site was built from a standard template. I'm unaware of any modifications using an editor like SP Designer.
    • SharePoint 2.0 on Windows 2003 Server.
    • Client machines are typically Windows XP with all SPs installed.

    Can anyone suggest how I can help these users?
    I've wondered if a toolbar or other IE add-on could cause this. We've tried disabling some add-ons, I assume we can trust add-ons from Microsoft.

Answers

  • Wednesday, December 02, 2009 5:35 PMSkurfur Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    For me, the problem was the User Agent string being too long or nested.  I don't know which, but I had both and I knew I wanted to cleanup both. 

    Scenario:

    SharePoint drop down not working.
      Error:  Object Expected , Line <don't remember>, Char <don't remember>, from the m = CMenu() function in the ows.js script.  But this type of error can come from other functions as well so your workstation's exact error may not be from the CMenu() function.

      Troubleshooting, I tried - Uninstall IE8, install IE8, security settings to low, added SharePoint URL to trusted, compatibility view, delete temp files (Disk Cleanup).  No dice.

      I read from a couple posts that the problem could be from SharePoint not detecting my browser as IE and thus not including the necessary dependent files (i.e. the one that had the CMenu() function).  I thought I might need to fiddle with my User Agent string, but first needed to verify the problem.

    Verify problem steps:
      1. Login on another computer that is known to work.
      2. Go to SharePoint site.
      3. View Source ( my problem computer was also missing a registry key that let Notepad view the source so it showed the Desktop folder instead, but I digress).
      4. Save Source as working.html.
      4.5 View and save the User Agent string by going to a website that automatically detects your user agent string.  I used http://user-agent-string.info/ but if you don't like that one Google or Bing for another.
      5. Do steps 1-4 on the problem workstation, but save file as problem.html .
      6. Compare the two html sources.  I used WinMerge, an excellent and free tool, (Google or Bing for it).
      7. View the results and use your judgement.  Look for **any** differences. 
        a. I huge clue is non-ie html tag in the source of the problem computer <SCRIPT language='javascript' src='/_layouts/1033/non_ie.js'></SCRIPT>.
        b. A few lines later after the non_ie.js html tag, I see that my problem computer was missing a huge chunk of dependency calls to other files... Menu.css and Menu.js .

    <link href="/_layouts/1033/styles/Menu.css" rel="stylesheet"/><style type="text/css">
    .ms-SrvMenuUI { behavior:url("/_layouts/1033/Menu.htc"); }
    </style><script src="/_layouts/1033/Menu.js" type="text/JavaScript" language="JavaScript"></script><script type="text/JavaScript" language="JavaScript">
    <!--
    var L_Menu_BaseUrl=http://sharepoint-hidden/to/protect/;
    var L_Menu_LCID="1033";
    var L_Menu_SiteTheme="arctic";
    //-->
    </script>

     <SCRIPT LANGUAGE='JavaScript' >
    <!--
    //-->
    </SCRIPT>

    Conclusion is the call to the problem function, CMenu in my case, is probably not working because it is hidden in Menu.js and it's not getting invited to the html party.

      8. Compare the two User Agent strings.  If they're vastly different, then that might be the problem.

    My Solution:

    Fix the user agent string.  (Google or Bing for the fix).

    IE7 User Agent String

    WAS:

      Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; MS-RTC LM 8)

    IS:

      Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; InfoPath.1; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; MS-RTC LM 8)

    I removed the Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; .NET CLR 1.1.4322; .NET CLR 2.0.50727; with Regedit (be sure to export the keys as backup before deleting).  Maybe your solution is different, but figuring out if the problem is SharePoint is detecting your IE browser as an IE browser is a great first step.

    Good job to charhall for pointing you in the right direction.  I hope others will find this post, not spend 4 hours troubleshooting like I did, and I'll get good IT karma.

    Peace.

All Replies

  • Thursday, July 23, 2009 6:52 PMMike Walsh MVPMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    >SharePoint 2.0 on Windows 2003 Server.

    This should really be highlighted and included in the Title because as it is a back product people reading the original Title will assume WSS 3.0 or MOSS 2007.

    I'll add it to the Title with the small problem that there are two "SharePoint 2.0" products, so I'll need to guess that you mean WSS 2.0.
    WSS FAQ sites: http://wssv2faq.mindsharp.com and http://wssv3faq.mindsharp.com
    Total list of WSS 3.0 / MOSS 2007 Books (including foreign language) http://wssv3faq.mindsharp.com/Lists/v3%20WSS%20FAQ/V%20Books.aspx
  • Thursday, September 24, 2009 4:43 PMEricATCorpo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hey,
    I have the same issue. I'm running IE 7.0.5730.13 with WSS 2.0 and for about 2 months now I can no longer customize the Shared views or get the properties drop-down menu on items. Where I use to have the link on the upper right that allowed me to customize the shared view, I now only see a link that says "Click to modify this page for all users", but when I click i can't do anything more. Since it started All my web parts are showing in boxes. When I try to use the Edit in spreadsheet, I click on the button and the page refresh but doesn't display as a Spreadsheet. Please help.
  • Friday, October 02, 2009 1:27 PMBrian1050 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hey,

    Has anyone found the cause of the problem.  I have the same issue.  I have tried removeing IE 8 with no success.  I have disabled all add ons and the problem still persists.  This is only happening on 2 workstations.  All other computer are working fine.  Any help is much appreciated. 
  • Wednesday, October 28, 2009 6:16 PMcharhall Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I have been having the same problem for several months now and am not having any luck finding the solution.  If there are any SharePoint gurus out there who know why this is happening, please post a response here.  Instead of being able to edit our web parts, I can only toggle between "Click to modify this page for all users" or "Click to modify this page only for me" and nothing else.
  • Thursday, October 29, 2009 7:09 PMcharhall Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I finally found an answer to this problem (for me anyway) and I am trying to post the solution in all of the forums where people asked about it.

    Click on START> RUN then type REGEDIT.

    The registry editor will open.  Browse to the following:

    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\User Agent

    Remove all lines except the following:

    .NET CLR 1.1.4322
    .NET CLR 2.0.50727
    .NET CLR 3.5.30729

    Then restart Internet Explorer and go into your SharePoint page and hopefully the problem will be solved for you too.

  • Friday, October 30, 2009 5:57 PMEricATCorpo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi,
    I don't have a folder named User Agent at the specified location, I only have an entry named User Agent under Internet Settings adn the value is not like you said.
  • Wednesday, November 25, 2009 2:46 AMzneiley Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I found a similar article with this response on another page.  Thank you for posting because many times there are no responses when it is fixed.  That being said, I've seen previous problems with IE7 with specific tool bars being used that are not from Microsoft.  Even some random tool bars from other apps will cause problems.  As soon as you remove them, it corrects itself.

    However, my problem started as soon as we had an MS push of IE8.  Our dept is having problems with using Sharepoint 2003 in Explorer view.  It thinks an unsupported version of IE is loaded and says that version 5.5 or higher needs to be installed.  So, based on this problem, I decided to revert back to IE7 and uninstall IE8.  When I did this, I started seeing the problem described in  these articles. 

    I did check the registery and found this location, however, I only have one setting for User Agent which is a default with no value set. 

    Has anyone found anything else other than "extra tool bars" or this registry setting that may cause the problem?  It's really causing me to lose quite a bit of time trying to resolve the problem.
  • Wednesday, December 02, 2009 5:35 PMSkurfur Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    For me, the problem was the User Agent string being too long or nested.  I don't know which, but I had both and I knew I wanted to cleanup both. 

    Scenario:

    SharePoint drop down not working.
      Error:  Object Expected , Line <don't remember>, Char <don't remember>, from the m = CMenu() function in the ows.js script.  But this type of error can come from other functions as well so your workstation's exact error may not be from the CMenu() function.

      Troubleshooting, I tried - Uninstall IE8, install IE8, security settings to low, added SharePoint URL to trusted, compatibility view, delete temp files (Disk Cleanup).  No dice.

      I read from a couple posts that the problem could be from SharePoint not detecting my browser as IE and thus not including the necessary dependent files (i.e. the one that had the CMenu() function).  I thought I might need to fiddle with my User Agent string, but first needed to verify the problem.

    Verify problem steps:
      1. Login on another computer that is known to work.
      2. Go to SharePoint site.
      3. View Source ( my problem computer was also missing a registry key that let Notepad view the source so it showed the Desktop folder instead, but I digress).
      4. Save Source as working.html.
      4.5 View and save the User Agent string by going to a website that automatically detects your user agent string.  I used http://user-agent-string.info/ but if you don't like that one Google or Bing for another.
      5. Do steps 1-4 on the problem workstation, but save file as problem.html .
      6. Compare the two html sources.  I used WinMerge, an excellent and free tool, (Google or Bing for it).
      7. View the results and use your judgement.  Look for **any** differences. 
        a. I huge clue is non-ie html tag in the source of the problem computer <SCRIPT language='javascript' src='/_layouts/1033/non_ie.js'></SCRIPT>.
        b. A few lines later after the non_ie.js html tag, I see that my problem computer was missing a huge chunk of dependency calls to other files... Menu.css and Menu.js .

    <link href="/_layouts/1033/styles/Menu.css" rel="stylesheet"/><style type="text/css">
    .ms-SrvMenuUI { behavior:url("/_layouts/1033/Menu.htc"); }
    </style><script src="/_layouts/1033/Menu.js" type="text/JavaScript" language="JavaScript"></script><script type="text/JavaScript" language="JavaScript">
    <!--
    var L_Menu_BaseUrl=http://sharepoint-hidden/to/protect/;
    var L_Menu_LCID="1033";
    var L_Menu_SiteTheme="arctic";
    //-->
    </script>

     <SCRIPT LANGUAGE='JavaScript' >
    <!--
    //-->
    </SCRIPT>

    Conclusion is the call to the problem function, CMenu in my case, is probably not working because it is hidden in Menu.js and it's not getting invited to the html party.

      8. Compare the two User Agent strings.  If they're vastly different, then that might be the problem.

    My Solution:

    Fix the user agent string.  (Google or Bing for the fix).

    IE7 User Agent String

    WAS:

      Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; MS-RTC LM 8)

    IS:

      Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; InfoPath.1; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; MS-RTC LM 8)

    I removed the Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; .NET CLR 1.1.4322; .NET CLR 2.0.50727; with Regedit (be sure to export the keys as backup before deleting).  Maybe your solution is different, but figuring out if the problem is SharePoint is detecting your IE browser as an IE browser is a great first step.

    Good job to charhall for pointing you in the right direction.  I hope others will find this post, not spend 4 hours troubleshooting like I did, and I'll get good IT karma.

    Peace.

  • Wednesday, December 02, 2009 6:04 PMSkurfur Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hello EricATCorpo, I forgot to mention, the User Agesnt string is not in one location in the Registry.   In my case, it was in 4 different registry keys (quite a white rabbit).  After you determine it is a User Agent string problem, then you should Google or Bing for the fix for the User Agent string for your version of IE.  There are plenty of good websites out there giving a fix.

    Good luck!
  • Wednesday, December 09, 2009 2:54 AMDeveloper Dan Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thanks! I spent about 30 minutes looking around before finding this solution, which solved my problem. Good IT karma for charhall and Skurfur!
  • Wednesday, December 09, 2009 11:21 PMEricATCorpo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hey,
    I don'T know if it's me who doesn't follow the instructions right but none of this fixed my issue. :-(
  • Wednesday, December 09, 2009 11:39 PMEricATCorpo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Finally fixed it. I did read the instruction wrong.

    I did a search in Regedit for "Mozilla/4.0" and deleted all value that were in or under a User Agent folder. I exported each before deleting. I then looked for "NET CLR" and also deleted these entry for the 2 versions identified in the above thread (NET CLR 1.1.4322; .NET CLR 2.0.50727). Closed IE 7, restarted and fixed.

    thanks 
  • Thursday, December 10, 2009 7:23 AMMighty B Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    Hi Henry

    Follow these steps to resolve the issue. It's a known bug of your IE.

    Open Browser. Go to Tools > Internet Options > Security > Custom Levels > enable Binary and Script behaviours.

    It's should be fine.

    Regards
    Balu
    • Proposed As Answer byMighty B Sunday, December 13, 2009 4:15 AM
    •  
  • Thursday, December 10, 2009 3:28 PMc1rid Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    This totally worked for me.  The path in the registry was different but contained the same info.  I was nervous to delete the entries but I did do the backup so I am good. 
  • Thursday, December 10, 2009 4:19 PMRKHenry Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi Henry

    Follow these steps to resolve the issue. It's a known bug of your IE.

    Open Browser. Go to Tools > Internet Options > Security > Custom Levels > enable Binary and Script behaviours.

    It's should be fine.

    Regards
    Balu

    That setting is already enabled on at least one of the machines that I've been able to check.  I don't think that's the cause.