Fail Team Project creation

Question

After installing TFS Beta 3, everything seems ok. Can connect to it, manage it, etc.

However I cannot create projects sucessfully. When I try to I get this (excerpt from log):

Event Description: TF30162: Task "SharePointPortal" from Group "Portal" failed
Exception Type: Microsoft.TeamFoundation.Client.PcwException
Exception Message: Unable to connect to the Windows SharePoint Services at TEAMSYS1
Exception Details: The Project Creation Wizard was not able to connect to the Windows SharePoint Services
at TEAMSYS1. The reason for the failed connection cannot be determined at this time.
Because the connection failed, the wizard was not able to complete creating
the Windows SharePoint Services site.

and later in the log:

 --   Inner Exception   --
Exception Type: System.Net.WebException
Exception Message: The request failed with HTTP status 404: Not Found.
WebException: Response Status Code: NotFound
WebException: Response Status Message: Not Found
WebException: Status : ProtocolError

When I try to get to http://teamsys1:8080 I get an Error 403.

None of the components installed complained about anything and all were running just fine. Any clue what's going on here?

Answer 1

Hi Enj,

  I have a similar problem :

---begin Exception entry---
Time: 9/28/2005 4:17:29 AM
Module: Engine
Event Description: TF30162: Task "SharePointPortal" from Group "Portal" failed
Exception Type: Microsoft.TeamFoundation.Client.PcwException
Exception Message: Unable to connect to the Windows SharePoint Services at 192.168.1.12
Exception Details: The Project Creation Wizard was not able to connect to the Windows SharePoint Services
at 192.168.1.12. The reason for the failed connection cannot be determined at this time.
Because the connection failed, the wizard was not able to complete creating
the Windows SharePoint Services site.
Stack Trace:
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)
   at Microsoft.VisualStudio.TeamFoundation.ProjectCreationEngine.TaskExecutor.PerformTask(IProjectComponentCreator componentCreator, ProjectCreationContext context, XmlNode taskXml)
   at Microsoft.VisualStudio.TeamFoundation.ProjectCreationEngine.RunTask(Object taskObj)
 --   Inner Exception   --
Exception Type: Microsoft.TeamFoundation.Client.PcwException
Exception Message: Unable to connect to the Windows SharePoint Services at 192.168.1.12
Exception Details: The Project Creation Wizard was not able to connect to the Windows SharePoint Services
at 192.168.1.12. The reason for the failed connection cannot be determined at this time.
Because the connection failed, the wizard was not able to complete creating
the Windows SharePoint Services site.
Stack Trace:
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.VerifyLcidOnServer(ProjectCreationContext ctxt, Int32 lcid)
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.ValidateSite(ProjectCreationContext context, XmlNode site)
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Validate(ProjectCreationContext context, XmlNode taskXml)
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)
 -- end Inner Exception --
 --   Inner Exception   --
Exception Type: System.Net.WebException
Exception Message: Unable to connect to the remote server
WebException: Status : ConnectFailure
Stack Trace:
   at System.Net.HttpWebRequest.GetRequestStream()
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.TeamFoundation.Proxy.Portal.Admin.GetLanguages()
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.VerifyLcidOnServer(ProjectCreationContext ctxt, Int32 lcid)
 -- end Inner Exception --
 --   Inner Exception   --
Exception Type: System.Net.Sockets.SocketException
Exception Message: No connection could be made because the target machine actively refused it
Stack Trace:
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
 -- end Inner Exception --
--- end Exception entry ---


succes ;-)
Bart

Answer 2

Yep, and I have the same problem.  Same exact error as above.

Answer 3

Have you tried adding your domain account as an administrator on the machine that is hosting Team System Server?

Answer 4

I can't create projects either. I get the same eventual error number but the log shows a different cause

----
9/28/2005 10:19:14 PM | Module: WssSiteCreator | Thread: 11 | TF30267: Exception: System.Net.WebException: The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF
   at System.Net.WebClient.UploadDataInternal(Uri address, String method, Byte[] data, WebRequest& request)
   at System.Net.WebClient.UploadData(Uri address, String method, Byte[] data)
   at System.Net.WebClient.UploadData(String address, String method, Byte[] data)
   at Microsoft.VisualStudio.TeamFoundation.WssUtilities.UploadData(Byte[] fileData, String remoteFullName, String siteUrl, ICredentials credentials)
   at Microsoft.VisualStudio.TeamFoundation.WssUtilities.UploadFile(String localFile, String remoteFullName, String siteUrl, ICredentials credentials)
   at Microsoft.VisualStudio.TeamFoundation.WssUtilities.UploadFile(String localFile, DocumentLibraryInfo docLib, String relativeUrl, String siteUrl, ICredentials credentials)
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.HandleFileCreation(ProjectCreationContext context, XmlNode taskNode)
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)
---begin Exception entry---
Time: 9/28/2005 10:19:14 PM
Module: Engine
Event Description: TF30162: Task "SharePointPortal" from Group "Portal" failed
Exception Type: Microsoft.TeamFoundation.Client.PcwException
Exception Message: The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF
WebException: Status : ServerProtocolViolation
Stack Trace:
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)
   at Microsoft.VisualStudio.TeamFoundation.ProjectCreationEngine.TaskExecutor.PerformTask(IProjectComponentCreator componentCreator, ProjectCreationContext context, XmlNode taskXml)
   at Microsoft.VisualStudio.TeamFoundation.ProjectCreationEngine.RunTask(Object taskObj)
 --   Inner Exception   --
