![]() |
![]() |
|
|
1305 |
ERROR: tpsubscribe failed due to a permissions violation in the EVENT_MIB | |
|
Description |
A call to |
Action |
Check and possibly retune the permissions on the EVENT_MIB object being accessed. For example, if you are subscribing to have a service called when an event occurs, check the T_EVENT_SERVICE class in the EVENT_MIB. | |
1307 |
ERROR: [tpunsubscribe - failed to set field field for tpunsubscribe message. Ferror32=ferror] | |
|
Description |
Unable to set the given |
Action |
Contact BEA Customer Support. | |
1308 |
ERROR: [tpsubscribe - failed to set field field for tpsubscribe message. Ferror32= ferror] | |
|
Description |
Unable to set the given |
Action |
Contact BEA Customer Support. | |
1309 |
ERROR: [tppost - failed to set field field for tppost message] | |
|
Description |
Unable to set the given |
Action |
Contact BEA Customer Support. | |
1311 |
ERROR: tpsubscribe - Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1312 |
ERROR: tpunsubscribe - Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
1313 |
ERROR: tppost - Can't add field field to FML32 buffer | |
|
Description |
Unable to set the given |
Action |
Contact BEA Customer Support. | |
1314 |
INFO: Compression Level set to level | |
|
Description |
The environment variable |
Action |
None. | |
1316 |
INFO: Enabled num bit link encryption, session key fingerprint hex_num | |
|
Description |
This informational message is written to the system log file when an encrypted link is established, if the The bit length is normally 40, 56, or 128. It represents the result of negotiation between the two processes, based on their encryption parameter settings and installed encryption software. The session key fingerprint is a 32-digit hexadecimal number that is securely derived from the session key. The fingerprint has no value to an attacker trying to break the encryption, and need not be protected. Both processes communicating over the encrypted link should report the same fingerprint value. Otherwise there may be an active network-based attack in progress, such as "man in the middle." |
Action |
None required | |
See Also |
BEA TUXEDO 6.5 Release Notes | |
1317 |
ERROR: Invalid attempt to use 40-bit or 56-bit encryption | |
|
Description |
A routine in the encryption subsystem was called in an improper context. |
Action |
Contact BEA Customer Support. | |
1318 |
ERROR: Invalid attempt to use 40-bit or 56-bit encryption | |
|
Description |
A routine in the encryption subsystem was called in an improper context. |
Action |
Contact BEA Customer Support. | |
1319 |
ERROR: Invalid attempt to use 40-bit or 56-bit encryption | |
|
Description |
A routine in the encryption subsystem was called in an improper context. |
Action |
Contact BEA Customer Support. | |
1320 |
ERROR: Invalid attempt to use 40-bit or 56-bit encryption | |
|
Description |
A routine in the encryption subsystem was called in an improper context. |
Action |
Contact BEA Customer Support. | |
1340 |
ERROR: pif: interceptor sequence for val is too long (>val) | |
|
Description |
The Interception Sequence attribute for the specified registered implementation is longer than the current version of the product allows. |
Action |
Change the interception sequence so that it's length is less than or equal to what is supported. | |
1341 |
ERROR: pif: can't load impl 'val' that is in InterceptorSequence for 'val' | |
|
Description |
The specified implementation identifier is in the Interception Sequence for the given FANOUT or STACK plug-in, but the framework was not able to realize/load it. |
Action |
Make sure the specified implementation is a correctly registered implementation. | |
1342 |
WARN: pif: No DefaultImpl for 'val', version val | |
|
Description |
The framework was asked to realize/load a plug-in that implements the specified version of the specified interface but there are no such registered plug-in implementations registered. |
Action |
Register an appropriate implementation or contact BEA Customer Support. | |
1343 |
WARN: pif: possible alias loop, interface 'val', alias 'val' | |
|
Description |
The framework has detected a possible alias (also known as Selectors) loop (where on alias directly or indirectly is an alias for itself). Alternatively the chain of aliases is too long (unlikely unless you have more than one hundred aliases for the given interface). |
Action |
Remove or change aliases so that aliases ultimately map to an identifier that is not the identifier for another alias. | |
1344 |
ERROR: pif: missing ImagePath for 'val' | |
|
Description |
The specified implementation is registered with out an ImagePath attribute and hence can not be realized/loaded. |
Action |
Reregister or edit the specified implementation with an ImagePath attribute (ImagePath is the name of the shared library or DLL that contains the executable code for the plug-in's implementation). | |
1345 |
ERROR: pif: can't load 'val' | |
|
Description |
The shared library or DLL for the specified implementation could not be loaded. |
Action |
Check the ImagePath attribute of the specified implementation, and/or that your shared library search path is set correctly. | |
1346 |
ERROR: pif: can't get address for EntryPoint 'val' (impl 'val') | |
|
Description |
The specified entry point could not be found in the shared library or DLL for the given implementation. |
Action |
Check the EntryPoint attribute of the specified implementation. If the EntryPoint is correct then check that the ImagePath attribute is referring to the correct shared library or DLL. | |
1347 |
ERROR: pif: 'val' InheritsFrom unregistered impl ('val') | |
|
Description |
The specified implementation's InheritsFrom attribute is set to an implementation identifier that is not registered. |
Action |
Register the desired implementation, or change the InheritsFrom attribute. | |
1348 |
ERROR: pif: can't allocate val bytes | |
|
Description |
The framework was unable to allocate memory. |
Action |
Check system configuration or per-process limitations. | |
1349 |
INFO: pif: impl 'val' contributes nothing to plugin 'val' | |
|
Description |
Implementation inheritance is being used and no part of the specified implementation is being used to contrast the composite plug-in. |
Action |
No action is needed, the message is only informational. However the InheritsFrom attribute could be deleted from the relevant implementation to stop this message from being logged. | |
1350 |
ERROR: pif: incomplete vtbl for 'val' | |
|
Description |
The [composite] plug-in's virtual function table does not provide an implementation of every operation in the specified interface. |
Action |
Possibly missing an InheritsFrom attribute from the implementation. | |
1351 |
WARN: pif: No DefaultImpl for 'val', version val | |
|
Description |
The framework was asked to realize/load a plug-in that implements the specified version of the specified interface but there are no such plug-in implementations registered. |
Action |
Register an appropriate implementation or contact BEA Customer Support. | |
1352 |
WARN: pif: plugin 'val' has private data but does not have a copy and/or destroy function | |
|
Description |
The specified implementation has private data, but does not have a plug-in framework copy and/or destroy function. |
Action |
Contact BEA Customer Support (or the appropriate vendor if the implementation comes from a 3rd party). | |
1353 |
WARN: pif: impl 'val' (in plugin 'val') is not stack aware but is a non-terminal member of a stack interception sequence | |
|
Description |
The specified implementation should not be registered in a stack interception sequence (except as the last member of the sequence). |
Action |
Possible solution is to re-arrange the order of the interception sequence or contact the vendor that provided the implementation. | |
1354 |
WARN: pif: impl 'val' (in plugin 'val') is not fan-out aware but is registered with a fan-out interception sequence | |
|
Description |
The specified implementation is registered as a FANOUT plug-in but it's internal implementation flags does not indicate that it is FANOUT aware. |
Action |
Possibly the implementation was registered incorrectly or contact the vendor that provided the implementation. | |
1355 |
ERROR: pifreg: can not create registry database | |
|
Description |
The framework is unable to create the database in which to register plug-in's. |
Action |
Make sure you have write access to the directory containing the database (by default TUXDIR/udataobj), and that the directory is not on an NFS mounted filesystem that does not support file locking. | |
1356 |
ERROR: pifreg: can not open registry database | |
|
Description |
The framework is unable to open the database in which plug-in's are registered. |
Action |
Make sure that the directory (default TUXDIR/udataobj) is not on an NFS mounted filesystem that does not support file locking. | |
1357 |
ERROR: pifreg: can not open \PIF registry key | |
|
Description |
The framework registry plug-in is unable to open the low level registry key under which all framework plug-in's are registered. |
Action |
Likely reason is that no plug-in's have ever been registered in this registry. | |
1358 |
ERROR: pifreg: can not create \PIF registry key | |
|
Description |
The framework registry plug-in is unable to create the low level registry key under which all framework plug-in's are registered. |
Action |
Contact BEA Customer Support. | |
1359 |
ERROR: pifreg: can not open PIF Profile `val' | |
|
Description |
The framework is unable to open the specified profile. |
Action |
The specified profile may not exist. Register a plug-in implementation in the specified profile, specify a different profile to use, or don't specify any profile. |
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|