BP v7.0.1 upgrade and callback channel error

[HongJooChoi]

Hi, Community.

Can anyone guide us regarding the following error message?

We have upgraded the BP from 6.8.1 to 7.0.1 and ASCR setting remained as default with its port = 10000, hostname = localhost, callback = gRPC.

We changed the port number to 20000 for try and fortunately, the server started successfully at the moment.


Since then, we have tested the RR by drag-n-drop the process from the control room, when we came across the following error:


Would there be any way to troubleshoot this?


Best regards




------------------------------
HongJoo Choi
------------------------------

[steven.boggs]

Hello,

We have a Knowledge Base article that describes this error with some troubleshooting steps to try; "Why do I get error message "Unable to establish communication with server callback channel." when trying to run a process after upgrading to Blue Prism 7?"

Have you reviewed this and implemented the suggestions? If so, what were the results?

Hope this helps.

------------------------------
Steve Boggs
Senior Product Support Engineer
Blue Prism
Austin, TX
------------------------------

[Tejaskumar_Darji]

This article page is not loading

------------------------------
If I was of assistance, please vote for it to be the "Best Answer".

Thanks & Regards,
Tejaskumar Darji - https://www.linkedin.com/in/tejaskumardarji/
Technical Lead
------------------------------

[kgupta]

I have the same issue, page is not loading and getting the error - 

Unable to establish communication with server callback channel. This will prevent certain features from functioning properly. If this error persists, please consult the documentation: https://bpdocs.blueprism.com/bp-7-3/en-us/ascr/ascr.htm

[Michael_S]

Try this link instead:

https://support.blueprism.com/en/support/solutions/articles/7000076986-bpe-error-unable-to-establish-communication-with-server-callback-channel-when-trying-to-run-a-proc 

[kgupta]

Thanks, I was able to resolve this error by opening inbound port 10000 on the App Server.

[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