I am currently in what appears to be exactly the same situation as Jonathan was. I just upgraded a TFS Server from 2005 to 2008 on new hardware after performing a restoration based move. The move went fine and SharePoint was working as expected. Becasue it was a new TFS 2008 installation I integrated SP1 into the TFS 2008 install. There were no VS2008 client components installed on the machine. The upgrade went fine and SharePoint was working as expected. I then installed Team Explorer,VS 2008 SP1, and Team System Web Access. SharePoint now doesn't work and shows the same errors as Jonathan. We hadn't yet upgraded SharePoint to 3.0. If a SharePoint upgrade fixes things then I'd say that there appears to be a TFS 2008 SP1, VS2008 SP1, and SharePoint dependency on a TFS 2008 application tier. i.e. SharePoint must be upgraded to 3.0 before installing VS 2008 SP1 on a TFS 2008 AT. I'll let you know if a SharePoint upgrade fixes thngs. Cheers,
David Feilen ES - Release and Technical Support Team Employment Systems Group Department of Education, Employment and Workplace Relations http://www.deewr.gov.au <http://www.deewr.gov.au/> Ph. 6121 8393 Ext. 68393 ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Zack Sent: Friday, August 15, 2008 6:33 AM To: listserver@oztfs.com Subject: Re: [OzTFS] Team Project Portal Issues After Installing TFS 2008 SP1 and VS 2008 SP1 Deepak, Thank you for the quick response. We don't have any custom webparts; our SharePoint portal has no customizations at all. I checked the web.config and these are the SafeControls: *** <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 <http://11.0.0.0/> , Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.SharePoint" TypeName="*" Safe="True"/> <SafeControl Assembly="Microsoft.SharePoint, Version=11.0.0.0 <http://11.0.0.0/> , Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.SharePoint.WebPartPages" TypeName="*" Safe="True"/> <SafeControl Assembly="Microsoft.SharePoint, Version=11.0.0.0 <http://11.0.0.0/> , Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.SharePoint.WebControls" TypeName="*" Safe="True"/> <SafeControl Assembly="Microsoft.SharePoint, Version=11.0.0.0 <http://11.0.0.0/> , Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.SharePoint.ApplicationPages" TypeName="*" Safe="True"/> <SafeControl Assembly="Microsoft.SharePoint, Version=11.0.0.0 <http://11.0.0.0/> , Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.SharePoint.SoapServer" TypeName="*" Safe="True"/> <SafeControl Assembly="Microsoft.SharePoint, Version=11.0.0.0 <http://11.0.0.0/> , Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.SharePoint.Meetings" TypeName="*" Safe="True"/> <SafeControl Assembly="Microsoft.PerformanceManagement.Scorecards.WebParts, Version=2.0.0.0 <http://2.0.0.0/> , Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="Microsoft.PerformanceManagement.Scorecards.WebParts" TypeName="*" Safe="True"/> </SafeControls> *** I noticed that the version for the SharePoint assembly was "11" rather than "12" as you indicated below and this reminded me that we never upgraded Windows SharePoint Services from 2.0 when we upgraded from TFS 2005 (everything was fine so we left it like that). It appears that the landscape might have changed since then and Windows SharePoint Services 3.0 is a requirement for SP1. I upgraded the server to 3.0 and everything is working fine now for the portal. Thanks again. Regards, Jonathan On Thu, Aug 14, 2008 at 8:24 AM, <[EMAIL PROTECTED]> wrote: 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 <http://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 <http://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 <http://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 <http://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: listserver@oztfs.com 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/listserver@oztfs.com/ Powered by mailenable.com <http://mailenable.com/> , supported by www.readify.net <http://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/listserver@oztfs.com/ Powered by mailenable.com <http://mailenable.com/> , supported by www.readify.net <http://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/listserver@oztfs.com/ Powered by mailenable.com, supported by www.readify.net Notice: The information contained in this email message and any attached files may be confidential information, and may also be the subject of legal professional privilege. If you are not the intended recipient any use, disclosure or copying of this email is unauthorised. If you received this email in error, please notify the DEEWR Service Desk and delete all copies of this transmission together with any attachments. 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/listserver@oztfs.com/ Powered by mailenable.com, supported by www.readify.net
