| I've seen this posted, however, I don't see an answer to the problem. I would like to resolve this issue this week. I have project teams waiting on this working. If I can't get it to work, I will be forced to use VSS. Thanks Eric J. Johnson ejjjohnson@ciber.com OR johnsonericj@att.net Error TF30004: The New Team Project Wizard encountered an unexpected error while initializing the Microsoft.ProjectCreationWizard.WorkItemTracking plug-in. |
| Explanation TF30171: The Microsoft.ProjectCreationWizard.WorkItemTracking plug-in used to create the new team project could not be initialized and returned the following error: TF26173: Team Foundation could not connect to the application tier. Check that you have a network connection and that the Team Foundation Server is available. If the problem persists, contact your Team Foundation Server administrator.. |
| User Action Contact your Team Foundation Server administrator. |
Log File
12/6/2005 1:39:38 PM | Module: ELeadServiceMediator | Team Foundation Server proxy retrieved | Completion time: 0.5897758 seconds
12/6/2005 1:39:38 PM | Module: ELeadServiceMediator | The template information for Team Foundation Server "AAPCC-DEV-SQL" was retrieved from the Team Foundation Server. | Completion time: 0.0899658 seconds
12/6/2005 1:39:38 PM | Module: Wizard | Retrieved IAuthorizationService proxy | Completion time: 0.3198784 seconds
12/6/2005 1:39:39 PM | Module: Wizard | TF30227: Project creation permissions retrieved | Completion time: 0.0799696 seconds
12/6/2005 1:39:49 PM | Module: Engine | Thread: 6 | New project will be created with the "MSF for CMMI Process Improvement" methodology
12/6/2005 1:39:49 PM | Module: Engine | Retrieved IAuthorizationService proxy | Completion time: 0 seconds
12/6/2005 1:39:49 PM | Module: Engine | TF30227: Project creation permissions retrieved | Completion time: 0.099962 seconds
12/6/2005 1:44:43 PM | Module: Engine | Wrote compressed process template file | Completion time: 0.5797796 seconds
12/6/2005 1:45:16 PM | Module: Engine | Extracted process template file | Completion time: 33.037441 seconds
12/6/2005 1:45:16 PM | Module: Engine | Thread: 6 | Starting Project Creation for project "AAPCC Core" in domain "AAPCC-DEV-SQL"
12/6/2005 1:45:17 PM | Module: Engine | The user identity information was retrieved from the Group Security Service | Completion time: 1.2795136 seconds
12/6/2005 1:45:17 PM | Module: Initializer | Thread: 6 | The New Team Project Wizard is starting to initialize the plug-ins.
12/6/2005 1:45:18 PM | Module: CssStructureUploader | Thread: 6 | Entering Initialize in CssStructureUploader
12/6/2005 1:45:18 PM | Module: CssStructureUploader | Thread: 6 | Initialize for CssStructureUploader complete
12/6/2005 1:45:18 PM | Module: Initializer | Thread: 6 | The New Team Project Wizard successfully Initialized the plug-in Microsoft.ProjectCreationWizard.Classification.
12/6/2005 1:45:18 PM | Module: Rosetta | Thread: 6 | Entering Initialize in RosettaReportUploader
12/6/2005 1:45:33 PM | Module: Rosetta | Thread: 6 | Exiting Initialize for RosettaReportUploader
12/6/2005 1:45:33 PM | Module: Initializer | Thread: 6 | The New Team Project Wizard successfully Initialized the plug-in Microsoft.ProjectCreationWizard.Reporting.
12/6/2005 1:45:33 PM | Module: WSS | Thread: 6 | Entering Initialize in WssSiteCreator
12/6/2005 1:45:34 PM | Module: WSS | Thread: 6 | Exiting Initialize for WssSiteCreator
12/6/2005 1:45:34 PM | Module: Initializer | Thread: 6 | The New Team Project Wizard successfully Initialized the plug-in Microsoft.ProjectCreationWizard.Portal.
12/6/2005 1:45:34 PM | Module: GSSStructureUploader | Thread: 6 | Entering Initialize in GssStructureCreator
12/6/2005 1:45:35 PM | Module: GSSStructureUploader | Thread: 6 | Exiting Initialize for GssStructureCreator
12/6/2005 1:45:35 PM | Module: Initializer | Thread: 6 | The New Team Project Wizard successfully Initialized the plug-in Microsoft.ProjectCreationWizard.Groups.
---begin Exception entry---
Time: 12/6/2005 1:45:36 PM
Module: Initializer
Event Description: TF30207: Initialization for plugin "Microsoft.ProjectCreationWizard.WorkItemTracking" failed
Exception Type: Microsoft.TeamFoundation.WorkItemTracking.Client.ConnectionException
Exception Message: TF26173: Team Foundation could not connect to the application tier. Check that you have a network connection and that the Team Foundation Server is available. If the problem persists, contact your Team Foundation Server administrator.
Stack Trace:
at Microsoft.TeamFoundation.WorkItemTracking.Client.DataStore.HandleComException(Int32 hr)
at Microsoft.TeamFoundation.WorkItemTracking.Client.DataStore.DatastoreClass.ConnectEx(String connectionString, Int32 hCredentials, String defaultCachePath, String instanceId)
at Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemStore.InitializeInternal()
at Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemStore.Microsoft.TeamFoundation.Client.ITeamFoundationServerObject.Initialize(TeamFoundationServer teamFoundationServer)
at Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemStore..ctor(TeamFoundationServer teamFoundationServer)
at Microsoft.VisualStudio.TeamFoundation.WorkItemTracking.CurrituckPcwPlugin.PcwPluginComponentCreator.Initialize(ProjectCreationContext ctxt)
at Microsoft.VisualStudio.TeamFoundation.EngineStarter.InitializePlugins(MsfTemplate template, PcwPluginCollection pluginCollection)
-- Inner Exception --
Exception Type: System.Net.WebException
Exception Message: The request failed with HTTP status 503: Service Unavailable.
WebException: Response Status Code: ServiceUnavailable
WebException: Response Status Message: Service Unavailable
WebException: Status : ProtocolError
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.WorkItemTracking.Proxy.ClientServiceProxy.GetMetadata(MetadataTableHaveEntry[] metadataHave, String& dbStamp, Boolean useMaster, Int32& locale, Int32& comparisonStyle, String& callerIdentity)
at Microsoft.TeamFoundation.WorkItemTracking.Proxy.ClientService.GetMetadata(String requestId, Boolean useMaster, MetadataTableHaveEntry[] metadataHave, String& dbStamp, IMetadataRowSets& metadata, Int32& locale, Int32& comparisonStyle, String& callerIdentity)
at CProdStudioBackendChannel.GetMetadata(CProdStudioBackendChannel* , tagVARIANT* pvarbstrCallerIdentity, tagVARIANT* pvarbstrDomainName, tagVARIANT* pvarbstrForestName, tagVARIANT* pvarbstrMachineName, tagVARIANT* pvarLocale, tagVARIANT* pvarComparisonStyle, Int32 fNoFire, Int32 fByPassFireOnThis)
-- end Inner Exception --
--- end Exception entry ---
12/6/2005 1:45:37 PM | Module: Engine | Thread: 6 | Attempting to delete MSF folder "C:\Documents and Settings\Johnson_Eric.DEVELOPMENT\Local Settings\Temp\TPW_tmp46.tmp"
12/6/2005 1:45:38 PM | Module: Engine | Thread: 6 | The temporary folder C:\Documents and Settings\Johnson_Eric.DEVELOPMENT\Local Settings\Temp\TPW_tmp46.tmp used to store the process template was removed.
APPLICATION EVENT LOG
APPLICATION EVENT LOG EnTRY (ERROR)
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): 12/6/2005 7:01:23 PM
Machine: AAPCC-DEV-SQL
Application Domain: TFSServerScheduler.exe
Assembly: Microsoft.TeamFoundation.Common, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: TFSServerScheduler
Process Id: 552
Thread Id: 1328
APPLICATION EVENT LOG EnTRY (WARNING)
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): 12/6/2005 7:01:23 PM
Machine: AAPCC-DEV-SQL
Application Domain: TFSServerScheduler.exe
Assembly: Microsoft.TeamFoundation.Common, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: TFSServerScheduler
Process Id: 552
Thread Id: 1328
Account name: DEVELOPMENT\TFSSERVICE
Detailed Message: TF50801: The initialization did not complete because there was no task list registered with the TFS Registration service, or an error prevented the TFS Registration service from providing the task list. Attempting to load the system task list from the latest log file.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
TF30207: Initialization for plugin "Microsoft.ProjectCreationWizard.WorkItemTracking" failed
Giles Knap
The message suggests that the URL for the Work Item Tracking service may be wrong. We can check that by looking into the client side cache at the service interface URL. If it is wrong, then hopefully the nature of the error will tell us something about how it got into that state. If not, we need to see if there is a problem with the path to the service or the service itself.
Here are the steps to find the Work Item Tracking service URL:
1) Shut down running instances of Visual Studio
2) Browse to \Documents and Settings\<username>\Local Settings\Application Data\Microsoft\Team Foundation\1.0\Cache
3) Find all instances of RegProxyFileCache.xml file under the Cache subdirectory. Open each in turn to identify the one which has your server name listed in all of the URLs.
4) Search for "WorkitemService" in the RegProxyFileCache.xml file.
If the URL looks right, you can test whether the service is accessible from the client by navigating to the service definition page. Copy the URL that you found into IE. You should see a page showing a list of operations on the ClientService interface (BulkUpdate, etc.).
If you find an inconsistency in the URL in the cache, it is fine to delete the whole cache subdirectory. In this case, please just rename the cache subdirectory to something like cache.old so that we will have the cache contents to help diagnose the source of the problem.
NewDBA
At a high level, the problem came down to an issue with the AD domain configuration. A new domain was created to hold the TFS server and all clients. When those machines acquired addresses from corporate DHCP servers, they ended up with a list of DNS servers for the corporate infrastructure. The new AD domain was not part of the corporate forest, so the machines that were added to that domain would ultimately fail to find their domain controller after a reboot. One symptom of this configuration issue was that the standard Windows dialogs to add domain accounts to groups only listed the local machine and would not allow domain accounts to be added. Another symptom was that all previously added domain accounts showed up only as unresolved SIDs (S-1-XXX...) instead of with the friendly account name. The loss of domain connectivity was masked to some degree by the fact that the default workgroup policy for a W2K3 machine allows domain credentials to be supplied up to 10 times without actually having the machine on the domain.
Fixing the domain connectivity issue and rebooting the servers allowed authentication between the application tier and data tier machines to work properly. Project creation was successful once that core issue was fixed.
Rasped
EJ
vivi_0606
1. Navigate to you AD machines Internet Protocol Properties
2. Click on the advanced button
3. Click on the DNS Tab, add the domain/DNS IP address to the DNS list
4. Click on the WINS Tab, add the domain/DNS IP address to the WINS list
I also recommend updating the client and server host and lmhost files in Windows or WINNT\system32\drivers\etc to have all the domain server IP addresses with their respective names listed. If you have any questions, please send me an email.
Object01
Thanks
EJ
Kerry_Dixon
The URL looks right. It is odd that you cannot navigate to http://aapcc-dev-sql:8080/WorkItemTracking/v1.0/ClientService.asmx when both the project creation log and the registration cache file confirm that the registration service is available (http://aapcc-dev-sql:8080/services/v1.0/registration.asmx).
A few of the URL entries might not have http://. I counted two in a quick scan of a healthy system.
The event log entries say that the scheduler service on the server is unable to make a web service call. It may well be the same problem, but it is another symptom rather than the root cause.
Please send me a copy of the install logs (display e-mail without nospam). You can find dd_vsinstall80.txt and VSMsiLogxxxx.txt on the AT in the "%ProgramFiles%\Microsoft Visual Studio 2005 Team Foundation Server\Microsoft Visual Studio 2005 Team Foundation Server (service) - ENU\Logs" folder.