Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Problem with Portal Web Parts

  Asked By: Nicholas    Date: Dec 06    Category: Sharepoint    Views: 1322

I'm working with a new firm and they had already installed
SharePoint Portal for their internal use.

Whenever we try to add a content editor web part to a page the web
part loads into the web part zone but when we open the tool pane and
the rich text editor, enter some text and try to save it, we get
this error:

Cannot Retrieve Properties at this time

Click OK and get this error:

Cannot Save Your changes

Okay, so that sucks.

So, trying to troubleshoot, I ended up in the web part gallery.

When I try to open a web part in it's "preview mode" in the gallery,
I get this SharePoint Page error:

A Web Part or Web Form Control on this Web Part Page cannot be
displayed or imported because it is not registered on this site as

Okay, so they bumbled something during the install and the web parts
are not considered safe.

Then, When I try to open the page in MSFrontPage, I get an error
that says:

The server could not complete your request. Contact your ISP or web
server administrator to make sure that the server has the FrontPage
Server Extensions or SharePoint Services installed. For More
specific information, click the details button.

and then, it has a details option with this error:

soap:Server Exception of type
Microsoft.SharePoint.SoapServer.SoapServerException was thrown. A
Web Part or Web Form Control on this Web Part Page cannot be
displayed or imported because it is not registered as safe on this
site. You may not be able to open this page in an HTML editor that
is compatible with Microsoft Windows SharePoint Services, such as
Microsoft Office FrontPage. To fix this page, contact the site
administrator to have the Web Part or Web Form Control configured as
safe. You can also remove the Web Part or Web Form Control from the
page by using the Web Parts Maintenance Page. If you have the
necessary permissions, you can use this page to disable Web Parts
temporarily or remove personal settings. For more information,
contact your site administrator.

So, finally, I go to the web part maintenance page and look at the
web parts and they are all titled "Error" with type = "web part

So my question is "how screwed am I?" with a possible
followup, "should I maybe find somewhere else to work?"



6 Answers Found

Answer #1    Answered By: Christop Mcfadden     Answered On: Dec 06

It could simply be that another web.config has been inserted somehwere in
the heirarchy and that is overriding the web.config that has the right safe
controls configuration.

Answer #2    Answered By: Gopal Jamakhandi     Answered On: Dec 06

I don't know much about any of the other errors, but if one web  part
is not working  on the page, then all of them will show an error  on the
web part  maintenance page.

Answer #3    Answered By: Chantal Rosa     Answered On: Dec 06

This is a long shot... but check the server’s event log… see anything about SharePoint not able to load an assembly? If so, are you running your virtual server  bound to an IP and running SPS RTM or SP1?

Answer #4    Answered By: Kyla Eckert     Answered On: Dec 06

You gotta love the details  SharePoint gives in it's error  messages!!!
(About 90% of the time the details are misleading).

I answered a similar thread in the Microsoft public newsgroups. In
short, the solution is to install  SP2 for both WSS and SPS. (Of
course, check the safecontrols entries in web.config... but I'm pretty
sure they're correct.) I've also seen this on my servers... I was
running in this config for about a year having to hack-around this issue.

Let me read your mind:

1. WSS SP2 and SPS SP2 are not installed.
2. The server  is running more than one web  site in IIS. (This confuses
the CRAP out of SharePoint prior to SP2). Especially when they're IP
or host-header bound-- different ports seam to have better luck.

Am I right? If so-- installing SP2 should clear up your problems. (And
if I'm wrong, still try installing SP2-- I'll bet it will fix  this).

Answer #5    Answered By: Damon Garner     Answered On: Dec 06

I have checked the web.config and it's indistinguisable from the
web.config that lives in portals that work  so I can't imagine it's
the source of my problem.

We are running multiple portals on a single server  and each is bound
to a different IP address and they are NOT running SP2.

So that will be on the agenda of our first ops meeting of 2006.

Answer #6    Answered By: Alexis Ellis     Answered On: Dec 06

Sharepoint definitely did not like bound IPs prior to SP2.

Didn't find what you were looking for? Find more on Problem with Portal Web Parts Or get search suggestion and latest updates.