Conference abbott::teamlinks_windows

    Rick,
    
    A couple of things that would help us to help you...
    
    1. Operating system and version.
    2. OFFICE.INI contents
    3. Date/time of MAPI*.DLL in the SYSTEM and/or SYSTEM32 subdirectories
       of your Windows directory.
    
    Does the Microsoft Exchange client work? If you use TLSETUP to select
    not to connect to the Exchange file cabinet in TeamLinks do the other
    cabinets work?
    
    My knee jerk reaction is that it's a clash between the TeamLinks Simple
    MAPI DLLs and the new TeamLinks service provider for Exchange
    (CFCMAPI). You can't install both of these at the same time. This is in
    the release notes and I would have expected the installation procedure
    to stop you from doing this, but maybe it doesn't.
    
    Installing TeamLinks Simple MAPI overwrites the MAPI DLLs previously
    installed with the Exchange client with ones which only support Simple
    MAPI. This prevents extended MAPI clients such as the Microsoft
    Exchange client and TeamLinks CFCMAPI from working.
    
    Joe.
    

    Rick,
    
    Since you're in a hurry, I'll assume that .1 is the correct diagnosis
    of your problem. The best way to confirm this is to see if the
    Microsoft Exchange client works and connects to the server properly. If
    not, then .1 is almost certainly the problem. In that case, here are
    your options.
    
    If you want to use TeamLinks Simple MAPI then you can't connect to an
    Exchange server at the same time so remove the Exchange file cabinet
    from the list of selected file cabinets in TeamLinks Setup.
                                                            
    If you want to connect to an Exchange file cabinet then you can't use
    TeamLinks Simple MAPI at the same time so you'll have to remove it.
    Probably the best way to do this is to reinstall the Microsoft Exchange
    client. This should overwrite the TeamLinks MAPI DLLs in your Windows
    directory.
    
    Joe.

Use Drwatson.exe if you can to create a log of the crash.

I've seen this sort of thing pre-eft1 where 32bit windows calls were attempted
on a Windows 3.1 system.

    re: .1
    
    > 1. Operating system and version.
    > 2. OFFICE.INI contents
    > 3. Date/time of MAPI*.DLL in the SYSTEM and/or SYSTEM32
    > subdirectories of your Windows directory.
    >    
    >  Does the Microsoft Exchange client work? If you use TLSETUP to
    > select not to connect to the Exchange file cabinet in TeamLinks do the
    > other cabinets work?
    
    Joe,
    
    Just for the record this is a Windows 95 system with Service Pack 1
    applied.  I won't post the OFFICE.INI contents - just too boring - AND
    long!
    
    You were right on with your assessment that this was the MAPI*.DLL
    files.  I checked in \WINDOWS\SYSTEM and found that MAPI.DLL was 102KB
    dated 2/18/97 @12:00AM.  MAPI32.DLL was 24KB and dated 1/14/97 @
    12:00AM.
    
    I attempted to launch Both Exchange and Outlook clients without
    success!
    
    Apparently the TLV3-EFT1 install had retained the previously installed
    DLL as .OLD, so I renamed the MAPI.DLL to MAPI.TL3 and the MAPI32.DLL
    file to MAPI32.TL3.  I then renamed the MAPI.OLD file to MAPI.DLL and
    the MAPI32.OLD file to MAPI32.DLL.
    
    I attempted to launch Exchange and it worked.  I shut it down and
    launched Outlook and it worked!  
    
    I now have to share that the problem exacerbated on Saturday when I
    attempted to launch WinFax Pro only to be advised that there was a
    fatal error in the main program there as a result of an error in
    OLE32.DLL.  I also had a problem in another program which utilizes
    OLE32.DLL just as a proof point.  So the acid test was to attempt to
    launch WinFAx Pro - that worked!
    
    So I figured it's time to get into TL V3.  I launched the app and the
    hourglass spins for five minutes (but I was asked about my Exchange
    account and I did provide connect information).  So I did the 3-finger
    salute and found that MAPISP32 (this is an I THINK, because I did not
    write the name of the app down, but this is what I recall) was Not
    Responding.  I did and "End Task" and my ALL-IN-1 drawers and Exchange
    drawers are now visible in the Information Manager window.
    
    I've checked my MAIN ALL-IN-1 drawer and looked and the INBOX.  I've
    checked the Exchange drawer and I can see things there.
    
    The only thing I would like to "fix" at this point is the attempted
    launch on "MAPISP32".  Any thoughts on that would be appreciated.  I
    presume I could do a reinstall of TL V3-EFT1 and that ould resolve the
    problem, but I know you folks like challenges and might have a more
    simplistic cure.
    
    So, I believe I'm back in business!  Joe, I really appreciate your
    assistance!  I don't believe we've met yet, and for goodness sake don't
    ask Nigel Dutt about me!  Check with me 1st on anything he might say
    about me.
    
    re: .3
    
    Carson,
    
    Really good to hear from you.  I believe we're beyond Dr. Watson at
    this point.  Good to hear from you!
    
    TO ALL:
    
    I am concerned that the TeamLinks V3 EFT1 install is not looking to
    determine if Exchange/Outlook is installed and not allowing the
    installation of DLLs that can cause problems.  Perhaps this requires
    dialog boxes during the installation or some additiona sophistication
    to prevent a further occurrance of my problems.
    
    THANKS!!
    
    Rick

    I neglected to mention that my reply in .4 was delayed by a two day
    Business Review meeting and a total lack of connectivity into ALF. 
    Sorry for the delay!
    
    The previous reply was produced in real time so the reolsution is
    effective as of the time stamp in .4.
    
    THANKS!!
    
    Rick

Yes, the issues of needing Exchange in the first place and
not installing simple MAPI (perhaps even detecting that the
simple MAPI that's there is ours already) all need to be
resolved before we ship.

We went to EFT1 with these restrictions and documented them
in the README as best we could.

Jerry

.0>    I couldn't find a note for problems with V3 so I thought it best to
  >  start one.

Please use separate topics for separate V3 EFT problems.  It'll be easier
to keep track of the problems that way (and easier for others to find 
information on them).

Thanks.

-- Nina, with moderator hat on

    re: .6
    
    Hi Jerry!
    
    Yes, I did review the README in detail prior to the install.  I don't
    know why I was possessed to turn on the check-box for MAPI and ODMA
    when I did the install.  I guess it's just the devil that's in me from
    having done beta testing for the last 15 years.
    
    I did realize that that was the source of the problem the instant I
    read Joe's note.  Hopefully others will see this thread and not make
    the same mistake.
    
    THANKS!!
    
    Rick