Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

BUG: You cannot sort some information by using the column headings in the SNA Manager MMC snap-in in Host Integration Server 2004 and in Host Integration Server 2000


View products that this article applies to.

Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 (http://support.microsoft.com/kb/256986/) Description of the Microsoft Windows registry

↑ Back to the top


Symptoms

In the SNA Manager Microsoft Management Console (MMC) snap-in that is in Microsoft Host Integration Server 2004, you cannot sort some information by using the column headings. Instead, the information is sorted based on the items that appear in the first column. For example, information in the Workstation container is sorted based on the Workstation ID column. You cannot sort the items by clicking the Comment column.

You do not experience this problem in other containers, such as the APPC Modes container. You can sort information in the APPC Modes container based on the Mode Name or the Comment columns. The information is sorted by using a case-sensitive sorting algorithm.

↑ Back to the top


Cause

This problem occurs because the sorting algorithm of SNA Manager is not applied to all containers. The sorting algorithm of SNA Manager only applies where the result items do not appear under the container name and the column name. For example, the workstation IDs can appear under the Workstations container name and in the Workstation ID column of the results window.

↑ Back to the top


Resolution

Host Integration Server 2000

No fix is currently available for Host Integration Server 2000.

Host Integration Server 2004

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
No prerequisites are required.
Restart requirement
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version     Size     File name
   ---------------------------------------------------
   10-Jun-2005  22:43  6.0.1960.0  252,416  Mmcsna.dll

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

After you apply this hotfix, SNA Manager sorts items that are listed in all the available columns in all containers. By default, sorting uses a case-sensitive algorithm. The following list is an example of items that are sorted in ascending order when you use case-sensitive sorting:
ALICE
TEST
TOM
WILLIAM
test
If the column is sorted in descending order, the results appear as follows:
test
WILLIAM
TOM
TEST
ALICE
In this example, "test" and "TEST" are not listed together because of the case-sensitive sorting algorithm. In some circumstances, you may want to sort information by using case-insensitive sorting. To use case-insensitive sorting, follow these steps to create the CaseInsensitiveSorting registry value:

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
1.Click Start, click Run, type regedit, and then click OK.
2.Locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Sna Server\CurrentVersion\Manage
3.Right-click Manage, point to New, and then click DWORD Value.
4.Type CaseInsensitiveSorting, and then press ENTER.
5.Double-click CaseInsensitiveSorting, type 1 in the Value data box, and then click OK.
6.Close and then restart SNA Manager.
Alternatively, you can create the CaseInsensitiveSorting registry value in the HKEY_CURRENT_USER key. To do this, follow these steps:
1.Click Start, click Run, type regedit, and then click OK.
2.Locate the following subkey in the registry:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Sna Server\CurrentVersion\Manage
Note By default, the Manage subkey under the HKEY_CURRENT_USER key does not exist on Host Integration Server 2004-based servers. You must add this subkey before you add the CaseInsensitiveSorting registry value. However, the Manage subkey does exist under the HKEY_CURRENT_USER key on Host Integration Server 2004-based client systems. To create the CurrentVersion\Manage subkey, follow these steps:
a. Locate the following subkey in the registry:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Sna Server
b. Right-click Sna Server, point to New, and then click Key.
c. Type CurrentVersion, and then press ENTER.
d. Right-click CurrentVersion, point to New, and then click Key.
e. Type Manage, and then press ENTER.
3.Right-click Manage, point to New, and then click DWORD Value.
4.Type CaseInsensitiveSorting, and then press ENTER.
5.Double-click CaseInsensitiveSorting, type 1 in the Value data box, and then click OK.
6.Close and then restart SNA Manager.
First, the SNA Manager snap-in searches for the CaseInsensitiveSorting registry value under the HKEY_CURRENT_USER key. If the CaseInsensitiveSorting registry value does not exist, the SNA Manager snap-in searches the HKEY_LOCAL_MACHINE key. If the CaseInsensitiveSorting registry value does not exist in either registry location, or if the value is any value that is different from "1", all sorting will be case-sensitive.

After you enable the CaseInsensitiveSorting registry value, SNA Manager uses the case-insensitive sorting algorithm the next time that you start SNA Manager. The following list is an example of items that are sorted in ascending order when you use case-insensitive sorting:
ALICE
test
TEST
TOM
WILLIAM
If the column is sorted in descending order, the results appear as follows:
WILLIAM
TOM
test
TEST
ALICE
When case-insensitive sorting is enabled, "test" and "TEST" are listed together.

For more information about standard terminology used to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top


Keywords: kbfix, kbqfe, kbui, kbusage, kbsnapin, kbhotfixserver, kbbug, KB898539

↑ Back to the top

Article Info
Article ID : 898539
Revision : 5
Created on : 12/4/2007
Published on : 12/4/2007
Exists online : False
Views : 411