Setup/Installation Related FAQ's

Q. If I choose to install the Connector on the TFS Server, should I select the “Default Website” ?
  • A. No. If you’re installing the Connector components on the TFS Server, the Default Web Site is typically under Sharepoint’s control. All requests to such sites are first intercepted and are managed by SharePoint. Rather than installing on the Default Web Site and configuring it to run outside of SharePoint’s control, it will be far easier to either install the Connector on the “Team Foundation Server” (this is port 8080 by default) site or you can create a new web site just for the Connector (both “Connector Web Site” and Connector Web Service” will be placed there by the installer).

Q. What is the difference between a two server and three server installation? How do I know which one to perform?
  • A. The Connector is logically designed so that it does not need to be installed on the same machine as Project Server 2007 nor does it need to be installed on the Team Foundation Server machine. It can be separated out to run on its own machine. This is referred to as a a three-server installation scenario -- it is one where separate machines are used for Project Server, Team Foundation Server, and the Connector. In this case, nothing specific must be kept in mind when running the installation; the defaults can be selected when running the installation wizards. Many times, however, customers do not want to use a different server for the Connector. In these cases, a two server installation routine can be performed. A two-server installation is one where the Connector is installed on the same box as Team Foundation Server. It is important to keep in mind that, by default, Windows SharePoint Services will also be running on this machine and will intercept requests to the Default Web Site. Therefore, the most straightforward procedure for installing the Connector on the same machine as Team Foundation Server (i.e., a two-server installation) is to configure it such that Parent Web Site is the one for Team Foundation Services. By default, this should be configured to run on port 8080 and will not be managed by Windows SharePoint Service.
  • There is no technical reason why the Connector can not be installed and configured on the same machine as Project Server 2007; however, this installation procedure has not been tested and therefore not recommended at this time.

Q. The Connector Web Site is returning an error message that starts "This operation could not be successfully performed. Please contact the administrator and refer to HandlingInstanceID: ". How do I determine the cause of the error?
  • A. Both the Connector Web Site and Connector Web Service subscribe to the best practice regarding error handling which suggests that detailed error information not be exposed to end users. Rather detailed information about the error should be recorded to aide operations staff in diagnosing the issue and only the only error message an end-user receives is a user-friendly one which allows them to provide the operations staff with the information needed to diagnose the problem. The Connector Web Site and Web service make use of the Enterprise Library 3.1 Exception Handling and Logging Application Blocks to accomplish this. When an exception occurs, it is logged in the Application Event Log (by default) and replaced with a message to the end user that affords the operations the ability to diagnose the cause of the issue. Because it leverages Enterprise Library to accomplish this, the behavior is highly configurable and can be easily modified. For example, the Connector web site and/or service can easily be configured to store the logs in a file or database instead of the Application Event Log.
  • When an error is reported, the operations staff should search the log for the handlingInstanceId. This will show the last exception that occurred before the error message was replaced and displayed to the end-user. Often times, there are error messages that contain more pertinent, meaningful information that are logged before this last one. The combination of the error messages that occur prior to and including the one including the relevant handlingInstanceId should provide an indication of the issue that occurred.
Q. Speaking of logging, there are way too many messages being logged. Can I turn this off?
  • A. Yes; however, it is not advised to turn logging off completely but rather filter the types of error messages that are logged. There are several different Priorities with which information is logged. They are: Verbose (0), Information (3), Warning (6), Error (9), Critical (12). Out of the box, the Connector is configured to log all messages (Verbose). As you become comfortable that the Connector is performing the way you intend it to perform, you can configure it so that it does not log as much information by creating a Priority filter for it. For more information about configuring the way information gets logged, please see the documentation for the Enterprise Library Logging Application Block.
Q. I am receiving a 401 error when I try to use the Connector Web Site. What is wrong?
  • A. A "401" error indicates that some type of authorization issue is occurring. The first thing to determine is where the issue is occurring. Most of the time, the issue occurs between the Connector and Project Server. This can be ascertained by navigating to the Connector Web Service and trying to invoke the GetPublishedPSProjects web method. This method simply calls Project Server's Project API to return the list of projects that are published. The Connector also uses the Statusing API to provide the EPM the ability to accept and reject Assignment creations and updates within Project Server (via Task Update). To do this, it needs to use the 'impersonation' model within Project Server and act on behalf of the resource for which it is updating the assignment. That is the sole reason why we need to collect the SiteGuid and SSP when the Connector is installed. If a 401 error occurs here, then there is an issue connecting and/or impersonating to Project Server.
  • First check that the account under which the Connector is running (can be found in the app pool for the Connector Web Service) has permission to update and create tasks in Project Server. Please refer to the Project Server documentation for details on configuring permissions for resources.
  • Also, ensure that you grant the account under which the Connector is running access to SharePoint. Make certain that appropriate permissions are given to this account given the policies of your organization. Obviously, allowing the Connector to be a farm admin will work; however, you may need/wish to lock this account down more. To understand how to enable access for specific accounts, please see the techNet article at
  • After that, check are to ensure that your SiteGuid and SSP are set correctly. These are stored in the web.config file for the Connector Web Service. Check this against what is displayed in SharePoint Central Administrator for your PWA. To do this:
    • Open SharePoint Central Administrator
    • Under Shared Services Administrator on the left Nav bar, you should see the name of your SSP. Make sure this is the same as the one you have in web.config
    • Click the SSP
    • Click Project Web Access Sites
    • Hover over your PWA site so that the dropdownselection appears and click edit
    • In the address bar, you should see a Guid at the end of the URL. This is the SiteGuid. Make sure it is the same as what is in the web.config file.
  • If the SiteGuid and SSP are correct, then the account under which the Connector runs may need to be added to the list of service accounts for the SSP. To do this (again in Sharepoint central administrator):
    • Click Shared Service Administration in the nav bar
    • Hover over your SSP (in bold) site so that the dropdownselection appears and click edit properties
    • At the bottom of this page you should see a text box that allows you to add "Process Accounts with Access to the SSP". Add the account under which the Connector is running here and retest
  • Sometimes the textbox for "Process Accounts with Access to the SSP" will not exist on the web page. To add the account in this circumstance, go to the command line, navigate to Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN and run:
  • stsadm.exe -o editssp -title <SSPNAME> -setaccounts <accounts to add for access>
  • This should handle the majority of the 401 issues you get as it relates to the Statusing API.

Last edited Feb 4, 2008 at 5:57 PM by lfenster, version 9


No comments yet.