Colin McNicholas
New Member
Hi all,
This morning we reset some BOT passwords as usual as they had expired. Once reset, the BOT was rebooted. When the BOT came back online on BP, we tried to run the start up procedure but we received an error message that the BOT is busy.
We have tried resetting the VDI session that the BOTS are associated with & we have also tried hard reboots of the VDI's but we still get the 'Busy' message when we try to run the BOT Awaken job.
Has anyone seen this type of behavior before? Is there anything else we can do to make the BOTS available again? We have a case open with BP Support but any suggestions/advice would be greatly appreciated. Thanks!
This morning we reset some BOT passwords as usual as they had expired. Once reset, the BOT was rebooted. When the BOT came back online on BP, we tried to run the start up procedure but we received an error message that the BOT is busy.
We have tried resetting the VDI session that the BOTS are associated with & we have also tried hard reboots of the VDI's but we still get the 'Busy' message when we try to run the BOT Awaken job.
Has anyone seen this type of behavior before? Is there anything else we can do to make the BOTS available again? We have a case open with BP Support but any suggestions/advice would be greatly appreciated. Thanks!