Description

 Removal of SAP Dlls from Evolve, Studio Manager and Studio installers

Applies To

Evolve, Studio Manager and Studio installers

Solution/Immediate Workaround

Removal of Dlls FAQ

Question 1: Which Dlls are in question?

Winshuttle used to bundle these SAP Dlls with Evolve, Studio Manager and Studio installers to make it easier for our customers to connect with the SAP GUI (available in 32 bit only) from a 64 bit version of Automate products. These SAP dlls will no longer be bundled with Studio, Evolve and Studio Manager installers:

• librfc32.dll
• sapnwrfc.dll
• icudt50.dll
• icuin50.dll
• icuuc50.dll

Question 2: When will these dlls will be removed?

We will be stop shipping these Dlls to connect with SAP GUI from 64 bit version of Automate products with the next maintenance release (planned for June/July 2022 time frame) of Studio; Evolve and Studio Manager Server and Worker installers

Question 3: Where should the customers get these dlls from and where to place these to make the connection to SAP possible?

These dlls can be downloaded off the SAP support site. To get these dlls customers should have valid SAP maintenance and the user placing these files on the server or client machine would require admin access.

We will document the exact steps to get these dlls and we will provide the links for its download. We will have to place these files at C:\windows\system32

Question 4: What is the impact of upgrade from 20.2.8 or earlier version of 20.x series?

In case of upgrade, these files will be retained by the installers.

In case of fresh installation, these Dlls will not be installed or placed with the product installation

Question 5: Will we implement any checks or warning during installation of Studio/Evolve Server/Worker, as an information or message in installer screen?

There will not be any checks in the installer, but we will add the steps in the installation guide to provide information on placing these files and perform Test connection as customers/engineers try to check this after installation.

Question6: The warning/error message that we are implementing, in which cases will it be shown.

It will show in all the Studio interaction points, execution of Auto-run, update plugin, Test connection, and other SAP end points on the Evolve Server and Worker.

Question7: What kind of information will be there in the error

The error message will show the missing file names, or we can see if another message is required. STUDIO UI can show message pop on interaction but in Evolve we may see such messages in Logs/Test connection may show error.

Question8: What happens when the error comes and I place the files after that, do I need to relaunch Studio/run the form again. What happens if the job fails at the worker site or say Winshuttle update plugin in case of Evolve form workflow.

User will have to reinitiate the process when files are placed back so that SAP connection works and workflow moves forward.

Customer will have to re-run the reports in case query scripts are used.

Studio need not to be re-launch. If files are placed after error appears around missing files, Studio will work.

Question9: What are the chances or scenarios of data loss in case these files are missing while running or recording?

No data loss w.r.t SAP upload/Download operations. Since SAP required files are not present, connection will fail, and subsequent SAP operations will not succeed.

Question 10: What happens if customer upgrade or reinstall SAP GUI?

SAP GUI will have no impact since SAP GUI is distributed as 32-bit installer.

Question 11: What changes are we doing in installers, is it just removing the dlls in question?

We will be un-bundling these files from installer. We will prepare an information guide, that user need to keep files on the machine.

Question 12: What happens in case of repair, will the files be removed?

Repair does not remove files.