Release Import causes all running processes to crash

[LourdesUrena]

Hello,
Since upgrading to 6.10 we have experienced extremely slow times to import releases which never happened in prior versions and due to the huge delay experienced when there are about 10 items in the release between processes and objects, all processes running collapse and crash in Production.  The fallen activity can be seen at the database level, but nothing indicates what can be causing this problem.  Ideas?

------------------------------
Lourdes Urena
Sr Solutions Engineering
Grainger Panama Services
Panama
------------------------------

[ewilson · Accepted solution]

Hi @LourdesUrena,

I would definitely recommend opening a ticket with support on this. For my own curiosity, does the release contain any common VBOs in it? Something that might be used by your other processes (ex. Utility - Strings VBO or something similar)?

Cheers,
​

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

[LourdesUrena]

Hi @ewilson, yes.  At least the 2nd import that this happened to did contain common VBOs in it.  However, the import continued (Didn't throw an error), but all processes flunked.​

------------------------------
Lourdes Urena
Sr Solutions Engineering
Grainger Panama Services
Panama
------------------------------

[EVIPUTI]

@LourdesUrena Just to confirm , whats the size of release file ? Is it more than 5 MB ?
Are you facing the same delays if you are importing single process or object ?​

------------------------------
------------------------------
Vipul Tiwari
Senior Process Simplification and Optimization Designer(Solutions Architect)
Fidelity International
------------------------------
------------------------------

[LourdesUrena]

Hello,

The release was 314KB and yes, even with a single object or process there is a huge delay.

Lourdes Urena  | Sr. Solutions Engineering (RPA) | W.W. Grainger, Inc.

Ph: 224-724-5080| lourdes.urena@grainger.com |www.grainger.com

[Wendy__Braem]

Hello Lourdes,

we now have the same problem. Did you solve it and what is the solution?

------------------------------
Wendy Braem-Baptist
Robotic Process Developer
Alliander
Europe/Amsterdam
------------------------------

[Walter.Koller]

This sounds like an issue we faced after the Windows security patch. We had to switch to .Net Remote Secure connection mode because of SSO ceased to work after the security patch.

Everything seemed to work fine until someone is importing a release or even a single object. It became quite common that the whole environment became unresponsive and the DB showed locks piling up for several minutes and even hours. 

Eventually we found the cause of those issues. The .Net Remote Secure has call back port enabled by default. Disabling the call back port in the connection definition fixed those issues.

The date of the original post would fit to our own timeline of issues but newer installation should be using SPN definitions (as described in the installation guided) and other connection modes should be used.

------------------------------
Walter Koller
Solution Manager
Erste Digital / Erste Group Bank
Europe/Vienna
------------------------------