After upgrading to TFS 2013, the TFS OLAP Cube fails processing with one of the following messages:
Invalid column name ‘System_AssignedTo__Name’.; 42S22;
Invalid column name ‘System_AssignedTo__SID’.; 42S22
Query execution failed for dataset ‘ds[Whatever]‘
Found in Jeff Hunsaker’s blog post:
- In TFS Admin Console, look up the account under “Account for accessing data sources” under the “Analysis Services” tab (Reporting » Edit).
- In SQL Server, add that account to the Tfs_Warehouse database, to the TFSEXECROLE role.
On the TFS Project Portal, you get a 404 error from SharePoint instead of the dashboard.
Then that project were probably created with the Visual Studio Scrum 1.0 template, and that template is not available on the new SharePoint server.
How to fix
- Download and install Visual Studio Scrum 1.0
- In the Project Portal subfolder, look at Readme.txt
- Execute the batch commands listed in that Readme.txt to upload the missing .WSP file
(on the first line, starting with “SET STSADM”, make sure to replace version “12” with “14” if you are using SharePoint 2010, or accordingly for any newer versions).
(Big thanks to Trevor Hancock, Hassan Fadili, and Wes MacDonald for the solution.)
In TFS you can use Project Alerts or Alerts Explorer to edit your subscriptions. You will not see subscriptions created by others.
To see all subscriptions you could have a look at the tbl_EventSubscription table in the collection database (Caution: Do not make any changes to the TFS DBs!).
To find out which user identity is hidden behind the GUID in the "SubscriberId" column, you can use the following SQL statement
FROM tbl_EventSubscription es
JOIN [Tfs_Configuration].[dbo].tbl_security_identity_cache sic
ON sic.tf_id = es.SubscriberId
WHERE es.Id = 123
where 123 is the Subscription ID (see "Id" column in the screenshot above).
(Thanks to Patrick Carnahan from Microsoft for helping me out with this and providing the SQL statement above)
The prerequisites installation fails with errors configuring IIS.
- Make sure to install all available Windows Updates.
- Try to manually install the required IIS features by executing the following command:
start /w pkgmgr /iu:IIS-WebServerRole;IIS-WebServer;IIS-CommonHttpFeatures; IIS-StaticContent;IIS-DefaultDocument;IIS-DirectoryBrowsing;IIS-HttpErrors; IIS-ApplicationDevelopment;IIS-ASPNET;IIS-NetFxExtensibility; IIS-ISAPIExtensions;IIS-ISAPIFilter;IIS-HealthAndDiagnostics; IIS-HttpLogging;IIS-LoggingLibraries;IIS-RequestMonitor;IIS-HttpTracing;IIS-CustomLogging;IIS-ManagementScriptingTools; IIS-Security;IIS-BasicAuthentication;IIS-WindowsAuthentication;IIS-DigestAuthentication; IIS-RequestFiltering;IIS-Performance;IIS-HttpCompressionStatic;IIS-HttpCompressionDynamic; IIS-WebServerManagementTools;IIS-ManagementConsole;IIS-IIS6ManagementCompatibility; IIS-Metabase;IIS-WMICompatibility;WAS-WindowsActivationService;WAS-ProcessModel; WAS-NetFxEnvironment;WAS-ConfigurationAPI;WCF-HTTP-Activation; WCF-NonHTTP-Activation
For more details visit this page:
There’s a new "Visual Studio Troubleshooting" page available on MSDN:
Information on how to troubleshoot your hardware/software configuration to gain optimum efficiency while using Visual Studio 2010.
Link: Suggestions for Improving the Performance of Visual Studio
Changes you make to local or Active Directory groups do not get reflected in TFS immediately. Instead, TFS will synchronize those groups regularly (by default every hour).
- You can re-add the security group in TFS, this will trigger a identity synchronization.
- In TFS 2005/2008: you could restart IIS or the TFS App Pool to force an identity synchronization (does not work for TFS 2010).
- Using the JobService webservice, you can queue the identity synchronization job.
- Or use this tool to trigger the web service:
(Note: The user needs to have the ‘Queue background jobs‘ permission on TFS)
Download the tool from here:
- You can specify "/status" to only query the time of the last identity synchronization.
(only requires ‘View background job information‘ permission on TFS)
Warning: In regular cases you should install the TFS Extensions for SharePoint as described here and do not follow the steps in this blog post.
The Microsoft.TeamFoundation.SharePoint.wsp did not get deployed to the SharePoint Products server. This web service is deployed to SharePoint as part of this package.
- Solution 1 (preferred): Install TFS Extensions for SharePoint and run the wizard (from TFS Admin Console).
- Solution 2: Manually deploy required solutions to your SharePoint servers.
(Detailed steps can be found here).
Short summary of manual steps:
- Locate .WSP files (default folder: "%ProgramFiles%\Microsoft Team Foundation Server 2010\Tools\Templates")
- Locate stsadm.exe (default folder: “%ProgramFiles%\Common Files\Microsoft Shared\web server extensions\14\BIN)
- Upload .WSP files to SharePoint using:
stsadm.exe -o addsolution -filename Filename.wsp
- Deploy Solutions (using Central Administration > Solution Management)
When double-clicking the Source Control node of a Team Project that has no source control folder you receive the following message:
No Source Control Folder
Cannot open $/Projectname. Source control has not been configured for this team project, you do not have permission to acces it, or the team project has been moved or deleted.
- In TFS 2010 there is no option in the Team Project Creation Wizard to create a team project without source control (as it was possible in TFS 2008).
- Therefore the prompt that asks if the user wants to recreate that folder, was removed as well.
- Use the TFS Object Model, specifically:
- Alternatively, I created a small command line utility that does exactly that.
Prerequisite: This tool requires Team Explorer 2010 to be installed.
(Thanks to Chandru R. from Microsoft for this tip and the support to resolve the issue)
Getting this error (and your TFS is installed on a Domain Controller)?
An error has occurred during report processing. (rsProcessingAborted)
Cannot impersonate user for data source ‘TfsReportDS’. (rsErrorImpersonatingUser)
Logon failed. (rsLogonFailed)
Logon failure: the user has not been granted the requested logon type at this computer. (Exception from HRESULT: 0x80070569)
Make sure that the local policy of the DC allows for login of non-admin users.
(Domain Controller Security Policy > Local Policies | User Rights Assignment | "Allow log on locally" policy and add domain users.
(Thanks to Carl Daniel who wrote about the solution in the MSDN Forums.)