problem with site portal after upgrade from b1 to b2

Question

hi, i just upgraded beta 1 to beta 2: the server part is working fine but i have problems with the site portals that are not accesible.
i wen in the administration console and tried to reconnect the sharepoint web application to tfs but i obtain the message:

Connecting project portal site at http://tfs2010/sites/DefaultCollection/Biotech Arpa (1 of 6)
[Error] Connection failed for project portal site at http://tfs2010/sites/DefaultCollection/Biotech Arpa: TF249038: The following Web service is not available: http://tfs2010/_vti_bin/TeamFoundationIntegrationService.asmx. This Web service is used for the Team Foundation Server Extensions for SharePoint Products. Either the extensions are not installed, or there is a problem with the URL. Verify that the following URL is a valid SharePoint Web application and is available: http://tfs2010. If the URL is correct, verify that it is available and the firewall is not blocking access to it.

i checke the .asmx and exists, but raise an exception when called: modifying the custom error i found that the error is

Parser Error Message: Could not load type 'Microsoft.TeamFoundation.SharePoint.Dashboards.ApplicationMasterModule' from assembly 'Microsoft.TeamFoundation.SharePoint.Dashboards, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. (c:\inetpub\wwwroot\web.config line 90)

Source Error:

Line 88: <add name="RoleManager" type="System.Web.Security.RoleManagerModule" /> Line 89: <!-- <add name="Session" type="System.Web.SessionState.SessionStateModule"/> --> Line 90: <add name="ApplicationMaster" type="Microsoft.TeamFoundation.SharePoint.Dashboards.ApplicationMasterModule, Microsoft.TeamFoundation.SharePoint.Dashboards, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> Line 91: <add name="TSWASPModule" type="Microsoft.TeamFoundation.SharePoint.WebAccess.TSWASPModule, Microsoft.TeamFoundation.SharePoint.WebAccess, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> Line 92: </httpModules>

in the sharepoint website: i checked and the dll is registered in the gac.

do you know how i can solve this?

best regards,
  luca morelli

Answer 1

I think you need to remove it.  There should have been a readme item and also beta1 to beta2 upgrade isn't publically supported (a few go live tap/mvp customers were approved).

I sent a mail to the process team that had the workitem around your issue.  They should reply to confirm your next steps.

Hope that helps

Bryan

Answer 2

thanks, removing that setting sharepoint start and seems to work fine. I find the the default collection and all the projects inside, but when i try to enter in the project portal and go the default.aspx page i find an error of file not found in the empty page.

retrying the reconnect sharepoint web application using administration console i obtain the message


[Error] Connection failed for project portal site at http://tfs2010/sites/DefaultCollection/Biotech Arpa: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.InvalidOperationException: TF250029: No user was found within the context of a Web site. Verify that the site does not allow anonymous access.
   at Microsoft.TeamFoundation.SharePoint.WssUtil.CheckPrincipal(IPrincipal user)
   at Microsoft.TeamFoundation.SharePoint.WssUtil.CheckHttpContextUser()
   at Microsoft.TeamFoundation.SharePoint.TeamFoundationIntegrationService.AttachWeb(String absolutePath, Guid applicationInstanceId)
   --- End of inner exception stack trace ---

can you help me?

thanks anyway and best regards,
  luca morelli

Answer 3

Hi Luca,
Can you verify that your site does not allow annonimous access? We do not support anonymous access on the Sharepoint sites.

Some more info on the previous error that you were experiencing below...

Removing the line from web.config temporarily resolves the issue however SharePoint still has this entry registered and will re-insert it the next time it applies web.config changes. This could be triggered by a number of events including adding a new server to the farm or through the SharePoint API.

To permanently remove the web.config change you can do the following:

1.       On the SharePoint server, navigate to the FEATURE folder in the SharePoint hive. This will typically be "%CommonProgramFiles%\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES"

2.       Create a folder called "TfsDashboardWebConfig"

3.       Inside that folder create a file called "feature.xml" with the following contents:

