Brand new Sharepoint 2003 install (Companyweb) giving Web Part Error

We have had Server 2003 deployeed for over 2 years now without an issue. We have decided to install sharepoint simply as neat way to share documents so that the less computer savvy people know where to find them. This is a clean install with no customisations and their is no content on each page just the below error.

Web Part 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 safe.

Please see attached screenshots for details. I know nothing about sharepoint so I am a bit lost on how to fix this.
SS1.png
SS2.png
Rondog_88Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JbondCommented:
Not sure if this works in 2003 because we decomissioned it long ago. Try adding ?Contents=1 at the end of your url. Like www.mysite.com/default.aspx?Content=1

this will show you what webparts are active and you should be able to remove them. Again, no guarantee this will work in 2003.
0
Rondog_88Author Commented:
Shows exactly the same page. Any other thoughts?
0
jessc7Commented:
Jbod is right, but I believe there was a typo in the example URL. It should be Contents, not Content. So using your screenshot:

http://companyweb/default.aspx?Contents=1
0
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

Rondog_88Author Commented:
Ok done. Now it tells me this, see new screenshot
SS3.png
0
jessc7Commented:
To remove the two web parts that are erroring out, you can click the check box next to each and then click Delete on the menu.
0
Rondog_88Author Commented:
How I add shared documents to the document library?
0
Rondog_88Author Commented:
It prompts me for admin privaledges but then errors when I enter them.
SS4.png
0
jessc7Commented:
Are you still able to view this page?

http://companyweb/default.aspx
0
Rondog_88Author Commented:
Yes, nothing has changed.
0
jessc7Commented:
Do you see any errors in the SharePoint logs?
0
Rondog_88Author Commented:
Where will I find Sharepoint logs?
0
ImaCircularSawTechnical LeadCommented:
It sounds like you need to add a safe control to the web.config file. Is the webpart in question a stock one or installed/custom made?
0
ImaCircularSawTechnical LeadCommented:
It sounds like you need to add a safe control to the web.config file. Is the webpart in question a stock one or installed/custom made?
0
ImaCircularSawTechnical LeadCommented:
This might be the step you need.  You're basically adding a ref to the webpart and code in the web.config file so that it knows it's allowed to use the webpart:

http://msdn.microsoft.com/en-us/library/ms581321(v=office.12).aspx
0
Rondog_88Author Commented:
It a stock installed webpart. I've made no customisation so far. What changes do I need to make?

This is the web.config file from C:\inetpub\wwwroot

<configuration>
  <configSections>
    <sectionGroup name="SharePoint">
      <section name="SafeControls" type="Microsoft.SharePoint.ApplicationRuntime.SafeControlsConfigurationHandler, Microsoft.SharePoint, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
      <section name="RuntimeFilter" type="System.Configuration.SingleTagSectionHandler, System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
      <section name="WebPartLimits" type="System.Configuration.SingleTagSectionHandler, System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
      <section name="WebPartCache" type="System.Configuration.SingleTagSectionHandler, System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
      <section name="WebPartWorkItem" type="System.Configuration.SingleTagSectionHandler, System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
      <section name="WebPartControls" type="System.Configuration.SingleTagSectionHandler, System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
      <section name="SafeMode" type="System.Configuration.SingleTagSectionHandler, System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
      <section name="OnlineLibrary" type="System.Configuration.SingleTagSectionHandler, System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
    </sectionGroup>
  </configSections>
  <SharePoint>
    <SafeMode MaxControls="50" CallStack="false" />
    <WebPartLimits MaxZoneParts="50" PropertySize="1048576" />
    <WebPartCache Storage="CacheObject" />
    <WebPartWorkItem Timeout="7000" />
    <WebPartControls DatasheetControlGuid="65BCBEE4-7728-41a0-97BE-14E1CAE36AAE" />
    <!--
