Tiago Pascoal

The only person who can truly persuade you is yourself. You must turn the issues over in your mind at leisure, consider the many arguments, let them simmer, and after a long time turn your preferences into convictions.
Milton Friedman
posts - 99, comments - 42, trackbacks - 33
<< Requirements Management with Team System | Home | Molding the shape of TFS next version >>

Project Server 2007 VSTS Connector installation gotchas on TFS 2005

On the 10th of March Lenny Fenster released a new version of the Project Server 2007 VSTS Connector.

This releases fixes some bugs and adds support for TFS 2008, unfortunately Lenny forgot (most probably lacked the time to do it) to update the requirements list. We had some issues while upgrading the older version of the connector on a installation still using TFS 2005.

The components install without problems except the connector for Team Foundation server (the third option on the installer). The installer aborts stating it had unexpected error. The log file hasn't any useful information.

After some heavy digging (and nagging Lenny over IM :-)) I figured out that the problem lied  on the fact that the connector installer references to TFS 2008 API instead of TFS 2005

To solve the installation problem you have two choices:

  • Install the TFS 2008 API on the server the connector is going to run. The only way to install the API is by installing Team Explorer 2008
  • After the first time the installation fails, create a standard .Net policy redirection DLL file configuration file on the installation folder temporary directory (c:\windows\PS2007-TFS Connector) so when the code attempts to to access TFS using the API it uses 2005 API instead of the 2008 version. I haven't gone this path, since this would also involve applying the same redirection on the connector. So in theory this should work but I haven't tested it. :-)

The web site to manage the connector is also configured to use framework 3.5 so you must install framework 3.5 on that machine (if the web site is installed in the same machine as the TFS connector then no need to worry about this since Team Explorer 2008 also installs framework 3.5).

 

Lost a bunch of hair on this one, I hope this saves you same time if you are in a similar situation.

Print | posted on Friday, March 28, 2008 12:03 PM

Feedback

# VSTS Links - 04/02/2008

Maor David on How To: Delete Build agent in TFS 2008 and Team Build 2008 Downloads One Level Only. Tiago...
4/2/2008 6:30 AM | Team System News
Gravatar

# PS-TFS Connector 2.0 Synchronization Problem

Hi,
We have installed the PSTFS Connector version 2.0 in a two machine environment where the configuration is:

Machine 1: Project Server 2007 and Connector Project Server component. (logged in with TFSService Domain Account with Local Admin rights)
Machine 2: TFS Server 2008, Connector TFS component & Connector Web Site + Web Service (Connector Website and Webservice are both running under the TFS Root at port 8080.) (logged in with TFSService Domain Account with Local Admin rights)


We have followed all the steps mentioned during installation and followed the following procedure:
1) Created a test project with two custom columns in MS Project for "Enterprise Workitem Type" and "AutoSync with external system". The value for first column was set to "Task" and value for AutoSync column set to "True" in the Task Usage View. We have also saved and published this project.
2) Created a test project on TFS Server from the template named "MSF Agile For PS Connector - v4.2".
3) Accessed the Connector Website which showed the button to create new project association.
4) Created the project association between the two newly created projects, (first 2 options checked). It looked as though the project was locked (after a long wait), when we unlocked the project using the Administraion Web Service, the project association had been created without creating any task/assignment association. No tasks appear in the drop down if you select or assignments otherwise.
5) We checked the Event Log for errors during this time and found the following related exceptions:

Exception # 1

Timestamp: 5/26/2008 7:27:58 AM
Message: Unable to locate configuration information for the process template of MSF Agile For PS Connector - v4.2
Category: General
Priority: 12
EventId: 0
Severity: Critical
Title:
Machine: TFS08
Application Domain: /LM/W3SVC/1648131788/Root/Connector Web Service-1-128562603052585440
Process Id: 692
Process Name: c:\windows\system32\inetsrv\w3wp.exe
Win32 Thread Id: 132

Exception # 2