Exception Type: System.Net.WebException
Exception Message: The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF
WebException: Status : ServerProtocolViolation
Stack Trace:
   at System.Net.WebClient.UploadDataInternal(Uri address, String method, Byte[] data, WebRequest& request)
   at System.Net.WebClient.UploadData(Uri address, String method, Byte[] data)
   at System.Net.WebClient.UploadData(String address, String method, Byte[] data)
   at Microsoft.VisualStudio.TeamFoundation.WssUtilities.UploadData(Byte[] fileData, String remoteFullName, String siteUrl, ICredentials credentials)
   at Microsoft.VisualStudio.TeamFoundation.WssUtilities.UploadFile(String localFile, String remoteFullName, String siteUrl, ICredentials credentials)
   at Microsoft.VisualStudio.TeamFoundation.WssUtilities.UploadFile(String localFile, DocumentLibraryInfo docLib, String relativeUrl, String siteUrl, ICredentials credentials)
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.HandleFileCreation(ProjectCreationContext context, XmlNode taskNode)
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)
 -- end Inner Exception --
--- end Exception entry ---

Answer 5

Hi Matthew,

  I have no domain, only 2 virtual machines on one pc. The first virtual machine runs the team server,the other one runs the visual studio tfs client.

Thanks for your feedback,
Bart

Answer 6

Okay... I will try to address the errors in this thread.

1. The request failed with HTTP status 404: Not Found.
 This is caused by the WSS default server not being extended or extended wrong.  Go into Central Admin site, and manage the virtual servers.  If default is not extended, extend the site.  If it is extended, remove it and re-extend.

2.No connection could be made because the target machine actively refused it
  This is caused because IIS or the computer force closed your connection you tried to make.  This usually occurs in a firewall port block or when there is no active listening app on the port you are trying to hit.  Ensure you have ports open for 80 on the server.  If you continue to get it, use a sniffer to determine where you are hitting and what port you are hitting.  It may be going to a different place/port

3. The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF
   See #1 above,  I cannot remember the exact cause of this, but I think it #1

Answer 7

I'm in the error #2 group. Port 80 is open on the tfs server, but in the course of checking that I noticed WSS had not extended my Default Web Site, which should have caused error #1.  When I try to extend it I get an error "unable to connect to database". Time to start over again.

Answer 8

I am able to browse by IP to the site. I am unable to determine why it is saying it can not connect to the server. Here is the project log:

...

9/29/2005 7:57:55 AM | Module: Engine | Thread: 10 | Running Task "" from Group ""
9/29/2005 7:57:55 AM | Module: Engine | Task "" from Group "" completed with success | Completion time: 0 seconds
9/29/2005 7:57:55 AM | Module: Engine | Thread: 10 | Running Task "SharePointPortal" from Group "Portal"
---begin Exception entry---
Time: 9/29/2005 7:58:23 AM
Module: Engine
Event Description: TF30162: Task "SharePointPortal" from Group "Portal" failed
Exception Type: Microsoft.TeamFoundation.Client.PcwException
Exception Message: Unable to connect to the Windows SharePoint Services at xxx.xxx.xxx.xx
Exception Details: The Project Creation Wizard was not able to connect to the Windows SharePoint Services
at xxx.xxx.xxx.xx. The reason for the failed connection cannot be determined at this time.
Because the connection failed, the wizard was not able to complete creating
the Windows SharePoint Services site.
Stack Trace:
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)
   at Microsoft.VisualStudio.TeamFoundation.ProjectCreationEngine.TaskExecutor.PerformTask(IProjectComponentCreator componentCreator, ProjectCreationContext context, XmlNode taskXml)
   at Microsoft.VisualStudio.TeamFoundation.ProjectCreationEngine.RunTask(Object taskObj)
 --   Inner Exception   --
Exception Type: Microsoft.TeamFoundation.Client.PcwException
Exception Message: Unable to connect to the Windows SharePoint Services at xxx.xxx.xxx.xx
Exception Details: The Project Creation Wizard was not able to connect to the Windows SharePoint Services
at xxx.xxx.xxx.xx. The reason for the failed connection cannot be determined at this time.
Because the connection failed, the wizard was not able to complete creating
the Windows SharePoint Services site.
Stack Trace:
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.VerifyLcidOnServer(ProjectCreationContext ctxt, Int32 lcid)
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.ValidateSite(ProjectCreationContext context, XmlNode site)
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Validate(ProjectCreationContext context, XmlNode taskXml)
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)
 -- end Inner Exception --
 --   Inner Exception   --
Exception Type: System.Net.WebException
Exception Message: Unable to connect to the remote server
WebException: Status : ConnectFailure
Stack Trace:
   at System.Net.HttpWebRequest.GetRequestStream()
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.TeamFoundation.Proxy.Portal.Admin.GetLanguages()
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.VerifyLcidOnServer(ProjectCreationContext ctxt, Int32 lcid)
 -- end Inner Exception --
 --   Inner Exception   --
Exception Type: System.Net.Sockets.SocketException
Exception Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
Stack Trace:
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
 -- end Inner Exception --
--- end Exception entry ---

