[Intel Navigation Header]

    LANDesk(R) Management Suite v2.x: Troubleshooting Tips from Tech Support

    Contents:

    • TROUBLESHOOTING TIPS FROM TECHNICAL SUPPORT FOR LANDESK(R) MANAGEMENT SUITE V2.X
    • "SERIALIZATION OBJECT NOT FOUND ON SERVER SERVERNAME" OR "ERROR: SERIALIZATION OBJECT NOT FOUND IN CONTEXT OU=OUNAME.O=ONAME." OR "UNABLE TO COMPLETE
    • "CALL TO UNDEFINED DYNALINK" OR "BLACK SCREEN OF DEATH"
    • WKSTACFG.EXE DOES NOT PROPERLY CONFIGURE A WORKSTATION
    • WORKSTATION HANGS
    • AMOUNT OF TIME NEEDED TO RUN SERIALIZATION PROGRAM
    • TIME STAMP OFF BY 1 HOUR OR MORE
    • COMPAQ NETFLEX LAN DRIVERS AND SERVER MONITOR
    • UNABLE TO MAP TEMPORARY DRIVES AFTER INSTALL
    
    

    TROUBLESHOOTING TIPS FROM TECHNICAL SUPPORT FOR LANDESK(R) MANAGEMENT SUITE V2.X

    
       This document discusses issues commonly encountered with LANDesk(R)
    
       Management Suite v2.x. It contains easy-to-use procedures and
    
       supplements the files in the LANDesk Management Suite Readme Viewer.
    
       This document contains the following items:
    
    
    
       Note:     Upgrade information is available in document  9739.
    
    
    
    

    "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.
    
    
    
    

    "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."
    
    
    
    

    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.
    
    
    
    

    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.
    
    
    
    

    AMOUNT OF TIME NEEDED TO RUN SERIALIZATION PROGRAM

    
       When you are adding licenses to LANDesk(R) Management Suite, the
    
       workstation may appear to hang while reading the floppy drive for the
    
       node license information.  The workstation is not hung, it may take up
    
       to 3 minutes for the process to finish.  During this time, the icon does
    
       not spin, but the floppy disk drive light is on.
    
    
    
    

    TIME STAMP OFF BY 1 HOUR OR MORE

    
       Symptom:
    
       Displayed time stamps in LANDesk(R) Management Suite v2.0x are off by an
    
       increment of 1 hour or more.
    
    
    
       Description:
    
       The time zone setting at the file server and/or workstation probably
    
       needs modification.  NetWare's SYSTIME.EXE fixes some time discrepancies
    
       between the file server and workstation, but not all. Novell's CLIB
    
    
    
       v3.12h reportedly reports time better than previous releases (not an
    
       hour off).
    
    
    
       Solution:
    
       To check the file server time zone setting, run SET TIME ZONE at the
    
       file server console.  Follow the instructions in NetWare* System
    
       Administration under SET TIMEZONE.  For example, a file server in Utah
    
       would use SET TIMEZONE=MST7  (during daylight savings, MST7MDT would be
    
       appropriate; the default is EST5EDT, but NetWare seems to ignore the
    
       daylight savings settings regardless, so many customers end up
    
       specifying EST5 or MST7 when they are really CST6, for example). To
    
       automatically set this parameter when the file server comes up, place
    
       this SET parameter in STARTUP.NCF or at the beginning of AUTOEXEC.NCF. 
    
       CLIB.NLM must be loaded after this parameter, so setting it manually may
    
       require you to unload several NLMs.  NetWare does not automatically
    
       adjust the time zone setting when daylight savings changes every six
    
       months.
    
    
    
       To set the time zone at a workstation, use SET TZ with similar syntax. 
    
       For example, a LANDesk  administrator's workstation in California would
    
       place SET TZ=PST8 in AUTOEXEC.BAT.
    
    
    
    

    COMPAQ NETFLEX LAN DRIVERS AND SERVER MONITOR

    
       Unlike other NIC vendors, Compaq NetFlex LAN drivers (CPQ*.LAN) use an
    
       optional, unique method to save registers which may ABEND a file server
    
       when MSM (Novell's Generic Media Support Module) calls
    
       DriverStatisticsChange and alters registers. Versions of Novell's
    
       MONITOR.NLM dated before 1993 uncover this same issue -- trying to view
    
       NetFlex LAN card statistics in MONITOR.NLM causes an immediate ABEND.
    
       Intel's NLMs (NW3AGNT or NW4AGNT), Novell's INSTALL.NLM, NMS, and old
    
       TCPIP NLMs induce the same missing register ABEND.
    
    
    
       Fortunately, NLMs can be modified to not require the Compaq LAN driver
    
       to save a register. Intel has modified NW3AGNT and NW4AGNT NLMs to
    
       prevent an ABEND by saving the register instead of asking the LAN driver
    
       to do so. Upgrade to the v2.01 or higher release of LANDesk(R)
    
       Management Suite. Order electronic document 9985, which has the upgrade
    
       form and instructions.
    
    
    
       In January 1995, Novell certified LANDesk Management Suite's NLMs with
    
       NetWare* v3.11, v3.12, v4.02, and v4.1 (certification number N-189). 
    
       Certification details are available from Novell Labs Faxback 801
    
       429-2776/800 414-LABS document 20113.
    
    
    
    

    UNABLE TO MAP TEMPORARY DRIVES AFTER INSTALL

    
       Symptom:
    
       Novell NetWare* v4.x:
    
       After expanding to a new Organizational Unit (OU), members of the
    
       LANDESKGROUP are not able to map temporary drives back to the core
    
       server.  All the appropriate rights are granted to the new LANDESKGROUP.
    
    
    
       Description:
    
       After expanding, the user does not have a connection to the core server
    
    
    
       so the authentication times out before the connection can be made. They
    
       therefore do not have rights to the SELTEMP directory on the core
    
       server.
    
    
    
       Solution:
    
       Create a SELTEMP directory on the managed server and give the
    
       LANDESKGROUP rights there. 
    
    

    Trademark information