Unanswered Having Trouble Creating New Team Project

  • Monday, February 13, 2012 6:46 PM
     
     

    Have a Team Foundation Server and around 30 Clients connected. Version is 2008.

    Permissions are assigned correctly, all current projects are accessed without issue.

    When anyone including Domain Admins/TeamFoundation Admins tries to creat a new team project we get the following error.

    TF30177: Team Project Creation Failed

     New Team Project Wizard encountered the follwing error and could not continue.

    • Error: The Project Creation Wizard encountered an error while uploading documents to the Windows SharePoint Services server on tfs2008.
    • Explanation: The Project Creation Wizard encountered a problem while uploading documents to the Windows SharePoint Services server on tfs2008. 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.
    • User Action: Contact the administrator for the Windows SharePoint Services server on tfs2008 to confirm that the server is running and you have sufficient privileges to create a project. Also, you might find additional helpful information in the project creation log. The log shows each action taken by the wizard at the time of the failure and may include additional details about the error.

    I am a Domain Admin and have all priviledges assigned. (As far as I know) I have checked this many times.

    Here is the team project creation log, I have only included the portion showing the exception, if the whole log is needed I can repost, please be aware that I am a security policy guy acting as the system administrator cause there isn't one :( Please HELP!

    2012-02-13 13:30:26Z | Module: WssSiteCreator | Thread: 10 | 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: 2012-02-13 13:30:26Z
    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 tfs2008.
    Exception Details: The Project Creation Wizard encountered a problem while uploading
    documents to the Windows SharePoint Services server on tfs2008.
    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="The">http://schemas.microsoft.com/sharepoint/soap/">The server instance specified was not found.  Please specify the server's address and port.</errorstring><errorcode xmlns="0x81070366</errorcode></detail">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 ---

    2012-02-13 13:30:26Z | Module: Engine | Thread: 10 | TF30202: Task "" from Group "" will not be run because a prior task failed.
    2012-02-13 13:30:26Z | Module: Engine | Thread: 10 | TF30202: Task "Site" from Group "Reporting" will not be run because a prior task failed.
    2012-02-13 13:30:26Z | Module: Engine | Thread: 10 | TF30202: Task "Populate Reports" from Group "Reporting" will not be run because a prior task failed.
    2012-02-13 13:30:26Z | Module: Engine | Thread: 10 | TF30202: Task "" from Group "" will not be run because a prior task failed.

    Though my knowledge is limited, I think I have narrowed it down to a SharePoint Permissions issue but I have admin rights! So I am at a roadblock. Also previous individuals who have created earlier project can no longer create new ones as they get this same error.

    Additional Notes: This is a Government Network using McAfee's HBSS modules, but so far it has been ruled out as the cause.



    • Edited by Justin P Campbell Monday, February 13, 2012 6:49 PM Included Visual Studio Version Info.
    •  

