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

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

548.0. "err=string operation requires bounded/dynamic" by AIMTEC::PERREAULT_K () Wed Apr 22 1992 18:17

        Hi,
        
        I have a customer that has ONE user who is getting the following 
        error message:
        
        " String operation requires bounded/dynamic bounded class
          error occurred while form DOCRECOG was current "
        
        The error occurs when the user is on the EM$INDEX$FIND form after 
        entering the INDEX option from the WP form. Then the user clears 
        out the folder field and presses FIND to get a listing of the 
        folders in the file cabinet.
        
        WP I{CR}
        {LF}  
        {FIND} 
        
        When the error occurs and the user has to exit ALL-IN-1 to get it 
        to work again. It is an intermittent problem and this user is the 
        only one getting it (or maybe the only one reporting the error).
        
        He said that this is an uncustomized system. There are no external 
        applications, the users cannot use VTX or NOTES on this system from 
        ALL-IN-1. The user is unprivileged and is not opening any other 
        form library that might have the EM$INDEX$FIND form in it.
        
        Any ideas as to what might be causing this? What to look for? Why 
        only one user is getting this error?
        
        
        
        Thanks,
        Kathy
        
T.RTitleUserPersonal
Name
DateLines
548.1A few shots into the darknessBUFFER::VICKERSPerfect is the enemy of goodWed Apr 22 1992 21:1014
    Kathy,

    This is certainly a strange one.

    As a wild guess it sounds like there may be some damage to the user's
    DOCDB.  Has the customer done an ANAL/RMS on it?  Are there any strange
    values in the FOLDER field?

    It sounds like the next best course of action would be to have a trace
    log file made to capture the actual event.  It sounds like it may take
    a few attempts but it might yield some clues.

    Hang in there,
    don
548.2BLISS bug?IOSG::TALLETTJust one more fix, then we can ship...Wed Apr 22 1992 21:3211
    
    	I have seen this message before, and it was a bug in the BLISS
    	code that time, passing the wrong sort of string to a library
    	routine. Sounds like unusual circumstances in your user's
    	account is exercising a previously unexplored code path that
    	has a bug....
    
    	Not that this is much help mind! :-)
    
    Regards,
    Paul
548.3Versions?UTRTSC::BOSMANWe're just sugar mice in the rainThu Apr 23 1992 08:296
    
    
    I don't see any version numbers mentioned in .0. If it was a bug, maybe
    the basenoter is running that version.
    
    Sjaak.
548.4IOSG::TALLETTJust one more fix, then we can ship...Thu Apr 23 1992 10:494
    
    	Oh, I may have mislead you. I don't think the bug I was fixing
    	was the bug you are seeing. What I meant was, the error message
    	sounds like a bug in BLISS code.