Ensure you’re using the latest versions of your third-party actions and variables
If you’re using any third party actions or variables, it’s really important to make sure that they are up-to-date. You can always download the most recent version from the relevant developer site to check you have the most up-to-date actions or variables.
Make sure you’re running the latest version of Java
You can always download the latest version of Java from http://www.java.com.
We also recommend that your operating system is completely up-to-date.
Common issues
"Unable to launch the application"
If you have been using CCleaner on Windows, the application is known for deleting some files required by Action(s) to perform properly. If you run a cleaner from this application, you might get the following error message next time you will be using Action(s):
To fix this problem, click on the launch button below. It will properly re-install Action(s). None of your data will be lost.
Piriform (editor of CCleaner) has been contacted and hopefully a fix to this issue will be provided.
You can prevent the issue by unselecting the "Sun Java" option in the "Applications" tab of CCleaner before running the cleaner:
"Splash recv failed"
Users of Comodo Firewall on Windows might experience issues while using Action(s). When launching, Action(s) may display an error message: "Splash recv failed".
This is a known issue due to Comodo Firewall. The Comodo team is aware of it and is working on a fix.
In the meantime, the following action will fix the issue:
What you need to do is to add the javaws.exe application file (used by Action(s)) into the exclusion of detect shellcode injections.
javaws.exe is normally located in the folder C:\Program Files\Java\jre1.6.0_xx\bin where xx is a number.
There is often a copy in C:\Windows\system32 too. I would suggest to add it too.
To add them in the exclusion of detect shellcode injections, in Comodo Firewall settings, go in CIS > Defense+ > Defense+ Settings > Execution control Settings > Detect shellcode injections (i.e. Buffer overflow protection) > Exclusions > Add > Browse..., and select the javaws.exe file to add.
This is a known issue due to Comodo Firewall. The Comodo team is aware of it and is working on a fix.
In the meantime, the following action will fix the issue:
What you need to do is to add the javaws.exe application file (used by Action(s)) into the exclusion of detect shellcode injections.
javaws.exe is normally located in the folder C:\Program Files\Java\jre1.6.0_xx\bin where xx is a number.
There is often a copy in C:\Windows\system32 too. I would suggest to add it too.
To add them in the exclusion of detect shellcode injections, in Comodo Firewall settings, go in CIS > Defense+ > Defense+ Settings > Execution control Settings > Detect shellcode injections (i.e. Buffer overflow protection) > Exclusions > Add > Browse..., and select the javaws.exe file to add.
Personalized icons for Windows system folders and NullPointerException
If you are using Windows and have a personalized set of icons for system folders, such as “My Computer” and “My Documents”, you might face issues when using Action(s). When trying to use a file selection window (such as in the “Save” menu or the “Ask for file” action), the following error message might appear: NullPointerException. It can be easily fixed by downloading the latest version of Java at http://www.java.com. If the new version does not fix the issue, or if you are already using the latest version of Java, an alternative solution is to restore the default system icons for system folders. To do so:
- Right-click on your desktop.
2 Click on Properties from the pop-up menu.
3 Under the Desktop tab select Customize Desktop button. List of desktop items will be displayed.
4 Set default icons for all system icons in the list.
Action(s)'s desktop icon is very ugly
Action(s) created a folder with a lot of subfolders, and I cannot remove them
If you are using Action(s) 1.0.0, some workflows might create a folder containing another folder with the same name, this sub-folder containing again a folder with the same name...
This issue occurs when you create a workflow that is trying to copy a folder into itself or into one of its sub-folders. This issue is corrected in Action(s) 1.0.1 and higher versions, so we highly recommend to download the latest version of Action(s) to avoid this problem.
To download the latest version of Action(s), click on the launch button:
This issue occurs when you create a workflow that is trying to copy a folder into itself or into one of its sub-folders. This issue is corrected in Action(s) 1.0.1 and higher versions, so we highly recommend to download the latest version of Action(s) to avoid this problem.
To download the latest version of Action(s), click on the launch button:
If when you are trying to remove the faulted folder an error message tells you that the folder cannot be removed, you can still remove it using Action(s).
WARNING - This solution delete definitely the faulted folder. It is impossible to retrieve its content. The folder is not move to the Recycle Bin.
In Action(s), create a new workflow with the 2 following actions:
- Ask for files
- Delete files
If you continue to experience issues, do not hesitate to contact us. Please be sure to include as many details as possible. Most queries can be solved incredibly quickly and easily with the right information. Here’s a guideline of what we’d love to see in every email:
- Version of Action(s) (found in the Action(s) about box).
- Any built-in actions and variables you’re using.
- Any third-party actions and variables you’re using.
- Clear, reproducible steps to show the issue you’re having. If you think you’ve found a bug in Action(s), please ensure that you can easily and consistently reproduce the error and let us know the steps that you are using. For bug reports, this is absolutely essential.
