Site Actions menu not working 1

[robFSS]

this is odd.

Without warning or provocation, my WSS3 site is rebelling!

I can't acces the web page setup screens because none of the menus are working properly. I don't know what web technology is used to make the Site Actions menu expand when you click on it, but it seems to have a bug.

This is the menu you would click to get to the site settings button.

When I try to access this menu by clicking the Site Actions button, the menu expands for a split second and then disappears. After the menu disappears, the area where the menu should be is blank, and nothing happens if you click that space.

What's also interesting is that this problem is affecting all the PCs on the network, so I figure it's got to be a back-end issue. However, this problem is only affecting this site. I logged onto the Central administration website, and the menus all work fine.

Any ideas?
-r

 

[Thomas2000]

Has there been any customizations done to this "rebelling site"? Through FrontPage Designer?
Is it just this site that does not work? Or does the behaviour also occur if you create a new site (that is based on the same template as the rebelling one?)

Cheers,
Thomas

http://www.thompa.se

 

[Thomas2000]

I think I invented a new application.. Frontpage designer?! LOL I do mean SharePoint Designer

http://www.thompa.se

 

[robFSS]

Thompa -

thanks for the feedback.

What's the technology that drives those animated menus?

I don't have frontpage yet.
I'm using WSS 3.0 upgraded from 2.0 on my SBS2003 standard server.

I had no problems after the upgrade, the site was built on 3.0, using all the "canned" design tools directly from the site.

I had been having some problems recently that I describe in thread820-1360123

I'm not sure how this could be effecting the other sub-sites/pages in this overall website.

I will try to create another site and see what happens.
note:I did mention the central administration site is functioning normally (thank heavens!).

 

[Hangy]

Did anyone find a solution for this problem?

We are facing the same problems... On an environment that used to work completely fine (running on a virtual pc), we've installed a custom CAD applet which installs some things in IIS. After doing so, everything still seemed to work fine, but when someone connects to the environment from a client pc, he gets exactly the same weird behavior... Removing all the files of the applet doesn't fix the problem, so it would be great if someone already got a way of solving this issue...

 

[robFSS]

I haven't yet resolved this issue.
It's really irritating.

Of note, there are some "persistent" errors that I'm experiencing on this servier that might be related. I constantly get error events on IIS and w3wp.
I'm scheduling some network services to come in to take a look at the overall server config.

hopefully they can fix. Such a drag, seems like this sharepoint technology is way ahead of the available tech support resources.

 

[PatricktheAnalyst]

For a client side problem I would:

I would try downloading and installing Office Web Components 11.

For the server side problem, why not recreate the web app and remount the databases?

 

[ShackDaddy]

I just taught a 3-day MOSS 2007 admin class this week in which we set up 9 different small farms and did a bunch of different operations. We ran into the problem you describe on two of them. To be honest, I don't remember exactly how we resolved it, but it was a server-side configuration, and it probably got resolved by either adding permissions with the stsadm tool or deleting/recreating the SSP.

The problem (in our situation) couldn't have been caused by customizations, since we didn't do any.

To insert permissions, which we had to do in several situations, we used the following command (edited to be appropriate for our environment):

stsadm.exe –o addpermissionpolicy –url [URL unfurl="true"]http://servername/sites/SiteHavingIssues[/URL] -userlogin {DOMAIN\username} -permissionlevel "Full Control"

ShackDaddy
Shackelford Consulting

 

[robFSS]

ShackDaddio -

your suggestion is a little hi-tek for my power-user skills. I will forward them along to my IT service provider with your regards.

BTW - Notice that this problem only presents itself in IE7. I don't have the problem in IE6...

-r

 

[ShackDaddy]

Your problem doesn't sound like permissions, with that key bit of information about browsers added to the equation. I'm not really sure where to go from there.

ShackDaddy
Shackelford Consulting

 

[robFSS]

update for those who care...

I got a hold of genuine Microsoft support on this issue. After 4+ enlightening hours on the phone with Bangalore, (and almost no time spent on hold (good timing on my part)), we got it fixed.

The WSS specialist determined that the site was corrupted. she tore out the databases and we rebuilt the site using the original data on a new site.

I couldn't replicate the tasks involved if my life depended on it, although I did watch her every move... Unfortunately, in the process, I was left with an entirely new error in which my web part pallet doesn't load.

I'm about ready to just start over...