This article contains information about how to change the TCP port that Microsoft Office SharePoint Portal Server 2003 uses to connect to Microsoft SQL Server 2000 and the TCP port that Microsoft Office SharePoint Server 2007 uses to connect to Microsoft SQL Server 2005. By default, both SQL Server 2000 and SQL Server 2005 use TCP port 1433 to listen for requests from clients.

If you configure SQL Server to listen on a different port in a server farm deployment of SharePoint Portal Server 2003 or of SharePoint Server 2007, you must also configure SharePoint Portal Server 2003 or SharePoint Server 2007 to connect to SQL Server by using that same port. This article describes the methods that you can use to perform this task.

SQL Server 2000

Before you use one of the following methods, Client Network Utility must be installed on the computers in your server farm that are running SharePoint Portal Server 2003 or SharePoint Server 2007. For more information about how to install Client Network Utility, visit the following Microsoft Web site: Note Client Network Utility is a tool that you can use to change network protocols and to create network protocol connections to computers that are running SQL Server 2000. For more information about how to use Client Network Utility, see Client Network Utility Help.

Method 1: Use Client Network Utility to specify the TCP port that is used to connect to SQL Server 2000

Use Client Network Utility to specify the TCP port, and then restart Internet Information Services (IIS) 6.0. Do this for each computer in your server farm that is running SharePoint Portal Server 2003. To do this, follow these steps:

1. Specify the port that you want to use. To do this, follow these steps:
   1. Start Client Network Utility.
   2. Click the General tab, click TCP/IP in the Enabled protocols by order box, and then click Properties.
   3. Specify the port number that you want in the Default port box, and then click OK two times.
2. Restart IIS. To do this, click Start, click Run, type iisreset in the Open box, and then click OK.

Method 2: Use Client Network Utility to add an alias and to specify the TCP port that is used to connect to SQL Server 2000

Use Client Network Utility to add an alias and to specify a TCP port for the new alias. Do this for each computer in your server farm that is running SharePoint Portal Server 2003. To do this, follow these steps:

1. Install the hotfix package that is described in the following Microsoft Knowledge Base article on a computer in your server farm that is running SharePoint Portal Server 2003:
   885263  (http://kbalertz.com/Feedback.aspx?kbNumber=885263/ ) Description of the SharePoint Portal Server 2003 post-Service Pack 1 hotfix package: September 30, 2004
   Note This hotfix package enables SharePoint Portal Server 2003 to correctly process alias information that is configured in Client Network Utility.
2. Add an alias, and then specify the port for the alias. To do this, follow these steps:
   1. Start Client Network Utility.
   2. Click the Alias tab, and then click Add.
   3. Type an alias in the Server alias box, and then click TCP/IP under Network libraries.
   4. Click to clear the Dynamically determine port check box, type the port number that you want in the Port number box, and then click OK two times.
3. Restart IIS. To do this, click Start, click Run, type iisreset in the Open box, and then click OK.

Notes

• If you do not install the hotfix package that is described in article 885263 in the Microsoft Knowledge Base, this method requires that User Datagram Protocol (UDP) port 1434 remain open.
• If you move the SharePoint Portal Server 2003 databases to another computer that is running SQL Server 2000, you may receive an error message that resembles the following error message when you try to access the portal site:
  Array cannot be null.
  Parameter name: Source
  For example, you receive this error message when you click the link that is displayed on the Web Parts Maintenance page. This error message may not be caused by a Web Part issue.
  
  You may receive this error message in situations when the TCP port that SQL Server 2000 uses is different from the TCP port that SQL Server 2000 used on the original computer. Use Client Network Utility to verify that the port that SQL Server 2000 uses is correct.

SQL Server 2005

Method 1: Use SQL Configuration Manager to specify the TCP port that is used to connect to SQL Server 2005

1. Specify the port that you want to use. To do this, follow these steps:
   1. Click Start, point to All Programs, click Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Configuration Manager.
   2. Expand SQL Native Client Configuration, click Client Protocols, and then double-click TCP/IP.
   3. Specify the port number that you want in the Default port box, and then click OK.
   4. Restart IIS. To do this, click Start, click Run, type iisreset in the Open box, and then click OK.

Method 2: Use SQL Configuration Manager to add an alias and to specify the TCP port that is used to connect to SQL Server 2005

1. Specify the port that you want to use. To do this, follow these steps:
   1. Click Start, point to All Programs, click Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Configuration Manager.
   2. Expand SQL Native Client Configuration, right-click Aliases, and then click New Alias.
   3. In the Alias-New dialog box enter the following information, and then click OK:
      • Alias Name: Type the alias name that you want to use.
      • Port Number: Type the port number that you want to use.
      • Protocol: Select TCP/IP.
      • Server: Type the name of the server where the alias will point.
   4. Restart IIS. To do this, click Start, click Run, type iisreset in the Open box, and then click OK.