Remote name could not be resolved

4 Years Ago
JorgeR
SCHEDULER AND UNDERLYING SERVICES

Summary

When end users are working within a Company network that uses a Proxy, Bizagi displays an error message: "Remote name could not be resolved" as the process tries to consume a Web Service through an activity. It is necessary to allow the .Net framework to use the default credentials. 

Applies to

All versions

Symptoms

When a process tries to execute an external service, Bizagi’s Work Portal displays an error message "Remote name could not be resolved". However the service consumed by Bizagi can be accessed from a browser normally. 

Cause

The .Net framework needs to use the credentials of the proxy in order to access the web service. 

For more information, refer to https://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2397357-fix-it-so-that-net-apps-can-access-http-thru-auth

Solution

1. Open the web.config file (located in C:\Bizagi\Projects\[ProjectName]\WebApplication) using the text editor of your choice.

2. Add the following key:

<system.net>
<defaultProxy useDefaultCredentials="true" />
</system.net>

3. Save the web.config file and restart the service.
Rate this Article:

Details

Last Modified:4 Years Ago
Last Modified By: Andread
Type: ERROR
Level: Expert
Rated 3 stars based on 1 vote
Article has been viewed 6.7K times.

Options