<Feature xmlns="http://schemas.microsoft.com/sharepoint/"

         Id="F736F611-3845-44aa-AFB4-AD3369A42A0C"

         Title="Team Foundation Server Dashboard Web Config Modifier"

         Version="1.0.0.0"

         ActivateOnDefault="true"

         Scope="WebApplication"

         Hidden="false"

         ReceiverAssembly="Microsoft.TeamFoundation.SharePoint.Dashboards, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"

         ReceiverClass="Microsoft.TeamFoundation.SharePoint.Dashboards.WebConfigReceiver"

         >

</Feature>

4.       From a command window run the stsadm.exe admin tool ("%CommonProgramFiles%\Microsoft Shared\web server extensions\12\BIN\stsadm.exe") to install the feature:

stsadm -o installfeature -name TfsDashboardWebConfig -force

5.       From the command window deactivate the feature for each of your affected SharePoing web applications:

stsadm -o deactivatefeature -name TfsDashboardWebConfig -force -url <URL for web application>

 

There are other changes which have occurred between Beta 1 and Beta 2 for the project portals which will affect existing sites. The easiest approach is to create a new site and connect it to the existing Team Project. This can be done by:

1.       manually create new SharePoint sites using the appropriate template (TFS2010 Agile Dashboard or TFS2010 CMMI Dashboard)

2.       connect the new site to your Team Project (Team Project Settings::Portal Settings...)

3.       activating the appropriate SharePoint Feature:

o   Dashboards with reports for Microsoft Office SharePoint Server, Enterprise Edition (Agile Software Development with Visual Studio Team System), or

o   Dashboards with reports for Microsoft Office SharePoint Server, Enterprise Edition (CMMI Process Improvement with Visual Studio Team System).

 

If you want to view the content for a TFS Project Portal site after upgrade, then some guidance is available here.

Hope this helps
Valentina

 

Answer 4

thanks, i removed the reference, removed the old sites and starting to recreating the site: your informations are very clear, but i have just 2 problems.

1. in the project dashboard i have two errors 
    Task Burndown (hours): i find the error message Impossibile eseguire la query per il set di dati 'dsIterationDefault'. (rsErrorExecutingCommand).
    Burn Rate (hours/day): i find the error message Impossibile trovare l'elemento '/TfsReports/DefaultCollection/Attività Mvc/Dashboards/Burn Rate'.

2. seems that the process guidance library is not loaded from the templace. In the portal site the guidance section exists but is empty, and in the project portal settings i cannot find the document library when i try to update it. if i try to configure it, using the project portal sittings, pointing to the site i find the dashboards and excel reports library, but not process guidance.

it's possible to solve these problems?

thanks anyway and best regards,
  luca morelli

Answer 5

Hi Luca,

1. The issue is that there's been a change in the SQL Server Reporting Services (SSRS) reports between Beta 1 and Beta 2. Some of the reports have been updated to incorporate changes to the TFS Analysis Services Cube and some reports were either removed, added or renamed. In this case, the Project Dashboard contains two Page Viewer web parts which pull in content from two of the SSRS reports - one of which has changed, and another which was added.

During upgrade from Beta 1 to Beta 2 existing deployments of RS Reports are not updated so you need to get the Beta 2 reports uploaded to the correct project in your Report Server.

A straight-forward way to achieve this is to upload the Beta 2 versions of the reports to the project's folder on your Report Server site. To obtain and upload the new reports you can start by creating a new Team Project, or downloading a Process Template.

If you create a new Team Project the Project Creation Wizard (PCW) will deploy the new reports to the Report Server. You can then:

1. Navigate to the new Report folder on the Report Server
2. Export the reports to separate files by opening each report, selecting the "Properties" tab, the "General" area and then "Edit" and "Save".
3. Navigate to your original project's Report folder
4. Upload each of the Beta 2 reports to the Report folder by first deleting any report with the same name (by opening the report, selecting the "Properties" tab, the "General" area, then "Delete"), then upload the report to the folder by selecting the "Upload file" toolbar button, browsing to the RDL file downloaded in step 2, then clicking "OK".
5. Confirm that the data sources for the report are configured by opening the report, selecting the "Properties" tab, selecting the "Data Sources" area and checking that each Data Source has "A shared data source" selected and that the name is either "/Tfs2010ReportDS" or "/Tfs2010OlapReportDs". If not, then browse to the appropriate data source and click "OK", followed by "Apply".
6. Select the "Parameters" area, locate the "ExplicitProject" parameter and clear the "Default Value" input box, and ensure that the "Hide" and "Prompt User" checkboxes are unchecked. Click "Apply".
7. Confirm that the report is displaying correctly by selecting the "View" tab.

