This documentation supports the 19.02 version of Remedy Action Request System.

To view an earlier version, select the version from the Product version menu.

Error messages 8501 to 8799

NumberDescription
8610 Error
Please ensure correct overlay specific group(s) for the user.

The error can occur due to the restrictions added for the users and groups. 

8700 Error

Attachment locator types can only be filename or the buffer. Use only these types.

The only acceptable attachment locator types are the filename or the buffer. Use only these types.

8701 ErrorBad attachment locator buffer size.
8702 ErrorBad attachment locator buffer pointer.
8703 ErrorBad attachment size.
8704 Error

OLE Automation active link action cannot be empty.

The automation structure required when you define an OLE Automation active link action is empty. Specify the appropriate contents for this structure.

8705 Error

OLE Automation active link action method list cannot be empty.

The method list required when you define an OLE Automation active link action is empty. Provide at least one method for this structure.

8706 Error

Bad ARCOMValueStruct variable value.

The value of an ARCOMValueStruct variable in a method or parameter of an OLE Automation active link action is invalid. Provide a valid value.

8707 Error

Bad OLE server or parameter name.

The name of an OLE server or a parameter of an OLE Automation active link action is empty or exceeding the maximum length allowed (64 characters). Fix the name to continue your work.

8708 Error

Bad OLE class ID or method ID, or interface of an OLE automation active link.

The name of an OLE class ID, a method ID, or an interface of an OLE Automation active link action is either empty or exceeding the maximum length allowed (128 characters).

8709 Error

Bad OLE Automation active link action Method.

The method structure of the OLE Automation active link action is invalid. Detailed errors follow that explain what part of the method structure is invalid.

8710 Error

Bad OLE Automation active link action Method name.

The name of a method in an OLE Automation either is empty or exceeds the maximum length allowed (128 characters).

8711 Error

Empty OLE Automation active link action Method.

The method structure required when you define an OLE Automation active link action is empty. Provide at least one method for this structure.

8712 Error

Empty OLE Automation active link action Parameter List.

The parameter list required when you define an OLE Automation active link action is empty. Provide at least one method for this structure.

8713 Error

Empty OLE Automation active link action Parameter.

The parameter structure of a method required when you define a method in an OLE Automation active link action is empty. Specify the appropriate contents for this structure.

8714 Error

Bad OLE Automation active link action Parameter.

The parameter structure of a method in this OLE Automation active link action is invalid. Detailed error messages explain what part of the structure is invalid.

8715 Error

Bad automation string in the OLE Automation active link action.

An automation action string required when you define an OLE Automation active link action either is empty or exceeds the maximum length allowed (2000 characters).

8716 Error

The RPC socket number for the Approval Server process is not one of the legal values (390600, 390621 - 390634, 390636 - 390669, 390680 - 390694).

The value for the RPC socket is not set properly. Use the Approval Server Admin-Server Settings form to set this to a legal value.

8717 Error

The value for the Application check interval is not within the legal range of 0 to 3600 seconds.

The value for Application Check Interval is not set properly. Set this to a legal value.

8718 WarningThe signal %d is not valid and is ignored.
8720 Error

Open dialog value is empty.

This message occurs when you try to create an Open Dialog active link action without specifying an open dialog structure value. To create the Open Dialog active link action, enter a value.

8721 Error

Call guide ID is empty.

This message occurs when you try to create a Call Guide active link action without specifying a Call Guide structure value. To create the Call Guide active link action, enter a value.

8722 Error

Guide name missing.

This message occurs when you try to create a Call Guide active link action without specifying a Call Guide active link name. To create the Call Guide active link action, enter a name.

8723 Error

Goto active link action label empty or too long.

This message occurs when you try to create a Go To active link action without specifying a Go To action label. To create the Go To active link action, enter a label.

8724 Error

Goto action tag must be a field or value.

This message occurs when you try to create a Go To active link action without specifying a field or value for the Go To action tag. To create the Go To active link action, use a field or value.

8725 Error

Continuation button title is empty or too long.

The button title cannot be empty or longer than the defined size of the button. If the title is empty, supply a title. If the title is too long, shorten the title or lengthen the button.

8726 Error

Guide calling itself is not allowed.

The guide cannot contain workflow that calls that same guide.

8727 Error

Invalid external table name in a vendor field mapping definition.

The name identified in the vendor field definition is empty or exceeds the defined length restriction.

8728 Error

Invalid vendor form definition.

The name identified in the vendor form definition is empty.

8730 Error

