Differences

This shows you the differences between two versions of the page.

Link to this comparison view

bmc:remedy:message-catalog:8760 [2015/03/28 03:14]
Giuseppe Di Terlizzi creata
bmc:remedy:message-catalog:8760 [2015/06/04 00:51] (current)
Giuseppe Di Terlizzi
Line 1: Line 1:
 {{:bmc:remedy:remedy-logo.png?nolink&16 |}} **AR System Message Catalog** {{:bmc:remedy:remedy-logo.png?nolink&16 |}} **AR System Message Catalog**
  
-====== Cannot establish a network connection to the AR System Plug-In server. ======+====== ARERR [8760] Cannot establish a network connection to the AR System Plug-In server. ======
  
 \\ \\
Line 15: Line 15:
 \\ \\
  
-{{bmc:remedy:error.gif?nolink |}} Error 8760 and error 8939 can be caused by a plug''-i''operation that fails when the AR System server's connection to the plug''-i''server fails. Either a configuration problem exists, or the plug''-i''server is not running.\\ +{{bmc:remedy:error.gif?nolink |}} 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''-i''functionality.\\+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:\\ To diagnose the cause of this error, check these items:\\
-  *  Confirm that the plug''-i''server is running:\\+  *  Confirm that the plug-in server is running:\\
 (UNIX) Confirm that the ''arplugin'' process is running.\\ (UNIX) Confirm that the ''arplugin'' process is running.\\
 (Windows) Check the Windows Task Manager to confirm that ''arplugin''.exe is running.\\ (Windows) Check the Windows Task Manager to confirm that ''arplugin''.exe is running.\\
-If plug''-i''logging is turned on, check the output at the time the error occurred to verify the state of the plug''-i''server.\\ +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''-i''ns are correctly configured to load when the plug''-i''server starts and that each is successfully loading:\\ +  *  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''-i''nLibrary, verify that the plug''-i''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.\\ +View the contents of the ''ar.conf'' or ''ar.cfg'' file. For each entry with the format Plugin:pathToPlug''-i''nLibrary, 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''-i''n Server logging, and set the Plugin Log Level to All. Verify that each plug''-i''listed in the ''ar.conf'' or ''ar.cfg'' file appears with a successful start in the log file.\\ +Turn on Plug''-i''n 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''-i''is associated with the error and, if possible, the events that lead to the error:\\+  *  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 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.\\ 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''-i''server can use a portmapper to troubleshoot this error, consider setting a plug''-i''port and a Server-Plugin-Alias setting in the configuration file to see whether it resolves the problem. For information about these settings, see the //Configuration Guide//.\\ +  *  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 the //Configuration Guide//.\\ 
-  *  If the plug''-i''connection error is related to a BMC Remedy application, make sure that you have applied the latest patches for the application.\\+  *  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.\\ For more troubleshooting information, see the BMC Remedy Support Knowledge Base at http://www.bmc.com/support.\\
  
Line 38: Line 38:
 \\ \\
  
-[[:bmc:remedy:message-catalog:start|Go back]]+[[:bmc:remedy:message-catalog:start|<= Go back]]
  
  
  • bmc/remedy/message-catalog/8760.1427508841.txt.gz
  • Last modified: 6 years ago
  • by Giuseppe Di Terlizzi