[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference abbott::teamlinks_windows

Title:TeamLinks for Windows
Notice:Kit and ECO locations: See replies to note 8.o note 8.
Moderator:ORION::chayna.zko.dec.com::tamara::eppesAN
Created:Mon Aug 28 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2238
Total number of notes:9650

2155.0. "Problem with out of memory errors" by ALFSS2::GIANNETTI_D () Fri Apr 25 1997 15:10

NT box.  They have both MailWorks for VMS as well as ALL-IN-1.                 
The NT user only has ALL-IN-1.  On both ALL-IN-1 is the                        
primary mail file cabinet.                                                     
                                                                                
The debug we were able to capture is when the Windows 95 user                  
was in TeamLinks and chose to print a message from her ALL-IN-1                
Inbox to a networked Digital Printer.  She received "Out of                    
Memory" with the only option being to Cancel.  She gets thrown                 
out of TeamLinks completely upon clicking Cancel.                              
                                                                                
We are not sure what is in the Title Bar of the message but he                 
will monitor to try to capture that information as well.                       
                                                                                
Also, the person calling this issue in told me that the Windows 95             
user had not rebooted her system all week (since Monday, today                 
is Thursday) and the other user the NT user never exits TeamLinks              
and never reboots.  The caller is trying to emulate this situation             
by not logging out of TeamLinks himself to test in a "controlled"              
situation.                                                                     
                                                                                
I asked for him to send me the debug and to add TRACE to see                   
if we can get more information.                                                
                                                                                
The PC's reported both have 32 mb of memory on them.                           


DEBUG w/o TRACE
---------------------------------------------------------------
                                                                                
**** CFC started Wed Apr 23 09:12:22 1997 ****
CFCIOS DLL version: TeamLinks Client IOS BaseLevel BL61
ALL-IN-1 on node ARIT is version V3.2, running File Cabinet Server version 6
CFCX400 connected to MailWorks server, version unknown 
TLCOMMON: Transparent mode: Device = N, App = Y
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed

AIDA DLL version: V3.2-0 AIDA$RG35B
AIDA Server version on arit: V3.2-0 OA$AIDA V3.2-90

Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
INFODLL PrPrintView (printer.c, line 4916): RestoreDC failed, continuing anyway.
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
TLADDR.DLL GetNextDOSDistList: Error getting directory C:\TEAMLINK\DISTLIST\SYSOP*.* into list: -1
TLADDR.DLL GetNextDOSDistList: Error getting directory N:\A1MAIL$\DISTLIST\SYSOP*.* into list: -1
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
CFCIOS reverting to slow list (111/67)
CFCIOS reverting to slow list (111/91)
CFCX400: Cannot get local route from office.ini 
CFCX400: Cannot get time offset from office.ini 
INFODLL PrPrintView (printer.c, line 4916): RestoreDC failed, continuing anyway.
CFCIOS reverting to slow list (111/92)
INFODLL PrPrintView (printer.c, line 4916): RestoreDC failed, continuing anyway.
CFCIOS reverting to slow list (111/102)
CFCIOS reverting to slow list (111/107)
Infoman: VB Error 7 during Setup of RMWrap
ALL-IN-1 on node ARIT is version V3.2, running File Cabinet Server version 6
CFCX400 connected to MailWorks server, version unknown 
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
Fcdata GetItemIndex failed
Fcdata FclistGetItemAttribute failed
Fcdata FclistUpdateCount failed
INFODLL PrAddPrinter (printer.c, line 4587): Array of printers too small; expanding it.
T.RTitleUserPersonal
Name
DateLines
2155.1XANADU::CUMMINGSJerry Cummings, TeamLinksFri Apr 25 1997 15:247
Mitre reported this and I don't think we ever figured
out what was going wrong. From some of the Mitre logs
it looked like something trashed memory and Print was
the first thing that ran into the corrupted memory.

Don't know what to tell you,
Jerry
2155.2Jerry, Jerry, JerryALFSS2::GIANNETTI_DMon Apr 28 1997 19:306
    Jerry,
    
    Your gonna have to do better than that.  Unfortunately,
    customers don't like that answer.  This time its Reuters.
    
    Debbie Giannetti
2155.3XANADU::CUMMINGSJerry Cummings, TeamLinksTue Apr 29 1997 13:294
Are they an EFT site? Perhaps we can add a bunch of semi-temporary
logging code to V3 EFT2 in that area.

Jerry
2155.4Could use 3.0 if needAIMTEC::GIANNETTI_DThu May 01 1997 15:0411
    Jerry,
    
    I talked with the customer and he said they are a Field Test Site. 
    This specific situation occurs in their production environment and
    he would be willing to test in 3.0 environment on his own PC since
    he also experiences the problem.
    
    What do you want me to do next?
    
    Debbie Giannetti
    
2155.5XANADU::CUMMINGSJerry Cummings, TeamLinksThu May 01 1997 18:309
I guess I should work with the customer
directly after we ship, and they install
EFT2. This would be late May. Will this
work for the customer?

Did they also see this problem with V3 EFT1?
Maybe we've already fixed it?

Jerry
2155.6Update ALFSS2::GIANNETTI_DMon May 05 1997 15:2520
    Jerry,
    
    I talked with the customer.  He said he will see about getting his
    own system set up with eft1 and report back to us.  He said he was
    concerned since one of the people who installed eft1 3.0 said it
    was so buggy they had to pull it off their system.
    
    I asked Bob if they were installing it in production mode and he
    said yes.  I explained that they should be instalilng the field
    test in a "test bed".  I also expressed to the customer that I
    am running eft1 3.0 and not experiencing problems that would render
    it "useless".
    
    He then said he would install 3.0 on his system and I explained that
    when eft2 is released (if the problem still exists with eft1) we 
    would work directly with you guys.
    
    I'll let you know what he finds out with 3.0 eft1 as soon as I can.
    
    Debbie Giannetti 
2155.7Update on "out of memory" issueALFSS2::GIANNETTI_DWed Jun 04 1997 17:4912
    Jerry,
    
    I talked with the customer today.  He installed eft2 of 3.0 on his
    own system and has not experienced the "out of memory" problem.
    
    He noted, on systems still with 2.7, if they install eco2 they have
    not experienced the "out of memory" problem.  We are keeping the
    call open and I will be in class the next two weeks.  I will follow
    up with him upon my return and we'll see if he is still in good
    shape.
    
    Debbie Giannetti