Changing the field mapping is not allowed for join fields.

The field definition for a field on a join form may not be modified after the field is defined. However, you can modify it without error by setting it to the existing mapping.

8731 Error

Changing the type in the field mapping structure is not allowed.

When modifying an existing field in a form, you tried to change a field to a different type.

8732 Error

Client type must be a non-negative integer.

You tried to define a disabled or nonexistent client type in the client list by setting the client type to a number less than zero.

8733 Error

Unrecognized currency part tag.

The currency part structure tag contains an illegal value.

8734 Error

Invalid currency code string length.

The currency code is not a valid three character string, for example, USD.

8735 Error

Bad decimal value.

The decimal data is formatted incorrectly. Only numeric characters are valid as decimal data. For example, 1.234 is a valid decimal value, while 1.abc##345 is an invalid decimal value.

8736 Error

An arithmetic error was encountered in a decimal calculation.

Your system is unable to complete the arithmetic operation. Contact your BMC Remedy AR System administrator for assistance.

8737 Error

Notify header name cannot exceed 255 bytes.

Enter a header name of 255 bytes or less for the email notification template.

8738 Error

Notify footer name cannot exceed 255 bytes.

Enter a footer name of 255 bytes or less for the email notification template.

8739 Error

Notify content name cannot exceed 255 bytes.

Enter a content name of 255 bytes or less for the email notification template.

8740 ErrorUnable to create a server thread.
8741 ErrorUnable to create a mutex.
8742 ErrorUnable to create a semaphore.
8743 ErrorUnable to lock a mutex.
8744 ErrorUnable to perform semaphore operation.
8745 ErrorUnable to create a queue to process RPC requests.
8746 ErrorUnable to allocate thread local storage.
8747 Error

Unable to access thread local storage.

The BMC Remedy AR System server encountered a serious error performing a fundamental operating system function. The most likely cause is that the system is out of memory.

8748 ErrorSemaphore operation timed out.
8749 ErrorApproaching physical stack limit.
8750 Error

Create entry operations are not supported for this form.

BMC Remedy AR System database connectivity plug-in associated with the form does not support create operations and a creation was attempted.

8751 Error

Set entry operations are not supported for this form.

BMC Remedy AR System database connectivity plug-in associated with the form does not support modify operations and a modification was attempted.

8752 Error

Delete entry operations are not supported for this form.

BMC Remedy AR System database connectivity plug-in associated with the form does not support delete operations and a deletion was attempted.

8753 Error

Error in plugin.

A run-time exception occurred during a Java plug-in server call to a plug-in. AR System adds detailed information about the error to the ARServerInstallDir\Arserver\Db\arjavaplugin.log file.

8754 Error

Retrieving attachment data is not supported for this form.

BMC Remedy AR System database connectivity plug-in does not support attachments.

8755 Error

The specified plug-in does not exist.

BMC Remedy AR System server referenced a plug-in that the plug-in service has not loaded. For more information, see Troubleshooting plug-in issues.

8756 Error

An error has occurred while loading a plug-in.

The plug-in service could not load the specified plug-in. An associated error message contains details.

8758 Error

The plug-in name is empty, contains invalid characters, or is a reserved name. The plug-in will not load.

Plug-in names may not be empty, may not contain space characters, and may not be a reserved name, such as "AREA."

8759 Error

The plug-in does not implement ARPluginIdentify(). The plug-in will not load.

All plug-ins must define the function ARPluginIdentify() and the specified plug-in does not do so.

8760 Error

Cannot establish a network connection to the BMC Remedy AR System Plug-In server.

Error 8760 and error 8939 can be caused by a plug-in operation that fails when the AR System server's connection to the plug-in server fails. Either a configuration problem exists, or the plug-in server is not running. Some operations that can generate this error are initial login to the AR System server, an attempt to create a vendor form, interaction with ITSM consoles, or any other operation supported by plug-in functionality. To diagnose the cause of this error, check these items:

  • Confirm that the plug-in server is running:
    • (UNIX) Confirm that the arplugin process is running.
    • (Windows) Check the Windows Task Manager to confirm that arplugin.exe is running.
    • If plug-in logging is turned on, check the output at the time the error occurred to verify the state of the plug-in server.
  • Verify that plug-ins are correctly configured to load when the plug-in server starts and that each is successfully loading:
    • View the contents of the ar.conf or ar.cfg file. For each entry with the format Plugin: <pathToPlug-inLibrary>, verify that the plug-in library exists in the specified location and has permissions and ownership consistent with other AR System server libraries and binaries in the <ARSystemInstallDir>/bin directory.
    • Turn on Plug-in Server logging, and set the Plugin Log Level to All. Verify that each plug-in listed in the ar.conf or ar.cfg file appears with a successful start in the log file.
  • Determine which plug-in is associated with the error and, if possible, the events that lead to the error:
    • To help isolate the workflow or operation triggering the error, turn on server API and Filter logging.
    • To identify the API call that results in the error, turn on client-side ARAPILOGGING on a client computer where the error appears.
  • Although the plug-in server can use a portmapper to troubleshoot this error, consider setting a plug-in port and a Server-Plugin-Alias setting in the configuration file to see whether it resolves the problem. For information about these settings, see Configuring a server to use plug-ins.
  • If the plug-in connection error is related to a BMC Remedy application, make sure that you have applied the latest patches for the application.