SafeControl Attributes:
          Assembly="[Assembly]" - The .NET assembly in which the control is contained. This attribute can also contain version, culture, and public key token information.
          Namespace="[Namespace]" - The .NET namespace in which the control is defined.                                         
          TypeName="[Typename]" - The .NET class name of the control. You can type an asterisk (*) wildcard character to indicate all TypeNames in a Namespace. 
          Safe="[True|False]" - Specifies whether a Web Part or Web Form Control is safe and can be displayed on a Web Parts Page. This attribute is True by default.
-->
    <SafeControls>
      <SafeControl Assembly="System.Web, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" Namespace="System.Web.UI.WebControls" TypeName="*" Safe="True" />
      <SafeControl Assembly="System.Web, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" Namespace="System.Web.UI.HtmlControls" TypeName="*" Safe="True" />
      <SafeControl Assembly="Microsoft.SharePoint, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.SharePoint" TypeName="*" Safe="True" />
      <SafeControl Assembly="Microsoft.SharePoint, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.SharePoint.WebPartPages" TypeName="*" Safe="True" />
      <SafeControl Assembly="Microsoft.SharePoint, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.SharePoint.WebControls" TypeName="*" Safe="True" />
      <SafeControl Assembly="Microsoft.SharePoint, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.SharePoint.ApplicationPages" TypeName="*" Safe="True" />
      <SafeControl Assembly="Microsoft.SharePoint, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.SharePoint.SoapServer" TypeName="*" Safe="True" />
      <SafeControl Assembly="Microsoft.SharePoint, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.SharePoint.Meetings" TypeName="*" Safe="True" />
      <SafeControl Assembly="System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" Namespace="System.Web.UI.WebControls" TypeName="SqlDataSource" Safe="False" />
      <SafeControl Assembly="System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" Namespace="System.Web.UI.WebControls" TypeName="AccessDataSource" Safe="False" />
      <SafeControl Assembly="System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" Namespace="System.Web.UI.WebControls" TypeName="XmlDataSource" Safe="False" />
      <SafeControl Assembly="System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" Namespace="System.Web.UI.WebControls" TypeName="ObjectDataSource" Safe="False" />
    </SafeControls>
    <OnlineLibrary Url="http://r.office.microsoft.com/r/hlidAwsGallery" />
  </SharePoint>
  <system.web>
    <securityPolicy>
      <trustLevel name="WSS_Medium" policyFile="C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\config\wss_mediumtrust.config" />
      <trustLevel name="WSS_Minimal" policyFile="C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\config\wss_minimaltrust.config" />
    </securityPolicy>
    <httpHandlers>
      <add verb="*" path="/_vti_bin/*.aspx" type="System.Web.UI.PageHandlerFactory, System.Web, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
      <add verb="*" path="*.aspx" type="Microsoft.SharePoint.ApplicationRuntime.SharePointHandlerFactory, Microsoft.SharePoint, Version=11.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
    </httpHandlers>
    <customErrors mode="On" />
    <httpRuntime maxRequestLength="51200" />
    <authentication mode="Windows" />
    <authorization>
      <allow users="*" />
    </authorization>
    <identity impersonate="true" />
    <httpModules>
      <clear />
      <add name="OutputCache" type="System.Web.Caching.OutputCacheModule" />
      <add name="WindowsAuthentication" type="System.Web.Security.WindowsAuthenticationModule" />
      <!--	<add name="Session" type="System.Web.SessionState.SessionStateModule"/>-->
    </httpModules>
    <globalization fileEncoding="utf-8" />
    <compilation batch="false" debug="false" />
    <pages enableSessionState="false" enableViewState="true" enableViewStateMac="true" validateRequest="false" enableEventValidation="false">
      <namespaces>
        <remove namespace="System.Web.UI.WebControls.WebParts" />
      </namespaces>
    </pages>
    <trust level="WSS_Minimal" originUrl="" processRequestInApplicationTrust="false" />
    <machineKey validationKey="BFF705C0AEA3F207919362942AC7B512A832357CB5EBBD8C" decryptionKey="C8879A4B17E890B211E45961B7E32D6B77EA7A0A718D80DC" validation="SHA1" />
  </system.web>