All Replies

  • Monday, February 13, 2012 6:50 PM
     
     

    Here is the problem:

    Error: The Project Creation Wizard encountered an error while uploading documents to the Windows SharePoint Services server on tfs2008.

    So ... it's a Sharepoint permissions issue. Just because you are a Domain Admin doesn't mean that you have write privileges to every Sharepoint site. You should make sure that your user account has Contributor permissions to any new Sharepoint site that gets created.


    DevBiker (aka J Sawyer)
    My Blog
    My Bike - Concours 14


    If I answered your question, please mark as answer.
    If my post was helpful, please mark as helpful.

  • Monday, February 13, 2012 6:57 PM
     
     

    Thanks for your swift reply. I figured it may be a Share Point Permissions Issue. I can access the Share Point Administration Page and I do have Full Control. Is there something else I should be doing that is being missed?

    "You should make sure that your user account has Contributor permissions to any new Sharepoint site that gets created."

    1. Would that be my domain user account or my sharepoint account?
    2. Is that a group my domain account can be added to?
    3. Would I do that on the DC or the Sharepoint Server itself?

    Would someone mind throwing me a step by step showing how I add Contributor permissions to any new site?

    I am not an expert with sharepoint so it is indeed plausible that I am missing something easy.




    UPDATE: I have full admin rights on the Sharepoint Server. I saw this at the Top Site Administration. This doesn't make any sense.
  • Tuesday, February 14, 2012 5:39 AM
     
     

    Hi Justin,

    When you indicated you have full control do you see this in the Policy for web application? I had been having a problem like the one you mentioned and I found that if I went into the Central Admin Console you can go into Application Management and then Policy for Web Application. Give yourself Full Control for all zones. You won't need to apply the security to any of the new sites created going forward.

    Jim

  • Tuesday, February 14, 2012 5:56 PM
     
     

    Hi Justin

    I had the similar issue.

    In my case the following was there.

    a. Sharepoint WSS 3.0 (some x.x version). TFS was installed (2008/2010) and everything was fine. Over the time, we saw this similar issue. As far as I can recall, the resolution we did is as follows:

    Steps: If you have WSS 3.0.

    NOTE: Can you go to Sharepoint Central admin page and under "Application Mgmt" and see if you are successfully able to "Create a site collection" ?? Try running "Sharepoint Product and Technologies configuration wizard" and see if that fixes any of the above said issues at my / your end. If they are still not resolved, proceed / follow the following points.

    1. Make sure you have your DBA team - take backup of your sharepoint WSS_Config/WSS_Content databases. Once done, go to 2.

    2. You will see that your sharepoint central administration - will most probably be running on port 17012 but if not, note that sharepoint central site port.

    3. Go to IIS (we had both 6/7 when we're TFS 2008/TFS 2010 running on Windows 2003/2008 R2) and stop "Sharepoint Central Administration v3..".

    4. Now, WSS/Sharepoint admin central admin site will not be active.

    5. Uninstall and re-install - Run WSS 3.0 installation again (use port 17012 for sharepoint central Admin site). Once done, go to WSS Sharepoint Central Admin page and under "Application Management", under "Sharepoint Web Application Management", select "Create or extend web application" option.

       a. You'll see a radio button for "Create a new IIS web site", There under the description, Put "Sharepoint - 121". Note, instead of using 121, use the same

           port you noted down above. 121 is just for an example number I used to tell that this site will be running under this port.

       b. In the port box, enter that port (that you noted down).

       c. Path box will be something like: "C:\inetpub\wwwroot\wss\VirtualDirectories\<xxxx>", where xxxx will match your port # or you can set it later using IIS.

       d. For next few radio buttons, select "NTLM", No, No.

       e. For URL: Select "http://yourTFSserver:yourPort#here/   for ex: http://tfsgigaserver.fifa.com:121/

       f. In Zone, let it be as "Default"

       g. Select "Create a new application pool" radio button and in the application name, put "Sharepoint - xxxx" where xxxx is the port number. If you get an error that it already exists, then go to IIS and rename/change the pool name over there to use a different number for app pool name.

       h. Select "Configurable" radio button and provide credentials. I used "MyCompanyDomain\TFSAdmin" user and it's password.

       i. Select the radio button for "Restart IIS manually".

       j. In Database Server name (as we have Dual Tier architechture i.e. Databases sit on a different server/db cluster/instance), so i have the following value:

          CSQLSERVERHCL2I12\SQLI50

          Note: if you database for WSS sit on your TFS App server, then you have to give your TFS server name here with any instance name after \ character.

       k. In the database name, Select WSS_Content (or the same WSS_Content.... name that your existing sharepoint content database has). This will make sure

           that you'll get your data back for all TFS project's sharepoint sites as WSS Central Admin holds all those site as site lists (under application mgmt tab).

       l. Select "Windows Authentication" or SQL whatever you want, we have Windows radio button selected. Provide an account credentials which has valid r/w

         access to SQL side databases. We use SQL 2005/2008R2 (when we had/have TFS2008/TFS2010).

       m. Search server: select / provide the name of server (usually your TFS app server) i.e. the server which is running "sharepoint search" service.

            We have "TFSGigaServer" listed there.

       n. Press OK button and now you'll have a new web site / new pool in IIS.

       o. Go to IIS, make sure you have correct port# showing under "Edit Bindings/properties" or in Advance settings.

       p. Make sure you are able to browse the Central Admin web site page by running http://tfsserver:17012

       q. Make sure On Sharepoint centrel admin site, under "Application Mgmt" tab, under "Sharepoint web app mgmt heading", click "Content Databases" and

          see if you are able to see "WSS_Content" database(s) listed there.

       r. Review your settings under "Web Application General Settings" for how much extra you can upload. If you want to upload more than 28MB limit, see MS blog to update "Web.config" file of the sharepoint site. Note: Their site says you should update web.config for central admin site / virtural directories folder, but instead of that you have to change the web.config for "sharepoint - xxx" app pool's web.config .. with the changes they have suggested in their blogs.

       s. See if you are able to see TFS project sites under "Site collection list" and able to successfully create "a test site" using "Create site collection".

          Note, you may have to reapply/deploy 3rd party templates (like Scrum from conchango)) using Team Explorer again.

       t. Review values under "Operations" tab and see if values for "email settings", "Default Database server", "Alternate Access mappings" are showing some /

          valid values. If not, set them. Also, see "Servers in farm"(this will tell you what WSS_Config or..." database you have currently set) and "Services on

          server" options.

       u. Retry your project creation with a specified project template and see if the error goes away. Make sure you have valid values set in TFS Admin console (if

          you are using TFS2010 with Windows 2008 R2 / IIS 7 and WSS 3.0) for Sharepoint and relative paths.

    Other quick thing: If you have MSDN subscription, then every person if your org, who has this, have FREE limited # of SRX tickets (that we open with Microsoft team). Open one, let them review your issue and they will help you out for free. Try this same exercise on any dev environment TFS server and if they resolve it, do the same procedure on your live TFS server as well.

    Hope this helps. 

      


    Arun Sangal Software Configuration Management Denver USA

  • Tuesday, February 14, 2012 7:56 PM
     
     
    When I access the Central Admin Console, I don't see an option for Application Management. Strange.
  • Wednesday, February 15, 2012 6:02 AM
    Moderator
     
     

    Hi Justin,

    Thank you for your post.

    According to your description of the issue, here are some situations i want to clarify from you:
    1. Can you open the SharePoint Central Administration, not the TFS Administration Console? If you can open it, would you please make a try of Jim and Arun's suggestion?

    2. Would you please use ConfigureConnections Command to displays the current connection settings for Team Foundation Server? Is the SharePoint server address right?
    TFSAdminUtil ConfigureConnections [/View]

    You can change the connection interface for TFS like,
    TFSAdminUtil ConfigureConnections [/SharepointUri:<uri>] [/SharepointSitesUri:<uri>] [/SharepointUnc:<unc>]

    3. Is there any log in Event Viewer that relate to this issue?

    If anything is unclear, please free feel to let me know.

    Best Regards,


    Lily Wu [MSFT]
    MSDN Community Support | Feedback to us