For more troubleshooting information, see the BMC Remedy Support Knowledge Base at http://www.bmc.com/support.

8761 Error

An invalid password has been used for access to the plug-in server. Contact your BMC Remedy AR System Administrator for assistance.

The plug-in server password was established to restrict access to BMC Remedy AR System servers that are similarly configured. In this case, the password used by BMC Remedy AR System server does not match that of the plug-in service.

8762 Error

The specified plug-in failed to initialize properly. Contact your BMC Remedy AR System Administrator for assistance.

The plug-in encountered an error while trying to initialize and failed to load.

8763 Error

The specified plug-in failed to set properties.

The set property function of the specified plug-in failed in some way.

8764 Error

Error while loading the native plugin hosting library arpluginjni.

This error from the Java plug-in server is logged to the arjavaplugin.log file. The Java plug-in server can host native and C plug-ins. It does this by first loading the arpluginjnia JNI- based library that hosts the C plug-ins. This error indicates that the Java plug-in server Java Virtual Machine could not find or load the JNI-based arpluginjni library that hosts the C plug-ins library, which results in none of the native plug-ins configured being loaded. You can ignore this error if you are not using C plug-ins in the Java plug-in server. The Java plug-ins will function without any problems. The appended text indicate the problem, such as if the file could not be found or dependencies could not be found. Make sure the arpluginjni library and all its dependencies are in the system PATH.

8765 Error

Error while initializing the JNI type manager for native plugins.

This error from the Java plug-in server is logged to the arjavaplugin.log file. The Java plug-in server can host native and C plug-ins. It does this by first loading the arpluginjnia JNI- based library that hosts the C plug-ins. The Java objects are converted to C structures by the ARTypeManager JNI layer. This is an internal error and indicates that the type manager could not be initialized. If you are unable to resolve the problem, contact Customer Support.

8766 Error

Error encountered while invoking a Native plugin host call.

This is error from the Java plug-in server is logged to the arjavaplugin.log file. The Java plug-in server can host native and C plug-ins. It does this by first loading the arpluginjnia JNI- based library that hosts the C plug-ins. This is an internal error and indicates that a call to a C plug-in could not be made even though the plug-in has been loaded successfully. If you are unable to resolve the problem, contact Customer Support.

8767 Error

Error while loading Java wrapper for native plugin.

All C plug-ins loaded by the Java plug-in server are internally represented as Java plug-ins. This is an internal error and indicates that although the C plug-in was loaded successfully, the Java plug-in wrapper failed to load. If you are unable to resolve the problem, contact Customer Support.

8768 Error

Could not load/Save the plugin server configuration file.

This error indicates that the pluginsvr_config.xml plug-in server configuration file could not be loaded. Make sure that the plug-in server configuration file is in the class path of the Java plug-in server.

8769 Error

Invalid configuration for a plugin. One of the required values was not provided.

An invalid value was provided for one of the parameters in the plug-in configuration in the pluginsvr_config.xml file. Make sure the values provided for configuration items in the plug-in server configuration are valid. For more information, see Configuring a server to use plug-ins.

8770 Error

The RPC socket number for plug-in loopback is not one of the legal values (390621 - 390634, 390636 - 390669, 390680 - 390694).

The value specified for the plug-in loopback RPC socket number in the configuration file is not in the acceptable range. Choose a number in the listed range.

8771 Error

Duplicate name detected for plugin. Skipping duplicate entry.

Plug-ins are identified by their names. Make sure that the names configured for plug-ins are unique.

8780 Error

Duplicate User.

BMC Remedy AR System does not support duplicate user names, such as two users called XYZ who use different passwords or belong to different user groups. User names must be unique. Contact your BMC Remedy AR System administrator.

