A blog run by the support folks from Microsoft, for TFS Setup/install related tips and tricks.

TFS installation and Error 28925

Here is another installment of list of fixes for a common Installation error. Again, while attempting the fix/ workaround mentioned in the list make sure you go thru the list and try to match the exact error you are facing as captured in the installation log file (as applicable).

Exception / Log snippet	Solution
Error 28925.TFServerStatusValidator: Calling the Team Foundation Server ServerStatus Web service failed. Additional details about the problem can be found in the setup log. Verify your network configuration. For more information on troubleshooting this error, see the Microsoft Help and Support Center	In IIS configuration, the .asmx mappings don't haveGET, POST ] by default. Resolution In IIS configuration, for .asmx mappings add [ GET, POST ] manually. Then "retry" the install and it completes successfully. More about Isapi configuration:
"Error 28925.TFServerStatusValidator: Calling the Team Foundation Server ServerStatus Web service failed. Additional details about the problem can be found in the setup log. Verify your network configuration. For more information on troubleshooting this error, see the Microsoft Help and Support Center." Log snippet: Invalid file name for file monitoring: 'C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Config'. Common reasons for failure include: - The filename is not a valid Win32 file name. - The filename is not an absolute path. - The filename contains wildcard characters. - The file specified is a directory. - Access denied. at System.Web.DirMonCompletion..ctor(DirectoryMonitor dirMon, String dir, Boolean watchSubtree, UInt32 notifyFilter) at System.Web.DirectoryMonitor.StartMonitoring() at System.Web.DirectoryMonitor.StartMonitoringFile(String file, FileChangeEventHandler callback, String alias) at System.Web.FileChangesMonitor.StartMonitoringFile(String alias, FileChangeEventHandler callback) at System.Web.Configuration.WebConfigurationHost. StartMonitoringStreamForChanges(String streamName, StreamChangeCallback callback) at System.Configuration.BaseConfigurationRecord.MonitorStream(String configKey, String configSource, String streamname) at System.Configuration.BaseConfigurationRecord.InitConfigFromFile() : An error occurred loading a configuration file: Invalid file name for file monitoring: 'C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Config'. Common reasons for failure include: - The filename is not a valid Win32 file name. - The filename is not an absolute path. - The filename contains wildcard characters. - The file specified is a directory. - Access denied. (C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Config\machine.config) at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal) at System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(ConfigurationSchemaE rrors schemaErrors) at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject) at System.Configuration.BaseConfigurationRecord.GetSection(String configKey, Boolean getLkg, Boolean checkPermission) at System.Configuration.BaseConfigurationRecord.GetSection(String configKey) at System.Web.Configuration.RuntimeConfig.GetSectionObject(String sectionName) at System.Web.Configuration.RuntimeConfig.GetSection(String sectionName, Type type, ResultsIndex index) at System.Web.Configuration.RuntimeConfig.get_HealthMonitoring() at System.Web.Configuration.HealthMonitoringSectionHelper..ctor() at System.Web.Management.HealthMonitoringManager..ctor() at System.Web.Management.HealthMonitoringManager.Manager() at System.Web.Management.WebBaseEvent.RaiseRuntimeError(Exception e, Object source) at System.Web.HttpResponse.ReportRuntimeError(Exception e, Boolean canThrow, Boolean localExecute) at System.Web.HttpRuntime.FinishRequest(HttpWorkerRequest wr, HttpContext context, Exception e)--> --. ErrorCallingServerStatus 02/08/07 09:53:46 DDSet_Status: Process returned 2325 02/08/07 09:53:46 DDSet_Status: Found the matching error code for return value '2325' and it is: '28925' 02/08/07 09:53:46 DDSet_Error: 2325 MSI (s) (0C!2C) [10:15:13:366]: Product: Microsoft Visual Studio 2005 Team Foundation Server - ENU -- Error 28925.TFServerStatusValidator: Calling the Team Foundation Server ServerStatus Web service failed. Additional details about the problem can be found in the setup log. Verify your network configuration. For more information on troubleshooting this error, see the Microsoft Help and Support Center.	Disable the “Maximum used memory” property for “TFS**” application pool. (Please see the note section, if there are no App Pools related to TFS present) Steps: 1) Open IIS manager (inetmgr) 2) Browse to Application pools. 3) Select the AppPool property, that is in question. 4) Disable “maximum used memory” by clearing the selection box
Microsoft Visual Studio 2008 Team Foundation Server - ENU -- Error 28925.TFServerStatusValidator: The tool could not call the Team Foundation Server ServerStatus Web service." Log snippet: Unhandled Exception: System.IO.FileLoadException: Unverifiable code failed policy check. (Exception from HRESULT: 0x80131402)    at Microsoft.TeamFoundation.Common. ExceptionFormatter.FormatExceptionForDisplay(Exception ex) 12/20/07 08:59:34 DDSet_Status: Process returned -532459699 12/20/07 08:59:34 DDSet_Error: The Commandline '"C:\DOCUME~1\EWITTE~1\LOCALS~1\Temp\TFServerStatusValidator.exe" ...' returned non-zero value: -532459699. MSI (s) (9C!20) [08:59:36:624]: Product: Microsoft Visual Studio 2008 Team Foundation Server - ENU -- Error 32000.The Commandline '"C:\DOCUME~1\EWITTE~1\LOCALS~1\Temp\TFServerStatusValidator.exe" ...' returned non-zero value: -532459699.	Changing the trust level in the web.config files <trust level> element to any level other than Full will cause Team Foundation Server installaiton to fail with a 28925 error. The change to the "root" web.config file causes all ASP.NET applications to attempt to run at the trust level specified.  TFSServerStatusValidator application requires Full Trust and fails if any level less than full is specified. Resolution Set the trust level to Full Trust to apply to Team Foundation Server Applications.  Preferred method: An entry can be added to the web.config file located in ([Team Foundation Program Files Folder]\Microsoft Visual Studio 2005 Team Foundation Server\Web Services) that applies only to Team Foundation Server Applications. Add to System.web node: <trust level="Full" originUrl="" /> Alternative: This can also be done in the root level web.config for all .NET 2.0 services. Details: http://support.microsoft.com/kb/949548
Error 28925.TFServerStatusValidator: Calling the Team Foundation Server ServerStatus Web service failed. Additional details about the problem can be found in the setup log. Verify your network configuration. For more information on troubleshooting this error, see the Microsoft Help and Support Center.	This error can be caused if the Team Foundation Server name is failing to resolve via DNS. This can be solved by: 1. Check the settings in internet explorer and select the option to bypass proxy server for local adresses. Tools - Internet Option - Connections - LAN Settings - Bypass proxy settings for local addresses. OR 2. Add server name to DNS so it resolves correctly.
Error 28925.TFServerStatusValidator: Calling the Team Foundation Server ServerStatus Web service failed. Additional details about the problem can be found in the setup log. Verify your network configuration. For more information on troubleshooting this error, see the Microsoft Help and Support Center. Log snippet:  TFServerStatusValidator - Team Foundation Server Status Validator tool (C) Copyright 2006 Microsoft Corporation. All rights reserved. The request failed with HTTP status 407: Proxy Authentication Required (The ISA Server requires authorization to fulfill the request. Access to the Web Proxy service is denied. ). ProxyAuthenticationRequired ErrorCallingServerStatus 01/18/07 13:03:04 DDSet_Status: Process returned 2325 01/18/07 13:03:04 DDSet_Status: Found the matching error code for return value'2325' and it is: '28925' 01/18/07 13:03:04 DDSet_Error: 2325 MSI (s) (C8!A0) [13:04:17:281]: Product: Microsoft Visual Studio 2005 Team Foundation Server (services) - ENU -- Error 28925.TFServerStatusValidator: Calling the Team Foundation Server ServerStatus Web service failed. Additional details about the problem can be found in the setup log. Verify your network configuration. For more information on troubleshooting this error, see the Microsoft Help and Support Center. 01/18/07 13:04:17 DDSet_CARetVal: 28925 01/18/07 13:04:17 DDSet_Status: QuietExec returned 28925 01/18/07 13:04:17 DDSet_Exit: QuietExec ended MSI (s) (C8:10) [13:04:17:328]: User policy value 'DisableRollback' is 0 MSI (s) (C8:10) [13:04:17:328]: Machine policy value 'DisableRollback' is 0 Action ended 13:04:17: InstallFinalize. Return value 3.	If you are using a proxy server in which ISA (Internet Security and Acceleration) Server for authentication. (<http://www.microsoft.com/technet/isa/default.mspx>) Edit the machine.config file in the %windir%\Microsoft.NET\Framework\v2.0.50727\CONFIG folder to use the defaults from the Internet Explorer proxy, specify the proxy address, and bypasses the proxy for local access and the customer’s domain. <configuration> ……….. <system.net> <defaultProxy enabled="true" useDefaultCredentials="true"> <proxy usesystemdefault="true" proxyaddress="http://192.168.1.100:8080" bypassonlocal="true" /> <bypasslist> <add address="[a-z]+\.Domainame\.com$"/> </bypasslist> </defaultProxy> </system.net> ………… </configuration>
Error 28925.TFServerStatusValidator: Calling the Team Foundation Server ServerStatus Web service failed. Additional details about the problem can be found in the setup log. Verify your network configuration. For more information on troubleshooting this error, see the Microsoft Help and Support Center.” Log snippet:  MSI (s) (B8:D4) [12:18:00:437]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI18C.tmp, Entrypoint: QuietExec 06/25/07 12:18:00 DDSet_Status: LANGID: 1033 06/25/07 12:18:00 DDSet_Entry: QuietExec started 06/25/07 12:18:00 DDSet_Status: Hiding command line parameters 06/25/07 12:18:00 DDSet_Status: Commandline: "C:\WINDOWS\TEMP\TFServerStatusValidator.exe" ... 06/25/07 12:18:00 DDSet_Status: IgnoreExitCode: 0 06/25/07 12:18:00 DDSet_Status: Silent: 0 06/25/07 12:18:00 DDSet_Status: ActionStart: 0 06/25/07 12:18:00 DDSet_Status: Cost: 0 06/25/07 12:18:00 DDSet_Status: WorkingDirectory: 06/25/07 12:18:00 DDSet_Status: HideCmdLine: 1 TFServerStatusValidator - Team Foundation Server Status Validator tool (C) Copyright 2006 Microsoft Corporation. All rights reserved. The request failed with HTTP status 403: Forbidden. Forbidden ErrorCallingServerStatus 06/25/07 12:18:04 DDSet_Status: Process returned 2325 06/25/07 12:18:04 DDSet_Status: Found the matching error code for return value '2325' and it is: '28925' 06/25/07 12:18:04 DDSet_Error: 2325 MSI (s) (B8!30) [12:18:25:062]: Product: Microsoft Visual Studio 2005 Team Foundation Server - ENU -- Error 28925.TFServerStatusValidator: Calling the Team Foundation Server ServerStatus Web service failed. Additional details about the problem can be found in the setup log. Verify your network configuration. For more information on troubleshooting this error, see the Microsoft Help and Support Center. 06/25/07 12:18:25 DDSet_CARetVal: 28925 06/25/07 12:18:25 DDSet_Status: QuietExec returned 28925 06/25/07 12:18:25 DDSet_Exit: QuietExec ended MSI (s) (B8:50) [12:18:25:109]: User policy value 'DisableRollback' is 0 MSI (s) (B8:50) [12:18:25:109]: Machine policy value 'DisableRollback' is 0 Action ended 12:18:25: InstallFinalize. Return value 3.	Start inetmgr (IIS manager) Under Websites Under Properties for all websites ->Directory Security Under IP Address and Domain Name Restrictions->Select Edit Enable ‘Grant Access’

 

Content by: Arunrama

Reviewed by: Lucky

TFS: "Could not start the TFSserverscheduler service on the local computer. Error 1069. The service did not start due to a logon failure."

You might experience a Windows service start failure for “Team Foundation Server scheduler” service with the error

"Could not start the TFSserverscheduler service on the local computer. Error 1069. The service did not start due to a logon failure." [ ]

Cause:

This might happen if the password for the account that runs the “Team Foundation Server scheduler” service is changed (normally the TFSservice account as mentioned in the install guide) in the Domain/the local computer but is not propagated to Team Foundation Server.

Solution:

If the password for the TFSservice account is changed, then to get the change propagated within Team Foundation Server, you got to run a command “TFSadmintuil changepassword”. For more details on the command please look at the following documents:

For TFS 2005: http://msdn.microsoft.com/en-us/library/ms252453(VS.80).aspx

For TFS 2008: http://msdn.microsoft.com/en-us/library/ms252453.aspx

In situations like the one mentioned above, if the “Team Foundation Server scheduler” service is stopped and not starting, then use the new password to start the service and then immediately after the service starts run the “TFSadminutil changepassword” command.

Content by: Arunrama

Reviewed by: lucky

TFS 2008 SP1 installation failing with TFRSConfig.exe "Configuring Report Manager virtual directory"

Issue

While installing Team Foundation Server 2008 SP1 it fails with following error

Configuring Report Manager virtual directory Reports to use application pool ReportServer...

Error: IllformedAccountString.

Microsoft.TeamFoundation.Admin.ReportingServices.ReportingServicesWmiException: Exception of type 'Microsoft.TeamFoundation.Admin.ReportingServices.ReportingServicesWmiException' was thrown.

Also when we tried to configure “Web Service Identity” thru SQL Reporting Service Configuration Manager manually, we got following error

______________________________________________________________________________________________

ReportServicesConfigUI.WMIProvider.WMIProviderException: The account name is not valid. Specify an account in the form domain\alias.

at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.SetWebServiceIdentity(String applicationPool)

______________________________________________________________________________________________

Environment

Team Foundation Server 2008 (RTM) With SQL 2005

Applies only to SQL Reporting Service 2005, we should not see similar issue with SQL Reporting Service 2008

Cause

From MSI  Log

DDSet_Status: Commandline: "c:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\TFRSConfig.exe" /setup /repair /s "TFS2008" /u "NT Authority\NetworkService" /buildInIdentity /l "1033" /verify /ignoreExistingIISArtifacts /instancename "MSSQLSERVER" /appPoolName "ReportServer" /reportServerUri "http://<Servername>:80/ReportServer" /reportManagerUri "http://< Servername>:80/Reports" /h "<Servername>"

03/16/09 12:11:21 DDSet_Status: IgnoreExitCode: 0

03/16/09 12:11:21 DDSet_Status: Silent: 0

03/16/09 12:11:21 DDSet_Status: ActionStart: 0

03/16/09 12:11:21 DDSet_Status: Cost: 0

03/16/09 12:11:21 DDSet_Status: WorkingDirectory:

03/16/09 12:11:21 DDSet_Status: HideCmdLine: 0

TFRSConfig - Team Foundation Server Reporting Services Configuration Tool

Copyright (c) Microsoft Corporation.  All rights reserved.

Connecting to SQL Server Reporting Services. Please wait...

Invalid namespace

Querying the following Windows Management Instrumentation (WMI) path: IIS://<Servername>/W3SVC.

Inspecting the following Web site: ID=1 Comment=Default Web Site.

The Web site with ID=1 contains the following binding: IP Address=  TCP Port=80 Host header value=.

No host header was set, but a potential Web site match was found: 1.

Inspecting the following Web site: ID=152936315 Comment=SharePoint Central Administration v3.

The Web site with ID=152936315 contains the following binding: IP Address=  TCP Port=17012 Host header value=.

The binding for the following Web site does not match the expected port: IP Address=  TCP Port=17012 Host header value=. The port value for the site does not match the given parameter.

Inspecting the following Web site: ID=1849097886 Comment=Team Foundation Server.

The Web site with ID=1849097886 contains the following binding: IP Address=  TCP Port=8080 Host header value=.

The binding for the following Web site does not match the expected port: IP Address=  TCP Port=8080 Host header value=. The port value for the site does not match the given parameter.

Inspecting the following Web site: ID=1849097887 Comment=Team System Web Access.

The Web site with ID=1849097887 contains the following binding: IP Address=  TCP Port=8090 Host header value=.

The binding for the following Web site does not match the expected port: IP Address=  TCP Port=8090 Host header value=. The port value for the site does not match the given parameter.

Skipping scan of non-Web-site child: AppPools.

Skipping scan of non-Web-site child: Filters.

Skipping scan of non-Web-site child: Info.

Web site id 1 is chosen since it had a matching binding with no host header set

Found web site identifier to use: 1

Deleting virtual directory Reports for Report Manager...

Deleting virtual directory ReportServer for Report Server...

Deleting application pool ReportServer...

Creating application pool ReportServer...

Creating virtual directory Reports for Report Manager...

Configuring Report Manager virtual directory Reports to use application pool ReportServer...

Error: IllformedAccountString.

Microsoft.TeamFoundation.Admin.ReportingServices.ReportingServicesWmiException: Exception of type 'Microsoft.TeamFoundation.Admin.ReportingServices.ReportingServicesWmiException' was thrown.

   at Microsoft.TeamFoundation.Admin.ReportingServices.WMIManagementObjectWrapper.PostProcessResult(ManagementBaseObject resultObject)

   at Microsoft.TeamFoundation.Admin.ReportingServices.WMIManagementObjectWrapper.InvokeWmiMethod(String methodName, Dictionary`2 parameters, String resultKey)

   at Microsoft.TeamFoundation.Admin.ReportingServices.ReportManagerAdmin.SetReportManagerIdentity(String applicationPool)

   at Microsoft.TeamFoundation.Admin.ReportingServices.ReportServerWmi.SetReportManagerIdentity(String appPoolName)

   at Microsoft.TeamFoundation.Admin.ReportingServices.ReportingServicesConfigurator.ConfigureWebServiceArtifacts()

   at Microsoft.TeamFoundation.Admin.ReportingServices.ReportingServicesConfigurator.Run()

   at Microsoft.TeamFoundation.Admin.ReportingServices.Program.Main(String args)

__________________________________________________________________________________________

The Reports & ReportServer web applications are hosted under the default web site.

The application pool for the defuult web site had an identity account which was not in [domain\computer]\UserName format.

The problem is when RS Configuration Manger or TFRSConfig.exe is used to configure the web apps & app pool for report, the sequence goes like this:

1. Create the ReportServer Web application.

2. Create the Reports Web applications.

3. These web applications default to the application pool for the physical site which will host the web apps, in this case the web site is default web site & its application pool is Default AppPool (In my case it was SharePoint - 80).

4. We now create a new app pool called ReportServer with desired [domain]\user account.

5. Next, RS Config manager/TFRSConfig.exe throw an expection when it tries to bind the ReportServer web app to the ReportServer application pool. It gives you an exception stating that the user name format should be in domain\user format.

In this case the DefaultAppPool was set to a user called "Administrator" (no computer name prefixed).

RS Configurations manager & TFRSConfig.exe does not seem to like the fact that the current app pool user account does not have the right user format.

Resolution

To resolve this problem:

1. Either change the user name for DefaultAppPool to [computer]\[username] format.

2. Or change the app pool for the default web site to one that has the user account in the right format. However this is a more expensive change.

 

Content by: Romitg

Reviewed by: lucky

Team Foundation Server 2008: Error while installing - ServerProtocolViolation

Found an issue while installing Team Foundation Server 2008 other day, took some time to drill down on it so thought of sharing.

Issue

While installing Team Foundation Server we were getting error 'ServerProtocolViolation'

From MSI Log

TFServerStatusValidator - Team Foundation Server Status Validator tool
Copyright (c) Microsoft Corporation.  All rights reserved.

Connecting to <ServerName>
Status Code: ServerProtocolViolation
System.Net.WebException: The server committed a protocol violation. Section=ResponseStatusLine
   at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object parameters)
   at Microsoft.TeamFoundation.TeamFoundationStatusValidator.ServerStatusServiceProxy.GetServerStatus()
   at Microsoft.TeamFoundation.TeamFoundationStatusValidator.MakeWebServiceCall()
   at Microsoft.TeamFoundation.TeamFoundationStatusValidator.CheckStat

We also found that at the time of installation, Team Foundation Server website was stopped in IIS. Tried starting the web site manually but it gave error

"The Web Site cannot be started. Another process might be using it"

Cause

Port 8080 was already in use by another application.

Resolution

We changed port of the other application from 8080 to another free port. Started the application and then were able to successfully install Team Foundation Server.

More Information

We can also configure Team Foundation Server to use a port other than 8080

Please refer to "How to customize Deployment of Team Foundation" section in InstallGuide

(Install Guide for Team Foundation Server 2008 can be downloaded from http://www.microsoft.com/downloads/details.aspx?familyid=FF12844F-398C-4FE9-8B0D-9E84181D9923&displaylang=en )

We can also use NETSTAT -n command to find open ports.

Content by: Romitg

Reviewed by: lakhmins

TFS installation and Error 28805

Here is a list of possible 28805 errors and fixes that worked wonders for us. This particular exception is thrown while configuring reporting services for use with Team Foundation Server. Please keep visiting this page for updates.

Exception / Log snippet	Solution
Error 28805.The setup program cannot complete the request to the server that is running SQL Server Reporting Services. Verify that SQL Server Reporting Services is installed and running on the Team Foundation app tier and that you have sufficient permissions to access it. For more information, see the setup log. The MSI log: 01/30/09 12:30:53 DDSet_Status: Commandline: "c:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\createds.exe" /setup /install "http://<serverName>/ReportServer/ReportService.asmx" TfsReportDS "Data source=TFS2008;initial catalog=TfsWarehouse" "TFSServer\TFSSERVICE" "01000000d08c9ddf0115d1118c7a00c04fc297eb" 0 1 01/30/09 12:30:53 DDSet_Status: IgnoreExitCode: 0 01/30/09 12:30:53 DDSet_Status: Silent: 0 01/30/09 12:30:53 DDSet_Status: ActionStart: 0 01/30/09 12:30:53 DDSet_Status: Cost: 0 01/30/09 12:30:53 DDSet_Status: WorkingDirectory: 01/30/09 12:30:53 DDSet_Status: HideCmdLine: 0 Cannot finish the request on Microsoft SQL Server Reporting Server. Please check that Microsoft SQL Server Reporting Services and Windows service are running and you have sufficient privileges on the data tier: System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: This operation is not supported on a report server that is configured to run in SharePoint integrated mode. ---> Microsoft.ReportingServices.Diagnostics.Utilities. OperationNotSupportedSharePointModeException: This operation is not supported on a report server that is configured to run in SharePoint integrated mode.    at Microsoft.ReportingServices.WebServer.WebServiceHelper.EnsureRSNativeMode()    at Microsoft.ReportingServices.WebServer.ReportingService2005..ctor()    at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)    at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object parameters)    at Microsoft.TeamFoundation.Proxy.Reporting.ReportingService.CreateDataSource(String DataSource, String Parent, Boolean Overwrite, DataSourceDefinition Definition, Property Properties)    at Microsoft.TeamFoundation.Client.Tools.createds.Program.Run(String args) Data source creation failed.	This issue is exhibited if Reporting services is configured to run with SharePoint integrated mode. Resolution To reconfigure Reporting services to run on "native" mode: 1) Do not cancel the TFS installation, let the error prompt stay 2) Delete the Reporting services databases (Reportserver and Reportservertemp) from SQL 3) Open reporting services configuration manager and navigate to "Database" section 4) create a new set of database and select "Native" 5) Complete the Database creation wizard 6) Delete the Encryption key inside Reporting services configuration manager 7) Stop and Start Reporting services within Reporting services configuration manager 8) Click "Retry" on the TFS 2008 installation error window.
Installing TFS with SSL enabled on Default web site. Error 28805.The setup program cannot complete the request to the server that is running SQL Server Reporting Services. Verify that SQL Server Reporting Services is installed and running on the Team Foundation app tier and that you have sufficient permissions to accept it. For more information, see the setup log.  Reference: http://ozgrant.com/2007/05/13/tfs-installation-error-28805	There was a SSL certificate associated with the Default Web Site in IIS. This meant that SQL Reporting Services automatically configured itself to require SSL connections. When TFS Setup tries to connect to Report Server to create the data sources, it fails because it is connecting over HTTP. Solution: 1) Open rsreportserver.config from C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\ 2) Set SecureConnectionLevel = 0 3) Continue Setup as normal
Error 28805.The setup program cannot complete the request to the server that is running SQL Server Reporting Services. Verify that SQL Server Reporting Serivces is installed and running on the Team Foundation app tier and that you have sufficient permissions to accept it. For more information, see the setup log.	The account that is configured to run SQL reporting services will be creating the application pool in IIS. If the account does not have enough permissions to create a Application pool, the installation would fail with this error.Enable modify permissions on  "<sysdrive>:\inetpub\WWWroot" folder for the account that runs the Reporing services windows services.

Content by: Arunrama

Reviewed by: Lucky

TFS 2010 Beta 2: Installation – First look!

For all those who are excited and interested to know how the new TFS 2010 installation would be, but did not get a chance to put your hands on it… here comes a detailed screen shot images from Romit on his first installation experience. For those who are still wondering if this release is going to be any better than the previous releases, in terms of installation, YES… it is lot more simple yet detailed. The installation is split into two phases namely Install and configuration.

During the installation phase, bits are laid on the box and the configuration phase takes care of setting up the environment (configuring connections, creating databases, etc...)

The installation launch screen:

Feature selection screen:

Note: This is different from earlier versions where Build, Proxy and SharePoint Extensions were separate install.

 

 

 

Once the installation completes, you are presented with a confirmation screen along with a Checkbox to launch the “Team Foundation Administration Console”. Note: The screen is not posted here.

The Installation phase is done now. Starts the Configuration screen, note the new console “Team Foundation Administration Console”

Configure Installed Features:

  

Basic Install

 

 

· As the name suggests, it’s a strip down edition of Team Foundation Server. Can be installed on Client OS with SQL Express or SQL Full Edition.

. SQL Server reporting Services and Windows SharePoint Services components are not available.

Standard Single Server

· “Standard Single Server” Installs as a single tier installation.

· Works with Default Instance of SQL and SSRS

· Does not ask for any input, takes all default values.

· Kerberos authentication is not supported.

Advanced

· “Advanced” would be the most commonly used option.

· To work with Named SQL, SSRS or already installed and configured WSS.

· To have multi server installation

· Options you for SharePoint and SQL Server reporting services. Allows you to use non default Ports

Detailed Advanced Configuration Wizard

 

Database configuration section:

· Use Pre-existing empty database can be tried after a failed installation attempt. It will only work if Database are empty (did not work for me after one of my attempt failed )

. Also it picked up instance name by itself (I only had one instance on that server)

. When choose to label, the database names changes accordingly.

Service account information section:

.  Now you have a option between NTLM or Kerberos authentication methods.

 

 

 

. “TF254021:The account name or password that you specified is not valid” – The error I got while testing without the domain controller turned ON. (fyi.. just to illustrate the online validation capability)

 

· Information for TFS Web Site, Can change Port Number here, no need to play with MSIproperty.ini file.

· New! you could opt to use Reporting services or not.

· If you uncheck this box, Reporting Services, Analysis Services and Report Reader Account will disappear from left side.

· URLs populate by itself.

SQL server Analysis services settings:

· Correct SSAS Instance was not picked up (unlike SQL and SSRS)

· With correct SSAS Instance

Reporting services reader account information:

· By default using TfsService Account for Reports. (latter during verification, shows a warning that Reports account require lesser permission than Service Account)

SharePoint site configuration section:

· New! you could opt to use SharePoint or not.

SharePoint configuration options:

Team Project collection settings:

Confirmation screen:

Validation check before actual configuration starts:

  

· 1^st Warning that TfsService and TfsReports account is same.

· Warning about TfsReports Account and that a new Application Pool would be created for Default Web Site.

 

 

 

Configuration progress:

 

 

 

 

 

 

 

 

 

 

. Status during Configuration

Application Tier Only

· To have high availability solution in place. (Multiple AT) (earlier we had only secondary AT option, now as many as you want)

· Helpful in Move and Restore scenarios.

Upgrade

· Upgrading from TFS2008 or TFS 2005 to TFS 2010.

Proxy

· To Install Proxy. (Bits should be installed along with MSI installation)

Build Service

· To install Build Service (Bits should be installed along with MSI installation)

Content created by: Romitg

Reviewed by: Lakhmins

“Invalid namespace” error connecting to SQL reporting Services

While installing Team Foundation Server you might see the following error:

The Commandline '"C:\Program Files\Microsoft Visual Studio 2008 Team Foundation
Server\Tools\TFRSConfig.exe" /setup /install /s "servername" /u "NT
Authority\NetworkService" /buildInIdentity /l "1041" /verify
/ignoreExistingIISArtifacts /instancename "MSSQLSERVER" /appPoolName "ReportServer"
/reportServerUri "http://<servername>/ReportServer" /reportManagerUri
"http://<servername>/Reports" /h "servername"' returned non-zero value:
-2147220956.

Applies To: TFS 2005, TFS 2008

MSI log:

TFRSConfig - Team Foundation Server Reporting Services Configuration Tool
Copyright (c) Microsoft Corporation.  All rights reserved.

Connecting to SQL Server Reporting Services. Please wait...
Invalid namespace
Querying the following Windows Management Instrumentation (WMI) path: IIS://<MACHINENAME>/W3SVC.
Inspecting the following Web site: ID=1 Comment=Default Web Site.
The Web site with ID=1 contains the following binding: IP Address=  TCP Port=80 Host header value=.
No host header was set, but a potential Web site match was found: 1.
Inspecting the following Web site: ID=2 Comment=Administration Web Site.
The Web site with ID=2 contains the following binding: IP Address=  TCP Port=5870 Host header value=.
The binding for the following Web site does not match the expected port: IP Address=  TCP Port=5870 Host header value=. The port value for the site does not match the given parameter.
Skipping scan of non-Web-site child: AppPools.
Skipping scan of non-Web-site child: Filters.
Skipping scan of non-Web-site child: Info.
Web site id 1 is chosen since it had a matching binding with no host header set
Found web site identifier to use: 1
Deleting virtual directory Reports_<INSTANCE> for Report Manager...
Deleting virtual directory ReportServer_<INSTANCE> for Report Server...
Deleting application pool ReportServer$<INSTANCE>...

Creating application pool ReportServer$DEVSQLTFS...
Error: OsNotSupported.
Microsoft.TeamFoundation.Admin.ReportingServices.ReportingServicesWmiException: Exception of type 'Microsoft.TeamFoundation.Admin.ReportingServices.ReportingServicesWmiException' was thrown.
   at Microsoft.TeamFoundation.Admin.ReportingServices.WMIManagementObjectWrapper.PostProcessResult(ManagementBaseObject resultObject)
   at Microsoft.TeamFoundation.Admin.ReportingServices.WMIManagementObjectWrapper.InvokeWmiMethod(String methodName, Dictionary`2 parameters, String resultKey)
   at Microsoft.TeamFoundation.Admin.ReportingServices.ReportManagerAdmin.CreateApplicationPool(String applicationPool, Boolean useBuiltin, String account, String password)
   at Microsoft.TeamFoundation.Admin.ReportingServices.ReportServerWmi.CreateManagerApplicationPool(String appPoolName, Boolean useBuiltInAccount, String identity, String password)
   at Microsoft.TeamFoundation.Admin.ReportingServices.ReportingServicesConfigurator.ConfigureWebServiceArtifacts()
   at Microsoft.TeamFoundation.Admin.ReportingServices.ReportingServicesConfigurator.Run()
   at Microsoft.TeamFoundation.Admin.ReportingServices.Program.Main(String args)

Configuring SQL Server Reporting Services failed.
08/20/08 15:10:41 DDSet_Status: Process returned -2147220956

Resolution:

Disable IIS 5.0 Isolation mode.

 

To disable IIS 5.0 Isolation Mode

1.         Click Start, click Control Panel, click Administrative Tools, and then click Internet Information Services (IIS) Manager.

2.         Right-click the Web Sites folder and then click Properties.

3.         On the Service tab. Clear Run WWW service in IIS 5.0 isolation mode.

4.         Click OK.

 

Content by: Vimal

Reviewed by: Lucky

TFS installation and Error 32000

With Team Foundation Server 2005 and 2008 installations, we come across a good number of generic errors. One such error is “Error 32000”. Here is a list of errors and the solutions that might help you.

Note: before trying the solutions given below, carefully look at the exception that you get and compare it with the list of exceptions that are listed here. For the ease of it, the specific command/switch/value to look out for is highlighted in RED.

Also a log snippet is added to the Exception section where ever it is applicable.

Please keep visiting this page as we would update the list as and when we have something new.

 

Exception / Log snippet	Solution
(During installation) Exception: “Error 32000.The Commandline '"C:\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Microsoft Visual Studio 2005 Team Foundation Server (services) - ENU\ConfigureNTLM.exe" /addntlm "Team Foundation Server"' returned non-zero value: 1.“ Log Snippet: Setting NTAuthenticationProviders and HTTP Compression for Website: Team Foundation Server. DDSet_Error: System.Security.SecurityException: Security error. at ManagedCA.GetSiteId(String sitename)at ManagedCA.SetNTLMForWeb(String web) DDSet_Error: Failed to set NTAuthenticationProviders and HTTP Compression for Team Foundation Server	Set My_Computer_Zone permission at FullTrust, under .Net Framework 1.1 Configuration Start > Administrative Tools > Microsoft .Net Framework 1.1 Configuration Runtime Security policy > Enterprise > Code Group > My Computer Zone Right Click and select Properties > Permission Set > Set FullTrust under Permission Set Most TFS installation CustomActions uses .Net Framework 2.0 but this CustomAction uses .Net Framework 1.1
(During installation) Exception: "Error 32000.The Commandline '"C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe" ...' returned non-zero value: -2130246810". log Snippet: 02/28/07 16:30:17 DDSet_Status: Process returned -2130246810 02/28/07 16:30:17 DDSet_Error: The Commandline '"C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe" ...' returned non-zero value: -2130246810. MSI (s) (5C!40) [16:30:56:303]: Product: Microsoft Visual Studio 2005 Team Foundation Server - ENU -- Error 32000.The Commandline '"C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe" ...' returned non-zero value: -2130246810. 02/28/07 16:30:56 DDSet_CARetVal: 32000 02/28/07 16:30:56 DDSet_Status: QuietExec returned 32000 02/28/07 16:30:56 DDSet_Exit: QuietExec ended MSI (s) (5C:8C) [16:30:56:319]: User policy value 'DisableRollback' is 0 MSI (s) (5C:8C) [16:30:56:319]: Machine policy value 'DisableRollback' is 0 Action ended 16:30:56: InstallFinalize. Return value 3.	Check if the default website on port 80 is set to use a static IP. If so,then change is to "All Unassigned". This setting is available in IIS under the websites property> "Web site" tab > IP address:
(During installation) Exception: Error 32000.The Command line '"C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe" ...' returned non-zero value: -1.”	Solution 1: Check for a Host Header value in the “Internet Information services manager” for the default web site. If there were any host header value, remove them. Solution 2: This problem can also happen if we remove “Front Page Server ExTensions” from the machine without unextending the Sharepoint Central Administration Site. Note: "Front page server extensions" is not required for TFS and if this was already installed on the server, the Team Foundation Server installation will fail. In some cases, the removal of FPSE from the machine does not automatically unextend the site. This can cause Windows Sharepoint Services to be misconfigured while installation which in turn could affect Team Foundation Server.
(During installation/ upgrade) Exception: Error 32000.The Commandline '"C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\TfsDb.exe" upgrade /server:"<SERVER_NAME>" /property:"TFS_SERVICE_ACCOUNT= <TFS_SERVICE_AC>;TFS_REPORTING_ACCOUNT= <TFS_REPORTS_AC>;LCID=1033;VSTF_AS_INSTANCE=<SERVER_NAME>; VSTF_AS_DATABASE=TfsWarehouse; VSTF_AS_ACCOUNT=" /showui:656038' returned non-zero value: 100 Log snippet: SQL Error #1 SQL Message: Cannot insert the value NULL into column 'owner_sid', table 'msdb.dbo.sysjobs'; column does not allow nulls. INSERT fails. SQL LineNumber: 137 SQL Source: .Net SqlClient Data Provider SQL Procedure: sp_add_job SQL Error #2 SQL Message: The specified @job_id ('C8EF920A-B2DF-4C5B-9C3E-79548AEF2F56') does not exist. SQL LineNumber: 41 SQL Source: .Net SqlClient Data Provider SQL Procedure: sp_verify_job_identifiers SQL Error #3 SQL Message: The specified @job_id ('C8EF920A-B2DF-4C5B-9C3E-79548AEF2F56') does not exist. SQL LineNumber: 41 SQL Source: .Net SqlClient Data Provider SQL Procedure: sp_verify_job_identifiers SQL Error #4 SQL Message: The specified @job_id ('C8EF920A-B2DF-4C5B-9C3E-79548AEF2F56') does not exist. SQL LineNumber: 41 SQL Source: .Net SqlClient Data Provider SQL Procedure: sp_verify_job_identifiers SQL Error #5 SQL Message: The specified @job_id ('C8EF920A-B2DF-4C5B-9C3E-79548AEF2F56') does not exist. SQL LineNumber: 41 SQL Source: .Net SqlClient Data Provider SQL Procedure: sp_verify_job_identifiers SQL Error #6 SQL Message: The specified @job_id ('C8EF920A-B2DF-4C5B-9C3E-79548AEF2F56') does not exist. SQL LineNumber: 41 SQL Source: .Net SqlClient Data Provider SQL Procedure: sp_verify_job_identifiers SQL Error #7 SQL Message: The statement has been terminated. SQL LineNumber: 137 SQL Source: .Net SqlClient Data Provider SQL Procedure: sp_add_job	The command is trying to create the following Jobs in the SQL server. TfsActivityLogging Administration Job, TfsBuild Team Build Administration Job, TfsIntegration Maintenance Job, TfsVersionControl Administration Job, TfsWorkItemTracking FullTextCrawl Job, TfsWorkItemTracking ProcessIdentities Job. All the Jobs are owned by the "sa" account on the SQL server.  If the SA account on the SQL server Database engine is renamed other than the default name "sa" the command will fail to create the jobs.
(During upgrade) Exception: Error 32000.The Commandline '"D:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\TfsDb.exe" upgrade /server:"<Server Name>" /property:"TFS_SERVICE_ACCOUNT=<Doman Name\TFSService>;TFS_REPORTING_ACCOUNT=<Domain Name\TFSREPORTS>;LCID=1033;VSTF_AS_INSTANCE=<Server Name>;VSTF_AS_DATABASE=TFSWarehouse;VSTF_AS_ACCOUNT=" /showui:131562' returned non-zero value: 100. Log snippet: Upgrading the Warehouse Database (TfsWarehouse) C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\SetupWarehouse.exe -upgrade -int TfsIntegration -s SRV-TFS -d TfsWarehouse -c "C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\Warehouseschema.xml" -a "ITMAR\TFSSERVICE" -ra "ITMAR\TFSREPORTS" -asinst "APPTIER" -asdbname "TFSWarehouse" -asacct "" C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\SetupWarehouse.exe -upgrade -int TfsIntegration -s APPTIERNAME -d TfsWarehouse -c "C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\Warehouseschema.xml" -a "DOMAIN\TFSSERVICE" -ra "DOMAIN\TFSREPORTS" -asinst "APPTIERNAME" -asdbname "TFSWarehouse" -asacct "" An unexpected error occurred: Error in the XML analysis in row 1, column 0: A document must contain exactly one root element. . Metadata Manager error. Failed to instantiate of a metadata object from the file '\\?\C:\Data\DB\MSSQL.2\OLAP\Data\TFSWarehouse.0.db\Build Flavor.1587.dim.xml'.	Once you see the error, don’t cancel the installation. Backup and delete / rename the TFSwarehouse.x.db folder and click the "retry" for the installation. The installation should go fine. The TFSWarehouse.x.db file is usually located in the <drive>:\Program files\Microsoft SQL Server\MSSQL.x\Data
(During upgrade) Exception: Error 32000. The Commandline ‘“C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\TfsDB.exe” From Log file : Invalid column name 'SchemaVersion'. Invalid column name 'SchemaVersion'. ---> System.Data.SqlClient.SqlException: In valid column name 'SchemaVersion'. Invalid column name 'SchemaVersion'	Remove the trigger "trg_Sp1Uninstall" under the database"TFSVERSIONCONTROL". More details on the error and the script to remove the trigger can be found on Microsoft KB 955008
(While installing the hotfix KB919156) Exception: Error 32000.The Commandline '"C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe" ...' returned non-zero value: -2130246810.	While installing Hotfix or doing any kind of servicing (repair/upgrade/installing service pack). TFS should be using Default configuration with NO Https and SSL. Disabled SSL and then install Hotfix To reconfigure SSL and HTTPS for TFS after the SP1 installation is done, please check this link.

Content created by: Romitg

Reviewed by: Lakhmins

TFS 2008: “Error 29112” during installation.

When you install Team Foundation Server 2008 to use an existing instance of SQL server Reporting services or if you have already installed and configured SQL server reporting services on the Application tier, you might encounter an error,

Error 29112. "Team Foundation Report Server Configuration. Either Sql Reporting Services not properly configured, or the Reporting services website could not be reached. Use the Reporting services configuration tool to confirm that SQL Reporting Services is configured properly and that the reporting service website can be reached, and then run the installation again. For more information, see the team foundation installation guide."

 

Cause

This error appears if SQL server reporting services databases are configured in SharePoint integration mode. Team Foundation Server 2008 works with reporting services databases on “native mode”. This part of the configuration is done by the Team Foundation server installation by itself. That is why it is recommended to just install SQL server reporting services with “Install but do not configure the server” option (refer point .13 of the install guide, section: How to: Install SQL Server Reporting Services in a Dual-Server Deployment)

Resolution

1)    Drop the existing reports databases (including the tempdb) from SQL server management studio.

