Conference abbott::teamlinks_windows

    The customer sent me the following message.  I still need assistance
    on this issue.
    
    When using Rich Text as the editor and sending the message he gets
    the following error.
    
    
        An error was encountered while creating or saving this mail message
        on the server.
        DOS file cannot be opened.
        The DOS file name is invalid, does not exist, or access to the file
        is not permitted, or the file is in use (locked) by other application.
        This operation will be cancelled.
    
    
    Any ideas,
    
    Beth
    

Hi Beth,


>    We are running TeamLinks 2.7, ALL-IN-1 3.2, and connecting via TCP/IP
>    (UCX).  One, and only one, of our clients is receiving the following
>    error message when trying to send a plain text mail message in 

Q1) Did this client previously contain an earlier version of TeamLinks 
which was functioning properly?

Q2) If another person uses this client, connect to their cabinet and 
attempt to send a mail message, do they get the same results?

Q3) Have you tried removing TeamLinks completely from the PC and then 
reinstalling?

Q4) What is running on the PC, Windows 96, WFW...etc?

> TeamLinks:
>    
>        An error was encountered while saving this message.
>    
>        This operation will be aborted.
>    
>    Upon trying to exit TeamLinks, he is asked if he wants to save the
>    message.  If he clicks the "Yes" button, the same message is
>    displayed.

Q5) What is the setting in "Setup | Mail Profile | Send Options | Place 
Sent Copies In:" field(s)?

Q6) What happens if the user, rather than actually sending the created 
message, simply saves it to the "Created" folder?

Q7) What happens if the user "forwards" and/or "replys" to a message?