8781 Error

Invalid Command line arguments. Usage: java ARPluginServerMain -x hostname -t portnum -i workingfolder.

Invalid or missing values were supplied for the Java plug-in server startup. Make sure the command-line arguments are valid.

8782 Error

Invalid port number. Usage: java ARPluginServerMain -x hostname -t portnum -i workingfolder.

The TCP port number to which the plug-in server will bind must have a valid value. Specify a free port in the range between 1 and 65000.

8783 Error

Unknown host. Usage: java ARPluginServerMain -x hostname -t portnum -i workingfolder.

The host name used for the Java plug-in server is invalid. Supply a valid value.

8784 Error

Data encryption error encountered.

Depending on the encryption policy, all data flowing between the AR System server and the plug-in server is encrypted unless the policy not to use encryption is chosen. An error occurred while data was being encrypted to be sent to the server. Try using a different encryption policy or algorithm.

8785 Error

Data decryption error encountered.

Depending on the encryption policy, all data flowing between the AR System server and the plug-in server is encrypted, unless the policy is chosen not to use encryption. An error occurred while data coming from the AR System server was being decrypted. Try using a different encryption policy or algorithm.

8786 Error

Error while setting up public/private key pair.

The plug-in server sets up the encryption keys for key exchange between a client (the AR System server in this case) and the server (plug-in server). An error occurred while these keys were being set up. Try using a different encryption policy or algorithm.

8787 Error

Error fetching private key.

The plug-in server sets up the encryption keys for key exchange between a client (the AR System server in this case) and the server (plug-in server). An error occurred while a private key was being fetched. Try using a different encryption policy or algorithm.

8788 Error

Error fetching public key.

The plug-in server sets up the encryption keys for key exchange between a client (the AR System server in this case) and the server (plug-in server). An error occurred while a public key was being fetched. Try using a different encryption policy or algorithm.

8789 Error

Error encountered while encoding string to bytes.

All string data sent to the AR System server from Java plug-in server is transcoded from the plug-in server character set to the AR System server character set. An error was encountered while encoding string to bytes using the AR System server character set. If you are unable to resolve the problem, contact Customer Support.

8790 Error

Unknown system error.

This error most commonly occurs when an exception occurred while processing a call that is not recognized by the plug-in server. The most common cause is uncaught exceptions encountered in the plug-ins, like null pointer exceptions.

8791 NoteAR System Plugin Server Version 7.1.0. Started up.
8792 Error

Exception occurred while loading the native plugin host library.

This error from the Java plug-in server is logged to the arjavaplugin.log file. The Java plug-in server can host native and C plug-ins. It does this by first loading the arpluginjnia JNI- based library that hosts the C plug-ins. This error indicates that the plug-in server Java Virtual Machine could not find or load this library, which results in none of the configured native plug-ins being loaded. You can ignore this error if you are not using C plug-ins in the Java plug-in server. The Java plug-ins still function without problems. The appended text indicates the problem, such as if the file could not be found or dependencies could not be found. Make sure the arpluginjni library and all its dependencies are in the system PATH.

8793 Error

AR Plugin Server Startup Error.

A fatal error was encountered during plug-in server startup. To resolve the issues, check the log files for information about the reason for the failure.

8794 Error

Plugin Termination Error.

When a thread goes down in the plug-in server, the terminate method is called on all the plug-ins. An error occurred during one of the terminate calls. See the log files for details.

8795 Error

Plugin Create Instance Error.

Create instance is called on each plug-in on a new thread startup so that plug-ins can create an instance of any thread safe data and save it in the plug-in server thread's context. An exception occurred while an instance was being created. See the log file for details.

8796 Error

Plugin Delete Instance Error.

Delete instance is called on each plug-in on a thread shutdown so plug-ins can clean up any thread safe data that was saved in the plug-in server thread's context. An exception occurred while an instance was being deleted. See the log file for details.

8797 Error

Error encountered while encoding bytes to string string .

All string data sent to the AR System server from Java plug-in server is transcoded from the plug-in server character set to the AR System server character set. An error was encountered while encoding a string to bytes using the server character set. If you are unable to resolve the problem, contact Support.