2)    Launch SQL server “Reporting services configuration manager” and connect to the reporting services instance.

3)    Select “Database setup” and click new to create a new set of databases and make sure “create the report server database in SharePoint Integrated mode.” option is unchecked.

4)    Once the databases are created and connected fine, continue with the Team Foundation Server installation.

 

Content by: Raviku

Reviewer: Lucky

TFS 2008: Error 32000 while upgrading TFS from 2005 to 2008+SP1

While upgrading Team Foundation Server from 2005 to 2008 with Slipstreamed SP1 you might experiance an error:

Error 32000.The Commandline '"Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\TfsDb.exe" upgrade /server:"SERVER" /property:"TFS_SERVICE_ACCOUNT=SERVER\TFSSERVICE;TFS_REPORTING_ACCOUNT=SERVER\TFSREPORTS;LCID=1033;VSTF_AS_INSTANCE=SERVER;VSTF_AS_DATABASE=TFSWarehouse" /showui:196682' returned non-zero value: 100.

Cause

The TFSWarehouse binaries inside the SQL OLAP data folders got corrupt.

Log snippet:

Upgrading the Warehouse Database (TfsWarehouse)
C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\SetupWarehouse.exe
-upgrade -int TfsIntegration -s SRV-TFS -d TfsWarehouse -c "C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\Warehouseschema.xml" -a "ITMAR\TFSSERVICE" -ra "ITMAR\TFSREPORTS" -asinst "APPTIER" -asdbname "TFSWarehouse" -asacct ""
C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\SetupWarehouse.exe -upgrade -int TfsIntegration -s APPTIERNAME -d TfsWarehouse -c "C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\Warehouseschema.xml" -a "DOMAIN\TFSSERVICE" -ra "DOMAIN\TFSREPORTS" -asinst "APPTIERNAME" -asdbname "TFSWarehouse" -asacct ""
An unexpected error occurred: Error in the XML analysis in row 1, column 0: A document must contain exactly one root element.
.
Metadata Manager error. Failed to instantiate of a metadata object from the file '\\?\C:\Data\DB\MSSQL.2\OLAP\Data\TFSWarehouse.0.db\Build Flavor.1587.dim.xml'.

