NWADMIN 5.19F fixes TLS (Thread Local Storage) issues.
(Last modified: 03Dec2002)
This document (10050015) is provided subject to the disclaimer at the end of this document.
goal
NWADMIN 5.19F fixes TLS (Thread Local Storage) issues.
fact
Formerly TID 2955955 See this TID for File Content information.
Associated File to download: admn519f.exe 3291928 bytes 08Mar2000 03:06PM
Novell NetWare
Microsoft Windows 95/98/NT
NetWare Administrator 32 (NWADMN32.EXE)
Novell ZENworks for Desktops 2
Novell GroupWise
Novell BorderManager
Novell NDS for NT 2.01
NDPS
All or most of the above products were installed to the same server.
Numerous snapins in the PUBLIC\WIN32\SNAPINS directory.
NWADMIN v5.16 or earlier
symptom
WMGR32R.DLL, NWDMSNAP.DLL, and DLU32R.DLL could not be loaded or found.
Error: "WMINV32.DLL is corrupt or missing".
Error: "WMINVEX.DLL is corrupt or missing".
Runtime Error When Starting NWADMIN32.
Error loading NWADMN32 on a Win95 workstation.
Error when creating an NDPS Printer Agent.
Error: "Microsoft Visual C++ Runtime Library Runtime Error! Program:. F:\PUBLIC\WIN32\NWADMN32.EXE abnormal program termination."
Error:"DLL is missing or corrupt".
Receiving errors that many .DLL files are missing or corrupt, but files are located on the server.
Loading NWAdmin32 sits at the splash screen.
NWAdmin32 will open if you rename the SNAPIN folder to SNAPIN.OLD, but you lose all SNAPIN functionality until you name it back.
Error creating a new user in NWADMIN
NWADMN32.EXE will not launch.
NWAdmin Snapin Errors.
Missing DLL errors.
Error: "wn3xsnap nwapp32.dll not found" .
Error: "wmcc32.dll cannot be found".
"language resource cannot be found".
Error: "Dr Watson error access violation".
"Access violation 0xc0000005".
NWADMN32 returns NDPSW32.DLL is missing or corrupt.
Error: "Microsoft Visual C++ Runtime Library Runtime Error! Program: Z:\Win32\Nwadmn32.exe Abnormal program termination".
The dynamic link library [drive letter]:\public\win32\NDPSW32.DLL cannot be located or is corrupted.
NWADMIN32.EXE entry screen will come up and flash repeatedly.
Your path variable is invalid or your DLLs were not installed correctly."
The NLS software for NetWare Administrator cannot be loaded
The software cannot locate the licensing library (NLSAP32.dll) or it cannot locate the most recent licensing library.
The NLS software for netware administrator could not initialize its language resources.
The software either cannot find the language resource file or it has attempted to load a resource file that is out of date.
All NLS administration will be displayed in English.
The license usage reporting tool is not available.
NWADMIN32 gets a MS C++ runtime error when creating an NDPS Printer Agent or when launching NWADMIN32.
Snapin / DLL Problem Resolution.
NWADMIN will not load after loading additional software on the server.
change
Added NetWare 5.0 Support Pack 4
New software (any software with snapins for NWADMIN) was loaded on the server.
cause
NWADMN32 is running out of Thread Local Storage (TLS) handles due to the amount of DLL snapins being loaded. Most Novell products/services installed on the server require Snapins (DLLs) to be copied to the Public directory so NWAdmin32 can manage that product. Having too many Snapins on a server can cause the NWADMIN process to run out of TLS handles. Windows 95, 98, and NT allocate 64 of these handles for NWADMIN to use. After installing a new product, any attempt to launch NWADMIN will error out in any of a variety of ways mentioned above. Windows cannot handle the amount threads being loaded. NWAdmin requires 17 handles, ZEN requires 4, and so on. Certain snap-ins for NWADMN32 require more threads than others making this a problem difficult to troubleshoot, simply installing a program that pushes your "required snapins" over the limit will cause NWADMIN to error when launched. NWADMIN 5.18 was a good work around for this problem, but the new release fixes this issue.
fix
NetWare Administrator version 5.19f corrects the problem.
This updated NetWare Administrator (NWadmn32) corrects the symptoms caused by too many Thread Local Storage (TLS) loaded on the workstation by allocating more threads from memory. This condition occurs on workstations that load NWADMN32.EXE from a server with multiple products installed that use snapins to nwadmn32.
Installation Instructions:
1. Copy the contents of the \public\win32 directory to a test directory, i.e. "win32test", to insure data integrity.
2. Download ADMN519F.EXE from the support page File Finder and save it to an empty directory that the customer created. Expand the file.
3. When expanded the folder will contain a new win32 directory. Copy the CONTENTS of this directory into the CONTENTS of the win32test directory for test purposes overwriting everything. This will replace the old NWADMIN, but retain all existing snapins.
4. Run the new NWADMIN32.EXE. If NWADMIN now appears as it should, it is safe to backup the old win32 directory and rename this directory to "win32". If there are still errors, contact Novell Support Services.
If errors continue to occur try deleting the TLS*.* files located in the sys:public\win32 directory of the server.
Nwadmn32.exe update available in NW5SP5.EXE for NetWare 5 and D51SP1.EXE for NetWare 5.1 Domestic
document
Document Title: | NWADMIN 5.19F fixes TLS (Thread Local Storage) issues. |
Document ID: | 10050015 |
Solution ID: | 1.0.59763959.2571262 |
Creation Date: | 10Mar2000 |
Modified Date: | 03Dec2002 |
Novell Product Class: | NetWare Novell BorderManager Services |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.