NumberDescription
8552 ErrorConfiguration-Name is missing from the configuration file.
8570
Error
JDBC Custom function not defined.;
Function testfunction is not defined in
AR System JDBC:Generic Db Functions Form for database SQL Server
8571
Error
Minimum parameters mismatch in function definition and execution;
minimum parameters not present for the function testfunction
8572
Error
Parameters mismatch in function definition and execution;
Argument 2 is defined in AR System JDBC:Generic Db Functions
form but not passed in the function
8573
Error
Parameters type mismatch in function definition and execution;
Argument 2  passed to function testfunction have dataType [CHAR] ,
which is not compatible with function argument type defined in AR
System JDBC:Generic Db Functions Form [Integer]
8574
Error
Some error occured fetching functions parameters type
8610 Error
Please ensure correct overlay specific group(s) for the user.

The error can occur due to the restrictions added for the users and groups. 

8700 Error

Attachment locator types can only be filename or the buffer. Use only these types.

The only acceptable attachment locator types are the filename or the buffer. Use only these types.

8701 ErrorBad attachment locator buffer size.
8702 ErrorBad attachment locator buffer pointer.
8703 ErrorBad attachment size.
8704 Error

OLE Automation active link action cannot be empty.

The automation structure required when you define an OLE Automation active link action is empty. Specify the appropriate contents for this structure.

8705 Error

OLE Automation active link action method list cannot be empty.

The method list required when you define an OLE Automation active link action is empty. Provide at least one method for this structure.

8706 Error

Bad ARCOMValueStruct variable value.

The value of an ARCOMValueStruct variable in a method or parameter of an OLE Automation active link action is invalid. Provide a valid value.

8707 Error

Bad OLE server or parameter name.

The name of an OLE server or a parameter of an OLE Automation active link action is empty or exceeding the maximum length allowed (64 characters). Fix the name to continue your work.

8708 Error

Bad OLE class ID or method ID, or interface of an OLE automation active link.

The name of an OLE class ID, a method ID, or an interface of an OLE Automation active link action is either empty or exceeding the maximum length allowed (128 characters).

8709 Error

Bad OLE Automation active link action Method.

The method structure of the OLE Automation active link action is invalid. Detailed errors follow that explain what part of the method structure is invalid.

8710 Error

Bad OLE Automation active link action Method name.

The name of a method in an OLE Automation either is empty or exceeds the maximum length allowed (128 characters).

8711 Error

Empty OLE Automation active link action Method.

The method structure required when you define an OLE Automation active link action is empty. Provide at least one method for this structure.

8712 Error

Empty OLE Automation active link action Parameter List.

The parameter list required when you define an OLE Automation active link action is empty. Provide at least one method for this structure.

8713 Error

Empty OLE Automation active link action Parameter.

The parameter structure of a method required when you define a method in an OLE Automation active link action is empty. Specify the appropriate contents for this structure.

8714 Error

Bad OLE Automation active link action Parameter.

The parameter structure of a method in this OLE Automation active link action is invalid. Detailed error messages explain what part of the structure is invalid.

8715 Error

Bad automation string in the OLE Automation active link action.

An automation action string required when you define an OLE Automation active link action either is empty or exceeds the maximum length allowed (2000 characters).

8716 Error

The RPC socket number for the Approval Server process is not one of the legal values (390600, 390621 - 390634, 390636 - 390669, 390680 - 390694).

The value for the RPC socket is not set properly. Use the Approval Server Admin-Server Settings form to set this to a legal value.

8717 Error

The value for the Application check interval is not within the legal range of 0 to 3600 seconds.

The value for Application Check Interval is not set properly. Set this to a legal value.

8718 WarningThe signal %d is not valid and is ignored.
8720 Error

Open dialog value is empty.

This message occurs when you try to create an Open Dialog active link action without specifying an open dialog structure value. To create the Open Dialog active link action, enter a value.

8721 Error

Call guide ID is empty.

This message occurs when you try to create a Call Guide active link action without specifying a Call Guide structure value. To create the Call Guide active link action, enter a value.

8722 Error

Guide name missing.

This message occurs when you try to create a Call Guide active link action without specifying a Call Guide active link name. To create the Call Guide active link action, enter a name.

8723 Error

Goto active link action label empty or too long.

This message occurs when you try to create a Go To active link action without specifying a Go To action label. To create the Go To active link action, enter a label.

8724 Error

Goto action tag must be a field or value.

This message occurs when you try to create a Go To active link action without specifying a field or value for the Go To action tag. To create the Go To active link action, use a field or value.

8725 Error

Continuation button title is empty or too long.

The button title cannot be empty or longer than the defined size of the button. If the title is empty, supply a title. If the title is too long, shorten the title or lengthen the button.

8726 Error

Guide calling itself is not allowed.

The guide cannot contain workflow that calls that same guide.