If you download the appropriate Process Template you can use the .rdl report files in there:

1. Using Team Explorer, right-click the Project Collection, select "Team Project Collection Settings", then "Process Template Manager..."
2. Select the appropriate process template, and click "Download", choose a location and save the files
3. Repeat steps 3-7 from above, where you upload each report from the "Reports" sub-folder which was created in step 2

This should result in you having the new Beta 2 reports deployed to your reporting site which your Project Portal should now be able to access.

2. As of Beta 2, Process Guidance is now available online. The files that are now provisioned to a Project Portal simply redirect the browser to the online documentation. The simplest approach is to change the location for process guidance by:

1. Right-clicking your Team Project in Team Explorer and selecting "Team Project Settings" then "Portal Settings..."
2. Navigate to the "Process Guidance" tab
3. Select "Link to a Web site" and enter "http://go.microsoft.com/fwlink/?LinkId=153652&clcid=0x409" for Agile guidance or "http://go.microsoft.com/fwlink/?LinkId=159602&clcid=0x409" for CMMI guidance, then OK.

Regards
Phil Hodgson

Answer 6

thanks, sorry for boring you, but is becoming an interesting way to understand how sharepoint and reporting services works :)
i downloaded the process template and reuploaded the reports in the first project: your instructions are very clear, i just noticed that may be is better to delete and reupload the reports, because seems that for iterationparam and areaparam the parameters are changed, and i have to copy from a new report to read the data correctly, but seems reports are working.
just another 2 things browsing the site portal:
1. i set the process guidance as you said, from team explorer works fine, trying from the site portal, clicking in the link goes to http://go.microsoft.com/fwlink/Supporting%20Files/ProcessGuidance.htm?LinkId=153652&clcid=0x409
2. trying to open a new work item, for example, i receive this javascript error
Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.3; WWTClient2; MS-RTC LM 8; Zune 4.0; FDM; .NET4.0C; .NET4.0E)
Timestamp: Sat, 24 Oct 2009 15:16:35 UTC

Message: 'CommonUrls' is undefined
Line: 34
Char: 5
Code: 0
URI: http://tfs2010/sites/DefaultCollection/Attività%20Mvc/_layouts/tswa/Resources/Scripts/DocumentService.js

after i fixed the projects already loaded, i tried to create a new team project from team explorer, but when the process start i receive this message

Error TF30004: The New Team Project Wizard encountered an unexpected error while initializing the Microsoft.ProjectCreationWizard.Portal plug-in.

Explanation TF30171: The Microsoft.ProjectCreationWizard.Portal plug-in used to create the new team project could not be initialized and returned the following error: TF218017: A SharePoint site could not be created for use as the team project portal. The following error occurred: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.InvalidOperationException: TF250029: No user was found within the context of a Web site. Verify that the site does not allow anonymous access. at Microsoft.TeamFoundation.SharePoint.WssUtil.CheckPrincipal(IPrincipal user) at Microsoft.TeamFoundation.SharePoint.WssUtil.CheckHttpContextUser() at Microsoft.TeamFoundation.SharePoint.TeamFoundationIntegrationService.CheckUrl(String absolutePath, Int32 options, Guid applicationInstanceId, Guid projectCollectionId) --- End of inner exception stack trace ---.

User Action Contact your Team Foundation Server administrator.

i don't understand very well where to find because the sharepoint doesn't allow anonymous access

trying to run the reports i found some problems in the paramters of some reports:
1. in the bug status and bug trends report, the state and severity list at the beginning of the form are empty, with out any value, and i cannot run the query, because are mandatory parameters.
2. same problem for the platfom field in the build quality indicator report

can you find a solution for this?

thanks anyway and best regards,
  luca morelli

Answer 7

Hi Luca,

Thanks for your feedback on the uploading instructions. I've incorporated it into the original post.