9/29/2005 7:58:23 AM | Module: Engine | Thread: 10 | TF30202: Task "" from Group "" will not be run because a prior task failed.
9/29/2005 7:58:23 AM | Module: Engine | Thread: 10 | TF30202: Task "Site" from Group "Reporting" will not be run because a prior task failed.
9/29/2005 7:58:23 AM | Module: Engine | Thread: 10 | TF30202: Task "Populate Reports" from Group "Reporting" will not be run because a prior task failed.
9/29/2005 7:58:23 AM | Module: Engine | Thread: 10 | TF30202: Task "" from Group "" will not be run because a prior task failed.
9/29/2005 7:58:23 AM | Module: Engine | Thread: 6 | Attempting to delete MSF folder "C:\Documents and Settings\HGSTFSSetup\Local Settings\Temp\TPW_tmpFD.tmp"
9/29/2005 7:58:25 AM | Module: Engine | Thread: 6 | The temporary folder C:\Documents and Settings\HGSTFSSetup\Local Settings\Temp\TPW_tmpFD.tmp used to store the process template was removed.
---begin Exception entry---
Time: 9/29/2005 7:58:26 AM
Module: Wizard
Event Description: TF30002: The New Team Project Wizard encountered an error deleting the project test15
Exception Type: System.Net.WebException
Exception Message: Unable to connect to the remote server
WebException: Status : ConnectFailure
Stack Trace:
   at System.Net.HttpWebRequest.GetRequestStream()
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.TeamFoundation.Proxy.Portal.Admin.GetLanguages()
   at Microsoft.TeamFoundation.Client.TeamProjectDeleter.Delete()
   at Microsoft.VisualStudio.TeamFoundation.PortfolioProjectForm.TryDeleteProject()
 --   Inner Exception   --
Exception Type: System.Net.Sockets.SocketException
Exception Message: No connection could be made because the target machine actively refused it
Stack Trace:
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
 -- end Inner Exception --
--- end Exception entry ---

note: the actual IP was replaced with xxx.xxx.xxx.xx

Any help would be appreciated.

Answer 9

This seems to be one of the most consistent and common problems so far in this build. From what I can tell there are issues surrounding how TFS communicates with Sharepoint Services. I have identified two scenarios:

1. Project creation and management is possible yet browsing to the portal itself is not regardless of group membership in TFS, SQL or Sharepoint. setting the authentication provider for the default web to NTLM with adsutil.vbs (this is not set by default) seems to allow browsing to the portal although after that I was no longer able to create projects (not sure if this was due to the NTLM change or me changing the admin port of sharepoint, I am reinstalling to verify setting NTLM before the other products go in)

2. Project creation is not possible with the log stating that either the connection was refused or that sharepoint simply could not be reached even though sharepoint seems to run correctly and can be managed.

I can't seem to find out what user TFS is using to communicate or how it's communcating. The log is fairly useless in identifying the problem.

The worst part of this scenario is that rollback of the project creation never happens, TFS thinks the project exists but no site is ever created. The name can no longer be used in TFS, TFSProjectDelete doesn't work (that indicates the server can't be found either) and the whole thing is now out of whack. Removing the project info from TFS data looked to be near impossible without a script of some sort.

Hopefully some dependencies are built in allowing it to be more intelligent about comitting and rolling back TFS data if the sharepoint site and data isn't successful.

Communication between the two products needs to be resolved and simplified along with a way to actually troubleshoot this beyond uninstalling everything.

I realize this is a beta but it is October after all and strangely enough Beta2 was a no brainer one shot success.

Not much help here but maybe this info will provide some clues.

Answer 10

jhoney,

I too am experiencing a similar issue.

Prior to getting to this point I was getting an error at 0% where windows identity I was using didn't have the necessary permissions with the reportserver. After running the permissions script in the reportserver tool for my windows identity I got stuck here.

This error seems to occur when the project creation is 80% complete. Here is my variation on the same error:

9/30/2005 1:06:38 PM | Module: Engine | Thread: 11 | Running Task "SharePointPortal" from Group "Portal"
---begin Exception entry---
Time: 9/30/2005 1:06:38 PM
Module: Engine
Event Description: TF30162: Task "SharePointPortal" from Group "Portal" failed
Exception Type: Microsoft.TeamFoundation.Client.PcwException
Exception Message: Client found response content type of 'text/html', but expected 'text/xml'.
The request failed with the error message:
--
<html>
<head>
<title>Server Unavailable
</title>
</head>
<body>
<h1><font face=Verdana color=#ff3300>Server Application Unavailable
</font></h1>
<p>
<font face=Verdana>
The web application you are attempting to access on this web server is currently unavailable.  Please hit the "Refresh" button in your web browser to retry your request.
</p>
<p>
<b>Administrator Note:
</b> An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.
</p>
</body>
</html>

--.
Stack Trace:
at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)
at Microsoft.VisualStudio.TeamFoundation.ProjectCreationEngine.TaskExecutor.PerformTask(IProjectComponentCreator componentCreator, ProjectCreationContext context, XmlNode taskXml)
at Microsoft.VisualStudio.TeamFoundation.ProjectCreationEngine.RunTask(Object taskObj)
-- Inner Exception --
Exception Type: Microsoft.TeamFoundation.Client.PcwException
Exception Message: Client found response content type of 'text/html', but expected 'text/xml'.
The request failed with the error message:
--
<html>
<head>
<title>Server Unavailable
</title>
</head>
<body>
<h1><font face=Verdana color=#ff3300>Server Application Unavailable
</font></h1>
<p>
<font face=Verdana>
The web application you are attempting to access on this web server is currently unavailable.  Please hit the "Refresh" button in your web browser to retry your request.
</p>
<p>
<b>Administrator Note:
</b> An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.
</p>
</body>
</html>