8727 Error

Invalid external table name in a vendor field mapping definition.

The name identified in the vendor field definition is empty or exceeds the defined length restriction.

8728 Error

Invalid vendor form definition.

The name identified in the vendor form definition is empty.

8730 Error

Changing the field mapping is not allowed for join fields.

The field definition for a field on a join form may not be modified after the field is defined. However, you can modify it without error by setting it to the existing mapping.

8731 Error

Changing the type in the field mapping structure is not allowed.

When modifying an existing field in a form, you tried to change a field to a different type.

8732 Error

Client type must be a non-negative integer.

You tried to define a disabled or nonexistent client type in the client list by setting the client type to a number less than zero.

8733 Error

Unrecognized currency part tag.

The currency part structure tag contains an illegal value.

8734 Error

Invalid currency code string length.

The currency code is not a valid three character string, for example, USD.

8735 Error

Bad decimal value.

The decimal data is formatted incorrectly. Only numeric characters are valid as decimal data. For example, 1.234 is a valid decimal value, while 1.abc##345 is an invalid decimal value.

8736 Error

An arithmetic error was encountered in a decimal calculation.

Your system is unable to complete the arithmetic operation. Contact your BMC Remedy AR System administrator for assistance.

8737 Error

Notify header name cannot exceed 255 bytes.

Enter a header name of 255 bytes or less for the email notification template.

8738 Error

Notify footer name cannot exceed 255 bytes.

Enter a footer name of 255 bytes or less for the email notification template.

8739 Error

Notify content name cannot exceed 255 bytes.

Enter a content name of 255 bytes or less for the email notification template.

8740 ErrorUnable to create a server thread.
8741 ErrorUnable to create a mutex.
8742 ErrorUnable to create a semaphore.
8743 ErrorUnable to lock a mutex.
8744 ErrorUnable to perform semaphore operation.
8745 ErrorUnable to create a queue to process RPC requests.
8746 ErrorUnable to allocate thread local storage.
8747 Error

Unable to access thread local storage.

The BMC Remedy AR System server encountered a serious error performing a fundamental operating system function. The most likely cause is that the system is out of memory.

8748 ErrorSemaphore operation timed out.
8749 ErrorApproaching physical stack limit.
8750 Error

Create entry operations are not supported for this form.

BMC Remedy AR System database connectivity plug-in associated with the form does not support create operations and a creation was attempted.

8751 Error

Set entry operations are not supported for this form.

BMC Remedy AR System database connectivity plug-in associated with the form does not support modify operations and a modification was attempted.

8752 Error

Delete entry operations are not supported for this form.

BMC Remedy AR System database connectivity plug-in associated with the form does not support delete operations and a deletion was attempted.

8753 Error

Error in plugin.

A run-time exception occurred during a Java plug-in server call to a plug-in. AR System adds detailed information about the error to the ARServerInstallDir\Arserver\Db\arjavaplugin.log file.

8754 Error

Retrieving attachment data is not supported for this form.

BMC Remedy AR System database connectivity plug-in does not support attachments.

8755 Error

The specified plug-in does not exist.

BMC Remedy AR System server referenced a plug-in that the plug-in service has not loaded. For more information, see Troubleshooting plug-in issues.

8756 Error

An error has occurred while loading a plug-in.

The plug-in service could not load the specified plug-in. An associated error message contains details.

8758 Error

The plug-in name is empty, contains invalid characters, or is a reserved name. The plug-in will not load.

Plug-in names may not be empty, may not contain space characters, and may not be a reserved name, such as "AREA."

8759 Error

The plug-in does not implement ARPluginIdentify(). The plug-in will not load.

All plug-ins must define the function ARPluginIdentify() and the specified plug-in does not do so.

8760 Error

Cannot establish a network connection to the BMC Remedy AR System Plug-In server.

