Hello,

There are various Callouts that we make from Salesforce to resources we have on Azure, mainly webservices that are on a cloud service and to the Azure Service Bus.

For the past 2 months (without any implementation changes on Salesforce or Azure on our part) we are getting a few times per week a "System.CalloutException Connection reset" error.

Any idea on how to avoid this? 

We make callouts to various other third parties and are not getting this error, only when calling Azure.

Hello all,

We have .NET developments in Windows Azure for about 4 years now. Since March 28th of this year, we have been getting an error about 10-15 times per week with API calls via SOAP queries or REST Webservices, where the error message reads: 

Unable to connect to the remote server
No connection could be made because the target machine actively refused it 96.43.148.104:443

On average we make around 8,000 API calls every day with no issue. 

Right now we are managing the error by catching it and making the call again, but we would like to solve it completely.

Any ideas on what might be causing this on Salesforce or Azure?

Hello all,

We have the following scalability issue.

We use emails internally to manage our operations and communications with clients, providers and internal employees. We have around 100 different types of emails that are sent programatically from APEX triggers, functions and webservices. Right now we send about 1000 emails daily and as we grow that number continues to increase (these are not mass emails, most emails are directed to only 1 recipient).

About a year ago we hit the 1,000 email mark for the first time and we basically had to shutdown our service because the operational emails couldn't be sent. At that point Salesforce increased our limit to 2,000. A couple of weeks ago we hit the 2,000 mark for the first time, but now it seems that the limit cannot be increased.

I have heard recommendations of using Pardot, ExactTarget and services like that. But, they offer a wide range of functionalities that we don't need and don't want to pay for.

Has anybody been able to solve this problem some other way? the important thing is to be able to send the emails from APEX code, having the flexibility of sending more emails.

Hello all,

We have .NET developments in Windows Azure for about 4 years now. Since March 28th of this year, we have been getting an error about 10-15 times per week with API calls via SOAP queries or REST Webservices, where the error message reads: 

Unable to connect to the remote server
No connection could be made because the target machine actively refused it 96.43.148.104:443

On average we make around 8,000 API calls every day with no issue. 

Right now we are managing the error by catching it and making the call again, but we would like to solve it completely.

Any ideas on what might be causing this on Salesforce or Azure?

Hello,

There are various Callouts that we make from Salesforce to resources we have on Azure, mainly webservices that are on a cloud service and to the Azure Service Bus.

For the past 2 months (without any implementation changes on Salesforce or Azure on our part) we are getting a few times per week a "System.CalloutException Connection reset" error.

Any idea on how to avoid this? 

We make callouts to various other third parties and are not getting this error, only when calling Azure.