[Intel Navigation Header]

    LANDesk(R) Management Suite v2.x: AMS Usage Tips

    Contents:

    • CONTENTS
    • REBUILD THE AMS DATABASE
    • "COULD NOT START THE ALERT CONVERTER BECAUSE, AMS.NLM IS NOT LOADED."
    • "CANNOT SEND EVENTS OR READ EVENT LOG TO/FROM LANDESK CORE SERVER BECAUSE: AMS.NLM IS NOT LOADED."
    • EVENT MANAGER DOES NOT SHOW ALL EVENTS FOR ALL UTILITIES
    • SET UP TO WRITE ALERTS TO A FILE BUT THE FILE DOES NOT GET UPDATED
    • SNMP TRAP FUNCTION FAILS
    • GPF IN FAXABILITY WHEN SENDING ALERT TO FAX
    • "RUN NLM" OPTION DOES NOT FUNCTION
    • UNABLE TO EXECUTE PROGRAMS VIA ALERT MANAGEMENT SYSTEM
    • CANNOT PRINT TO A NON-WINDOWS* DEFAULT PRINTER
    • SUPPORTED MODEMS DO NOT SHOW UP IN THE MODEM INSTALLATION LIST
    • CANNOT GET THE EVENTS TO SEND TO NETWARE* MHS
    • CANNOT GET THE ALERTS TO SEND TO MS/MAIL
    • CC:MAIL MESSAGE CAN'T BE SENT
    • VPWIN SAYS THAT THE CORE NLMS AREN'T LOADED AND AMS CAN'T INITIALIZE
    • MANAGED SERVER CAN'T COMMUNICATE WITH THE CORE SERVER
    • AMS.NLM WON'T LOAD
    • LOG NO LONGER DISPLAYS ANY LOG ENTRIES
    • JOBS ARE NOT BEING EXECUTED
    • "PLAY A WAVE FILE" DOES NOT PLAY THE SPECIFIED SOUND
    • CHANGING THE CLIENTNAME IN THE WIN.INI FILE
    • DETERMINING WHICH BROADCAST OPTION TO USE
    • CONMAN.NLM CANNOT ESTABLISH A CONNECTION FROM A CONSOLE WORKSTATION TO A CORESERVER
    • CONNECTIONS MAY BE LOST ON CONMAN RUNNING IN A NETWARE* 4.X ENVIRONMENT
    
    

    CONTENTS

    
       This document discusses issues commonly encountered with Alert
    
       Management System (AMS).  It supplements the files in LANDesk(R)
    
       Management Suite's Readme Viewer.
    
    
    
    

    REBUILD THE AMS DATABASE

    
       Starved Btrieve* environment space may cause your LANDesk(R) Management
    
       Suite AMS database to become corrupt. Another cause could be that the
    
       Btrieve database mushroomed (for example, 15 MB compared to a normal 1
    
       MB or less) and cause the Btrieve access to show up as high CPU
    
       utilization with AMS.NLM .
    
    
    
       If you are suspicious of the integrity of the AMS database, you must
    
       unload AMS.NLM, which will require that all but 4 of the other LANDesk
    
       Management Suite NLMs be unloaded as well. Refer to the LDORDER.DAT in
    
       SYS:SYSTEM (the installation process built this file according to your
    
       installation choices) to unload them. Reload AMS with an option:
    
    
    
            Load AMS NEWDB
    
    
    
       You probably don't want to permanently modify your LD_AUTO.NCF to load
    
       AMS.NLM with this parameter. To troubleshoot why the database corruption
    
       occurred in the first place, see the Btrieve Issues on the pink card
    
       included in the shipping release documentation.
    
    
    
    

    "COULD NOT START THE ALERT CONVERTER BECAUSE, AMS.NLM IS NOT LOADED."

    
       Either AMS.NLM is truly not loaded, or the WIN.INI [Core Services]
    
       section is pointing to the wrong file server. If the latter, change the
    
       ClientDomain=FILESERVERNAME to the core file server. Then Alert
    
       Converter will launch successfully.
    
    
    
    

    "CANNOT SEND EVENTS OR READ EVENT LOG TO/FROM LANDESK CORE SERVER BECAUSE: AMS.NLM IS NOT LOADED."

    
       Error message:
    
       "Cannot send Events or Read Event Log to/from LANDesk Core Server
    
       because: AMS.NLM is not loaded."
    
    
    
       Description:
    
       Traffic Monitor or another LANDesk(R) Mangement Suite application tried
    
       to load while either the AMS.NLM is truly not loaded, or the WIN.INI
    
       [Core Services] section is pointing to the wrong file server. 
    
    
    
       Solution:
    
       In this case, change the WIN.INI line ClientDomain=FILESERVERNAME to the
    
       core file server. Then Traffic Monitor, etc., will launch without first
    
       displaying this error message.
    
    
    
    

    EVENT MANAGER DOES NOT SHOW ALL EVENTS FOR ALL UTILITIES

    
       In LANDesk(R) Management Suite v2.x, if you open MANAGE | EVENTS from
    
       the Management Console, before opening and configuring other LANDesk
    
    
    
       Utilities, you will see some of the events, but not all of them.
    
    
    
       To make events appear in the MANAGE | EVENTS window, run the various
    
       LANDesk utilites.  When a utility is run, it registers its events with
    
       the Event Manager.  This only needs to be done once.
    
    
    
    

    SET UP TO WRITE ALERTS TO A FILE BUT THE FILE DOES NOT GET UPDATED

    
       LANDesk(R) Management Suite v 2.01x
    
    
    
       Symptom:
    
       Alert Management System is set up to write alerts to a file but the file
    
       does not get updated.
    
    
    
       Solution:
    
       The path to the file defined in the configuration must exist on the
    
       workstation that executes this task.  If the you choose the append
    
       option, the file will be created if it does not exist and appended to
    
       thereafter.
    
    
    
    

    SNMP TRAP FUNCTION FAILS

    
       LANDesk(R) Management Suite v2.01x
    
    
    
       Symptom:
    
       The SNMP trap function in Alert Management System fails.
    
    
    
       Solution:
    
       If the SNMP trap fails to execute, make sure that AMSAPI.NLM is loaded
    
       with the exec option. (At the NetWare* prompt type, "load amsapi exec").
    
    
    
       If the alert fails to show up in the log file, make sure you have
    
       compiled in the LANDesk MIBS located in the network landesk\snmpmibs
    
       directory.
    
    
    
    

    GPF IN FAXABILITY WHEN SENDING ALERT TO FAX

    
       Symptom:
    
       Windows* General Protection Fault occurs in FAXability software when
    
       attempting to send LANDesk(R) Management Suite (v2.01x) alert to fax.
    
    
    
       Solution:
    
       For the task of forwarding the AMS alert to FAXability to function
    
       properly, you must have the FAXability software loaded on your system. 
    
       GPFs have been known to occur if you do not load the FAXability TSRs
    
       before starting Windows.
    
    
    
    

    "RUN NLM" OPTION DOES NOT FUNCTION

    
       LANDesk(R) Management Suite v 2.01x
    
    
    
       Symptom:
    
       The "RUN NLM" option in Alert Management System does not function.
    
    
    
       Solution:
    
       If this tool fails to execute, make sure that AMSAPI.NLM is loaded with
    
    
    
       the exec option.  (At the NetWare* prompt type, "load amsapi exec").
    
    
    
       Also, check that the NLM is located on the server trying to execute the
    
       task.
    
    
    
    

    UNABLE TO EXECUTE PROGRAMS VIA ALERT MANAGEMENT SYSTEM

    
       LANDesk(R) Management Suite v2.01x
    
    
    
       Symptom:
    
       Unable to execute programs via Alert Management System.
    
    
    
       Solution:
    
       The path to the executable defined in the configuration must be
    
       locatable from the workstation that executes the task.
    
    
    
    

    CANNOT PRINT TO A NON-WINDOWS* DEFAULT PRINTER

    
       LANDesk(R) Management Suite v2.01x
    
    
    
       Symptom
    
       Cannot print to a non-Windows* default printer.
    
    
    
       Description:
    
       Alert Management System only prints to the default printer defined in
    
       Windows Print Manager.
    
    
    
       Solution:
    
       None at this time.
    
    
    
    

    SUPPORTED MODEMS DO NOT SHOW UP IN THE MODEM INSTALLATION LIST

    
       LANDesk(R) Management Suite v2.01x
    
    
    
       Symptom:
    
       Supported modems, under Alert Management System Pager\Beeper functions, 
    
       do not show up in the Modem installation list.
    
    
    
       Solution:
    
       Delete the Windows\WAPI.INI file and copy the WAPI.INI file from the
    
       Network SYS:\LANDESK directory to the workstations \Windows directory.
    
    
    
       or
    
    
    
       Change the path information in the Windows\WAPI.INI file by modifying
    
       the entries in the [Directories] section to point to the Network LANDESK
    
       directory. 
    
    
    
    

    CANNOT GET THE EVENTS TO SEND TO NETWARE* MHS

    
       LANDesk(R) Management Suite v2.01x
    
    
    
       Symptom:
    
       Cannot get the events to send  to NetWare* MHS.
    
    
    
       Description:
    
    
    
       Generally a setup configuration issue.
    
    
    
       Solution:
    
       By default, the "Location of MHS Directory" field is filled in with the
    
       path set in the MV environment variable.  If this variable is not set,
    
       you need to fill this field in with the directory where MHS can be found
    
       (the directory where the mail\snd subdirectories are located).  For
    
       example:
    
    
    
          \\ServerName\SYS\MAILAPPS\MHS
    
    
    
       This directory must be locatable from the workstation in order to
    
       complete the MHS configuration.
    
    
    
       The "To" field will accept either SMF long or short names.
    
    
    
    

    CANNOT GET THE ALERTS TO SEND TO MS/MAIL

    
       LANDesk(R) Management Suite v2.01x
    
    
    
       Symptom:
    
       Cannot get the alerts to send to MS/MAIL.
    
    
    
       Description:
    
       Generally a configuration issue.
    
    
    
       Solution:
    
       In MS/MAIL:
    
    
    
         *  Make sure that the  "From" field is filled in with the same name as
    
             the "Mailbox Name" field on the Login screen.
    
    
    
    

    CC:MAIL MESSAGE CAN'T BE SENT

    
       LANDesk(R) Management Suite v2.01x
    
    
    
       Symptom:
    
       Configured the events to send out a cc:Mail message, but message is
    
       never sent.
    
    
    
       Description:
    
       This is probably due to the configuration setup for cc:Mail.
    
    
    
       Solution:
    
       In cc:Mail make sure that:
    
    
    
         *  cc:Mail is active on the Management console or node sending
    
            (running ALCONV) the alert to the server.
    
    
    
         *  The password has been typed in correctly on the "Login" screen.
    
    
    
       Note: The name specified in the "To:" field may need to be in a
    
       different format.  For example, instead of entering "Doe, John", try
    
       entering "John Doe". 
    
    
    
    

    VPWIN SAYS THAT THE CORE NLMS AREN'T LOADED AND AMS CAN'T INITIALIZE

    
       LANDesk(R) Mangement Suite v2.01x
    
    
    
       Symptom:
    
       VPWIN  says that the core NLMs aren't loaded and Alert Management System
    
       can't initialize.
    
    
    
       Description:
    
       This problem will appear with a message similar to "Cannot start
    
       [Application] because the core NLMs are not loaded on [SERVER NAME]". 
    
    
    
       Solution:
    
    
    
         1. Verify that the NLMS are actually loaded on the core server.
    
    
    
         2. Verify that the installation is correct. The [CoreServices] section
    
            in the win.ini file on the workstation contains two important
    
            pieces of information:
    
    
    
           ClientDomain=<The name of the AMS core server>
    
    
    
           ClientName=<The name of this service executor workstation>
    
    
    
         Make sure that the name specified in ClientDomain corresponds to the
    
            correct core server.
    
    
    
         3. If the Windows* console and server are on different networks,
    
            verify that SAP 102 packets can cross the router.
    
    
    
         4. Unload all NLMs and reload them manually taking care to note any
    
            error messages which appear when a particular NLM is loaded.
    
    
    
         5. If there are problems with AMS database initialization try loading
    
            AMS.NLM with the newdb option:
    
    
    
           load ams newdb
    
    
    
         This will create a new database if the database has become corrupted.
    
    
    
         6. If there are still problems creating the database it could be that
    
            the btreive environment is insufficient or that BTRIEVE.NLM or
    
            CLIB.NLM are the wrong version (This is commonly the case with
    
            NetWare* 3.11).
    
    
    
       Note: For information on what to do about the btrieve* environment see
    
       the LANDesk Management Suite install or LANDesk Management Suite Scoop
    
       btreive information.
    
    
    
         7. If the NLMs have loaded without error and all of the other
    
            installation information is correct then further diagnosis is
    
            necessary to determine the problem.  CORETEST.EXE was developed to
    
            help diagnose LANDesk Management Suite client server communications
    
            and may give information which can help to determine the problem.
    
    
    
    

    MANAGED SERVER CAN'T COMMUNICATE WITH THE CORE SERVER

    
       LANDesk(R) Management Suite v2.01x
    
    
    
       Symptom:
    
       A managed server does not seem to be communicating with the correct core
    
       server.
    
    
    
       Solution:
    
       If you experience these problems with a managed server, check the
    
       CONMAN.INI file to make sure that the name specified in ClientDomain
    
       corresponds to the core server. The CONMAN.INI file in the SYS:SYSTEM
    
       directory contains two of the following:
    
    
    
         [CoreServices]
    
    
    
         ClientDomain=<The name of the AMS core server that I get services
    
            from>
    
    
    
         DomainName=<The server name if this server is a core server>
    
    
    
         ClientName=<The server name if this server is a managed server>
    
    
    
       Both core servers and managed servers must have a ClientDomain that
    
       corresponds to a core server.
    
    
    
       DomainName and ClientName are mutually exclusive: each server is either
    
       a core server or a managed server and has only a DomainName or a
    
       ClientName, not both.
    
    
    
    

    AMS.NLM WON'T LOAD

    
       Symptom:
    
       AMS.NLM won't load
    
    
    
       Description
    
       LANDesk(R) Management Suite v2.01x requires Btrieve* version 6.1 or
    
       higher and CLIB 3.12g or higher.
    
    
    
       Solution:
    
       Check the [CoreServices] section of the WIN.INI and CONMAN.INI files. 
    
       If you determine that these files contain correct information and you
    
       are running NetWare* 3.11 you should check for correct versions of 
    
       BTRIEVE.NLM and CLIB.NLM.  
    
    
    
    

    LOG NO LONGER DISPLAYS ANY LOG ENTRIES

    
       LANDesk(R) Management Suite v2.01x
    
    
    
       Symptom:
    
       The log no longer displays any log entries
    
    
    
       Description:
    
       If the transport fails, the log will no longer be updated properly.
    
    
    
       Solution:
    
       To restore the log, close all LANDesk applications including the Alert
    
    
    
       Converter and restart Management Console.  This should cause the log to
    
       correctly display log entries.
    
    
    
    

    JOBS ARE NOT BEING EXECUTED

    
       LANDesk(R) Management Suite v2.01x
    
    
    
       Symptom:
    
       Jobs that are supposed to execute on a workstation are not being
    
       executed.
    
    
    
       Solution:
    
    
    
         1. Go to the manage events dialog and select an event that is mapped
    
            to a Tool configuration whose primary service field is set to the
    
            correct workstation (you can verify this by looking in the advanced
    
            dialog of the Tool Configuration).  Check to see if the service
    
            executor is online. Service executors which have an exclamation
    
            ("!") mark at the end of their name are currently registered as
    
            service executors.
    
    
    
          2.Select the test button.  If the job executes, that indicates that
    
            the system is in a fairly normal state and that there may be a
    
            problem with the Tool configuration. 
    
    
    
          3.If you determine that the workstation that should be executing jobs
    
            is running but not registered as a service executor (it doesn't
    
            have a "!" next to its name), make sure that alert converter is
    
            running on that workstation and that the service executor option
    
            has been selected.  If alert converter has been closed, the
    
            workstation will no longer be registered as service executor since
    
            it registers the workstation as a service executor.
    
    
    
         4. If the workstation is registered as a service executor and jobs are
    
            still not being executed, it is likely that there is a transport
    
            problem which may be cured by closing all LANDesk applications and
    
            relaunching alert converter.
    
    
    
    

    "PLAY A WAVE FILE" DOES NOT PLAY THE SPECIFIED SOUND

    
       Symptom:
    
       The option, "Play a wave file associated with a system sound" does not
    
       play the sound associated with that particular action as specified in
    
       the system.ini
    
    
    
       Description:
    
       The "Play a Wave File" option in LANDesk(R) Management Suite v2.01x
    
       requires that the path defined there be the same as the path on the
    
       workstation where this tool executes.
    
    
    
       Solution:
    
       Make sure the full, correct path is specified.
    
    
    
    

    CHANGING THE CLIENTNAME IN THE WIN.INI FILE

    
       LANDesk(R) Management Suite v2.01x
    
    
    
       When Alert Management System is installed, it creates a unique name
    
       (MACHINEXXXXXX) for each console that specifies the service executor
    
       name for the workstation.  This is the name that appears in the primary
    
       execution location field in the Tool configuration advanced dialog. When
    
       this name is assigned by AMS, often the only way to determine the name
    
       of the workstation on which you are configuring the service is the added
    
       text (This Workstation).
    
    
    
       If you would like a more recognizable name, you can change the
    
       ClientName to something more descriptive and easier to distinguish from
    
       other service executors.  Be aware that any Tools configured with the
    
       old workstation name will still have their primary service location set
    
       to the name of the old service executor workstation.
    
    
    
       Since the secondary service location is set to Any by default, these
    
       jobs will likely still execute.  If  the Tool needs to be configured for
    
       a specific service executor that you have renamed, you should change the
    
       primary service execution location to correspond with the new name you
    
       assigned in the WIN.INI file. 
    
    
    
    

    DETERMINING WHICH BROADCAST OPTION TO USE

    
       The following Broadcast options are available in LANDesk(R) Management
    
       Suite v2.01x:
    
    
    
       Send to User on Server:
    
       This option configures messages to be broadcast to 3.x users, or users
    
       using bindery emulation.
    
    
    
       Select User from NDSTree
    
       This option is for directory services users.  In order for this option
    
       to be enabled, the user must be logged in to a directory services tree. 
    
       The user can then browse the treee to select the person he wishes to
    
       broadcast the message to.
    
    
    
    

    CONMAN.NLM CANNOT ESTABLISH A CONNECTION FROM A CONSOLE WORKSTATION TO A CORESERVER

    
       LANDesk(R) Management Suite v2.01x
    
    
    
       Symptom
    
       CONMAN cannot establish a connection from a console workstation to a
    
       core server if the console workstation is using NETX.EXE with token ring
    
       drivers.
    
    
    
       Solution
    
       Use the current release of VLMs available on Netwire/CompuServe. Make
    
       sure to only upgrade drivers in a complete set (ie:VLMUPx.EXE,
    
       WINDRx.EXE & NWDLLx.EXE, where x is the same number for all 3 files).
    
    
    
    

    CONNECTIONS MAY BE LOST ON CONMAN RUNNING IN A NETWARE* 4.X ENVIRONMENT

    
       LANDesk(R) Management Suite v2.01x
    
    
    
       Symptom 
    
    
    
       Connections may be lost on CONMAN running in a NetWare* 4.x environment.
    
    
    
       Description
    
       The thread scheduling algorithm employed in NetWare 4.x may allow
    
       starvation of low priority threads (basically anything which uses
    
       CLIB.NLM) in favor of high priority threads.  As a result, connections 
    
       may be lost on CONMAN from time to time.
    
    
    
       Solution
    
       Add "Set Upgrade Low Priority Threads = On" anywhere within the 
    
       AUTOEXEC.NCF file.
    
    

    Trademark information