Error 8760 and error 8939 can be caused by a plug-in operation that fails when the AR System server's connection to the plug-in server fails. Either a configuration problem exists, or the plug-in server is not running. Some operations that can generate this error are initial login to the AR System server, an attempt to create a vendor form, interaction with ITSM consoles, or any other operation supported by plug-in functionality. To diagnose the cause of this error, check these items:

  • Confirm that the plug-in server is running:
    • (UNIX) Confirm that the arplugin process is running.
    • (Windows) Check the Windows Task Manager to confirm that arplugin.exe is running.
    • If plug-in logging is turned on, check the output at the time the error occurred to verify the state of the plug-in server.
  • Verify that plug-ins are correctly configured to load when the plug-in server starts and that each is successfully loading:
    • View the contents of the ar.conf or ar.cfg file. For each entry with the format Plugin: <pathToPlug-inLibrary>, verify that the plug-in library exists in the specified location and has permissions and ownership consistent with other AR System server libraries and binaries in the <ARSystemInstallDir>/bin directory.
    • Turn on Plug-in Server logging, and set the Plugin Log Level to All. Verify that each plug-in listed in the ar.conf or ar.cfg file appears with a successful start in the log file.
  • Determine which plug-in is associated with the error and, if possible, the events that lead to the error:
    • To help isolate the workflow or operation triggering the error, turn on server API and Filter logging.
    • To identify the API call that results in the error, turn on client-side ARAPILOGGING on a client computer where the error appears.
  • Although the plug-in server can use a portmapper to troubleshoot this error, consider setting a plug-in port and a Server-Plugin-Alias setting in the configuration file to see whether it resolves the problem. For information about these settings, see Configuring a server to use plug-ins.
  • If the plug-in connection error is related to a BMC Remedy application, make sure that you have applied the latest patches for the application.

For more troubleshooting information, see the BMC Remedy Support Knowledge Base at http://www.bmc.com/support.

8761 Error

An invalid password has been used for access to the plug-in server. Contact your BMC Remedy AR System Administrator for assistance.

The plug-in server password was established to restrict access to BMC Remedy AR System servers that are similarly configured. In this case, the password used by BMC Remedy AR System server does not match that of the plug-in service.

8762 Error

The specified plug-in failed to initialize properly. Contact your BMC Remedy AR System Administrator for assistance.

The plug-in encountered an error while trying to initialize and failed to load.

8763 Error

The specified plug-in failed to set properties.

The set property function of the specified plug-in failed in some way.

8764 Error

Error while loading the native plugin hosting library arpluginjni.

This error from the Java plug-in server is logged to the arjavaplugin.log file. The Java plug-in server can host native and C plug-ins. It does this by first loading the arpluginjnia JNI- based library that hosts the C plug-ins. This error indicates that the Java plug-in server Java Virtual Machine could not find or load the JNI-based arpluginjni library that hosts the C plug-ins library, which results in none of the native plug-ins configured being loaded. You can ignore this error if you are not using C plug-ins in the Java plug-in server. The Java plug-ins will function without any problems. The appended text indicate the problem, such as if the file could not be found or dependencies could not be found. Make sure the arpluginjni library and all its dependencies are in the system PATH.

8765 Error

Error while initializing the JNI type manager for native plugins.

This error from the Java plug-in server is logged to the arjavaplugin.log file. The Java plug-in server can host native and C plug-ins. It does this by first loading the arpluginjnia JNI- based library that hosts the C plug-ins. The Java objects are converted to C structures by the ARTypeManager JNI layer. This is an internal error and indicates that the type manager could not be initialized. If you are unable to resolve the problem, contact Customer Support.

8766 Error

Error encountered while invoking a Native plugin host call.

This is error from the Java plug-in server is logged to the arjavaplugin.log file. The Java plug-in server can host native and C plug-ins. It does this by first loading the arpluginjnia JNI- based library that hosts the C plug-ins. This is an internal error and indicates that a call to a C plug-in could not be made even though the plug-in has been loaded successfully. If you are unable to resolve the problem, contact Customer Support.

8767 Error

Error while loading Java wrapper for native plugin.

All C plug-ins loaded by the Java plug-in server are internally represented as Java plug-ins. This is an internal error and indicates that although the C plug-in was loaded successfully, the Java plug-in wrapper failed to load. If you are unable to resolve the problem, contact Customer Support.

8768 Error

Could not load/Save the plugin server configuration file.

This error indicates that the pluginsvr_config.xml plug-in server configuration file could not be loaded. Make sure that the plug-in server configuration file is in the class path of the Java plug-in server.

8769 Error

Invalid configuration for a plugin. One of the required values was not provided.

An invalid value was provided for one of the parameters in the plug-in configuration in the pluginsvr_config.xml file. Make sure the values provided for configuration items in the plug-in server configuration are valid. For more information, see Configuring a server to use plug-ins.

8770 Error

The RPC socket number for plug-in loopback is not one of the legal values (390621 - 390634, 390636 - 390669, 390680 - 390694).

The value specified for the plug-in loopback RPC socket number in the configuration file is not in the acceptable range. Choose a number in the listed range.

8771 Error

Duplicate name detected for plugin. Skipping duplicate entry.