Resolution

Once you see the error, don’t cancel the installation. Backup and delete / rename the TFSwarehouse.0.db folder and click the "retry" for the installation. The installation should go fine.

Content by: Raviku

Reviewed by: Lakhmins 

TFS 2008: Prescan.exe error while performing a SharePoint upgrade

As part of upgrade, you might decide on upgrading SharePoint from 2.0 to 3.0. The SharePoint upgrade requires a prerequisite step of running a tool called “prescan.exe” which is shipped along with the WSS 3.0 redistributable or can be downloaded here.

When you run the tool, you might see this error:

Error: Prescan has encountered sites or lists that were not updated because they cannot be accessed using the SharePoint Products and Technologies object model. The most likely reasons for Prescan to skip a list are covered in the Knowledge Base article at: http://go.microsoft.com/fwlink/?linkid=69958&clcid=0x409.
Skipping virtual server: http://<machinename>:8080/. Server state = NeedExtend. Most likely this virtual server is not extended with WSS v2

LOG SNIPPET:
Checking if Server="SQLPROD11";Database="STS_Content_TFS";Trusted_Connection=yes;App="prescan.exe" is a WSS V2 SP2 database.
02/16/2009 14:47:26 Checking if any site has not yet been scanned in Server="SQLPROD11";Database="STS_Content_TFS";Trusted_Connection=yes;App="prescan.exe".
02/16/2009 14:47:26 Error: The following site has not been scanned. Id = aecdb1fd-79f8-43f5-8c8a-0e8e2b665bd9 and Url = /sites/Integration
02/16/2009 14:47:26 Checking if any list has not yet been scrubbed in Server="DATATIERNAME";Database="STS_Content_TFS";Trusted_Connection=yes;App="prescan.exe".
02/16/2009 14:47:26 Error: Prescan has encountered sites or lists that were not updated because they cannot be accessed using the SharePoint Products and Technologies object model. The most likely reasons for Prescan to skip a list are covered in the Knowledge Base article at: http://go.microsoft.com/fwlink/?linkid=69958&clcid=0x409.
02/16/2009 14:47:26 Skipping virtual server: http://<machinename>:8080/. Server state = NeedExtend. Most likely this virtual server is not extended with WSS v2.
02/16/2009 14:47:26 Scan finished with failure.
02/16/2009 14:47:26 ===============================Logs=============================
02/16/2009 14:47:26 Log file: C:\DOCUME~1\tfssetup\LOCALS~1\Temp\PreupgradeReport_633703924432084507_Log.txt
02/16/2009 14:47:26 Summary file: C:\DOCUME~1\tfssetup\LOCALS~1\Temp\PreupgradeReport_633703924432084507_Summary.xml
02/16/2009 14:47:26 ==============================Totals=============================
02/16/2009 14:47:26 Number of sites skipped (already scanned):   0
02/16/2009 14:47:26 Number of sites scanned:   16
02/16/2009 14:47:26 Number of broken sites:   1 (6.25% of total).
02/16/2009 14:47:26 Number of webs scanned:   16
02/16/2009 14:47:26 Number of broken webs:   1 (6.25% of total).
02/16/2009 14:47:26 Number of webs using custom template:   1 (6.25% of total).
02/16/2009 14:47:26 Number of pages scanned:   1397
02/16/2009 14:47:26 Number of unghosted pages:   14 (1.00% of total).