The process guidance issue is being tracked as a product bug. In the short term you can update the Quick Launch link by:

1. Opening "Site Actions", "Site Settings" then "Quick Launch"
2. Edit the properties for the "Process Guidance" link
3. Remove "&tf%3aDocumentPath=Supporting+Files%2fProcessGuidance.htm" from the URL, then click "OK".

The JavaScript error looks like it may be caused by some web.config entries that need to be updated. Could you try the following:

1. Open SharePoint's Central Administration site and select "Application Management"
2. Under the "SharePoint Web Application Management" section select "Manage Web Application Features"
3. On this page deactivate the "Visual Studio Team System Configuration" feature if its status is "Active" and the activate the feature.
4. Step 3 needs to be repeated for each Web Application where TFS Web Access web parts or controls are going to be used (this includes any web applications that will host TFS Dashboards). You can change web applications from the drop-down on the right-hand side of the page and selecting a different value on the "Select Web Application" screen.

Deactivating the feature will remove any old (Beta 1) web.config entries, and activating the feature sets up the new (Beta 2) entries.

To check fpr anonymous access can you go into IIS Manager and check that the Directory Security for each application does not allow anonymous access? You'll need to confirm this for both your SharePoint Central Administration and SharePoint content web sites (e.g. http://tfs2010:8080/ and http://tfs2010). Could you also ensure that anonymous access is disabled for the _layouts application under each of these web sites (e.g. http://tfs2010/_layouts).

Some of the RDL reports may not show parameter information if data is not getting into the Analysis Services Cube. To check the processing of the Data Adapters and the Cube processing you can view the Warehouse Control Web Service:

http://localhost:8080/TeamFoundation/Administration/v3.0/WarehouseControlService.asmx?op=GetProcessingStatus

When you invoke the service (from the local machine) you can check the results of the LastRun for the various Jobs and see if there's an error that needs to be resolved. You can also use SQL Server Management Studio to check if your project is in the cube:

1. Open the database for the TFS Analysis Services Cube using SSMS
2. Select the database and create a new MDX Query
3. Change the "Cube:" filter to "Team System"
4. Expand "Work Item", "Work Item .Area Hierarchy", "Members", "All", <CollectionName>
5. You should see your project in here. If not then there's an issue with data not getting into the cube which will affect the reports.

Regards
Phil Hodgson

Answer 8

hi,
   i tried to remove  "&tf%3aDocumentPath=Supporting+Files%2fProcessGuidance.htm" from the URL, leaving /sites/DefaultCollection/Attività Mvc/_layouts/tfsredirect.aspx, but if i come back to the projects portal and click the link i obtain the message "TF250011: You must specify the following required querystring parameter: tf:Type." 
  
   the disactivation and reactivation ot the system configuration worked fine: the only thing i noticed now opening the form, is that when i open the new bug window, in the details tab, below Steps to reproduce i obtain the message: Error: Unable to create 'ReproStepsControl'.  in the hover tooltip i find the message : Microsoft.TeamFoundation.WebAccess.WorkItemTracking.Controls.WorkItemFormException: Unable to load custome control manifest for 'ReproStepsControl', the other forms seems work fine.

   i checked the anonymous access for both sharepoint content and administration website, and for the _layouts application in bothh of them, and the anonynous access is disable. the only site that allows anonymous access is theam foundation server on port 8080.

  running http://localhost:8080/TeamFoundation/Administration/v3.0/WarehouseControlService.asmx?op=GetProcessingStatus i obtain the message

HTTP Error 403.1 - Forbidden: Execute access is denied.
  i tried to check management studio and all the creates projects of the default collection are present: the strange thing is that for bugs status report iteration, are and priority lists works, and state and severity don't work.
 
  best regards,
     luca morelli

  

Answer 9

Hi Luca

The Process Guidance link in the Quick launch should have originally contained two query parameters; tf:Type and tf:DocumentPath (where the ':' is URL-encoded as "%3a"). For process guidance, TfsRedirect needs at least the "tf:Type=ProcessGuidance" parameter, so your adjusted Quick Launch URL should look something like:

/sites/DefaultCollection/Attività%20Mvc/_layouts/tfsredirect.aspx?tf%3aType=ProcessGuidance

For the ReproStepsControl issue, in Beta 1 the control was defined in the Work Item Type definitions as a custom control which was not avilable for Team System Web Access interface. For Beta 2 the control is now an HTML control so for new Beta 2 Team Projects it should display correctly in the Web Access interface. After Upgrade the Beta 1 WIT definitions still reference the custom control, so if you want to manually correct this you can use the witadmin tool that is installed with VS 2010:

1. Export the existing Bug Work Item definition:
   "%DevEnvDir%\witadmin" exportwitd /collection:http://<server>/<collection> /p:<ProjectName> /n:Bug /f:bug.xml
2. Edit Bug.xml and replace Type="ReproStepsControl" with Type="HtmlFieldControl"
3. Import the updated definition:
   "%DevEnvDir%\witadmin" importwitd /collection:http://<server>/<collection> /p:<ProjectName> /f:Bug.xml

For the anonymous access issue I think we need to move this to Microsoft Connect (http://connect.microsoft.com/) where we can get some further details. It would be useful if you could log a bug and post details of the steps you're going through, a link to this forum post and the the log file created by the Project Creation Wizard (PCW) when project creation fails.

You can locate PCW log files by following the link in the wizard when project creation fails or find previous PCW log files by locating them on the client machine (where you run PCW) under the temp folder for the user running PCW. To find the previous log files:

1. runas /user:<USER> cmd
2. cd %TEMP%\..
3. dir /s VSTS_TeamProject*

It's odd that you get a permission denied message when attempting to access the WarehouseControlService. Check that you have permissions to each of the folders in the path to the ASMX file along with access to the underlying file system.

Another of our team members will respond about the report parameter issue.

Regards
Phil Hodgson

Answer 10

thanks for the support:
  now the process guidance and ReproStepsControl issue are ok.

  i opened a bug in the connect site https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=507793 for the creation wizard problem, adding 2 logs, but seems that the problem happens very early.

  for the WarehouseControlService issue i found the problem, very stupid: the address was http://localhost:8080/TFS/TeamFoundation/Administration/v3.0/WarehouseControlService.asmx?op=GetProcessingStatus not http://localhost:8080/TeamFoundation/Administration/v3.0/WarehouseControlService.asmx?op=GetProcessingStatus. i needed time to understand my mistake because i don't know tfs, and the error message was not clear. Now i'm able to open the webservice: running it without paramters for serviceHostName and JobName i obtain :

<?xml version="1.0" encoding="utf-8" ?>

- <WarehouseProcessingStatus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/TeamFoundation/2005/06/Services/Controller/03">

<RequestTimeUtc>2009-11-03T09:03:20.7025216Z</RequestTimeUtc>

<WarehouseProcessingOnlineStatus>Started</WarehouseProcessingOnlineStatus>

<AnalysisProcessingOnlineStatus>Started</AnalysisProcessingOnlineStatus>

<JobProcessingStatus>Idle</JobProcessingStatus>

<JobsRunning>0</JobsRunning>

<JobsQueued>0</JobsQueued>

- <Instance Name="TEAM FOUNDATION" JobProcessingStatus="Idle" JobsRunning="0" JobsQueued="0">

- <Jobs>

+ <Job Name="Full Analysis Database Sync" JobProcessingStatus="Idle">

<LastRun QueueTimeUtc="2009-11-01T00:00:00Z" ExecutionStartTimeUtc="2009-11-03T07:11:57.623Z" EndTimeUtc="2009-11-03T07:17:20.653Z" Result="Succeeded" />

<NextRun QueueTimeUtc="2009-11-03T12:00:00Z" JobState="QueuedScheduled" />

</Job>

- <Job Name="Incremental Analysis Database Sync" JobProcessingStatus="Idle">

<LastRun QueueTimeUtc="2009-11-03T09:00:39.137Z" ExecutionStartTimeUtc="2009-11-03T09:00:39.64Z" EndTimeUtc="2009-11-03T09:01:36.45Z" Result="Succeeded" />

<NextRun QueueTimeUtc="2009-11-03T09:30:39.137Z" JobState="QueuedScheduled" />

</Job>

</Jobs>

</Instance>

- <Collections>

- <Collection Name="DefaultCollection" JobProcessingStatus="Idle" JobsRunning="0" JobsQueued="0">

- <Jobs>

- <Job Name="Build Warehouse Sync" JobProcessingStatus="Idle">

<LastRun QueueTimeUtc="2009-11-03T08:30:50.34Z" ExecutionStartTimeUtc="2009-11-03T08:30:51.237Z" EndTimeUtc="2009-11-03T08:30:51.69Z" Result="Succeeded" />

<NextRun QueueTimeUtc="2009-11-03T09:04:05.547Z" JobState="QueuedScheduled" />

</Job>

- <Job Name="Common Structures Warehouse Sync" JobProcessingStatus="Idle">

<LastRun QueueTimeUtc="2009-11-03T08:30:50.33Z" ExecutionStartTimeUtc="2009-11-03T08:30:51.2Z" EndTimeUtc="2009-11-03T08:30:51.607Z" Result="Succeeded" />

<NextRun QueueTimeUtc="2009-11-03T09:04:05.547Z" JobState="QueuedScheduled" />

</Job>

- <Job Name="Test Management Warehouse Sync" JobProcessingStatus="Idle">

<LastRun QueueTimeUtc="2009-11-03T08:30:50.34Z" ExecutionStartTimeUtc="2009-11-03T08:30:52.22Z" EndTimeUtc="2009-11-03T08:30:52.437Z" Result="Succeeded" />

<NextRun QueueTimeUtc="2009-11-03T09:04:05.547Z" JobState="QueuedScheduled" />

</Job>

- <Job Name="Version Control Warehouse Sync" JobProcessingStatus="Idle">

<LastRun QueueTimeUtc="2009-11-03T08:30:50.34Z" ExecutionStartTimeUtc="2009-11-03T08:30:51.733Z" EndTimeUtc="2009-11-03T08:30:52.24Z" Result="Succeeded" />

<NextRun QueueTimeUtc="2009-11-03T09:04:05.547Z" JobState="QueuedScheduled" />

</Job>

- <Job Name="Work Item Tracking Warehouse Sync" JobProcessingStatus="Idle">

<LastRun QueueTimeUtc="2009-11-03T08:30:50.34Z" ExecutionStartTimeUtc="2009-11-03T08:30:51.663Z" EndTimeUtc="2009-11-03T08:30:52.207Z" Result="Succeeded" />

<NextRun QueueTimeUtc="2009-11-03T09:04:05.547Z" JobState="QueuedScheduled" />

</Job>

</Jobs>

</Collection>

</Collections>

</WarehouseProcessingStatus>

thanks,
  luca morelli

Answer 11

hi,
  the pcw issues is more clear now: thanks to the help of the connect support, i found that the problem (permissions) was in the _vti_bin directory, where is the .asmx file that is called from the pcw wizard: trying to rememeber is possibile that i enabled anonymous access in that directory when i was tracking the first initial problems, and forgot the disable it.
  now the wizard start the team project creation, but at certain point i receive the message:

Error TF30170: The plugin Microsoft.ProjectCreationWizard.WorkItemTracking failed during task WITs from group WorkItemTracking.

Explanation Plugin error text: “Work item type validation failed. The operation cannot be completed.”

User Action Contact your Team Foundation Server administrator.

best regards,
  luca morelli

Answer 12

The problem here is that the reporting type for the Microsoft.VSTS.TCM.AutomationStatus field changed between beta1 and beta2.

You can change it to the correct setting using the witadmin tool:

witadmin changefield /collection:http://servername:8080/tfs/collectionname /n:Microsoft.VSTS.TCM.AutomationStatus /reportingtype:dimension


Thanks,
  Mary Ellen Chaffin

Answer 13

i found another thing, but i don't know is a problem or not.
i deleted a team project using the administration console selectin delete external artifacts and workspace data, and i see that the project in tfs is removed, the reports are removed, but in the sharepoint part the projects portal exists, even is not bound to tfs anymore.
is this normal? i have to remove the project portal manually?

best regards,
  luca morelli