Blue Prism 7.2 Utility environment VBO Issue

[JeslinArmstrong]

Hi Community,

We recently upgraded Blue Prism to 7.2 from 7.1 in Windows Server 2019 (64bit OS). While we were testing the process, the “start process” & “Run Until End” actions fails in utility environment VBO.

When we run it, Blue Prism 7.2 is showing below error but same works in Blue Prism 7.1

Anyone know what could be happening?

Thank you very much.

[harish.m]

HI Jeslin Armstrong,

Did you imported  the latest VBO's from below folder ? and check that make any difference

C:\Program Files\Blue Prism Limited\Blue Prism Automate\VBO

[JeslinArmstrong]

Hi Harish,

We tried importing the VBOs from the location : C:\Program Files\Blue Prism Limited\Blue Prism Automate\VBO and also from Digital exchange. Still the issue persists.

[ZdeněkKabátek]

Hi, Jeslin,

get in touch with support. The root cause could be that 7.2 is truly 64 bit and some dlls reference in VBO might be 32 bit which is causing the troubles.

Regards

Zdenek

[_Amlansahoo]

@ewilson Will be the best person to guide on the same. Hi Eric please help in this issue.
In the mean time I have tested "Start Process" in my local and it's working absolutely fine.

[JeslinArmstrong]

Hi Amlan,

We have already tried it in our local machine where its working fine with no issues. But its not working in windows server OS.

[_Amlansahoo]

Hi Jeslin,

Sorry for that I guess I missed that in your question. I guess BP support team can help with this.

[ewilson]

Hi @JeslinArmstrong 

My guess is this has something to do with the change between 32-bit and 64-bit. Blue Prism v7.2 is the first release of the software that is truly 64-bit. We'll take a look at this today and get back to you.

Cheers,
Eric

[ewilson]

@JeslinArmstrong 

I've gone through an tested the actions on on a v7.2 instances (upgraded from a v7.1 instance), but I'm not seeing any errors. You mentioned you're seeing this only on Windows Server. What version of Windows Server are you running?

Cheers,
Eric 

[SaranSasidharan]

Hi @ewilson , This issue is noticed in Windows Server 2019 ,
Thanks,
Saran Sasidharan