TF31001 and TF31002 Errors on TFS
-
Tuesday, May 09, 2006 8:34 AM
Hi,
Logging on TFS as TFSSetup for creating team project causes the error TF31002 when trying to connect to available TFS. The TFS is online, name(TFS),port (8080) and protocol (http) are correct, also the password is correct because i'm logging on the TFS via Remote Desktop with the same Password.
When trying to log on the same TFS with another name (TFSService) and trying to the the same action (creating Team project), the error TF31001 occurs with message (The request failed with HTTP status 404:.). This occurs also when trying to connect to the available tfs.
Anyone can help!
Thanks a lot!
N.B.: Trying the server connection with http://localhost/default.aspx works correct (the share point server portal is displayed!!!).
All Replies
-
Friday, June 23, 2006 3:19 PM
Please let us know if you are still having problems connecting to the server.
A quick test for basic connectivity is to open IE on the client machine and navigate to: http://<server>:8080/services/v1.0/serverstatus.asmx. You should see a description of the Team Foundation Server Status web service.
-
Wednesday, July 12, 2006 3:07 PM
I encountered TF31001 error when I am trying to connect to TFS with Team Explorer. It says "The request failed with HTTP status 404". Could anybody give me help on this? Thanks a lot.
Neil
-
Thursday, July 13, 2006 2:00 AMBesides, I can't open http://<server>:8080/services/v1.0/serverstatus.asmx, it returned http status 404 as well. After that, I cleared all information in team explorer, and readded a TFS server, this time, it returned TF31002. I am sure the TFS is running well. Because I am able to open http://server:8080 with the same account in browser. Even I used Team explorer on the same machine as TFS, I got the same error.
-
Thursday, July 13, 2006 12:55 PM
If you cannot use IE to browse to http://<server>:8080/services/v1.0/serverstatus.asmx you will not be able to connect using the client. You say that TFS is running well because you can open http://server:8080. That URL would normally not serve up a page on a TFS system that is running well. What do you see?
Please try this:
- Open Internet Information Services Manager on the TFS application tier machine
- Expand the local computer node, Web Sites and the Team Foundation Server 2005 site
- Expand Services/v1.0
- Right click on serverrstatus.asmx and select Browse
-
Thursday, July 13, 2006 2:58 PM
Thanks Bill. Originally, I created a virtual site with URL http://server:8080 in SharePoint Service central management, so I can see it in browser. After I removed the whole site. And tried servicestatus.asmx as you said. This time I got error as follows:
The XML page cannot be displayed
Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.
Invalid at the top level of the document. Error processing resource 'http://localhost:8080/services/v1.0/ServerStatus.asmx'...
TF10216: Team Foundation services are currently unavailable. Try again later. If the problem persists, contact your Team Fou...
I checked Event log, there is error item for TFS, the error message is:
TF53010: An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
Technical Information (for the administrative staff):
Date (UTC): 7/13/2006 2:50:05 PM
Machine: LTI-STATION
Application Domain: /LM/W3SVC/3/Root/services-95-127972758049375000
Assembly: Microsoft.TeamFoundation.Server, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: w3wp
Process Id: 5048
Thread Id: 3804
Account name: LTI-STATION\tfsDetailed Message: TF30059: Fatal error while initializing web service
Web Request Details
Url: http://lti-station:8080/Services/v1.0/ServerStatus.asmx [method: POST]
User Agent: Team Foundation (TFSServerScheduler.exe, 8.0.50727.147)
Headers: Content-Length=354&Content-Type=text%2fxml%3b+charset%3dutf-8&Accept-Encoding=gzip&Accept-Language=en-US&Expect=100-continue&Host=lti-station%3a8080&User-Agent=Team+Foundation+(TFSServerScheduler.exe%2c+8.0.50727.147)&X-TFS-Version=1.0.0.0&SOAPAction=%22http%3a%2f%2fschemas.microsoft.com%2fTeamFoundation%2f2005%2f06%2fServices%2fServerStatus%2f03%2fCheckAuthentication%22
Path: /Services/v1.0/ServerStatus.asmx
Local Request: True
Host Address: 172.16.113.222
User: LTI-STATION\tfs [authentication type: NTLM]Exception Message: TF30055: Visual Studio could not find or read the Team Foundation Server server name in the configuration file. Contact your Team Foundation Server administrator. (type VstfNotConfiguredException)
Exception Stack Trace: at Microsoft.TeamFoundation.Server.TeamFoundationApplication.get_TfsNameUrl()
at Microsoft.TeamFoundation.Server.Plugin.InitializePlugins()
at Microsoft.TeamFoundation.Server.Global.EnsureInitialized(HttpApplication app)In addition, there are some error items for SQLBrowser in event viewer, the error message is:
The SQL configuration for SQL is inaccessible or invalid.
The SQLBrowser service is started. Could you please help me on this and give me any useful suggestion? Thanks.
-
Friday, July 14, 2006 2:00 PM
Extending SharePoint to the site hosting TFS did some damage. That also explains why you were not able to see serverstatus.asmx. SharePoint uses an ISAPI filter that must be explicitly configured to pass traffic to other applications like TFS. It seems like the installation of SharePoint over TFS also modified the top level web.config file. The error messages are complaining about not being able to find a key called TfsNameUrl in %ProgramFiles%\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\Web.config. You might check the vicinity for a web.config.sav... otherwise, you will either need to reinstall or try to find a healthy web.config file to replace the one that was overwritten. If you do drop in a new web.config file, the TfsNameUrl and TFS Name will need to be updated with your machine name. -
Friday, July 14, 2006 3:50 PM
Thanks for the quick reply. I decided to reinstall both sharepoint service and TFS. However, almost at the end of the installation for TFS, I encountered a new error:
Failed to load EventService proxy object: Requested registry access is not allowed..
07/14/06 23:11:19 DDSet_Status: Process returned 1120
07/14/06 23:11:19 DDSet_Status: Found the matching error code for return value '1120' and it is: '28100'
07/14/06 23:11:19 DDSet_Error: 1120
MSI (s) (EC!08) [23:35:16:093]: Product: Microsoft Visual Studio 2005 Team Foundation Server - ENU -- Error 28100.Error loading Event web service.Someone said that give creat/write privilidge on c:\windows\temp for tfsservice, I did this, but the problem still there.
-
Monday, July 17, 2006 2:59 PM
The error looks like the account you are using to install TFS does not have permission to create a new event log source. You should be installing TFS as an Administrator, so we need to check the permissions associated with the Administrators group. Here is how you do that:
- Open regedit
- Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog
- Right click on the Eventlog node and select permissions
- Click the Advanced button
- Verify that Administrators are granted Full Control to the key and all subkeys
-
Monday, July 17, 2006 3:22 PM
Hi Bill, I am terrible sorry that I failed again after I did as what you described. I reset the permission for administrators group. But it still reported 28100 during the installation. I am really confused why the first time I am able to successfully install TFS, then after I removed and reinstall it, always failed.
Thanks,
Neil
-
Monday, July 17, 2006 3:43 PM
Did the permission for the Administrators group actually need to be reset to grant full control or did you just do that for safe measure?
Are there any entries in the system event logs that might provide a clue?
-
Monday, July 17, 2006 3:55 PM
I reset permission for administrators group just for safe based on your suggestion. I checked the event log on Win server 2003, found there is error for TFS:
The description for Event ID ( 9002 ) in Source ( TFS Services ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Team Foundation Core Web Service Application shut down..
In addition, there are dozons of errors for SQLBrowser, I don't know what they are, there are 4 - 5 errors for SQLBrowser generated per minutes. The error description for it is:
The SQL configuration for SQL is inaccessible or invalid.
You've already given me much help on my problem, really thanks on that.
Neil
-
Monday, July 17, 2006 4:19 PM
New issues seem to be cropping up at every turn. The best recovery path for this failed installation may end up being a complete rebuild of both the application and data tier machines.
You have uninstalled TFS from the AT but you are seeing an event log entry declaring that the application has been shut down? Does the time stamp put the entry at or near one of your installation attempts? That would make some sense...
We need to get the DT healthy before trying to install the AT. You might try bringing up the SQL Server Management Studio to look at the SQL Server Logs under the Management node. You could also try launching the SQL Server Configuration Manager and try to start the SQL Server Browser service manually to see if you get a different error code.
-
Tuesday, July 18, 2006 9:50 AM
Hi Bill,
Thanks for the help again. I removed/reinstalled SQL Server 2005 and Sharepoint service 2 SP2, no more SQLBrowser errors. And then started to install TFS, however the 28100 error still there. Finally, I found one post message, it works. Here's the detail:
1- open regedit and go to: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\TeamFoundation\Servers
2- locate a key under servers with the name: <%YourServerName%>
3- delete this key (not only the value, yet the entire key).
4-rerun setup.
And I can use Team explorer to create one team project successfully this time. This is really great. :)

