Conference pcbuoa::server_works

    This has not happened on any of our Intel platforms. Could you please
    note on which platform this is happening and what <path> is on Intel
    or Alpha server and the remaining part of the "some other stuff".
    It may be helpful in resolving it.

    Rich,
    
    Let's separate this into two scenarios - mine and the customer's. They
    are similar but different errors.
    
    My config:
    	Prioris 5100 MP server - NT 4.0 SP2 - SW Agent installed
    	DecPC LPX 566 - NT 4.0 SP1 - SW Agent installed
        DecPC Axp 150 (Jensen) - SW Console with ManageWORKS
    
    Customer's config - Alpha with NT agent - not sure of the model - I'll
    	find out and post it here.
    
    Customer's problem:
    
    1. On boot, the error that it can't load decssm.sys occurs - I will get
    the entire message and post it.
    
    2. Went into Manageworks and got a GPF on module swextomm.dll - had him
    look in the .ini for the problem with the path pointing to the F: drive
    but he only had two lines in the swextomm.ini. He's going to reinstall.
    
    My problem:
    	Install the agent - starts without errors. Reboot and get the
    general error on boot saying a system service didn't start.  The text
    version of the Event Viewer log is included below.
    
    Tried this over and over - very predictable - reinstall the agent,
    errors go away. Reboot and they occur.
    
    
    Event log: (removed unimportant stuff - Browser, Logon, etc.)
      ALSO - I flagged one error reporting ServerWORKS drivers failing to
    load (or so it appears).
    
    ------------------------------------------------------------------------
    2/24/97 3:18:40 PM      ServerSystemAgent       Error   None    2003   N/A
    HXONFIRE      The Digital Server System extension agent failed to 
    initialize. %1
    
    2/24/97 3:18:39 PM      HostResourcesAgent      Information     None   
    3002 N/A   
    HXONFIRE        The Host Resources extension agent was
    successfully initialized.
    
    ***** THE FOLLOWING ERROR SEEMS TO BE SIGNIFICANT  ****************
    
    2/24/97 3:18:39 PM      ServerSystemAgent       Error   None    2010   N/A
     HXONFIRE      A required device driver is missing: SWLLDRV or SWOLDDRV
    or SWLLIND or SWLLSKA
    
    
    2/24/97 3:18:39 PM      SNMP    Information     None    1001    N/A    
    HXONFIRE      The SNMP Service has started successfully.
    
    2/24/97 3:18:37 PM      NTClusterAgent  Information     None    2002   N/A
    HXONFIRE      The Digital Cluster Management Extension Agent has 
    successfully initialized.
    
    2/24/97 3:18:37 PM      ServerManagementAgent   Information     None   
    2002 N/A   HXONFIRE        The Digital Server Management Extension Agent
    has successfully initialized.
    
    2/24/97 3:18:36 PM      Service Control Manager Error   None    7000   N/A
     HXONFIRE      The Steam service failed to start due to the following
    error: The filename, directory name, or volume label syntax is incorrect.
    
    2/24/97 3:17:33 PM      EventLog        Information     None    6005   N/A
     HXONFIRE      The Event log service was started.
     
    =======================================================================
    
    Thanks,
    
    Gary

    
    
    
    
    
    
    
    
    
    
    
    
    
    Looks like these are two different issues.
    
    I just talked to the customer - we reinstalled Serverworks cleanly and
    the decssm.sys error went away, however he still got the GPF in
    swextomm.dll. Swextomm.ini again only had 2 lines in it.
    
    We ran the Management Module setup and removed the ServerWORKS module
    and the error disappeared (predictably). Put it back in and the error
    appeared (sanity check). With that module out, however he gets a
    winsock error loading the event dispatcher.
    
    He was able to run ip autodiscovery, set alarms, etc.
    
    QUESTIONS:
    
    1. Any ideas on the error on the Agent machine with NT 4.0 (re: .2)?
    
    2. The Swextomm.dll error seems to be a bug but I assume unless you
    have one of those infamous 3rd party apps to hook into ServerWORKS, it
    won't hurt not to have it. True?
    
    3. Why does the swextomm.ini file only have 2 lines?
    
    4. Have you seen this winsock error before? Could it be a winsock 1 vs
    winsock 2 problem on NT 4.0?
    
    Thanks for all the help,
    
    Gary

    The Agent message that the SWOLDDRV etc Driver is missing has a patched
    fix which you can get from \\jules\public \ntagents\v1.4fix\x86.
    The remainder we'll be looking into.

    If you get the decssm problem would you also attempt to do a 
       "net start decssm" on the command prompt and see what error
    it reports.
    
    Thanks,
    
    Rich
    

    this is in the notes file.
    
    the 3rd party extension omm,  was given a bad bitmap file
    specification.
    The bug was in the installation.  It was found and posted in the notes
    file last december.  The extension omm file ini file had a
    f:\mworks\rcm.bmp
    as an entry, and it should not have.  It should just say rcm.bmp.
    
    

    Rich,
    
    As noted in .3, we reinstalled serverworks and manageworks and the
    decssm.sys error went away, but still get the GPF in swextomm.dll - I
    am aware of the swextomm.ini change as you noted - but the problem is
    that .ini file on his pc only has 2 lines in it - both in the section
    as rcm.bmp but not the line in question. Even after reinstall the ini
    only had two lines.
    
    We got a workaround by removing the ServerWORKS extension via Setup and 
    everything works fine.  
    
    Still seems to be a bug somewhere.
    
    Gary

       <<< Note 222.7 by ALFSS2::OLSEN_G "Hey y'all, how y'all doin'?" >>>
                   -< swextomm.dll only has 2 lines in it! >-

