Article ID: 185447
Article Last Modified on 5/23/2003
APPLIES TO
- Microsoft SNA Server 3.0 Service Pack 4
- Microsoft SNA Server 4.0
- Microsoft SNA Server 3.0 Service Pack 2
- Microsoft SNA Server 3.0 Service Pack 3
- Microsoft SNA Server 4.0
This article was previously published under Q185447
SYMPTOMS
If an LUA RUI or SLI application is started while the SnaBase
service is
not running, SnaBase will be started automatically. However, if
the SnaBase
fails to open a sponsor connection to SNA Server and then fails to
initialize, the LUA application may fail with an access violation
in
SNADMOD!sepdbubl.
CAUSE
The problem occurs because the LUA RUI DLL file (Winrui32.dll)
does not
properly handle a failure to initialize the underlying
Snadmod.dll.
RESOLUTION
SNA Server 3.0
To resolve this problem, obtain the latest service pack for SNA Server version 3.0. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
184307 How to Obtain the Latest SNA Server Version 3.0 Service Pack
SNA Server 4.0
This problem has been corrected in the latest U.S. Service Pack
for SNA
Server version 4.0. For information on obtaining the Service Pack,
query on
the following word in the Microsoft Knowledge Base (without the
spaces):
S E R V P A C K
WORKAROUND
To work around the problem you must correct the problem which is
preventing
the SnaBase service from initializing properly.
STATUS
Microsoft has confirmed that this is a problem in SNA Server, versions 3.0, 3.0 SP1, 3.0SP2, 3.0 SP3, and4.0. This problem was first corrected in SNA Server 3.0 Service Pack 4.
Keywords: kbbug kbfix KB185447