--.
Stack Trace:
at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Validate(ProjectCreationContext context, XmlNode taskXml)
at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)
-- end Inner Exception --
-- Inner Exception --
Exception Type: System.InvalidOperationException
Exception Message: Client found response content type of 'text/html', but expected 'text/xml'.
The request failed with the error message:
--
<html>
<head>
<title>Server Unavailable
</title>
</head>
<body>
<h1><font face=Verdana color=#ff3300>Server Application Unavailable
</font></h1>
<p>
<font face=Verdana>
The web application you are attempting to access on this web server is currently unavailable.  Please hit the "Refresh" button in your web browser to retry your request.
</p>
<p>
<b>Administrator Note:
</b> An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.
</p>
</body>
</html>

--.
Stack Trace:
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.Portal.Sites.GetSiteTemplates(UInt32 LCID, Template[]& TemplateList)
at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.VerifySiteTemplate(ProjectCreationContext context, String template, Int32 lcid)
at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.ValidateSite(ProjectCreationContext context, XmlNode site)
at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Validate(ProjectCreationContext context, XmlNode taskXml)
-- end Inner Exception --
--- end Exception entry ---

9/30/2005 1:06:38 PM | Module: Engine | Thread: 11 | TF30202: Task "" from Group "" will not be run because a prior task failed.
9/30/2005 1:06:38 PM | Module: Engine | Thread: 11 | TF30202: Task "Site" from Group "Reporting" will not be run because a prior task failed.
9/30/2005 1:06:38 PM | Module: Engine | Thread: 11 | TF30202: Task "Populate Reports" from Group "Reporting" will not be run because a prior task failed.
9/30/2005 1:06:38 PM | Module: Engine | Thread: 11 | TF30202: Task "" from Group "" will not be run because a prior task failed.

Answer 11

Bruce,

Thanks for the reply. I've followed your suggestion concerning the WSS default server not being extended or incorrectly extended but to no avail.

Currently I have SQL Server 2005 September CTP Enterprise edition and WSS 2.0 with SP1 configured exactly as per the installation notes. Team Foundation Server installs fine as a single server installation on top of this and the system health check reports no problems. I can happily interact with the server using the command line tools (e.g manage security groups) and Team Foundation Client can readily connect to the server from VS 2005 RC1, from where I can manage groups, etc. When I try to create a new Team Foundation project from the client I get about 80% of the way through then get the protocol violation error again whilst it's trying to create the WSS site.

Over the last 24 hours I've uninstalled and reinstalled SQL, WSS and TFS several times and I consistently get the protocol violation error occuring whenever I try to create a project. Either must be a configuration problem or something I'm just not doing right with the installation. Checking the WSS configuration shows that the default virtual server is extended when TFS installation completes. Removing the WSS extensions from the default virtual server, then extending it again (using the same content database) makes no difference and the protocol violation error persists.

I've spent 3 full days so far trying to get beta 3 working and I'm about ready to give up on it as I've tried just about everything I can think of now. We're really keen to use it for some new projects we're starting and, as a C# MVP, I'd love to recommend it to other developers I deal with but I'm loathe to do so unless I can get it going myself. The annoying thing is that I got beta 2 going with no problems and it has been working (mostly) flawlessly for us for the last few months. Right now beta 3 really does look like a big step backwards

Answer 12

David,

I'm just now jumping into this discussion and I haven't had a chance to catch up yet on the full thread.

A couple of questions

1. Do you have a HTTPS certificate installed anywhere on your system?
2. Did you install WSS SP2 anywhere along the way
3. Did you look in the event logs for anything related
4. The user id you are using to create the project - is it the same as the installing user or the service account?  If neither, did you do the right permissions things?

Also, can you take a look in either the %temp% directory of the TFS installing user or in the programfiles directory (TFS) for a file named VSMSI*.txt (the * is a # which is random).  If you could attach the latest one of these then we'll have the installation log to review as well.

thanks

Answer 13

Marc,

1. I haven't installed an HTTPS certificate on the machine; I just wanted to get a base installation going first over HTTP before worrying about getting a secure installation going over HTTPS
2. No, WSS SP2 is definitely not installed
3. There's nothing in the event logs related to failure of creation of the WSS site specifically, but there are some Team Foundation errors occurring. The following error seems to have occured several times after the installation completed:

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): 30/09/2005 14:10:30

Machine: xxxxxxxxx

Application Domain: /LM/W3SVC/3/Root/Warehouse-4-127725629660583758

Assembly: Microsoft.TeamFoundation.Warehouse, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727

Process Details:

Process Name: w3wp

Process Id: 4060

Thread Id: 2860

Account name: xxxxx\TFSSERVICE

The installation itself also seems to have generated three warnings in the event log, two regarding the fact that the BigBuild_Web_Service could not be detected and the third is a failure message: Failed to connect to server. Error: 0x80070005