Cause

One of the sites that the pre-scan tool is failing on is using a SFTS template (scrum for team system.)

The issue shows itself after an upgrade to TFS 2008. The symptom can be felt when you try to browse the project portal site with existing SFTS 1.2 template, the site shows a 404 error.

This has been caused by the removal of files required for the WSS template.

Resolution

1. Backup the following folders:

Program files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Layouts [ if present - might have been deleted already during upgrade ]

Program files\Common Files\Microsoft Shared\Web Server Extensions\60\Template\1033

2. Download this file and extract it into Program files\Common Files\Microsoft Shared\Web Server Extensions. The zip contains the relevant paths to the files it needs to copy.

3. Run an IIS Reset.

Now the site should start using the SFTS templates. Run the Prescan tool it should run successfully

More references:

http://blogs.conchango.com/sfts/archive/2008/04/28/sharepoint-fix-for-scrum-for-team-system-2-1-upgrades.aspx
http://blogs.msdn.com/tfsao/archive/2008/05/13/problems-upgrading-conchango-s-scrum-for-team-system-from-1-x-to-2-x-with-tfs-2008.aspx

Content by: Raviku

Reviewed by: Lakhmins

TFS 2008: PCW fails with An internal error occurred on the report server. The EXECUTE permission was denied on the object 'xp_sqlagent_notify'

