BP 7.1 - Runtime Resource ASCR configuration

[FelixGerdwilker]

Dear community,

I am reaching out as we want to upgrade to BP 7.1. So far everything looks sharp. We were able to schedule processes over our App server.

Now when our developers want to run a process from one resource on an other. We hit issues with ASCR:

I checked the documentation and there was nothing mentioned on specific settings for the ASCR.

The server is configured to use gRPC an listens on port 10000 for the callback. The RR-connections are using default settings. Even if the schedule is scheduled on the same RR we see this issue.

I checked the windows firewall which is open on port 10000 inbound. So I wonder if this is due to BP misconfiguration or some network related settings we have in our environment.

------------------------------
Felix Gerdwilker
------------------------------

[diane.sanzone · Accepted solution]

Hi Felix,

We're experiencing the same issue and actually met with BP support yesterday about that and other things. We learned that if you're using gRPC for your communication method, the port you select must be open both inbound AND outbound on both the application server AND the client resource.  If you're getting that message, it means the port isn't open somewhere or the communication is otherwise blocked.

We're still working through those configurations (we have multiple intermediary firewalls which complicate things) so I can't confirm that this is the cause, just sharing the info support gave us.

Good luck and hope this helps.

------------------------------
Diane Sanzone
------------------------------

[FelixGerdwilker]

Hi Diane,

thanks for your input. It really did the trick. We had the firewalls not configured on both sides correctly and thus it did not work. Also the callback ports were not set to the same as on the server. Finally a localhost entry snuck into the BPServer config which I am sure I had changed after I created the config. Anyway it does work now and now I will have to work on permanent changes to our firewall. Thanks a lot!

------------------------------
Felix Gerdwilker
------------------------------

[pranavred]

Make sure your ASCR setting here at hostname has the server name, and not localhost. 

------------------------------
Pranav
------------------------------

[Tejaskumar_Darji]

Thank you, this helped us fix the ASCR error. Team, update the localhost to the full FQDN name of the App Server machine in the AS machine App Server configuration.

Here’s how to check a fully qualified domain name in Windows:

1. Open the Control Panel.
2. Click on “System and Security,” then select “System.”
3. Under “Device specifications,” you will see the “Full device name,” which includes the FQDN.

FYI, we opened port 10000, but still, the ASCR error was not resolved, so after that, you can try this option and restart VMs to check how it goes.

Refer to this KB article