4) Unfortunately the latest installation log doesn't seem to be in the temp directory. I have logs from two previous installations but not the one I completed earlier today.

I'm going to give it one last go on a completely clean VPC image; if it still fails I'll grab and post the installation log from that install


The account I'm using to create the project is not the TFSSETUP account, but another domain level account which I have previously added to the TFS Admin security group using the TFSSecurity commmand line tool. I've noticed after each install that WSS does not have an administrative group defined. I have a domain-level group called TFS Project Creators which contains both the TFSSETUP account and the account I'm using to (attempt to) create the project. I've set the TFS Project Creators group as the administrative group for WSS. If my understanding is correct, this should mean that the domain-level account I'm using to create the project has project creation rights in TFS and site creation rights in Sharepoint.

Answer 14

Is anyone else running through a proxy? I think this is were I'm running into problems. I'm waiting on our network staff to make some changes before I can confirm my theory. Can those having the same error please confirm that they are not running through a proxy?

Answer 15

No, I'm definitely not using a proxy Jeremy.

Answer 16

David,

If the setup completed properly then the MSI logs will be under:
%programfiles%\Microsoft Visual Studio 2005 Team Foundation Server\Microsoft Visual Studio 2005 Team Foundation Server - ENU\Logs
If you could reply with zipped up logs, we can take a look at what is going on.

We're working on trying to identify all the issues that we're seeing regarding installation and configuration of Sharepoint, and working on putting together a blog to address those issues.

Answer 17

When PCW is attempting to create a new site it uses the Sharepoint central administration to do so.  To see if the central admin site is available to the client do the following:

From the AT open the IIS manager and get the port number for the central administration web site (right click on the 'SharePoint Central Administration' web site and select 'properties', the port number will be shown on the dialog).

From your client machine, log in as the same user you are using to attempt project creation and start IE.  Browse the site :/_vti_adm/admin.asmx">http://<AT_machine>:<port>/_vti_adm/admin.asmx  where <port> is the port number for the central admin web site.  You should see the Admin web service page.  If this page is not visible then there is a connectivity problem between the client and the web service.

The problem that David is seeing is most likely not a connectivity issue (though others in this thread may be).  It appears that it is in the process of uploading files when it fails with a protocol error so it is past the point of creating the site and is now attempting to populate it.  We are actively working on this problem.

If you cannot get around this issue and would like to test out the other parts of the system it is fairly easy to remove the Wss site creation step from the process template.  Use the process template manager (right click on the server name in the Team Explorer and select 'Team Foundation Server Settings' \ 'Process Template Manager...').  In the Process Template Manager dialog you download the process template to a local directory.  Once it is downloaded, find and edit the ProcessTemplate.xml file and remove the following:

            <plugin name="Microsoft.ProjectCreationWizard.Portal" wizardPage="true"/>

Remove the entire 'portal' group element:

        <group id="Portal"
            ...
        </group>

and remove any dependencies on the 'Portal' group (there should only be one):

     <dependency groupId="Portal"/>

It may also be a good idea to rename the template so you don't overwrite the existing one:

        <name>MSF for Agile Software Development - no wss</name>

Upload the new template with the Process Template Manager and select it when running the project creation wizard.

Answer 18

Modifying the process template sounds like a sensible idea and would probably work - if only the SharePoint configuration on my VPC image hadn't gotten corrupted. Once I've gotten SharePoint working on there again I'll try it out.