Issue

When a new TFS project is created, you might see the following error

F30225: Error uploading report : Work Item with Tasks
Exception Details: The Project Creation Wizard encountered a problem while
creating reports on the SQL Server Reporting Services on <Server Name>.
The reason for the failure cannot be determined at this time.
Because the operation failed, the wizard was not able to finish.

 See the error log for more details. ---> The EXECUTE permission was denied on the object 'xp_sqlagent_notify', database 'mssqlsystemresource', schema 'sys'.
SoapException

Cause

 xp_sqlagent_notify,xp_sqlagent_is_starting and  xp_sqlagent_enum_jobs under Master Database did not have the execute permission for the RSEXECROLE.

Resolution

1.    On the data-tier server, click Start, point to All Programs, point to Microsoft SQL Server, and then click SQL Server Management Studio.  

2.    In the Server type list, click Database Engine.

3.    In the Server name list, click or type the appropriate server.

4.    In the Authentication list, click the appropriate scheme.

5.    In User name, type the user name of a valid account.

6.    In Password, type the password of the account if SQL Server requires it, and then click Connect.

7.    Expand Database

8.    Expand System Databases

9.    Expand Master Database

10.  Expand Programmability

11.  Expand Extended Stored Procedures

12.  Under System Extended Stored Procedures

