![]() |
![]() |
|
|
200 |
ERROR: Class instance specification is not unique | |
|
Description |
The specification given for a new or modified class was not unique. |
Action |
Ensure that the class specification presented to the | |
203 |
ERROR: Unable to mark invalid record for principal principal. | |
|
Description |
When marking an entry as invalid in the principal file, an error writing the principal file occurred. This error can occur when deleting a principal from the |
Action |
Run a diagnostic on the disk to see whether the disk is corrupted. If it is corrupted, buy a new disk and run the command again. If it is not, then contact BEA TUXEDO system Technical Support. | |
204 |
ERROR: Could not find principal. | |
|
Description |
The principal which the |
Action |
Make sure that only one person is accessing the | |
205 |
ERROR: Unable to append to file filename. | |
|
Description |
While attempting to open a file, an error occurred. This error happens when using the |
Action |
There are several kernel parameters which could cause this error. Two obvious ones include the maximum allowed size for files and the number of allowable open file descriptors. Disk space could also be a problem. Increase the appropriate kernel parameters or buy a new disk, then try the command again. | |
207 |
ERROR: Unable to mark invalid record for principal name. | |
|
Description |
While modifying a principal in the |
Action |
Run a diagnostic on the disk to see whether the disk is corrupted. If it is corrupted, buy a new disk and run the command again. If it is not, then contact BEA TUXEDO system Technical Support. | |
212 |
ERROR: Unable to mark invalid record. | |
|
Description |
When marking an entry as invalid in the group file, an error writing the group file occurred. This error can occur when deleting a group from the |
Action |
Run a diagnostic on the disk to see whether the disk is corrupted. If it is corrupted, buy a new disk and run the command again. If it is not, then contact BEA TUXEDO system Technical Support. | |
213 |
ERROR: Could not find group. | |
|
Description |
The group which the |
Action |
Make sure that only one person is accessing the | |
214 |
ERROR: Unable to append to file filename. | |
|
Description |
While attempting to open the given file, an error occurred. This happens when updating the |
Action |
There are several kernel parameters which could cause this error. Two obvious ones include the maximum allowed size for files and the number of allowable open file descriptors. Disk space could also be a problem. Increase the appropriate kernel parameters or buy a new disk, then try the command again. | |
217 |
ERROR: Unable to mark invalid record. | |
|
Description |
When marking an entry as invalid in the group file, an error writing the group file occurred. This error can occur when modifying a group from the |
Action |
Run a diagnostic on the disk to see whether the disk is corrupted. If it is corrupted, buy a new disk and run the command again. If it is not, then contact BEA TUXEDO system Technical Support. | |
219 |
ERROR: Unable to change attributes of the other group. | |
|
Description |
The other group is a group that always exists and which cannot be altered. |
Action |
Do not attempt to alter the other group. | |
220 |
ERROR: Unable to change state of the other group. | |
|
Description |
The other group is a group that always exists and which cannot be altered. Hence this group cannot be removed. |
Action |
Do not attempt to remove the other group. | |
222 |
ERROR: Unable to append to file filename. | |
|
Description |
While attempting to open the given file, an error occurred. This happens when updating the |
Action |
There are several kernel parameters which could cause this error. Two obvious ones include the maximum allowed size for files and the number of allowable open file descriptors. Disk space could also be a problem. Increase the appropriate kernel parameters or buy a new disk, then try the command again. | |
224 |
ERROR: Unable to mark invalid record. | |
|
Description |
When marking an entry as invalid in the access file, an error writing the access file occurred. This error can occur when deleting a permission from the |
Action |
Run a diagnostic on the disk to see whether the disk is corrupted. If it is corrupted, buy a new disk and run the command again. If it is not, then contact BEA TUXEDO system Technical Support. | |
226 |
ERROR: Unable to find the end of the acl file. | |
|
Description |
When attempting to find the end of the acl file, an error occurred. |
Action |
There are several kernel parameters which could cause this error. Two obvious ones include the maximum allowed size for files and the number of allowable open file descriptors. Disk space could also be a problem. Increase the appropriate kernel parameters or buy a new disk, then try the command again. | |
227 |
ERROR: Unable to mark invalid record. | |
|
Description |
When marking an entry as invalid in the access file, an error writing the access file occurred. This error can occur when modifying a permission in the |
Action |
Run a diagnostic on the disk to see whether the disk is corrupted. If it is corrupted, buy a new disk and run the command again. If it is not, then contact BEA TUXEDO system Technical Support. | |
229 |
ERROR: Unable to print in the principal file. | |
|
Description |
While attempting to write into the principal file, an error occurred. This error is usually caused by disk corruption. |
Action |
Run a diagnostic on the disk to see whether the disk is corrupted. If it is corrupted, buy a new disk and run the command again. If it is not, then contact BEA TUXEDO system Technical Support. | |
230 |
ERROR: Missing key field(s) in /Admin service request | |
|
Description |
One or more required key fields is missing from an /AdminAPI request. The identifier of the first missing key field is supplied in the |
Action |
Using | |
See Also |
| |
231 |
ERROR: Inappropriate key field(s) for /Admin service request for unconfigured application | |
|
Description |
The |
Action |
Resubmit the /AdminAPI request, but omit the | |
See Also |
| |
232 |
ERROR: TA_MIN is greater than TA_MAX | |
|
Description |
A |
Action |
Correct the values of | |
See Also |
| |
233 |
ERROR: TA_SRVID plus TA_MAX yields server identifier greater than 30,000 | |
|
Description |
A |
Action |
Correct the values of | |
See Also |
| |
234 |
ERROR: | |
|
Description |
The |
Action |
Correct the /AdminAPI request to use the local logical machine identifier. | |
See Also |
| |
235 |
INFO: .SysResourceConfig: system configuration change | |
|
Description |
This message indicates that parameters in the |
Action |
This is an informational message. | |
See Also |
| |
236 |
ERROR: SET operation did not specify required key field | |
|
Description |
If a class contains any key fields necessary for a |
Action |
Add one of the required | |
237 |
ERROR: Unable to add to the access control file. | |
|
Description |
When modifying the |
Action |
Run a diagnostic on the disk to see whether the disk is corrupted. If it is corrupted, buy a new disk and run the command again. If it is not, then contact BEA TUXEDO system Technical Support. | |
240 |
INFO: .SysMachineConfig: LMID configuration change | |
|
Description |
This message indicates that parameters in the |
Action |
This is an informational message. | |
See Also |
| |
243 |
ERROR: | |
|
Description |
The |
Action |
Resubmit the /AdminAPI request and use the correct logical machine identifier. | |
See Also |
| |
245 |
ERROR: There are no more valid group identifiers | |
|
Description |
Group identifiers can only be in the range 0 through 16383. If all group identifiers have been used, then it is impossible to add a new group to the system. |
Action |
Remove a group, then add a new group. | |
246 |
ERROR: There are no more valid user identifiers | |
|
Description |
User identifiers can only be in the range 1 through 131,071. If all user identifiers have been used, then it is impossible to add a new user to the system. |
Action |
Remove a user, then add a new user. | |
248 |
INFO: .SysMachineState: LMID state change to state | |
|
Description |
This message states that the specified machine changed to a new state as mentioned in the message. A complete listing of the current parameters are sent along in the posted buffer. |
Action |
This is an informational message. | |
See Also |
| |
249 |
INFO: .SysServerConfig: servername, group srvgrp, id srvid configuration change | |
|
Description |
This message indicates that the configuration parameters for the server specified above have been updated. A complete listing of the attributes of the server are sent along in the posted buffer. |
Action |
This is an informational message. | |
See Also |
| |
250 |
INFO: .SysServerState: servername, group srvgrp, id srvid state change to state | |
|
Description |
This message indicates that the server specified above changed to a new state. A complete listing of the server attributes are sent in the posted buffer. |
Action |
This is an informational message. | |
See Also |
| |
251 |
INFO: .SysClientState: User usrname on LMID state change to state | |
|
Description |
This message indicates that the client specified above changed to a new state. A complete listing of the current attributes of the client are sent in the posted buffer. |
Action |
This is an informational message. | |
See Also |
| |
252 |
INFO: .SysGroupState: Group groupname on lmid state change to state | |
|
Description |
This message indicates that the group specified above changed to a new state. A complete listing of the group attributes are sent in the posted buffer. |
Action |
This is an informational message. | |
See Also |
| |
253 |
INFO: .SysClientConfig: User usrname on LMID configuration change | |
|
Description |
This message indicates that the attributes on the client specified above have been changed. A complete listing of the current attributes of the client are sent in the posted buffer. |
Action |
This is an informational message. | |
See Also |
| |
254 |
ERROR: Required field not present on SET request | |
|
Description |
The field indicated by |
Action |
Regenerate the request using an appropriate value for the indicated field. | |
See Also |
| |
255 |
ERROR: Class only valid on security levels greater than APP_PW. | |
|
Description |
This class is only valid if the security level in the |
Action |
Change the | |
256 |
ERROR: Unable to seek in group file. | |
|
Description |
While attempting to manipulate the file position indicator in the group file, an error occurred. This error is usually caused by disk corruption. |
Action |
Run a diagnostic on the disk to see whether the disk is corrupted. If it is corrupted, buy a new disk and run the command again. If it is not, then contact BEA TUXEDO system Technical Support. | |
257 |
ERROR: Unable to print in group file. | |
|
Description |
While attempting to write into the group file, an error occurred. This error is usually caused by disk corruption. |
Action |
Run a diagnostic on the disk to see whether the disk is corrupted. If it is corrupted, buy a new disk and run the command again. If it is not, then contact BEA TUXEDO system Technical Support. | |
258 |
ERROR: Unable to seek in principal file. | |
|
Description |
While attempting to manipulate the file position indicator in the principal file, an error occurred. This error is usually caused by disk corruption. |
Action |
Run a diagnostic on the disk to see whether the disk is corrupted. If it is corrupted, buy a new disk and run the command again. If it is not, then contact BEA TUXEDO system Technical Support. | |
260 |
ERROR: Cannot create | |
|
Description |
A |
Action |
Regenerate the request specifying the required networking addresses. | |
See Also |
| |
261 |
ERROR: Inconsistent user attributes detected. | |
|
Description |
While looking at the access control cache an inconsistent entry was found in the shared memory. |
Action |
If this error happens consistently, contact your BEA TUXEDO system Technical Support. | |
262 |
ERROR: T_WSL creation conflicts with existing server | |
|
Description |
An attempt was made to create a |
Action |
Change the | |
263 |
ERROR: Server group name does not match existing group | |
|
Description |
While attempting to create a new service group, the |
Action |
The | |
264 |
INFO: Restarting server at alternate location | |
|
Description |
A server has been migrated to a new location |
Action |
None. | |
265 |
ERROR: Cannot open file | |
|
Description |
The |
Action |
If the host operating system has a limit on the number of open files, or the number of open files per user or the number of open files per process, then you may need to increase that limit. The file system /tmp may be full. The directory where temporary files are placed may be full. If it seems that there should be enough file descriptors and disk space for this operation, contact your BEA TUXEDO system Technical Support. | |
266 |
ERROR: Cannot write to file | |
|
Description |
The |
Action |
The file system | |
267 |
ERROR: Cannot open file | |
|
Description |
The |
Action |
If the host operating system has a limit on the number of open files, or the number of open files per user or the number of open files per process, then you may need to increase that limit. The file system | |
268 |
ERROR: Cannot write to file | |
|
Description |
The |
Action |
The file system | |
269 |
ERROR: Cannot open file | |
|
Description |
The |
Action |
If the host operating system has a limit on the number of open files, or the number of open files per user or the number of open files per process, then you may need to increase that limit. The file system | |
270 |
ERROR: Cannot write to file | |
|
Description |
The |
Action |
The file system | |
271 |
ERROR: Cannot open file | |
|
Description |
The |
Action |
If the host operating system has a limit on the number of open files, or the number of open files per user or the number of open files per process, then you may need to increase that limit. The file system | |
272 |
ERROR: Cannot write to file | |
|
Description |
The |
Action |
The file system /tmp may be full. The directory where temporary files are placed may be full. | |
273 |
ERROR: sbblrtn could not send reply error-core | |
|
Description |
The sbbl process could not send a reply to the requestor. |
Action |
The code in error-code may provide clues as to the cause of this problem. | |
274 |
ERROR: Failed to get information on the migrating server group | |
|
Description |
A |
Action |
Check the log for related messages. | |
275 |
ERROR: Failed to get information on the service group | |
|
Description |
A |
Action |
Check the log for related messages. | |
276 |
ERROR: TA_MINENCRYPTBITS(min) must be less than or equal to TA_MAXENCRYPTBITS(max) | |
|
Description |
An attempt has been made to change the |
Action |
The value of min must be less than or equal to the value of max. Change the | |
277 |
ERROR: TA_MINENCRYPTBITS(min) must be less than or equal to TA_MAXENCRYPTBITS(max) | |
|
Description |
An attempt has been made to change the |
Action |
The value of min must be less than or equal to the value of max. Change the MIB request to comply with this requirement. You may need to change the value of | |
278 |
ERROR: Cannot open file | |
|
Description |
The |
Action |
If the host operating system has a limit on the number of open files, or the number of open files per user or the number of open files per process, then you may need to increase that limit. The file system /tmp may be full. The directory where temporary files are placed may be full. | |
279 |
ERROR: Cannot write to file | |
|
Description |
The MIB has failed to write to a file for the sbbl process while getting information from an application queue space. |
Action |
The file system /tmp may be full. The directory where temporary files are placed may be full. | |
280 |
ERROR: Cannot open file | |
|
Description |
The |
Action |
If the host operating system has a limit on the number of open files, or the number of open files per user or the number of open files per process, then you may need to increase that limit. The file system /tmp may be full. The directory where temporary files are placed may be full. | |
281 |
ERROR: Cannot write to file | |
|
Description |
The |
Action |
The file system /tmp may be full. The directory where temporary files are placed may be full. | |
282 |
ERROR: Cannot open file | |
|
Description |
The |
Action |
If the host operating system has a limit on the number of open files, or the number of open files per user or the number of open files per process, then you may need to increase that limit. The file system /tmp may be full. The directory where temporary files are placed may be full. | |
283 |
ERROR: Cannot write to file | |
|
Description |
The |
Action |
The file system /tmp may be full. The directory where temporary files are placed may be full. | |
284 |
ERROR: Cannot open file | |
|
Description |
The |
Action |
If the host operating system has a limit on the number of open files, or the number of open files per user or the number of open files per process, then you may need to increase that limit. The file system /tmp may be full. The directory where temporary files are placed may be full. | |
285 |
ERROR: Cannot write to file | |
|
Description |
The |
Action |
The file system /tmp may be full. The directory where temporary files are placed may be full. | |
286 |
ERROR: Cannot open file | |
|
Description |
The |
Action |
If the host operating system has a limit on the number of open files, or the number of open files per user or the number of open files per process, then you may need to increase that limit. The file system /tmp may be full. The directory where temporary files are placed may be full. | |
287 |
ERROR: Cannot write to file | |
|
Description |
The |
Action |
The file system /tmp may be full. The directory where temporary files are placed may be full. | |
288 |
ERROR: can't SET Internet type of network address(es). | |
|
Description |
Internet addresses cannot be used in a configuration which contains releases older than the BEA TUXEDO system 6.3 release. |
Action |
Since older sites cannot properly interpret internet addresses, internet addresses cannot be used when interoperating with a release of the BEA TUXEDO system older than 6.3. Change the address in the | |
289 |
ERROR: Unable to determine license level | |
|
Description |
An attempt to determine the license information for the BEA TUXEDO system failed. |
Action |
Check the log for related messages. Ensure that the BEA TUXEDO system has been properly installed and licensed. | |
290 |
ERROR: SET operation is not allowed on ADMGRP server | |
|
Description |
An attempt was made to perform a |
Action |
No action required. | |
See Also |
| |
291 |
ERROR: Cannot change own state to | |
|
Description |
A |
Action |
Make sure that the client id you specify is not your own. | |
292 |
ERROR: Cannot change own state to SUSPENDED | |
|
Description |
A |
Action |
Make sure that the client id you specify is not your own. | |
293 |
ERROR: Cannot invalidate | |
|
Description |
The specified |
Action |
The | |
See Also |
| |
294 |
ERROR: | |
|
Description |
Dynamically changing the |
Action |
Dynamically changing the | |
See Also |
| |
295 |
ERROR: | |
|
Description |
The administrator must identify each |
Action |
Choose a different | |
See Also |
| |
296 |
ERROR: | |
|
Description |
The * |
Action |
Increase | |
See Also |
| |
297 |
ERROR: A network mapping cannot be created for a non existant network group | |
|
Description |
The |
Action |
Create | |
See Also |
| |
298 |
ERROR: A network mapping cannot be created for a non existant LMID | |
|
Description |
The |
Action |
The | |
See Also |
| |
299 |
ERROR: Cannot invalidate the | |
|
Description |
The reserved |
Action |
The reserved | |
See Also |
|
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|