Conference abbott::teamlinks_windows

What server is involved?

>  Now, they have problem on "sub or functions not define" when trying to
>  read or send mails.

Did this right away when the Read window or Create Message window
was called up?  Or when using a menu command in one of these windows?

>  Investigation shows that this happens after reading mails
>  on behalf of another users.

What do you mean by "reading mail on behalf of another user"?  Was
this after using Set Mail User?

Bob

    
Bob, thanks for replying.

>>What server is involved?

Server:
VAX Mailworks 1.3A.
VMS 5.5-2
UCX 3.2

Client:
Windows NT workstation 3.51 with service pak 3
Teamlinks Office version 2.7 

>>Did this right away when the Read window or Create Message window
>>was called up?  Or when using a menu command in one of these windows?

See Below.

>>What do you mean by "reading mail on behalf of another user"?  Was
>>this after using Set Mail User?

After activiting Teamlinks Information Manager Icon, when TL asks for
username/password, customer would first key in her own-name/password 
and continue reading mails and etc.

Next, she would get out of TL completely and re-enter it again using 
Teamlinks Infor Manager using her boss's
username/password (so as to read mails for her boss).

Having done that, when she exit TL and re-enter it again using her own
username/password, she now has problem reading mail as it encounter
'sub or function not define problem'.

Regards.
THS

You got me!  Never seen this one before.

How does she fix it?  Does re-booting Windows NT make it go away?

Bob

    Not even power off the NT and restart.
    
    Down-grading TL to 2.5 and reboot NT client will solve the problem.
    
    Do I miss anything?
    
    Regards
    THS

I don't understand why it would work once, then stop just because
another user's FC was accessed.

Perhaps there are DLLs that are duplicated on the PC.   Can you 
check for that?  We've had cases in the past where problems were
caused by Filecab.dll being on the system twice.  In that case
the one in the TL directory was the one to keep.

Does anyone else have any idea what the problem could be?

Bob

    Bob,
    
    I am not sure what the common denominator is going to be here but
    we would commonly get this error and the xs errors when the network
    connection was lost and when TeamLinks was run in a client server
    environment.  I have had several calls on this "sub or function
    not defined" error in Windows 95.  I also received the error last
    week using Aisha's PC.  She was running 2.7eco1 and I was trying to
    import a file from DOS and I received the error when importing.
    
    Debbie Giannetti 

Deb,

Which network connection was lost?  To the mail server or to the
server directory where TL's EXEs and DLLs load from?  If it's the
latter, then TL would not run.

Is it possbible that TL DLLs are installed both locally on the
PC and on the network?

Bob

    Bob,
    
    The connection that was lost was to the server directory where
    the TL's and EXE's and DLL's load from.  No it is not possible
    that the files are in both locations.  On Aisha's PC I made sure
    that no "duplicates" existed locally.
    
    Thanks,
    
    Deb

If the network connection to the EXE and DLL files goes away
while TeamLinks is running, then general confusion will occur.
This isn't specific to TeamLinks, though.

Jerry

    I talked with ONE of my "Sub or function not defined" customer's
    yesterday.  They were searching to see if they had duplicate 
    DECnet addresses causing their problem.  They did not.  He said
    they did do some tuning on the DEC MailWorks server and they seem
    to not have the error occur quite as often but it still does occur
    on occasion and they have not been able to narrow down what is going
    on.
    
    This is a hard one.  I have two open calls on this one and have not
    been able to make headway.  I also had the problem occur here when
    using Aisha's PC and doing a file import.  The server connection
    had not been lost.  I don't know what is going on.
    
    Help!  Does anyone in engineering experience this error?
    
    Debbie

Here's one case when I think you would see that:

- TeamLinks installed on the network drive.
- TeamLinks running
- connection to network drive drops
- User action causes TeamLinks makes a call to a DLL
  that was on the network drive
- And you will get "Sub or Function not defined"

So I guess one thing to rule out would be these
dropped network drives. If this error occurs, before
clicking on OK, bring up a DOS box and see if you
can do a dir of the TeamLinks directory on the
network drive.

Is that of any help?

Jerry

    ref. 1967.5,
    
    Bob, you are right, the cause of the problem was due to duplicated
    DDLs, removing them and so far no problem at all.
    
    Many thanks.
    HS

    HS,
    
    If you don't mind, what DLL's were duplicated?  I have had my customers
    look but they say they cannot find any duplications and I really would
    like to close out this issue and find the solution once and for all.
    
    Debbie Giannetti

    Debbie,
    
    Somehow, each NT workstation seems to have different duplicated DLLs from
    the other one. These duplicated DLLs are in windows/system or/and 
    windows/system/system32. But what is vital is that, these DLLs should
    only be in the /teamlink directory. If any of the DLL listed in
    /teamlink dir also appears in any other dir (eg windows/system or
    windows/system/system32), then you got to delete them.
    
    Hope it helps.
    
    Regards
    HS

    Hi,
    
    The customer determined that they had duplicate decnet addresses and
    this was causing the quirk with the IP stack.  The customer fixed the
    duplicate decnet address issue and now they are not having this
    problem.  The customer now wants to know why decnet is the issue since
    they were correcting over Ip and what DECnet had to do with TC/PIP over
    WINSOCKs.
    
    Thanks,
    
    Angela 

    Angela,
    
      This question has come up before so I'm calling someone in Pathworks
    to see if I can get an answer.  It's well below the Winsock level and
    probably has to do with an "error" packet being passed up to all
    transports on the PC, but I will try to get a definitive answer.
    
      / Peter

    Angela,
    
        The basic idea is that when the DECnet driver starts, it changes
    the ethernet "station address" of the machine.  This is the logical
    address of the machine on the ethernet and is established by a protocol
    called ARP (Address Resolution Protocol).
    
        I don't understand exactly what happens after that.  Normally the
    DECnet transport starts first and after changing the station address to
    a unique number based upon the DECnet-Area.DECnet-Node, transports
    which start after that simply use the new station address and there
    are no problems.  I assume the problem is that a duplicate DECnet
    address essentially gives a duplicate TCP/IP address which then
    causes problems for TCP/IP.
    
      / Peter

    Hi,
    
    Thanks,
    
    Angela