13.  Right Click on sys.xp_sqlagent_notify, Seletect Properteis and click on Permissions Make sure that RSExecRole has Execute permssion 

 Set same permissions for sys.xp_sqlagent_is_starting and sys.xp_sqlagent_enum_jobs

Content by: Romitg

Reviewed by: Lucky

TFS 2008 / Visual Studio Team Foundation Server Task Scheduler not starting automatically

Issue

When we restart the Team Foundation Server(The AT box, on a dual tier server), Visual Studio Team Foundation Server Task Scheduler service might not start automatically even if it is set to start automatically

 

Resolution

To resolve this issue make the SQL Server Agent a dependency to Visual Studio Team Foundation Server Task Scheduler Service.

To do this, go to the registry editor and add a Multi-String Value to the corresponding service entry:

Start | Run | Regedit

Key: \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TFSServerScheduler
Right click "New Multi-String Value"
Name: DependOnService
Value: SQLAgent  (you will have to mentioned SQL Server Name/Instance Name)

Content by: Romitg

Reviewed by: Lucky

TFS 2008/ Setupwarehouse command would fail after upgrading SQL

As part of upgrading SQL 2005 to 2008, you are required to recreate the TFSwarehouse cube. When the Setupwarehouse.exe command is ran you might see the following error:

"An unexpected error occurred: Error encountered when creating connection to Analysis Services. Contact your Team Foundation Server administrator"