Thanks
Joe

    Joe,
    
    I will answer as many of these as I can and get the other answers
    from this customer.
    
    Q1) Did this client previously contain an earlier version of TeamLinks
    which was functioning properly?
    
    **Not sure I will check.
    
    Q2) If another person uses this client, connect to their cabinet and
    attempt to send a mail message, do they get the same results?
    
    **Another user gets the same error when connecting to their account
    **from this PC.  This user's account works fine with logged in
    **from another PC.
    
    3) Have you tried removing TeamLinks completely from the PC and then
    reinstalling?
    
    **I thought it had been removed and reinstalled but in reading back
    **over this call it has just been reinstalled.  I will check to see
    **if removing it occurred.
    
    Q4) What is running on the PC, Windows 96, WFW...etc?
    
    **Windows 95
    
    Q5) What is the setting in "Setup | Mail Profile | Send Options | Place
    Sent Copies In:" field(s)?
    
    **Since this is IOS place sent copies is set to OUTBOX
    
    Q6) What happens if the user, rather than actually sending the created
    message, simply saves it to the "Created" folder?
    
    **Saving gives him the same error.  I had them also try setting
    **TL to offline mode and sending and the the same error occurred
    
    Q7) What happens if the user "forwards" and/or "replys" to a message?
    
    **Don't know I will have them try this.
    
    Thanks,  I will be getting back with you.
    
    Beth
    

    Joe,
    
    I just received this from the customer.
    
    
    
        Q1) Did this client previously contain an earlier version of
    TeamLinks which was functioning properly?
    
        No
    
        Q2) If another person uses this client, connect to their cabinet
    and attempt to send a mail message, do they get the same results?
    
        Another user gets the same error when connecting to their account
        from this PC.  This user's account works fine with logged in
        from another PC.
    
        3) Have you tried removing TeamLinks completely from the PC and
    then reinstalling?
    
        Yes.  Let me say that by removing, I did the following:  I deleted
    the C:\TEAMLINK directory and the TeamLinks Program Group.  I also
    deleted from the C:\WINDOWS directory OFFICE.INI and TL*.*.  It was after
    these deletions that I re-installed.
    
        Q4) What is running on the PC, Windows 96, WFW...etc?
    
        Windows 95
    
        Q5) What is the setting in "Setup | Mail Profile | Send Options |
    Place Sent Copies In:" field(s)?
    
        Since this is IOS place sent copies is set to OUTBOX - Also isn't
    this an account Profile setting?  When I check this on his machine, I
    see my information.  See question and answer 2.
    
        Q6) What happens if the user, rather than actually sending the
    created message, simply saves it to the "Created" folder?
    
        Saving gives him the same error.  I had them also try setting
        TL to offline mode and sending and the the same error occurred
    
        Q7) What happens if the user "forwards" and/or "replys" to a
    message?
    
        I get the same message.

    We finally have the answer to this problem.  As a matter of fact
    this problem has happened twice in the last two weeks.
    
    When creating a mail message and sending it with a Rich Text format
    the following error is being returned
    
            An error was encountered while creating or saving this mail
            message on the server.
            DOS file cannot be opened.
            The DOS file name is invalid, does not exist, or access to the
            file is not permitted, or the file is in use (locked) by other
            application.
    
            This operation will be cancelled
    
    
    On one site that was getting this message, the problem was the file
    C:\WINDOWS\SYSTEM\TX_RTF.DLL had a size of 35,070 and the version when
    checking properties was not the same version as the one that ships
    with TeamLinks.  (I don't remember the version of the 35,070 file).
    Once the file TX_RTF.DLL (size 30,800) that ships was TeamLinks was
    placed in the C:\WINDOWS\SYSTEM directory all worked fine.
    
    The second site sent me a directory listing of the TX*.* files in
    their WINDOWS\SYSTEM directory.  Below was the information they sent:
    
    
        TX_BMP.FLT           8KB    11/01/95 01:10am
        TX_TIFF.FLT         17KB    11/01/95 02:32am
        TX_WWF.FLT           5KB    01/31/95 01:02am
        TX4VBB.VBX          47KB    03/15/95 12:00am
        TX4VBC.VBX          60KB    02/09/96 04:04pm
    
    I sent a list of the following files that should be in that directory:
    
    TX_WMF.FLT       5,056  3-15-95
    TX_BMP.FLT       7,648  3-15-95
    TX_TIFF.FLT     16,752  3-15-95
    TX_RTF.DLL      30,800  3-15-95
    TXTOOLS.DLL     39,488  3-15-95
    TX4VBB.VBX      47,328  3-15-95
    TXB.DLL         152,048 3-15-95
    
    Once the files that ship with TeamLinks were copied to WINDOWS\SYSTEM
    they could also send messages.
    
    Neither site was sure what would have been installed that gave
    different versions of these files.
    
    Beth 

Excellent!

Jerry

    Another site just reported having problems and they have
    found that after installing a produce called ProSite
    the TX_RTF.DLL file is updated and TeamLinks no longer works.
    If the TX_RTF.DLL file that is shipped with TeamLinks is
    reinstalled then TeamLinks works but ProSite does not.
    
    I'm not sure if there are other applications that ship
    this file.
    
    Beth
     

I forwarded your note to Karen. We'll see if there's
anyway we can get this worked out.

Thanks.

    Here is some additional information from the customer on the versions
    of the TX* files that are shipped with TeamLinks and ProCite.
    
    You must be looking at the "Product version" rather than the "File
    version".  It is the "file versions" that I was looking at.  At any
    rate, here is how the numbers break down:
    
    File versions:
                Team Links       ProCite
    Tx_rtf.dll    1.1              1.21
    Txb.dll       4.11             4.40.503
    Txtools.dll   1.08             1.1
    Wndtools.dll  1.00             1.03
    
    Product versions:
                 Team Links      ProCite
    Tx_rtf.dll    4.1              3.0
    Txb.dll       4.1              3.0
    Txtools.dll   4.1              4.3
    Wndtools.dll  1.0              1.03
    
    
    Any additional information I could give this customer would be helpful.
    
    Thanks,
    
    Beth
    

I forwarded your note to Karen Chiasson.


Jerry

    I have a customer that is experiencing the same problem using
    TLV3.0 EFT2.  Is this issue going to be resolved or shall I report
    as a future enhancement.
    
    Thanks
    AL
    Teamlinks

Forwarded your note to Karen.