Question
Tata Consultancy Services Ltd
US
Last activity: 22 Jul 2020 7:53 EDT
Unable to validate the script after installing Robotics plugin
Hi Team
I have installed Pega Robot Studio Plugin Proprietary information hidden version on my official Laptop with Windows 10 OS. I have created fresh PEGA project and added a script inside Global Container. Script have a very small function that adding a+b and sending output to automation.
I am not able to validate the script and keep on getting below error message:
error 1299: Error generating design component class: Exception has been thrown by the target of an invocation.
I have uninstall the PEGA, restart laptop and install in again. Still, this error is not resolved.
Can someone please provide suggestion about how to resolve the issue?
Thanks in advance for the help.
Branched Information: Originally posted as reply here.
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
Updated: 22 Jul 2020 7:53 EDT
Tata Consultancy Services Ltd
US
I found the cause of this issue.
I was developing a DLL where I have included few Nuget Packages. One of them was "Newtonsoft"
I was trying to add reference of my Custom DLL from a folder other than "C:\Program Files (x86)\Pegasystems\Pega Robot Studio Plug-In" folder and sometimes PEGA recognizes the DLLs and some times it doesn't.
After going through few help on google, I pushed my custom DLL to "C:\Program Files (x86)\Pegasystems\Pega Robot Studio Plug-In" folder along with other dependent DLLs then "Newtonsoft.DLL" was overwritten in this location.
The issue start occurring after that overwrite of Newtonsoft.DLL.
I did multiple hit and try and uninstall/install etc. Later the issue was resolved when I removed PEGA completely, removed all folders, install it back and not pushed this particular Newtonsoft.DLL
This is how the issue was resolved.
Updated: 16 Jul 2020 15:02 EDT
Pegasystems Inc.
US
I suggest you post this as a new question as it isn't related to this post. I think it would be better to have this discussion on a new thread.
Pegasystems Inc.
US
I have moved this into a new post of its own. Thanks for the heads up @tsasnett!
Marissa | Senior Moderator | Pega Collaboration Center
Pegasystems Inc.
US
Can you post you script here?
Pegasystems Inc.
US
Re-reading this, I actually suspect some other issue with your project. When you validate a script, it does a build on the project. Can you build your project without the script?
Tata Consultancy Services Ltd
US
Thank you both for moving my Query to a new post. Please find the response to your query:
Yes, I can build and run the project without the script.
The issue starts occurring immediately after adding a script in the project. No matter if you write any code in script or keep it blank.
Following error - "error 1299: Error generating design component class: Exception has been thrown by the target of an invocation." starts occurring on validate the script even if the script is blank.
Please provide suggestion about how to resolve the issue?
Thanks in advance for the help.
Pegasystems Inc.
US
Are you able to attach your solution? If not, can you recreate this in an example solution that you can attach?
Accepted Solution
Updated: 22 Jul 2020 7:53 EDT
Tata Consultancy Services Ltd
US
I found the cause of this issue.
I was developing a DLL where I have included few Nuget Packages. One of them was "Newtonsoft"
I was trying to add reference of my Custom DLL from a folder other than "C:\Program Files (x86)\Pegasystems\Pega Robot Studio Plug-In" folder and sometimes PEGA recognizes the DLLs and some times it doesn't.
After going through few help on google, I pushed my custom DLL to "C:\Program Files (x86)\Pegasystems\Pega Robot Studio Plug-In" folder along with other dependent DLLs then "Newtonsoft.DLL" was overwritten in this location.
The issue start occurring after that overwrite of Newtonsoft.DLL.
I did multiple hit and try and uninstall/install etc. Later the issue was resolved when I removed PEGA completely, removed all folders, install it back and not pushed this particular Newtonsoft.DLL
This is how the issue was resolved.