Resolution

Edit the application configuration file for Setupwarehouse.exe.

You can find setupwarehouse.exe.config file typically at %Program Files%\Microsoft Visual Studio 2008 Team Foundation Server\Tools

Change the newVersion attribute from 9.0.242.0 to 10.0.0.0.

Cause

This would happen if you have upgraded SQL 2005 to SQL 2008

SQL upgade will not update configure file of the Setupwarehouse.exe it would still have newVersion as "9.0.242.0"

Content by: Romitg

Reviewed by: Lucky

TF31005 Error is coming up, and not able to connect to Team Foundation Server

Next couple of blogs are from Romitg, these are some of the interesting issues he had fixed:

Issue

When you try accessing Team Foundation Server using Team Explorer within the server, you might see a connection failure with error TF31005.

Symptoms:

Open http://localhost/default.aspx this should work fine
Open http://<servername>.aspx , you might get an Error Message: 403.6 - Forbidden: IP address rejected
Try connecting to TFS with IP address or using  local host  the connection should be successful

Cause:

 The Default website on port 8080 might be set with “Denied access” under  “IP address access restrictions” and have a exception set only for the loopback adaptor (127.0.0.1)

Solution:

 Start| Run| inetmgr
Expand Web site| Default Web Site Properties | Directory Security | Edit “IP address
and domain name restriction” and selected Grant access

Content by: Romitg

Reviewed by: Lucky

Posted by Arunrama | 0 Comments

Filed under: TFS Connectivity, error TF31005