The article describes how to establish a connection between Microsoft SharePoint Team Services in Microsoft Project Web Access after you run the SharePoint Configuration Wizard (Stswiz.exe).

Part 1: Account Permissions

To set account permissions for the SharePoint Team Server and Microsoft SQL Server, follow these steps:

1. Designate a Windows user account that has Administrative permissions on the SharePoint Team Services computer.
   
   Note Microsoft recommends that the Microsoft Windows User Accounts have passwords that are set to Password never expires.
2. Designate a Windows user account that will have db_datareader permissions to the SharePoint Team Services database in SQL Server. To add the db_datareader rights to the SharePoint SQL Server database, follow these steps:
   1. Click Start, point to Programs, click Microsoft SQL Server, and then click Enterprise Manager.
   2. Expand the Security folder, right-click Logins, and then click New Login.
   3. On the General tab, type the name in the form of Domain\UserName in the Name box.
   4. In the Defaults section, change the name of the database to your SharePoint database.
   5. On the Database Access tab, click to select the Permit check box for the SharePoint database.
   6. In the Database Roles area, click to select db_datareader, and then click OK.
3. Run the PSCOM+ utility to impersonate the accounts for a COM+ application.
   
   Note Pscomp+.exe is used to create or set the identity of the accounts that will be used to impersonate the component services for Microsoft Project Server.
   
   To run the PSCOM+ utility, follow these steps:
   1. Double-click Pscom+.exe. The Pscom+.exe utility is located in the Microsoft Project Server\Bin\1033 folder.
   2. On the Microsoft Project Server Com+ Settings menu, type the Windows user account and password (in the form of domain\username) that you created earlier in this article for the SharePoint Team Services Administration Identity (Windows User Account that is an Administrator on the STS Server) and the SharePoint Team Services Database Access Identity (Windows Account that has db_datareader rights in SQL Server).
   3. Click Create\Update Com+ Apps.
      
      Note You can enter the OLAP Access Identity for the Windows user account that has Administrative permissions to the OLAP Administrators group, or you can defer this for later.

Part 2: Configure Project Server for a Proxy Server

Project Server communicates with SharePoint Team Services by using the XMLHTTP protocol. For Project Server to communicate with the SharePoint Team Services computer successfully, the Project Server computer must be configured to connect through the proxy server, if your organization uses one.

If your organization does not use a proxy server, that information must be configured also. This requirement is true even if Project Server and SharePoint Team Services are installed on the same computer.

1. On the Project Server-based computer, click Start, click Run, type cmd in the Open box, and then click OK.
2. Change the folder to the location of Proxycfg.exe.
   
   For example, type cd C:\Program Files\Microsoft Project Server\Bin.
3. Type the following command. When you do this, specify the ServerName, the IP address, and the fully qualified domain name (FQDN) of the SharePoint Server in the bypass list. For example, type the following: proxycfg -d -p " YourProxyServer " "local;ServerName;IPAddress; FQDN"
   
   Note If you are not in a proxy server environment, type NoProxyServer in the YourProxyServer section.
4. The Proxy Server information will process and write to the registry.
5. After returning to the command prompt, type iisreset to restart Internet Information Server (IIS).
6. Try to connect SharePoint Team Services to Project Web Access.

For more information about the configuration of SharePoint Team Services in Microsoft Project Web Access, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the WinHTTP Proxy configuration utility, see the following Microsoft Web site: