Consider the following scenario. You use a Web page that uses Excel Web Access (EWA) to open a workbook on a computer that is running Microsoft Office SharePoint Server 2007. If there are many connections to the computer that is running SharePoint Server 2007, the workbook does not load. Typically, this issue occurs if there are more than 2,000 sessions on the computer that is running SharePoint Server 2007 server. Additionally, you may receive one or more of the following error messages.
Note This issue applies only to a Kerberos environment. This issue does not apply to a Trusted Subsystem (TSS) configuration.
- Error message 1
- Error message 2
Failed with the following response<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap: Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring xml:lang="en-US">An error has occurred.</faultstring><detail /></soap:Fault></soap:Body></soap:Envelope>
Additionally, the following warning message is logged in the Application log:
Event Type: Warning
Event Source: Office SharePoint Server
Event Category: Excel Services Web Front End
Event ID: 5236
User: User_Name
Computer: Server_Name
Description:
An Internal error prevented the request from being processed. Excel Calculation Services
http://Server_Name:56737/Shared_Service_Provider_Name/ExcelCalculationServer/ExcelService.asmx Exception: Client found response content type of 'text/html', but expected 'text/xml'.
The request failed with the error message:
<html><head><title>Error</title></head><body>No authority could be contacted for authentication.
</body></html>
--.
[Session: (null)
User: User_Name].
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
You may also experience this issue if you access workbooks by using the Excel Web Services for SharePoint Server 2007.
To resolve this issue, change the MaxUserPort setting on the computer that is running SharePoint Server 2007. To do this, follow these steps:
- Click Start, click Run, type regedit in the Open box, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters
- After you select the subkey that is specified in step 2, point to New on the Edit menu, and then click DWORD Value.
Note If the MaxUserPort DWORD value already exists, go to step 5. - Type MaxUserPort, and then press ENTER.
- Right-click MaxUserPort, and then click Modify.
- In the Value data box, type a value that is more than 5000 and less than 65535. Then, click OK.
For example, type 10000 in the Value data box, and then click OK.
Note The MaxUserPort value controls the maximum dynamic port number. The exact number that is used for this value depends on your scenario. - On the File menu, click Exit to exit Registry Editor.
- Restart the computer that is running SharePoint Server 2007.
The TCPTimedWaitDelay setting can also be added to determine how long a closed port waits until the closed port can be reused.
For more information about how to change the MaxUserPort setting and the TCPTimedWaitDelay setting, click the following article number to view the article in the Microsoft Knowledge Base:
328476Â
(http://kbalertz.com/Feedback.aspx?kbNumber=328476/
)
Description of TCP/IP settings that you may have to adjust when SQL Server connection pooling is disabled