Conference abbott::teamlinks_windows

    Has anybody been assigned to look at this problem? 
    
    Any suggestions for further diagnosis gratefully received.
    
    Thanks,
    
    Brian

    Another site has reported the GPF in MSOLE2.VBX when exiting
    Teamlinks. 
    
    There are 2 PCs running TL 2.7, WFW.  He thinks both have Pathworks
    installed but is not completely sure.  He is also not sure of the
    version of Pathworks.
    
    This GPF is showing up more and more.  Any further ideas what might
    be causing it.
    
    Beth
    

Someone has recently been assigned to this problem.

Dave

Can this problem be reproduced on the problem PCs as follows:

- Remove all apps from Windows startup group.
- Turn off auto connect at startup in Infoman.Options.
- Reboot
- Invoke TeamLinks (no connect gets done)
- Exit TeamLinks

Does the error (always) occur at this point? What is the address in MSOLE2.VBX 
that is displayed in the error message?

Also, on all the problem PCs, please verify that there is only one copy of the 
following files (should be in Windows system directory). Also, list the 
following information for each file. You can see it using File Manager's 
File.Properties command. Values on my system are listed for comparison.

File		Version		Date		Size	Product Name

MSOLE2.VBX	03.00.0532	4/28/93		10,560	Visual Basic V3.0
MSOLEVBX.DLL	03.00.0535	4/28/93		151,296	Visual Basic V3.0
OLE2.DLL	2.03		6/15/95		304,640	Microsoft OLE 2.03

If you have WPS.EXE, run it before exiting TeamLinks, and verify that the above 
files are loaded, and let me know what the "Usage" count value is for each. If 
you don't have it, I can loan you a copy.

Thanks,

John

Another thing to try.

With no other apps running (after a fresh reboot), run OLE2DEMO.EXE. Exit it. 
Does it crash? If not, repeat, but after running it, do a File.New, then cancel 
from the Insert Object dialog, then exit the app. Does it crash? If not, repeat, 
but after the File.New, select an object to insert (bitmap image for eg.), then 
exit it's app (Paintbrush), then exit OLE2DEMO.EXE. Does it crash?

I'm trying to see if we can reproduce the problem without TeamLinks being 
involved.

You can copy OLE2DEMO.EXE from XANADU::

Thanks,

John

    My customer from before came back and now wants to work this issue.
    He still has the DEC PC's in the training class that cause the problem.
    He installed 2.7 on a new system and it gives the same error.
    The new system does not use PathWorks or TCP/IP as a transport, it
    uses TeamLinks Remote so that throws out the issue of the network 
    transport being a factor.  But... this customer noticed that Windows
    for Workgroups is the common denominator with his problem.  Is that
    true for everyone?  Just wondering.  I gave him the things to try from
    .18 and .19 but perhaps the Windows version is worth pursuing.
    
    Debbie Giannetti

We had kind of assumed it was only happening on WFW.  We never had
a report of this on Win95.

Bob

I received the following message from my customer who experienced the
problem.  See below for details...

*********************************************************************
Subject: TLV2.7 & MSOLE2 Problem

Debbie,

The good news is that I found a difference when comparing the files
you listed.  

Here's the list from a PC that has the problem:

 FILE          SIZE     DATE     VERSION      PRODUCT
 MSOLE2.VBX    10560    4/28/93  03.00.0532   Visual Basic 3.0
 MSOLEVBX.DLL  151296   4/28/93  03.00.0535   Visual Basic 3.0
 OLE2.DLL      313344   11/16/93 2.01         MS OLE 2.01 for Windows

Here's the list from a PC that works properly:

 FILE          SIZE     DATE     VERSION      PRODUCT
 MSOLE2.VBX    10560    4/28/93  03.00.0532   Visual Basic 3.0
 MSOLEVBX.DLL  151296   4/28/93  03.00.0535   Visual Basic 3.0
 OLE2.DLL      304640   9/7/94   2.03         MS OLE 2.03 for Windows

The better news is that when I copied OLE2.DLL and OLE2.REG from the
PC that worked to the PC that had the problem, the problem went away!
So I assume it was caused by a bug in the older version of OLE2.DLL.

I also merged the newer OLE2.REG with the registry using REGEDIT.

It would be nice to have someone confirm the problem with 2.01 of
OLE2.DLL, and also to let me know if I needed to copy OLE2.REG, plus
execute the merge.  Should I also copy all of the other OLE*.* files
(which all seem to be newer on the PC that works properly)?

Hope all of this helps.

Thanks,

 Patrick Murray
 Colorado Department of Transportation

**************************************************************************

Can someone confirm the additional questions?

Debbie Giannetti

Great, 

Now I can reproduce it too. It turns out that TeamLinks V2.7 ships version 2.01 
of OLE. It should ship version 2.03. My system has Pathworks installed on it, 
and I bet it installed 2.03 of OLE, thus I couldn't reproduce the problem.

By overwriting OLE2.DLL on my system with the version on the TeamLinks kit, I 
can reproduce the problem (both with OLE2DEMO.EXE and TeamLinks).

This problem has been entered as PTR case 11-3-827. TeamLinks V3.0 will be
updated to ship version 2.03 of OLE, and this will also be addressed in 
the next ECO of TeamLinks V2.7.

Thanks to all for the feedback and investigations.

John

    John,
    
    What would a customer do to get the proper ole2.dll in the meantime?
    (Let's say they don't have another app that gives them a correct
    version)
    
    Debbie Giannetti

    
>    What would a customer do to get the proper ole2.dll in the meantime?
>    (Let's say they don't have another app that gives them a correct
>    version)
    
    Debbie,

    I think the customer can get it directly from the Microsoft
    web site.  Go to www.microsoft.com.  From there invoke the search
    and look for WW1116.  The second item returned will be an article
    titled "WW1116:OLE Version 2.03".  If you go there you will find an 
    executable that you can download and run.  It will extract
    the files from the executable and then you run the setup.  It
    will install the Version 2.03 ole files.

    ......helen

Debbie,

The OLE version 2.03 files (including OLE2.DLL) can be gotten off Microsoft's 
home page by downloading WW1116.EXE, a self-extracting file off of Microsoft's 
World Wide Web Site on the Internet:
	http://www.microsoft.com/kb/articles/q123/0/87.htm

If you want to grab just OLE2.DLL itself, I've copied it to XANADU::

It's probably best to install all the OLE2 files using the WW1116.EXE method, 
but you could try just OLE2.DLL by itself first to verify that it fixes their 
problem.

John