I had one last go at installing TFS. This time I chose a real machine (different to the one I've been using with VPC), inserted a new hard drive, installed a clean copy of Windows 2003 Server with SP1, SQL Server 2005 Standard Edition, WSS 2 with SP1 and Team Foundation Server. No problems during the install but I stll cannot create projects on this installation either. I don't get as far through the process as the SharePoint site creation this time, and the error is definitely different. Here I get TF30170 (or occasionally TF30171) during the project creation process. The project creation log indicates that this error is due to the 'connection was unexpectedly closed'. Looking at the error log, the only obvious error occuring (and it occurs frequently) is from the .NET Runtime Optimization Service which continually fails to compile Microsoft.ReportingServices.QueryDesigners.

The account I'm using to create the project is a member of the TFS Administrative group, a member of the SharePoint administrative group and has Content Manager rights in SQL Reporting Services. I know the problem is not the firewall on the server as I do not have the firewall enabled. Similar 'connection was unexpectedly closed' erros occur when using the Team Foundation client in VS 2005 RC 1 to perform tasks such as Group Memberships or Security Settings. Here the error is flagged in a dialog but the client invariably recovers and allows the appropriate command to go ahead.

I guess the code gods have fated me not to get this TFS beta working properly. I've wasted almost a full week on it now and I guess I'm going to have to give up

Answer 19

David, I really apologize for all the troubles you are running into with this installation. We sincerely want to make sure that we can get TFS up and running so that you can continue on with the Beta Bits. Can you follow up with me oofline with the PCW long and i can use it as a starting point to involve the right folks here to fix the problem as soon as possible.

Answer 20

I followed Dennis' recommendation to remove the portal creation step from the process template and it a project created successfully. I haven't actually begun working with the project yet, but the operation succeeded.

FWIW, I started a post on my blog detailing my experience setting up TFS Beta 3.

Answer 21

I have some info that I hope will help...

I'm getting the exact same error, but only if TFS is running in Workgroup mode.  I first installed TFS into a Virtual Machine that is part of a domain, and everything worked fine.

I then installed TFS into a non-domain server VM with a Workgroup client in a separate VM which is running the RC1 VS 2005.  (In other words, everything was identical except for the fact that they are not part of a domain).  Then it breaks with error TF30162.

I can get to the Sharepoint server just fine using the port number (http://VMW03STFS:17012/_vti_adm/admin.asmx)

So... I really suspect something having to do with the Workgroup authentication.  The user I am running it on is an admin on both machines. (See my other post which may be right before this one for the workaround).

Let me know if you need any more info.
Bruce F

Answer 22

I have a workaround which I believe will work for at least some of the problems.

My configuration:
Single Server deployment
Workgroup, not domain

I originally followed the install instructions which tell you that the TFSService account does NOT need to be an adminstrator.

I changed TFSService to be a part of the Administrators group on the machine that TFS is running on, after restoring my VM to a snapshot from before first project creation.

Two things happened after rebooting:
1.  The ASP.NET startup error in the event log: "Unable to get private bytes memory limit for the W3WP process" (0x80070005) went away.  (This error wasn't on the domain version of my test environment).
2. Project creation from my client machine was successful, including the Sharepoint part of the project.

Hope this helps,
Bruce F.

Answer 23

Bruce, can you send me your Project creation log so that we can investigate further on the two issues TF30171 andTF30170 you ran into when working with TFS in a work group mode when running TFSService as a non-admin user.

Answer 24

I've sent it via e-mail to you.

Answer 25

I've been watching this thread for two weeks while experiencing many of the same problems.

I can confirm two solutions for a single-server install.
1) Workgroup authentication doesn't work but when creating an AD, do it first.
2) Installation order matters.

My setup (all under a single VPC 2004 image with 1.5 GB of RAM):

1) Install Windows Server 2003 SP1 VL with latest patches.
2) Add AD DC role.
3) Add Application Server (IIS) with ONLY ASP.NET, don't install FP extensions.
4) Install SQL Server 2005 Sept CTP.  (follow TS install guide for setup, hint: all defaults under complete install and enable network access under Surface Area Configuration)
5) Install Windows Sharepoint Services with SP1.  (follow TS install guide for setup, hint: Server Farm)
6) Added users for services and reporting.  For testing, I gave both users full Administrator group rights.  If I have time, I'll verify the proper security settings.  At a minimum, you have to give "tfsservice" both db_securityadmin and db_owner for the STS_Config database as highlighted here.
7) Install Team Foundation Server (from TFD1-Beta3).
8) Install Office 2003 Pro SP2 and Project 2003 Pro SP2.
9) Install VS 2005 Team Suite DVD RC.
10) Install Team Foundation Client (aka Team Explorer) (from TFD1-Beta3).

That will allow you to successfully add a new project without error.

/David.

Answer 26

Hi there,

from what i can say is - never use spaces or any other special character in the Project Name. Thats what the Server doesn't seem to like.

Thats what fixed my Problem :)

Greets /Pal

Answer 27

Hi!

My TFS is running in Workgroup mode and I have experienced more or less all the problems described in these posts.

After granting permissions on the SQL Server Reporting services and Windows SharePoint Services, the following error persisted:

Event Description: TF30162: Task "SharePointPortal" from Group "Portal" failed

Exception Type: Microsoft.TeamFoundation.Client.PcwException

Exception Message: The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF

And then, simply after removing one "little" underscore from the name of my project, it finally worked
Therefore, I would also suggest, like Palpatime, avoiding spaces and special characters if you want to create new projects...

AnneR

Answer 28

JonathanTew wrote:

jhoney, I too am experiencing a similar issue. Prior to getting to this point I was getting an error at 0% where windows identity I was using didn't have the necessary permissions with the reportserver. After running the permissions script in the reportserver tool for my windows identity I got stuck here. This error seems to occur when the project creation is 80% complete. Here is my variation on the same error: 9/30/2005 1:06:38 PM | Module: Engine | Thread: 11 | Running Task "SharePointPortal" from Group "Portal" ---begin Exception entry--- Time: 9/30/2005 1:06:38 PM Module: Engine Event Description: TF30162: Task "SharePointPortal" from Group "Portal" failed Exception Type: Microsoft.TeamFoundation.Client.PcwException Exception Message: Client found response content type of 'text/html', but expected 'text/xml'. The request failed with the error message: -- <html> <head> <title>Server Unavailable </title> </head> <body> <h1><font face=Verdana color=#ff3300>Server Application Unavailable </font></h1> <p> <font face=Verdana> The web application you are attempting to access on this web server is currently unavailable.  Please hit the "Refresh" button in your web browser to retry your request. </p> <p> <b>Administrator Note: </b> An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur. </p> </body> </html>

Hi Jonathon,

I'm facing the same problem as you. Has your problem been resolved? Or anybody else has a solution for this?


Thanks

Answer 29

Bruce Lee wrote:

Hi Jonathon, I'm facing the same problem as you. Has your problem been resolved? Or anybody else has a solution for this? Thanks

Hi Bruce (and Jonathan).

My problem was not exactly the same, but perhaps you should check out a IIS setting as described in: http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=104436 

Just a thought...

Regards,
Carsten

Answer 30

