PSS ID Number: 191702
Article Last Modified on 5/23/2003
The information in this article applies to:
- Microsoft SNA Server 4.0
- Microsoft SNA Server 4.0 SP1
This article was previously published under Q191702
SYMPTOMS
If an LUA pool is deleted from SNA Server Manager and the configuration is
saved, SNA Server Manager suddenly closes. When the manager is re-opened,
the LUA pool is still in the configuration.
Steps to Reproduce the Problem:
- Insert an LUA/LU on a connection.
- Assign the LUA/LU to an LUA pool.
- Assign the LUA pool to a user or group, such as "Everyone".
- Save the configuration.
- Delete the LUA pool. When you are prompted "Are you sure you want to
remove LUAPOOL?", click OK.
- Save the configuration. SNA Server Manager closes.
- Re-open SNA Server Manager. The LUA pool is still present in the
configuration.
CAUSE
The LUA pool has been assigned to a configured user or group. If the
assignment is not removed before the LUA pool is deleted, the SNA Server
Manager traps. Deleting the LUA pool does not remove it from the user
record automatically.
WORKAROUND
To work around this problem, before you delete an LUA pool from SNA Server
Manager, delete the LUA pool from the configured user's assigned LUs.
STATUS
Microsoft has confirmed this to be a problem in SNA Server versions 4.0 and
4.0 SP1.
A supported fix is now available, but has not been fully regression-tested
and should be applied only to systems experiencing this specific problem.
Unless you are severely impacted by this specific problem, Microsoft
recommends that you wait for the next Service Pack that contains this fix.
Contacts Microsoft Product Support Services for more information.
MORE INFORMATION
In SNA Server 3.0 and 2.11, an LUA pool could not be assigned to a
configured user.
This also occurs on SNA Microsoft Management Console (MMC).
Keywords: kbbug kbfix kbQFE KB191702
Technology: kbAudDeveloper kbSNAServ400 kbSNAServ400SP1 kbSNAServSearch