Jonathan,
A custom webpart should be registered as a safe control
before it is deployed. You can find the registered webparts in the
SafeControls of the web.config section. This is typically in $drive
\inetpub\wwwroot\wss\portnumber directory. (If you can't find a
portnumber directory, then your web.config of interest is in
$drive\inetpub\wwwroot)
<SafeControl Assembly="Microsoft.SharePoint, Version=12.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c"
Namespace="Microsoft.SharePoint.Workflow" TypeName="*" Safe="True"
AllowRemoteDesigner="True" />
<SafeControl Assembly="Microsoft.SharePoint.Search,
Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"
Namespace="Microsoft.SharePoint.Search.WebControls" TypeName="*"
Safe="True" AllowRemoteDesigner="True" />
<SafeControl Assembly="Microsoft.SharePoint.Search,
Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"
Namespace="Microsoft.SharePoint.Search.Internal.WebControls"
TypeName="*" Safe="True" AllowRemoteDesigner="True" />
<SafeControl Assembly="customwebpart,
Version=1.0.0.0,Culture=neutral,PublicKeyToken=f16dbce23312d46d"
Namespace="customwebpart" TypeName="*" Safe="True"
AllowRemoteDesigner="True" />
The one I have highlighted above is a custom webpart being declared as a
safecontrol. I am guessing that the SP1 has overwritten your
web.config,and hence your custom webpart is not registered as safe.
I suggest that you turn CustomErrors off (in the same web.config) and
change the Safemode node's callstack to true as shown below
<customErrors mode="Off" />
<SafeMode MaxControls="200" CallStack="true" DirectFileDependencies="10"
TotalFileDependencies="50" AllowPageLevelTrace="false">
This will show you the stack trace. I hope that will help you find the
problem. In the worst case, you can go to the web part gallery and
delete the error-causing webpart if you don't need it anymore.
Deepak Srinivasan
Sogeti USA
222 W. Las Colinas Blvd.
Irving, TX. 75039
Office: 972.892.3400
eMail : [EMAIL PROTECTED]
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Jonathan Zack
Sent: Thursday, August 14, 2008 10:07 AM
To: [email protected]
Subject: [OzTFS] Team Project Portal Issues After Installing TFS 2008
SP1 and VS 2008 SP1
Hi,
Everything appears to be fine after installing TFS 2008 SP1 and VS 2008
SP1 except for a Team Project portal site which displays this 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.
Notes:
* The team project originated from TFS 2005 and was upgraded to
TFS 2008 when it was released. It has been fine since that upgrade until
SP1 was installed.
* The Documents folder in VS 2008 for that Team Project doesn't
seem to have any issues.
* No Beta release of SP1 was installed on that server.
Anybody else encounter this type of issue? I checked the ReadMe for SP1
and poked around the Internet but didn't find any references to problems
with SharePoint sites after the install of SP1.
Regards,
Jonathan
OzTFS.com - to unsubscribe from this list, send a message back to the
list with 'unsubscribe' as the subject. View the web archives at
http://www.mail-archive.com/[email protected]/
Powered by mailenable.com, supported by www.readify.net
OzTFS.com - to unsubscribe from this list, send a message back to the list with
'unsubscribe' as the subject. View the web archives at
http://www.mail-archive.com/[email protected]/
Powered by mailenable.com, supported by www.readify.net
