cancel
Showing results for 
Search instead for 
Did you mean: 

BOT Triggering Issue

Hello,

We are facing issue with particular series VMs. For example in the production there are VM's of different series example 10.150.87.XX and 10.150.97.XX. Both 87 series and 97 series are configured on single BP server which is 10.150.88.XX. when we run BOT files(from resource PC bat file) all the 87 series VM's gets triggered automatically according to the schedule and run the process A. But the 97 series VM's will not trigger automatically we have to trigger manually from control room. Though 97 series is scheduled to run the same process A.

We are unable to figure out the issue need your support on this.

Regards,


------------------------------
Sayeed
------------------------------
Senior Consultant - Automation Developer
Wonderbotz
4 REPLIES 4

Hi, Sayeed,

what the schedule log says? Without that I doubt that we can provide any hint. You can get there when you are in control room->Scheduler->Reports->Recent Activity. There you will see your records about schedules with errors encountered.

Regards,

------------------------------
Zdeněk Kabátek
Head of Professional Services
NEOOPS
http://www.neoops.com/
Europe/Prague
------------------------------

Hi  Kabátek,

Thanks for the response, in schedulw logs it show resource pc xxxxxxx offline - retried 10 times.

I have tried to telnet from one of the client machines to BP server and was successfully able to do so.

Appreciate you support.

Regards

------------------------------
Sayeed
------------------------------
Senior Consultant - Automation Developer
Wonderbotz

Hi, Sayeed,

well, with schedules there is a little hook - if you have a schedule which is triggering processes on more machines and one of the machines is unavailable the whole schedule will not run. Can you check this?

Do you see the resource pc as online in control room at time when the schedule is supposed to run?

Do you use Login Agent?

You wrote you telnet from machine to BP Server but could you try the opposite direction too?

Regards,

------------------------------
Zdeněk Kabátek
Head of Professional Services
NEOOPS
http://www.neoops.com/
Europe/Prague
------------------------------

Hi Kabátek,

Thank you so much for the support, i have identified that the issue was due to the firewall. Due to some security check failure firewall was not allowing to run Automate.exe which was causing the triggering issue in specific series VM's. Now we are working on to get it fixed.

Regards,


------------------------------
Sayeed
------------------------------
Senior Consultant - Automation Developer
Wonderbotz