Hi guys, after uninstall and reinstall my AT server twice, my TFS seems start to work properly now. At least I can create new projects successfully. Thanks for all your advices and ideas. :D

Answer 31

Hi Dennis - I tried browsing the site as you mention in your post and it works fine when I use localhost but when I use the actual name of my server it fails. I am getting the  "server actively refused the connection" error. I am just taking a guess that my problem is obviously not related to TFS and instead related to the way my IIS is configured? Any thoughts or help would be appreciated. Thanks!

Don

BTW, I was able to get my project creation to work properly by following your instructions on modifying the process template. Thanks for that little workaround ;-).

Answer 32

Thanks for this advice. Hoping not too late here (i.e. still actively being monitored).

I'm in an odd situation where I was able to create my initial team project but can no longer create new ones, and my existing one broke auto-magically (ie nothing was explicitly done).

Doing what you advised (disabling WSS) does seem to help at least so I can do source control and work items (and honestly those other items are far more important to me ... in fact having a default project type to NOT create the WSS integration I would consider favourable, though perhaps it is because I had lost some faith in WSS a while ago).

But I find it odd that the previous day all was working, then I shutdown VS.NET last night, loaded it up today and all of the sudden I cannot access my previous projects reports or documents (they have little 'x's in the team explorer), and I cannot create new team projects.  The only error in my event viewer are the .NET optimizer not being able to compile (which started this thread).

Answer 33

After tearing my hairs out for a week and following all the other suggestions on Forum, this suggestion of taking out the WSS from the template finally allowed me to create a project.

I am still interested in getting the WSS to work, but this was a big step forward.

Thanks!

 

Answer 34

Hello every one ... i am accessing a network resource a cgi command using httpweb request ....

when i use it with proxy it executes well on all the network ... but when i close the proxy then it only executes on few machines... can any one tell me about the problem ...

when i use it without proxy it is running fine in non multithreaded mode but when i use it in multi threaded it gives the exception "System.Net.WebException: The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF
   at System.Net.HttpWebRequest.GetResponse()
   at jpeg.JPEGSource.WorkerThread() "

can any one help me plz

 

Answer 35

I have installed Team Foundation Server 2005, uninstalled, and re-installed several times and keep running into the same problem.  After successfully creating a couple of projects, I installed Team System Web Access (not positive this is the cause of the problem) I am no longer able to create projects.  It gets about 80% of the way through and provides the following log:

2008-06-17 16:32:54Z | Module: WssSiteCreator | Thread: 11 | TF30267: Exception: System.Web.Services.Protocols.SoapException: Exception of type Microsoft.SharePoint.SoapServer.SoapServerException was thrown.
   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.Portal.Admin.CreateSite(String Url, String Title, String Description, Int32 Lcid, String WebTemplate, String OwnerLogin, String OwnerName, String OwnerEmail, String PortalUrl, String PortalName)
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.CreateSite(WssSiteData siteCreationData, ProjectCreationContext context)
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)
---begin Exception entry---
Time: 2008-06-17 16:32:54Z
Module: Engine
Event Description: TF30162: Task "SharePointPortal" from Group "Portal" failed
Exception Type: Microsoft.TeamFoundation.Client.PcwException
Exception Message: The Project Creation Wizard encountered an error while uploading documents to the Windows SharePoint Services server on TFSServer.
Exception Details: The Project Creation Wizard encountered a problem while uploading
documents to the Windows SharePoint Services server on TFSServer.
The reason for the failure cannot be determined at this time.
Because the operation failed, the wizard was not able to finish
creating the Windows SharePoint Services site.
Stack Trace:
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)
   at Microsoft.VisualStudio.TeamFoundation.ProjectCreationEngine.TaskExecutor.PerformTask(IProjectComponentCreator componentCreator, ProjectCreationContext context, XmlNode taskXml)
   at Microsoft.VisualStudio.TeamFoundation.ProjectCreationEngine.RunTask(Object taskObj)
--   Inner Exception   --
Exception Type: System.Web.Services.Protocols.SoapException
Exception Message: Exception of type Microsoft.SharePoint.SoapServer.SoapServerException was thrown.
SoapException Details: <detail>
        <errorstring xmlns="http://schemas.microsoft.com/sharepoint/soap/">The server instance specified was not found.  Please specify the server's address and port.</errorstring>
        <errorcode xmlns="http://schemas.microsoft.com/sharepoint/soap/">0x81070366</errorcode>
      </detail>
Stack Trace:
   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.Portal.Admin.CreateSite(String Url, String Title, String Description, Int32 Lcid, String WebTemplate, String OwnerLogin, String OwnerName, String OwnerEmail, String PortalUrl, String PortalName)
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.CreateSite(WssSiteData siteCreationData, ProjectCreationContext context)
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)
-- end Inner Exception --
--- end Exception entry ---

