![[Intel Navigation Header]](/CONTENT/PIX/HEADER.GIF)
LANDesk(R) Management Suite v2.x: Install/Serialization Usage Tips
Contents:
CONTENTS
This document discusses common installation issues. It supplements the
files in LANDesk(R) Management Suite's Readme Viewer.
"CALL TO UNDEFINED DYNALINK" OR "BLACK SCREEN OF DEATH"
This condition appears in LANDesk(R) Manager Suite v2.0 when the
NetWare* (VLM, NETX)/ Windows* (DLL) drivers on a workstation are from
mismatched sets. A complete matching set could only mean that you have
installed all 3 sets of drivers: VLMUPx.EXE or NET33x.EXE, WINDRx.EXE,
and NWDLLx.EXE, where x is the same number for all sets. These drivers
are available on the LANDesk CD-ROM in the \NWCLIENT\DOSWIN directory.
When Microsoft Windows looks for DLL files to load, it searches the
WINDOWS directory before the WINDOWS\SYSTEM directory. Look for
mismatched NW*.DLL files in the WINDOWS (not SYSTEM) directory or
elsewhere in the search path.
For example, this error appeared when the following files were found in
the WINDOWS directory:
NWCALLS.DLL 5-18-93
NWNETAPI.DLL 5-18-93
NWIPXSPX.DLL 5-18-93
NWLOCALE.DLL 5-18-93
NWPSRV.DLL 10-20-93
Other ways to indentify the error:
After the "call to undefined dynalink" error, you may get a General
Protection Fault.
After you exit Microsoft Windows, the error "Emm386 error #06 in an
application at memory address 00b8.0bcflTo minimize the change of data
loss, EMM 386 has halted your computer. For more information, see the
README.TXT file. To restart your computer, press ENTER."
SECURITY AND SERIALIZATION
Installing to a 3.x server places security and serialization information
in the bindery. Installing to an NDS tree, creates two LANDesk(R)
objects at the root of the tree for security and serialization.
Installing LANDesk Management Suite v2.0 into NetWare* v4.x requires
admin rights to the root of the tree in order to create the security and
serialization objects. If you do not have access, locate SCHEMOD.EXE in
the DISK2 directory on the CD and have someone with admin rights to the
root of the tree run this utility to create the objects.
"SERIALIZATION OBJECT NOT FOUND ON SERVER SERVERNAME" OR "ERROR: SERIALIZATION OBJECT NOT FOUND IN CONTEXT OU=OUNAME.O=ONAME." OR "UNABLE TO COMPLETE
CHECK FOR SERIALIZATION"
LANDesk(R) Management Suite v2.0x
Symptom:
"Serialization Object not found on Server SERVERNAME" or
"ERROR: serialization object not found in context OU=OUNAME.O=ONAME" or
"Unable to complete check for serialization".
Description:
This error occurs when a user tries to run USERTSR.EXE while logged in
to a file server or OU that is not part of the LANDesk Management
Domain. (Being attached to a server that is part of the domain is not
enough.)
Solution:
For Netware* v3.11/v3.12, check the following requirements for proper
serialization:
* Add a "Preferred Server = SERVERNAME" line to the workstation
NET.CFG or use the "/PS=SERVERNAME" command-line option when the
workstation loads NETX or VLMs
* Login to a file server that is part of the LANDesk Management
Suite domain.
* Include the file server that you log in to as part of the LANDesk
management domain (using the management console)
* Create a new management server by installing LANDesk Management
Suite v2.0x on the file server you log in to
For NetWare v4.02/4.1, check the following requirements for proper
serialization with Netware Directory Services (NDS):
* Expand the LANDesk Management Domain to the container which you are
a member of (using the management console under
Manage|Domain|Assign Members to Domain).
Note: That adding an O or OU to the Management Domain will not
automatically include subcontainers unless you activate that option
in the lower left corner of the Define Domain screen.
* A leading dot in the context parameter of the NET.CFG could also
account for a serialization error; removing the leading dot from
the NET.CFG allows serialization to function properly.
* in the NET.CFG make sure the Netware Protocol statement has NDS
first,
Example: "Netware Protocol = NDS BIND", not BIND NDS
* Place a "Preferred tree = TREENAME" in NET.CFG, do not use the
preferred server option.
* IN NWADMIN.EXE highlight the User, choose Details/Environment;
there is a preferred server setting, change this to point to the
LANDesk server where authentication should occur.
WORKSTATION HANGS
LANDesk(R) Management Suite v2.0 only
Symptom:
Workstation hangs in DOS or Windows*.
Description1:
Calls to Interrupt 21h via the NetWare* shell hang a PC running the
shipping release version of USERTSR.EXE. The majority of calls to Int
21h function properly, but programs like BINDVIEW v3.5, pcANYWHERE v2.0,
RPRINTER, and NPRINTER may cause conflicts while making calls via the
NetWare shell. The Novos Terminal Emulation interrupt redirector for
mainframes has also been reported to cause workstation hangs.
Description2:
Versions of NetManage Chameleon prior to v4.5 (released April 1995)
contain NetWare/Windows incompatibilities that hang PCs running LANDesk
Management Suite or LANDesk Manager. WUSER.EXE and IDISPLAY.DLL bring
out the NetWare/Windows conflict with NetManage Chameleon.
Solution1:
Upgrade to LANDesk Management Suite v2.01x which resolves this problem.
Solution2:
Upgrade to NetManage Chameleon v4.5 or later. Contact NetManage at
408-973-7171 to get their current release.
NETWORK CONNECTION ERROR
System Error: Cannot read from device NETWORK
Error message:
User receives a network connection error during installation of
LANDesk(R) Management Suite or when adding licenses in the serialization
process. It may repeatedly appear as a system error like "Cannot read
from device NETWORK" with Cancel and Retry options.
Description:
The standard network connection was NOT lost, but the serialization
process was probably checking a remote server and timed out before
receiving a response.
Solution:
Press the appropriate key to continue (Retry). The serialization
process will continue without a problem after any occurrence of this
error.
WKSTACFG.EXE DOES NOT PROPERLY CONFIGURE A WORKSTATION
Symptom:
Changes are made to the WIN.INI (for example, METERWIN.EXE and WUSER.EXE
are added to the load= line), but WKSTACFG.EXE doesn't place WUSER.EXE,
METERWIN.EXE, etc. in WINDOWS\SYSTEM or modify SYSTEM.INI.
Description:
The WKSTACFG.EXE supplied with LANDesk(R) Management Suite is the first
to require Windows to be in the search path in order to make the proper
Windows* modifications. This allows network administrators to keep
backup copies of Windows on their hard drives without having
WKSTACFG.EXE modify them.
Solution:
Place the WINDOWS directory in the search path.
"DISK SPACE ALERT. THERE IS NOT ENOUGH SPACE ON SERVERNAME\SYS: FOR THE FILESTHAT NEED TO BE COPIED THERE. IF YOU CHOOSE TO CONTINUE, LANDESK(R)
MANAGEMENT SUITE MAY NOT BE ABLE TO INSTALL CORRECTLY."
Error message:
Disk Space Alert. There is not enough space on SERVERNAME\SYS: for the
files that need to be copied there. If you choose to continue,
LANDesk(R) Management Suite may not be able to install correctly.
Description:
If sufficient disk space is available (50-100 MB), a 4.x target file
server may return a faulty value to our query for available disk space
when volume size exceeds approximately 1 GB or more.
Solution:
Reply "Yes" to the "Continue?" option. LANDesk Management Suite will
install properly.
SLOWNESS DURING INSTALLATION FROM CD-ROM
Symptom:
LANDesk(R) Management Suite v2.x installs very slowly.
Solution:
Certain CD players may need SETUP /DELAY=100 to install properly,
especially if the CD player is connected directly to the file server.
This switch may also address some errors like "error decompressing" or
"unable to decompress" files.
"OLE SERVER AUTOMATION ERROR"
OLE registration files can be an issue if newer versions of OLE are
installed after LANDesk(R) Management Suite or if there is a mixed
version of OLE DLL's on the system. By default, the OLE upgrade process
automatically upgrades only OLE files Microsoft supplies. The LANDesk
Management Suite OLE files must be registered again.
During the initial install of LANDesk Management Suite, the OLE files
are copied down to the C:\LANDESK directory and then registered with
REGEDIT.EXE in Windows*. To register them again, complete the following
steps:
1. Run REGEDIT.EXE and delete the LANDesk Management Suite
applications shown on the list.
2. Re-Merge the .REG files from the C:\LANDESK directory with REGEDIT
one by one ( takes about two minutes), then close Windows entirely.
3. Re-start Windows and try the Management Console and Application
Task again.
Note: If the Management Console and Application Task still does not
work, delete the Management Console icon and the C:\LANDESK directory.
Then re-run SETUP.EXE from F:\LANDESK.
"ERROR: UNABLE TO GET PRIMARY SERVER INFORMATION"
LANDesk(R) Management Suite v2.0x
Symptom:
USERTSR will not load if the network shell is NETX (any version) and the
user has not logged into a managed server. However, USERTSR will load
if the network shell is VLM and the user has not logged into a managed
server.
Description:
In previous releases of LANDesk Manager USER.COM loaded before login
using NETX.EXE or VLM.EXE. However, in the process of adding NDS support
temporarily removed this functionality (for workstations running
USERTSR.EXE and NETX.EXE).
Solution:
Upgrade to LANDesk Management Suite v2.0x. If you haven't received this
upgrade you should get electronic document 9985 from Intel's online
services.
INSTALLING TO A NETWARE* V3.11 CORE SERVER
Make sure the file server is running matching or current versions of
CLIB and STREAMS. Many NetWare* v3.11 file servers may run a CLIB v3.11h
and the original STREAMS v3.11d. Problems may occur with CLIB v3.12
(supplied with Btrieve* files on the CD) and an older STREAMS v3.11. For
example, the LANDesk(R) Management Suite Btrieve databases may not be
created or linked properly, which prevents some of the LANDesk
Management Suite NLMs from loading. Also, METER.NLM will load, but RELAY
will continually 'EXIT' after loading because PSCAN .NLM cannot determin
what version of NetWare is running due to a CLIB/STREAMS mismatch like
the one above.
Run a matched set of CLIB/STREAMS versions to resolve this conflict.
"ERROR LANS011: INVALID TEMPORARY PATH" OR UNABLE TO LOAD POPUPTSR /T=SELTEMPBEFORE LOGIN IS RUN
LANDesk(R) Management Suite v2.0x
Symptom:
Error message:"Error LANS011: Invalid temporary path" or Unable to load
POPUPTSR /t=SELTEMP before LOGIN is run
Description:
POPUPTSR requires sufficient rights to store a temporary file during DOS
workstation processes like chat, file transfer, and software
distribution.
When POPUPTSR.EXE tries to load before a workstation is logged into a
file server, it checks to see if the temporary file can be stored in a
default location (SYS:\LOGIN\LANDESK unless the
/t=SYS:\LOGIN\LANDESK\SELTEMP switch was used). Because the users
aren't logged in yet, the check for write privileges fails, and POPUPTSR
checks the DOS environment for a TEMP=DIRECTORYNAME setting. If one
does not exist, POPUPTSR cannot load and this message appears.
Solution:
Create a DOS setting TEMP=C:\ (or another existing directory where the
workstation can write files) or load POPUPTSR with the /t=DIRECTORYNAME
option. For example, POPUPTSR /t=C:\ or POPUPTSR /t=C:\TEMP.
BACK UP THE ALERT MANAGEMENT SYSTEM DATABASE
To back up the Alert Management System database files in LANDesk(R)
Management Suite v2.01x:
To avoid losing your alert setup in the event of database corruption,
you should back up the three AMS_DB files and the NW*AGNT.INI after
setting up all the events and alert functions you need. Then if you ever
have the occasion that you need to rebuild the Alert Management System
database you simply can delete the existing files and restore them from
the backup file set.
Trademark information