Plug-ins are identified by their names. Make sure that the names configured for plug-ins are unique.

8780 Error

Duplicate User.

BMC Remedy AR System does not support duplicate user names, such as two users called XYZ who use different passwords or belong to different user groups. User names must be unique. Contact your BMC Remedy AR System administrator.

8781 Error

Invalid Command line arguments. Usage: java ARPluginServerMain -x hostname -t portnum -i workingfolder.

Invalid or missing values were supplied for the Java plug-in server startup. Make sure the command-line arguments are valid.

8782 Error

Invalid port number. Usage: java ARPluginServerMain -x hostname -t portnum -i workingfolder.

The TCP port number to which the plug-in server will bind must have a valid value. Specify a free port in the range between 1 and 65000.

8783 Error

Unknown host. Usage: java ARPluginServerMain -x hostname -t portnum -i workingfolder.

The host name used for the Java plug-in server is invalid. Supply a valid value.

8784 Error

Data encryption error encountered.

Depending on the encryption policy, all data flowing between the AR System server and the plug-in server is encrypted unless the policy not to use encryption is chosen. An error occurred while data was being encrypted to be sent to the server. Try using a different encryption policy or algorithm.

8785 Error

Data decryption error encountered.

Depending on the encryption policy, all data flowing between the AR System server and the plug-in server is encrypted, unless the policy is chosen not to use encryption. An error occurred while data coming from the AR System server was being decrypted. Try using a different encryption policy or algorithm.

8786 Error

Error while setting up public/private key pair.

The plug-in server sets up the encryption keys for key exchange between a client (the AR System server in this case) and the server (plug-in server). An error occurred while these keys were being set up. Try using a different encryption policy or algorithm.

8787 Error

Error fetching private key.

The plug-in server sets up the encryption keys for key exchange between a client (the AR System server in this case) and the server (plug-in server). An error occurred while a private key was being fetched. Try using a different encryption policy or algorithm.

8788 Error

Error fetching public key.

The plug-in server sets up the encryption keys for key exchange between a client (the AR System server in this case) and the server (plug-in server). An error occurred while a public key was being fetched. Try using a different encryption policy or algorithm.

8789 Error

Error encountered while encoding string to bytes.

All string data sent to the AR System server from Java plug-in server is transcoded from the plug-in server character set to the AR System server character set. An error was encountered while encoding string to bytes using the AR System server character set. If you are unable to resolve the problem, contact Customer Support.

8790 Error

Unknown system error.

This error most commonly occurs when an exception occurred while processing a call that is not recognized by the plug-in server. The most common cause is uncaught exceptions encountered in the plug-ins, like null pointer exceptions.

8791 NoteAR System Plugin Server Version 7.1.0. Started up.
8792 Error

Exception occurred while loading the native plugin host library.

This error from the Java plug-in server is logged to the arjavaplugin.log file. The Java plug-in server can host native and C plug-ins. It does this by first loading the arpluginjnia JNI- based library that hosts the C plug-ins. This error indicates that the plug-in server Java Virtual Machine could not find or load this library, which results in none of the configured native plug-ins being loaded. You can ignore this error if you are not using C plug-ins in the Java plug-in server. The Java plug-ins still function without problems. The appended text indicates the problem, such as if the file could not be found or dependencies could not be found. Make sure the arpluginjni library and all its dependencies are in the system PATH.

8793 Error

AR Plugin Server Startup Error.

A fatal error was encountered during plug-in server startup. To resolve the issues, check the log files for information about the reason for the failure.

8794 Error

Plugin Termination Error.

When a thread goes down in the plug-in server, the terminate method is called on all the plug-ins. An error occurred during one of the terminate calls. See the log files for details.

8795 Error

Plugin Create Instance Error.

Create instance is called on each plug-in on a new thread startup so that plug-ins can create an instance of any thread safe data and save it in the plug-in server thread's context. An exception occurred while an instance was being created. See the log file for details.

8796 Error

Plugin Delete Instance Error.

Delete instance is called on each plug-in on a thread shutdown so plug-ins can clean up any thread safe data that was saved in the plug-in server thread's context. An exception occurred while an instance was being deleted. See the log file for details.

8797 Error

Error encountered while encoding bytes to string string .

All string data sent to the AR System server from Java plug-in server is transcoded from the plug-in server character set to the AR System server character set. An error was encountered while encoding a string to bytes using the server character set. If you are unable to resolve the problem, contact Support.

Was this page helpful? Yes No Submitting... Thank you

Comments