Question
Infosys
IN
Last activity: 6 Nov 2018 20:02 EST
How to deploy the Pega Robotics Automation solution with different MS Office version on end user system
Hi Team,
I have developed a solution having Microsoft Excel and Microsoft outlook Mail connectors containing the Office 2016 dlls as components.
But the end user system contains Microsoft Office 2013 and the solution is not executiong.
Steps followed in my machine are:
(1) Replaced the Microsoft.Office.Interop.Excel.dll and Microsoft.Office.Interop.Outlook.dll present in the path C:\Program Files (x86)\OpenSpan\OpenSpan Studio for Microsoft Visual Studio 2015 with the dlls present in the folder C:\Program Files (x86)\OpenSpan\OpenSpan Studio for Microsoft Visual Studio 2015\Office2013
(2) Changed the office version from 2016 to 2013 in RuntimeConfig.xml and StudioConfig.xml as well in the statement as follows from :
<add key="OfficeVersion" value="2016" /> to the following statement
<add key="OfficeVersion" value="2013" />
(3) When tried executing the solution the following error is fired. Please find the below two snapshots for reference
Could you please help me how to resolve this office versioning problems.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems Inc.
AU
Please rebuild the solution and the machine which got similar configuration of the end user and redeploy to the end users machine.
Or Alternatively you need to go through the detailed log files [i.e. verbose category "4"] to identify the exact cause of the failure.
Thanks,
Sudheer
Pegasystems Inc.
US
I think you're doing this wrong. When you install Runtime or Studio you select the version of Office that you have installed. Your solution will not work if you do not have that version installed. Your solution will likely work on a machine with a different version of Office installed, assuming that you selected the correct Office version when you installed Studio or Runtime on that machine. You can't simply switch out your dlls on your machine with Office 2016 for Office 2013 dlls. That won't work.