Troubleshooting external script actions

This topic describes the issues that you might encounter while running an external script action. 

An external script action fails because of an incorrect script reference

On Linux, you cannot execute external script actions because the device adapters refer to the .bat file instead of the .sh file.

Workaround: Follow these steps to resolve the issue:

1. Export the required device adapter.
2. Search for the scriptName tag and modify its value to refer to the .sh file.
3. Import the device adapter.

Cannot run an external script action due to the limited number of characters in the runtime parameter value

You cannot run the Populate Cisco End of Life Date external script action due to a limited number of characters allowed in the runtime parameter value.

Fix: Modify the number of maximum characters allowed in the runtime parameter value.

On the Admin > Network Admin > Device Adapters page, do the following:

1. Navigate to External Script Actions > End of Life > Populate End of Life Date external script action.
2. In the Actions list, click Export for the Populate End of Life Date external script action.
3. Open the exported XML file (Populate_End_of_Life_Date_Baseline.xml) with a text editor.
4. Locate the <runtimeParameter> element for the runtime parameter for which you want to increase the limit. 

5. Include the <maxSize> tag and its value, as shown in the following example for the TrueSight Network Automation Server User Name parameter (bnaServerUsername):

   <runtimeParameter>
       <name>bnaServerUsername</name>
       <prompt key="externalAction.runtimeParameter.eolUsernameBnaServer"/>
       <type>text</type>
       <required>true</required>
       <sortOrder>3</sortOrder>
       <maxSize>100</maxSize>
   </runtimeParameter>
6. Save the file.
7. On the Device Adapters page, import the modified file.