Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Why can't Robot Studio build projects that are on a network drive?

Updated on October 17, 2022

Pega Robot Studio cannot build projects that are on a network drive due to a change in Microsoft's .NET Common Language Runtime (CLR) between versions 2 and 4. Previously, .NET CLR allowed the loading of binaries by default. In later versions of .NET CLR, this is denied.

The following steps might resolve this issue. These steps let the Robot Studio deployment executable (OSD.exe) access any remote binaries on a network drive:

  1. Open Notepad.
  2. Paste in the following text:
    <configuration>
       <runtime>
          <loadFromRemoteSources enabled=”true” />
       </runtime>
    </configuration>
    
  3. Save the file as OSD.exe.config in the same folder as the OSD.exe program, such as in C:\Program Files (x86)\OpenSpan\OpenSpan Plug-in for Microsoft Visual Studio 2015 for 8.0 SP1, or C:\Program Files\Pegasystems\Pega Robot Studio Plugin for 19.1.
    • For the 8.0 SP1 standalone version of Robot Studio, save the file to the following folder: C:\Program Files\OpenSpan\OpenSpan Studio for Microsoft Visual Studio 2015\Application.
    • For version 19.1 and later, save the file to the following folder: C:\Program Files\Pegasystems\Pega Robot Studio\Application.
    • If you are using a 64-bit operating system, use the following folder: C:\Program Files (x86)\.
  4. Rebuild the project.
Note: The system does not support this configuration and your results may vary.
  • Previous topic Pega.Loader parameters
  • Next topic Why do I get an error when calling the SetCellValue method and using a MicrosoftExcel Connector?

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us