T.R | Title | User | Personal Name | Date | Lines |
---|
1749.1 | Not sure how you're getting this! | IOSG::STANDAGE | Oink...Oink...Mooooooooooooooooooooooooooooooooo | Tue Nov 10 1992 16:14 | 25 |
|
Hi Trev,
>>%OAFC-E-TLVBADSTREAM, Invalid TLV stream
This message is returned from the Filecabinet server. The invalidity of
the TLV stream is either due to it being out of range or unknown
attribute types/tags. (I think !)
Could you possibly give me more information as to the keystrokes you
are performing to reproduce this, at the moment I'm not even sure what
subsystem you're in !
If it is reproducable, attempt to stop/restart the server(s) and see
what happens then. Also, take a look at the bottom of the server log
file (SYS$MANAGER:OAFC$SERVER.LOG) and see if there is any useful
errors written there.
Let me know the scoop,
Kevin.
|
1749.2 | Need more information | CHRLIE::HUSTON | | Thu Nov 12 1992 16:10 | 11 |
|
Kevin is right, more info is needed as to EXACTLY what you are doing.
invalid TLV stream comes from the FCS, it is returned when we received
a request for an attribute that we don't know about, or an attribute
request stream that is improperly built.
More information is needed.
--BOb
|
1749.3 | Think I've got it too. | IOSG::STANDAGE | Oink...Oink...Mooooooooooooooooooooooooooooooooo | Thu Nov 19 1992 15:32 | 44 |
|
I've managed to reproduce this now...
On our performance machine, we have 361 drawers in the partition.
If the Manager enters ALL-IN-1, goes to SM MFC MD, does IAD and just
presses return - the first 16 drawers are displayed.
From here :
GOLD-B (to the 361st drawer) gives :
OAFC-E-BUFFUNFL, Invalid length specified for TLV buffer
Typing 222 (to go to the 222nd entry) works.
Typing 223 (to go to the 223rd entry) produces the same error message.
THe same applies for any entry after the 223rd.
If the manager goes to the 222nd entry and then tries to progress
further by typing a later number (say 300), then this error is
returned:
Invalid TLV stream passed in
The only workround seems to be going to the 222nd entry and just
pressing NextScreen endlessly - this seems to function normally.
Incidently, this bug exists in other related areas. If the
manager does IAD and enters an Owner that doesn't exist, the FCS
happily runs through the partition until the same problem is found,
and the same error message is returned.
IPR Time!
Kevin.
|
1749.8 | Nope on both counts (I think!) | IOSG::STANDAGE | | Thu Dec 09 1993 10:06 | 10 |
|
Paul,
To the best of my knowledge I don't believe this is fixed in either
MUPA or V3.0-1.
Sorry,
Kevin.
|