Link to home
Start Free TrialLog in
Avatar of LCMSdev
LCMSdev

asked on

SharePoint: unable to access in-browser SharePoint menus

I have a SharePoint site running under MOSS 2007 on IIS6. Whenever I try to edit the site using the browser, I am unable to access any SharePoint menus. All menu-related graphics, such as the "Site Actions" or "Edit Web Part" buttons, appear as red X's. Additionally, after authenticating, I get the following javascript errors on each page:

Error: Object expected
Error: 'WPSC' is undefined
Error: '_spBodyOnLoadFunctionNames' is undefined

I don't get the errors unless I'm authenticated into the site. Also, the actual page content displays and functions just fine...it's only the SharePoint menus and controls that aren't loading. This is true for every page on the site.

If anyone has any advice, I'd greatly appreciate it.

ASKER CERTIFIED SOLUTION
Avatar of zephyr_hex (Megan)
zephyr_hex (Megan)
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of LCMSdev
LCMSdev

ASKER

That's a good idea, which brings me to a related question. This is probably a stupid question — I'm not that familiar with SharePoint — but how do I determine where a given SP file is located on the physical server drive? I can go through the entire website directory tree in IIS, and I don't see a Themes directory. I can see it in SharePoint designer, but I can't modify the permissions there and I don't see a way to find the server path, just the URL.

Thanks for your help.
Avatar of LCMSdev

ASKER

I'll look into that, pramdosk40, thanks. I would like to test the permissions theory first, though, since it's easy to confirm...if I can find the files on the server, that is.

Can someone please help me out with how to do that?
if this is sharepoint 2007, then it's located on web front end servers:

Program Files\common files\microsoft shared\web server extensions\12

Avatar of LCMSdev

ASKER

Ok, the [mywebserver]\Users group has permissions on everything underneath that folder. If there's something else that needs to, I don't know what it is.

pramodsk40, both of your article reference adding javascript snippets to fix this error, but neither article mentions which file to add them to, or where. Do you by any chance know what these fixes are referring to?

Again, sorry for the newbie-ish nature of my questions, but I honestly am more or less a newbie at SharePoint...I know next to nothing about the back end of it, but I inherited this problem and now I have to fix it. Thanks again to both of you.
one test you may try...
when you create a new site, does the problem happen on the new site?

i can't imagine javascript is the fix here (maybe i am wrong... have been many times before!)

the Red X sounds like permissions.  it's like the user doesn't have access to the image.

have you tried a different browser?
any errors in Event Viewer on the web front end server when you launch a page?
also, try enabling sharepoint logging (in central admin).  go with the verbose logging, and then bring up the page to produce the red x... and then check the sharepoint log.
I have seen this problem before and instead of thinking about it as a permissions issue from the end user / client side of things, it almost always turns out to be related to the service account you used when installing and configuring the farm.  Things to watch out for are:

- Dont's use a domain controller to install moss 2010 on
- Try not to use the same account you logged on as when installing MOSS as the farm account when running the configuration wizard
WPSC undefined JavaScript error- you need to add it to master page. Edit your master page using sharepoint designer and add it.

for _spBodyOnLoadFunctionNames you need to goto

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\1033 and file name is init.js.

Do iisreset once the changes are done before testing.
Avatar of LCMSdev

ASKER

I've tried different browsers, and different machines on and off the network, as well as other accounts with full access. All exhibit the same problem.

Don't know why I didn't think of the Event Viewer. It's actually throwing a bunch of "could not load type" errors every time I try to access these pages. Examples include:

[bullet]Load control template file /_controltemplates/ExamRegistrations.ascx failed: Could not load type 'MysiteCommerceWeb.UserControls.ExamRegistrations'.[/bullet]
[bullet]Load control template file /_controltemplates/ProgramStructure2.ascx failed: Could not load type 'MysiteCommerceWeb.ProgramStructure'.[/bullet]
[bullet]Load control template file /_controltemplates/CourseDetails.ascx failed: Could not load type 'MysiteCommerceWeb.CourseDetails'.[/bullet]

MysiteCommerceWeb (not the real text; "Mysite" is actually the name of my site) sounds like a namespace of some kind? Could this be caused by permissions issues?
Avatar of LCMSdev

ASKER

Blarg, apparently I can't even code bullets let alone debug ASP.NET. Still, you get what I mean.
Avatar of LCMSdev

ASKER

Oh, one thing I should add...this site was working fine until today. I didn't do anything to the configuration. I'm not the only one with server access, but the others are my 3rd-party webhost (I RDP into the server directly) and a guy who's on vacation; I don't think either of them did anything server-side either.
hmm... not sure if those Event Viewer error are related or not.  but in any event, see here:
http://todd-carter.com/post/2010/05/03/Help-Wanted-Taxonomy-Picker.aspx

sounds similar...  but you're on sharepoint 2007...  
but it might be worth trying a similar approach in your case.

or... look at this:
http://www.eggheadcafe.com/software/aspnet/28894751/moss-2007-file-not-found-error.aspx

it suggests getting a "clean" web.config file.
Avatar of LCMSdev

ASKER

Still not fixed, but on further testing I'm almost sure this is something to do with permissions. I don't have time to work through it immediately, so I'm going to accept the solution for now. When I get it sorted, I'll come back and post the specifics for the curious. Thanks again for your help!
I am having the same problem after service account password change.