.net error after changing server to TLS 1.2

Server Code
1

Hi Guys

Bit of a weird one, which we can’t solve.

We changed the security protocol on our server and since then the .net application has been down. We are stuck on hopefully one remaining error.

We have a backendless call which creates and saves some backendless data. This is working fine in the main .net application, but it fails in the .net web service where it is being called from the main application so there must be a pointer in that. The server guys have checked all the permissions and can’t find anything wrong. This was working before we upgraded the security. It is a backendless 3.0 app

The error we are getting when we try and save to backendless is
Unable to create the store directory.

Does this trace help?
<Data>BackendlessException</Data>
<Data>The underlying connection was closed: An unexpected error occurred on a receive.
at BackendlessAPI.Engine.Invoker.InvokeSync[T](String className, String methodName, Object[] args, Boolean enableUnderFlowInspection)
at BackendlessAPI.Service.PersistenceService.Find[T](BackendlessDataQuery dataQuery)
at BackendlessAPI.Data.DataStoreFactory.DataStoreImpl`1.Find(BackendlessDataQuery dataQueryOptions)
at backendupdate.Page_Load(Object sender, EventArgs e)
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

2

Hi Mike,

Backendless doesn’t do anything special related to sockets. Here’s the code which creates a WebRequest: https://github.com/Backendless/.NET-SDK/blob/master/Backendless/WebORB/Client/HttpEngine.cs#L234-L265

To isolate the problem, I suggest creating a super simple .net web service which makes a call to our backend (perhaps as simple as fetching a file). Any errors you get from that should provide more pointers for the problem resolution.

Regards,
Mark

3

Thanks Mark, Yes I can try that or I can move that code out of the service into the main application as that might be quicker than finding this problem!

Do you know if Backendless is trying to create a store directory in any specific locations in case it is a permissions issue still on the server?

4

Yes, it would try to create a persistent store if you use the stayLoggedIn functionality.

5

I do, but not in the web service. All I do is something very simple which is

Backendless.Data.Of(Of Voucher)().Save(myVoucher)

where Voucher is
Imports Microsoft.VisualBasic

Public Class Voucher

Private _voucherID As String
Public Property VoucherID() As String
    Get
        Return _voucherID
    End Get
    Set(ByVal value As String)
        _voucherID = value
    End Set
End Property

…

6

You could try substituting the call with the corresponding REST API to completely rule out anything that might be happening in the SDK