SWEXTOMM.DLL is a binary file, and should have lots of code in it.

SWEXTOMM.INI is the file I think you are talking about and it too has lots
of lines in it initially.  However, attempting to be safe, when the error
occured, the install is prevented from overlaying the file, as it has
a newer date.  This file has lots of information.  Turning off the
task with 3rd party will stop most of the problems.  What 3rd party
application have you integrated with?  We need to see the SWEXTomm.ini file
as it is, and need to know what you have integrated with, to fix this.

tag.

    Tag,
    
    Oops - you are right - I meant swextomm.ini - not .dll!
    
    We aren't integrating any 3rd party apps - that's why we took it out.
    Again, I was surprised it only had two lines in it - even after we
    de-installed and re-installed manageworks/serverworks.
    
    This is the entire swextomm.ini file:
    
     [KCRCM]
            ExePath=C:\[path here]\HyperTerminal\HYPERTRM.EXE\hypertrm.ex
    
    I guided him thru the install so I know that's ok. We immediately
    looked at this ini file and this is what we see.
    
    Again, the customer is happy but I think it's something we should
    figure out for next time...
    
    Any ideas?
    
    Gary

    Rich,
    
    re: .4:
        The Agent message that the SWOLDDRV etc Driver is missing has a
        patched fix which you can get from \\jules\public \ntagents\v1.4fix\x86.
        
    I have another customer getting this error but I can't connect to Jules
    for some reason (have done in the past). Could you e-mail them to me
    or give me a VMS pointer so I can copy them and get them to this
    customer?
    
    Question - I built a diskette with the NT driver for this customer. I
    installed it on 4 NT machines - went smoothly. I zipped it up and sent
    it to him. He installs it on one machine and gets this error.  Why?
    
    Why does it install on some machines and fails on others?
    
    Thanks,
    
    Gary
    
    

    If I recall, the Drivers will unload if they are not on the proper
    platform and the install script checks to determine if the driver stuck
    before finalizing the registry entries. However, he could be making the
    check before the load of the driver got started on fast systems. 
    Since we did most of our installs over the network it always worked.
    
    Rich