Functionality Breaks after updating Windows
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
14-10-20 11:29 AM
Dear All,
We have upgraded our Virtual Machines running Windows 10 Enterprise version from 10.0.17763 to 10.0.18363.... and this has resulted in a number of our bots which are interfacing with Chrome to stop working or detecting the elements... such functionality included opening the 'menu' button on Chrome, clicking print, and saving a pdf of the website.... the press button action stopped working, and was only resolved when changing to 'Global Click Centre'...
Another process which was affected includes searching for text on a website and taking a screenshot....
Both of these tasks function well on a VM which is still running the old Windows version.... Howcome is the windows update affecting such Blue Prism functionality??
I also noticed that functionality can break when moving from a physical resource to a virtual machine... a bot which interacted with Adobe Acrobat using the 'Write' action no longer worked until all actions were changed to "Global Send Keys"....
Why is this the case please, and how can this be avoided? As it is inducing an overhead in maintaining our processes...
Best Regards,
------------------------------
Jean Luc Farrugia
------------------------------
We have upgraded our Virtual Machines running Windows 10 Enterprise version from 10.0.17763 to 10.0.18363.... and this has resulted in a number of our bots which are interfacing with Chrome to stop working or detecting the elements... such functionality included opening the 'menu' button on Chrome, clicking print, and saving a pdf of the website.... the press button action stopped working, and was only resolved when changing to 'Global Click Centre'...
Another process which was affected includes searching for text on a website and taking a screenshot....
Both of these tasks function well on a VM which is still running the old Windows version.... Howcome is the windows update affecting such Blue Prism functionality??
I also noticed that functionality can break when moving from a physical resource to a virtual machine... a bot which interacted with Adobe Acrobat using the 'Write' action no longer worked until all actions were changed to "Global Send Keys"....
Why is this the case please, and how can this be avoided? As it is inducing an overhead in maintaining our processes...
Best Regards,
------------------------------
Jean Luc Farrugia
------------------------------
5 REPLIES 5
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
14-10-20 01:00 PM
Hi Jean
It can be related to the .Net version and also the " OLEACC.DLL " version file during upgrade Windows OS.
------------------------------
Hossein Azimi
Customer Support Engineer, APAC
Blue Prism
Sydney NSW
------------------------------
It can be related to the .Net version and also the " OLEACC.DLL " version file during upgrade Windows OS.
------------------------------
Hossein Azimi
Customer Support Engineer, APAC
Blue Prism
Sydney NSW
------------------------------
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
23-10-20 01:10 PM
Dear Sir,
Thank you for your reply. Does Blue Prism 6.8 require a specific version of the .NET framework and associated DLL files so as to prevent the functionality of our bots from breaking?
Can be Blue Prism be configured so that it makes use of a specific version of the .NET framework and DLL files, if multiple versions are installed?
As debugging and changing algorithms each time an update is installed or migrated to a new machine is inhibiting our productivity... and users are losing confidence in the processes that were already built and tested to be working well previously...
Best Regards,
------------------------------
Jean Luc Farrugia
------------------------------
Thank you for your reply. Does Blue Prism 6.8 require a specific version of the .NET framework and associated DLL files so as to prevent the functionality of our bots from breaking?
Can be Blue Prism be configured so that it makes use of a specific version of the .NET framework and DLL files, if multiple versions are installed?
As debugging and changing algorithms each time an update is installed or migrated to a new machine is inhibiting our productivity... and users are losing confidence in the processes that were already built and tested to be working well previously...
Best Regards,
------------------------------
Jean Luc Farrugia
------------------------------
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
29-10-20 03:11 PM
We have the same issues after upgrading Windows 10 version 1803 to 1909. Which version has your BP installation an which .NET version is installed?
------------------------------
Ron G
------------------------------
------------------------------
Ron G
------------------------------
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-11-20 11:19 AM
We are using Blue Prism 6.8, and .NET Framework version 4.0
------------------------------
Jean Luc Farrugia
------------------------------
------------------------------
Jean Luc Farrugia
------------------------------
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
20-11-20 01:29 PM
We found the cause in our infrastructure. the vmware version was updated and the resolution settings in SENS no longer worked. Our IT fixed this and now it works again with the new windows version.
------------------------------
Ron G
------------------------------
------------------------------
Ron G
------------------------------
