Last Updated: May 10, 2022
When I start the Developer Bot I get the error "Connection to Jiffy Server failed". This error occurs when Jiffy Server you are connecting to is down, Jiffy services are not running, or some firewall/antivirus is blocking Jiffy services.
It is recommended not to restart Jiffy System Manager and Jiffy JPipe Client services in multi-bot machines, as it can impact other bots which are in use.
I am trying to install Jiffy Client. I do have admin rights but when I run the diagnostic test, I get that it failed for Permissions for Admin and Connectors. This occurs when Jiffy Client installer and Diagnostic Report is not run as an Administrator.
I get “Requested machine is not registered with Jiffy” message when I start the Bot, as in the following screenshot. Register your machine and restart the Bot.
I am unable to start the Execution bots from Jiffy Bot Console. If the execution bot is not starting,
Make sure that you have logged in to the remote machine with the same user which was used while creating the execution Bot.
When starting the execution bot, error “User-Level service is down. Please check the BOT Machine” is displayed. How can I get this issue resolved?
Am unable to start the execution Bot. The status is Not Running and the error “Please check if the Jiffy system manager is running on the machine” is displayed. How can I start the execution bot? This issue is seen when the bot user doesn’t have admin privileges or the Jiffy System Manager is down.
This issue occurs when the number of bots reach its maximum allowed licensed Bot limit. If you're having trouble starting the execution bot from bot management page, try starting the developer bot on your machine. If you encounter the error message "Bot count has reached the allowed limit", that confirms the bot limit is reached the allowed licensed bot. Check the Jiffy Service Log to investigate the issue further. Raise a separate request if the bot limit needs to be increased. Please refer to the licensing steps here.
Oracle GSM forms fail to load after installing jiffy 4.x on the client machine This issue occurs due to permission issues.
Add the above code in in java.policy and javaws.policy files under lib\security of the jre\jdk being used to launch java apps.grant { permission java.security.AllPermission; };
When the RDP password is changed, it can prevent the user from stopping the bot from bot management. To address this, stop the javaw.exe process for the affected bot from the bot machine.