When Tealeaf is installed or upgrade, the required permissions are automatically configured for IIS. If permissions are modified for enterprise reasons, Portal functionality can be compromised. Behaviors are varied.

To run TLIISUtility:

1. Open a command line on the Portal server.
2. Navigate to the following directory:

   
   <install_directory>\Tools\Install
   

3. Launch TLIISUtility.exe.
4. Configure permissions per the following requirements:
   1. Required Permissions for IIS6:

      Check the Microsoft Support site for information about permissions and user rights for IIS 6.0.

   2. Required Permissions for IIS7:

      Check the Microsoft Support site for information about permissions and user rights for IIS 7.0 and later.

5. Restart IIS.

The error in the HTTPSYS error log (HTTPERRx.log) is the following:

400 - RequestLength

If Integrated Authentication is enabled in IIS and it negotiates Kerberos, some users may have a very large Kerberos ticket that exceeds limits in the request header.

• In one case, users were unable to access the Portal due to a large number of group memberships.

For more information, see the following web pages:

• Http.sys registry settings for IIS (Microsoft™ KB 820129) http://support.microsoft.com/?kbid=820129
• Kerberos Authentication Problem with Active Directory http://blogs.technet.com/surama/archive/2009/04/06/kerberos-authentication-problem-with-active-directory.aspx
• HTTP 400 Bad Request Discussion http://www.issociate.de/board/post/314237/HTTP_400_Bad_Request.html

To fix this issue, complete the following steps.

1. Add registry keys on the Reporting Server to increase the Maximum Field Length and Maximum Request Bytes to accommodate the larger Kerberos tickets:

   
   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters\
      MaxFieldLength = 32768 (default = 16384)
   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters\
      MaxRequestBytes = 32768 (default = 16384)
   

2. Restart IIS.

The Total Sessions count is incremented whenever a new website session starts. The Archived Sessions count is incremented when sessions are marked for saving. This difference in definition may cause differences in count.

Around midnight, there can be more Total Sessions than Archived Sessions because some active sessions were not yet saved to the Long-Term Canister.

Similarly, a day can have more archived sessions than total sessions, if a burst of sessions that are started before midnight and ended and were saved some time after midnight.

1. Run the following SQL against the TL_SYSTEM database using the TLADMIN or TLUSER account:

   
   USE TL_SYSTEM
   
   DELETE FROM RS_PROFILE_ITEM WHERE PROFILE_ID = 1 AND OBJ_ID = 100
   GO
   
   INSERT INTO RS_PROFILE_ITEM
   SELECT 1, 100, NODE_ID FROM RS_MENU
   GO
   

2. Perform an IIS reset after the above is executed.
3. Users who are members of the Admin group can now access all available pages in the Portal menu.

The steps to set the time zone are as follows:

1. Log in to the Portal as a Portal administrator.
2. Navigate to Portal Management.
3. Select the type of accounts to administer.
4. Select the user who is experiencing time discrepancies.
5. From the Time Zone drop-down, select the user's correct time zone.
6. To complete the change, click Save.
7. To verify that time change was effectively applied, select Active > Sessions and check the timestamps for active sessions.

On a system with Microsoft Office installed, by default Windows™ attempts to open all XML documents using MSOXMLED.EXE. This application scans the document for the mso-application tag, which identifies the Office application to use to open the XML document.

If this association was changed to use, for example, Notepad.exe, then Windows cannot correctly open Office XML documents.

To verify the proper mapping:

1. Open Windows Explorer to any folder on your local computer.
2. In the Windows Explorer menu, select Tools > Folder Options....
3. Click the File Types tab.
4. Select the XML/XML Document entry.
5. Click Advanced.
6. There should be two actions listed: edit and open.
7. For each action, click Edit and review the value for Application used to perform action. They should similar to the following paths for 64-bit Windows:

   
   "C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSOXMLED.EXE"
      /verb edit "%1"
   "C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSOXMLED.EXE"
      /verb open "%1"
   

If the above paths do not point to the MSOXMLED.EXE application, XML documents cannot open properly in Excel. To remedy this problem, change the paths to point to the proper application.