Conference ucrow::desktop_acms

852.0. "Decnet links not deleted." by TAV02::GODOVNIK (Haim Godovnik) Wed May 07 1997 05:52

Hi,

A customer has a problem with his application running acms desktop 2.2 on
Windows 95 using Decnet (pathworks). I succeeded to reproduce his problem
with the AVERTZ sample application on my PC. The problem occurs only with
the application that is running with DLL's.
I have opened a new seesion from the AVERTZ menu then tried to create a
reservation and then closed the session. After that I opened a new session
and closed it. The errors from sign out You can see in the attached ACMSDI LOG.

Also attached are the dir output of the files of the Avertz application and
DLL's in use.


The problem we have is that the DECNET links remain Running and run out of
links and cannot make more connections to the application on VAX.


Regards,

Haim Godovnik


===============================================================================

   Avertz Application

===============================================================================

 Volume in drive C has no label
 Volume Serial Number is 3A21-16D3
 Directory of C:\av2

.              <DIR>        07-05-97   8:46 .
..             <DIR>        07-05-97   8:46 ..
AVERTZ   DEF         1,527  06-11-92   4:15 AVERTZ.DEF
AVERTZ               4,561  05-11-92  11:41 AVERTZ
AVERTZ   EXE        70,144  07-04-94  10:37 AVERTZ.EXE
         4 file(s)        150,664 bytes
         2 dir(s)      45,924,352 bytes free


===============================================================================

   ACMSDI DLL's

===============================================================================

 Volume in drive C has no label
 Volume Serial Number is 3A21-16D3
 Directory of C:\WINDOWS\SYSTEM
DI_CNV   DLL        13,963  11-10-95   6:33 DI_CNV.DLL
ACMSDI   DLL        74,432  18-10-95  17:07 acmsdi.dll

===============================================================================

  ACMSDI LOG

===============================================================================

ACMSDI_DISPATCH_MESSAGE: starting at Wed May 07 09:19:24 1997
  1   2   3   4   5   6   7   8   9  10  20  30 

ACMSDI_SIGN_IN: starting at Wed May 07 09:19:56 1997

ACMSDI_DISPATCH_MESSAGE: starting at Wed May 07 09:19:56 1997
  1   2   3   4   5   6   7 

ACMSDI_CALL_TASK: starting at Wed May 07 09:20:03 1997

ACMSDI_DISPATCH_MESSAGE: starting at Wed May 07 09:20:03 1997
  1   2   3   4   5   6   7   8   9  10  20 

ACMSDI_SIGN_OUT: starting at Wed May 07 09:20:26 1997

ACMSDI_DISPATCH_MESSAGE: starting at Wed May 07 09:20:27 1997
  1   2 
NET__CLIDIS: DECNET(13), DECnet error

CONNECTION_DELETE: RPC(22), Fatal internal error
  3   4   5   6   7   8   9  10  20  30  40  50  60  70  80  90 100 200 
300 

ACMSDI_SIGN_IN: starting at Wed May 07 09:27:17 1997

ACMSDI_DISPATCH_MESSAGE: starting at Wed May 07 09:27:18 1997
  1   2   3   4   5   6   7   8   9  10  20 

ACMSDI_SIGN_OUT: starting at Wed May 07 09:27:42 1997

ACMSDI_DISPATCH_MESSAGE: starting at Wed May 07 09:27:43 1997
  1   2 
NET__CLIDIS: DECNET(13), DECnet error

CONNECTION_DELETE: RPC(22), Fatal internal error
  3   4   5   6   7   8   9  10  20  30  40  50  60  70  80  90 100 200 
300 

          Haim      
    
          We have managed to reproduce the problem and have
          created a new DECnet DLL which seems to fix it.  We still
          need to do some more testing to be sure the new DLL will
          not break something else.  However, it looks promising.
    
          When we finish testing, if all goes well, we will enter
          instructions on how you can access the fix.
    
                John
                  

    John,

Thanks for Your help. Waiting for the fix.

Haim G.

    Haim,
    
    We have created three new versions of the DECnet ACMSDI.DLL
    (ACMSDIDN.DLL) which have been tested and which have been 
    shown to fix this problem.  The problem has been seen to 
    occur only when running the 16-bit DECnet DLL under Windows 95.
    
    For ACMS Desktop V2.2 this fix is the third ECO (ECO3).  See the
    README.TXT files found in UCROW::DESKTOP_ACMS$ROOT:[PUBLIC.V22.ECO1]
    and in UCROW::DESKTOP_ACMS$ROOT:[PUBLIC.V22.ECO2] for descriptions
    of the previous ECOs.
    
    For ACMS Desktop V2.3 this fix is the first ECO (ECO1).
    
    If you are running ACMS Desktop V2.2, you can choose between two
    versions of the DLL.  If you are running V2.2 with no previous ECOs 
    applied, copy the DLL from the following location:
    
         UCROW::DESKTOP_ACMS$ROOT:[PUBLIC.V22.ECO3.NO_ECOS]ACMSDIDN.DLL
    
    If you are running ACMS Desktop V2.2 with ECO1 or ECO2 applied, copy
    the DLL from the following location:
    
         UCROW::DESKTOP_ACMS$ROOT:[PUBLIC.V22.ECO3.INCL_ECOS]ACMSDIDN.DLL
    
    
    Note:  ECO2 includes ECO1. However, the fix for ECO2 by itself does not
    effect this DLL.
    
    If you are running ACMS Desktop V2.3, copy the DLL from the following
    location:
    
         UCROW::DESKTOP_ACMS$ROOT:[PUBLIC.V23.ECO1]ACMSDIDN.DLL
    
    All of the locations contain README.TXT files which you may wish to
    read.
    
    Let us know if this fixes the problem (or if it doesn't).
    
         Regards,
    
             John
    
    

John,

The customer installed the new DLL and his application works fine. The problem	
with the unclosed connections is solved!

Thank You very much for Your help.

Haim G.