Timestamp: 5/26/2008 7:27:58 AM
Message: Unable to obtain the WorkItemTypeMapping from configuration for WorkItemType MSF Agile For PS Connector - v4.2 and ProcessTemplate Task
Category: General
Priority: 12
EventId: 0
Severity: Critical
Title:
Machine: TFS08
Application Domain: /LM/W3SVC/1648131788/Root/Connector Web Service-1-128562603052585440
Process Id: 692
Process Name: c:\windows\system32\inetsrv\w3wp.exe
Win32 Thread Id: 132

Exception # 3

Timestamp: 5/26/2008 7:27:58 AM
Message: Unable to create a list of WorkItems for the project with the id of fe545123-5075-4a4b-a5ad-75da98e511d4
Category: General
Priority: 12
EventId: 0
Severity: Critical
Title:
Machine: TFS08
Application Domain: /LM/W3SVC/1648131788/Root/Connector Web Service-1-128562603052585440
Process Id: 692
Process Name: c:\windows\system32\inetsrv\w3wp.exe
Win32 Thread Id: 132

Exception # 4

Timestamp: 5/26/2008 7:27:58 AM
Message: Unable to obtain a list of WorkItems for the project with the id of vstfs:///Classification/TeamProject/f07407dc-dcb2-41f3-b55f-67efd69901b4
Category: General
Priority: 12
EventId: 0
Severity: Critical
Title:
Machine: TFS08
Application Domain: /LM/W3SVC/1648131788/Root/Connector Web Service-1-128562603052585440
Process Id: 692
Process Name: c:\windows\system32\inetsrv\w3wp.exe
Win32 Thread Id: 132


and finally the ASP.Net Worker Process exception

Exception # 5
An unhandled exception occurred and the process was terminated.

Application ID: DefaultDomain

Process ID: 692

Exception: System.Runtime.Serialization.SerializationException

Message: Unable to find assembly 'Microsoft.Vsts.Ranger.Connector.PS2007Providers, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null'.

StackTrace: at System.Runtime.Serialization.Formatters.Binary.BinaryAssemblyInfo.GetAssembly()
at System.Runtime.Serialization.Formatters.Binary.ObjectReader.GetType(BinaryAssemblyInfo assemblyInfo, String name)
at System.Runtime.Serialization.Formatters.Binary.ObjectMap..ctor(String objectName, String[] memberNames, BinaryTypeEnum[] binaryTypeEnumA, Object[] typeInformationA, Int32[] memberAssemIds, ObjectReader objectReader, Int32 objectId, BinaryAssemblyInfo assemblyInfo, SizedArray assemIdToAssemblyTable)
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWithMapTyped(BinaryObjectWithMapTyped record)
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWithMapTyped(BinaryHeaderEnum binaryHeaderEnum)
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at System.Runtime.Remoting.Channels.CrossAppDomainSerializer.DeserializeObject(MemoryStream stm)
at System.AppDomain.Deserialize(Byte[] blob)
at System.AppDomain.UnmarshalObject(Byte[] blob)

We are waiting for your quick response since we have searched the forums for this and also tried different things mentioned in the forums but its still not working.

Thanks a lot for your help!!!

Regards
Imran Khawar Bodla
5/26/2008 6:24 AM | Imran Khawar Bodla

# re: Project Server 2007 VSTS Connector installation gotchas on TFS 2005

It seems you are experiencing two different problems.

The first one seems to be a trouble with the connector mappings for your project template.

Which project template are you using for the test project? and is it mapped on the connector web.config file?

The other problem seems to be lack of permissions under which application pool is the code running?
5/26/2008 7:36 AM | Tiago Pascoal
Gravatar

# re: Project Server 2007 VSTS Connector installation gotchas on TFS 2005

Hi, I am implementing Team System 2008 in Company, how sincronized project server with team System 2008? what configuration I do? the instalation was complete and I was working with workitems, and I don`t how sincronized project server with team System 2008

Thanks
1/21/2010 5:29 PM | Eleonora Peña Rodriguez
Gravatar

# re: Project Server 2007 VSTS Connector installation gotchas on TFS 2005

Hi,

Please,

Browse Website connector: service unavailable

Microsoft Project Server 2007- VSTS Connector

The connector installed ok,

The team system installed ok

What I do?



Thanks you

1/21/2010 7:47 PM | Eleonora Peña

Post Comment

Title  
Name  
Email
Url
Comment   

Powered by:

Copyright © Tiago Pascoal