2008-06-17 16:32:54Z | Module: Engine | Thread: 11 | TF30202: Task "" from Group "" will not be run because a prior task failed.
2008-06-17 16:32:54Z | Module: Engine | Thread: 11 | TF30202: Task "Site" from Group "Reporting" will not be run because a prior task failed.
2008-06-17 16:32:54Z | Module: Engine | Thread: 11 | TF30202: Task "Populate Reports" from Group "Reporting" will not be run because a prior task failed.
2008-06-17 16:32:54Z | Module: Engine | Thread: 11 | TF30202: Task "" from Group "" will not be run because a prior task failed.
2008-06-17 16:32:54Z | Module: Engine | Thread: 9 | Attempting to delete MSF folder "C:\Documents and Settings\114263\Local Settings\Temp\TPW_tmp8DA.tmp"
2008-06-17 16:32:54Z | Module: Engine | Thread: 9 | The temporary folder C:\Documents and Settings\114263\Local Settings\Temp\TPW_tmp8DA.tmp used to store the process template was removed.
2008-06-17 16:32:54Z | Module: Wizard | Thread: 9 | The project OBTS was deleted successfully.


I have read many posts on this and have tried just about all the solutions, but have gotten nowhere.  I was hoping there would be a fix in place for this by now.  Any help would be greatly appreciated.

Thanks,
Mike

Answer 36

I should mention that this is a single server install.

Michael Dannenbring wrote:

I have installed Team Foundation Server 2005, uninstalled, and re-installed several times and keep running into the same problem.  After successfully creating a couple of projects, I installed Team System Web Access (not positive this is the cause of the problem) I am no longer able to create projects.  It gets about 80% of the way through and provides the following log: 2008-06-17 16:32:54Z | Module: WssSiteCreator | Thread: 11 | TF30267: Exception: System.Web.Services.Protocols.SoapException: Exception of type Microsoft.SharePoint.SoapServer.SoapServerException was thrown.    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.Portal.Admin.CreateSite(String Url, String Title, String Description, Int32 Lcid, String WebTemplate, String OwnerLogin, String OwnerName, String OwnerEmail, String PortalUrl, String PortalName)    at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.CreateSite(WssSiteData siteCreationData, ProjectCreationContext context)    at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml) ---begin Exception entry--- Time: 2008-06-17 16:32:54Z Module: Engine Event Description: TF30162: Task "SharePointPortal" from Group "Portal" failed Exception Type: Microsoft.TeamFoundation.Client.PcwException Exception Message: The Project Creation Wizard encountered an error while uploading documents to the Windows SharePoint Services server on TFSServer. Exception Details: The Project Creation Wizard encountered a problem while uploading documents to the Windows SharePoint Services server on TFSServer. The reason for the failure cannot be determined at this time. Because the operation failed, the wizard was not able to finish creating the Windows SharePoint Services site. Stack Trace:    at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)    at Microsoft.VisualStudio.TeamFoundation.ProjectCreationEngine.TaskExecutor.PerformTask(IProjectComponentCreator componentCreator, ProjectCreationContext context, XmlNode taskXml)    at Microsoft.VisualStudio.TeamFoundation.ProjectCreationEngine.RunTask(Object taskObj) --   Inner Exception   -- Exception Type: System.Web.Services.Protocols.SoapException Exception Message: Exception of type Microsoft.SharePoint.SoapServer.SoapServerException was thrown. SoapException Details: <detail>         <errorstring xmlns="http://schemas.microsoft.com/sharepoint/soap/">The server instance specified was not found.  Please specify the server's address and port.</errorstring>         <errorcode xmlns="http://schemas.microsoft.com/sharepoint/soap/">0x81070366</errorcode>       </detail> Stack Trace:    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.Portal.Admin.CreateSite(String Url, String Title, String Description, Int32 Lcid, String WebTemplate, String OwnerLogin, String OwnerName, String OwnerEmail, String PortalUrl, String PortalName)    at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.CreateSite(WssSiteData siteCreationData, ProjectCreationContext context)    at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml) -- end Inner Exception -- --- end Exception entry --- 2008-06-17 16:32:54Z | Module: Engine | Thread: 11 | TF30202: Task "" from Group "" will not be run because a prior task failed. 2008-06-17 16:32:54Z | Module: Engine | Thread: 11 | TF30202: Task "Site" from Group "Reporting" will not be run because a prior task failed. 2008-06-17 16:32:54Z | Module: Engine | Thread: 11 | TF30202: Task "Populate Reports" from Group "Reporting" will not be run because a prior task failed. 2008-06-17 16:32:54Z | Module: Engine | Thread: 11 | TF30202: Task "" from Group "" will not be run because a prior task failed. 2008-06-17 16:32:54Z | Module: Engine | Thread: 9 | Attempting to delete MSF folder "C:\Documents and Settings\114263\Local Settings\Temp\TPW_tmp8DA.tmp" 2008-06-17 16:32:54Z | Module: Engine | Thread: 9 | The temporary folder C:\Documents and Settings\114263\Local Settings\Temp\TPW_tmp8DA.tmp used to store the process template was removed. 2008-06-17 16:32:54Z | Module: Wizard | Thread: 9 | The project OBTS was deleted successfully. I have read many posts on this and have tried just about all the solutions, but have gotten nowhere.  I was hoping there would be a fix in place for this by now.  Any help would be greatly appreciated. Thanks, Mike

Answer 37

Hi Mike

 

Can you post the entire log?  I'd like to see what parameters are being passed to the 'CreateSite' web method and some of the other urls that are being used...

 

Thanks!

 

-Dennis

 

Answer 38

I actually figured out what was wrong, it was a user error.  I had changed the site configuration for the default site so it was unable to find it.  Sorry for wasting your time.

Thanks,
Mike

Answer 39

No worries, I'm glad you figured it out.

 

-Dennis