</configuration>

Open in new window

0
JbondCommented:
Ron,

Lets back up. What type of Webpart are you adding?

SharePoint is prompting for credentials because its trying to access a list.
0
Rondog_88Author Commented:
I am not trying to add a webpart. This is what shows up in companyweb straight after install.

All i need companyweb to do is:
- annoucements on the mainpage
- 1 shared document library with approx 100 documents
- contact list, list of all staff with job title, office location, phone number and email address

But no matter what page I go to, it shows these webpart errors. And yes all webparts are standard I have done no customisation at all
0
JbondCommented:
What webpart is throwing the error? by using ?Contents=1 you can remove the webparts one at a time and figure out which one is causing the problem.
0
Rondog_88Author Commented:
As I said before I cant remove the webparts by using ?Contents=1

It prompt me for administrator details, I then enter admin details, it then errors out. Yet when I click site settings and it prompts me for admin details, I enter the same username and password and then it works.
0
JbondCommented:
Like I said before, I dont' have 2003. But try going to Site Settings and see if you can access the list of installed webparts. see if it throws a security error that way. If it does then the problem is in the web library.
0
Rondog_88Author Commented:
I went to:

Site Settings > Go to Site Administration > Manage Web Part Gallery

And all it loaded was:
Web Part 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 safe.

Does this mean the problem is in the web library? If so, how do I go about fixing this?
0
JbondCommented:
Okay, so its saying the webpart is not trusted. Might have a couple options here.

First can you get to the web.config. If so do you have a <SafeControls> section? and if so, what is in it.

The other option. Maybe. Again, just guessing. under Site Administration see if you have something like Site Collection Features. You may be able to deactivate the feature/features. this will completely remove the webparts from sharepoint, errr disable them anyway.

Otherwise if you need the web part thats throwing the error we'll need to add it to the SafeControl section of the web config. Another option, If you don't want to add it to the SafeControl section is to move the DLLs that power the webpart into the GAC. IIS assumes that DLLs in the GAC are all safe and there is no need for the SafeControl entry in the web.config
0
Rondog_88Author Commented:
Up about 6 posts in the section of code is my entire web.config file from c:\inetpub\wwwroot. Does that help?

Under Site Collection Administration I have these choices:
 - View site hierarchy
 - View site collection usage summary
 - View storage space allocation
 - View site collection user information
 - Configure connection to portal site

What DLL's do I move to where? Sorry complete SharePoint beginner here.
0
JbondCommented:
So, the DLLs are going to be the ones mentioned in the SafeControl section of the Web.Config. But they're already labeled as SafeControl. It makes me think it is one that isn't listed in the safe control section.

What is in your \Inetpub\wwwroot\virtualdirectories\sitename\bin

Also, see if you have some logs

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12

this is where they are in WSS 3.0. Post the most recent copy of the log. It should tell us the DLL thats missing the SafeControl

0
Rondog_88Author Commented:
Under C:\Inetpub\wwwroot I dont have the folder virtualdirectories I only have wpresources and aspnetclient

Under C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions I only have 50, 60 and wpresources. No other folders.

Any other thoughts?
0
JbondCommented:
yea, see if you have a logs folder in the 50 - 60 or WPreasources. Also see if you have a Bin folder in the wpresources in wwwroot
0
Rondog_88Author Commented:
Nope, none of those at all.
0
JbondCommented:
We need to find the logs, getting the logs will get us to the cause of the problem.

http://weblogs.asp.net/soever/archive/2004/12/16/319509.aspx
0
Rondog_88Author Commented:
I read through the link you have me, I am not sure what you want me to change the registry key has no mention of a log location.
0
Rondog_88Author Commented:
That link says to go the Central Administration page click Configure Diagnostic Settings. I do not have that option at all.
0
Rondog_88Author Commented:
I fixed it by upgrading to SharePoint 3.0
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Rondog_88Author Commented:
Problem was only fixed by upgrading to new version
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.