.NET (Core and Framework)

Emanuela Meraglia wrote:

strange errors occur

Emanuela Meraglia wrote:

errors in the queries due to lack or incorrect formatting of dates

<pre>Private Sub AvviaServizio(ByVal t As Type, ByVal uri As String, ByVal classe As String)
        Dim binding As New BasicHttpBinding
        binding.OpenTimeout = New TimeSpan(0, 10, 0)
        binding.CloseTimeout = New TimeSpan(0, 10, 0)
        binding.SendTimeout = New TimeSpan(0, 10, 0
        'binding.ReceiveTimeout = New TimeSpan(0, 10, 0)
        'binding.Security.Mode = SecurityMode.Transport
        'binding.Security.Transport.ClientCredentialType = HttpClientCredentialType.None
        'binding.Security.Transport.ProxyCredentialType = HttpProxyCredentialType.None
        binding.MaxBufferPoolSize = 2147483647
        binding.MaxBufferSize = 2147483647
        binding.MaxReceivedMessageSize = 2147483647
        binding.MessageEncoding = WSMessageEncoding.Text

        Dim host As New ServiceModel.ServiceHost(t)
        host.AddServiceEndpoint(classe, binding, New Uri(uri & classe))
        Try
            host.Description.Behaviors.Add(New ServiceMetadataBehavior With {
                .HttpGetEnabled = True,
                .HttpGetUrl = New Uri(uri & classe)
            })
            host.Open()

            _service.Add(host)
        Catch ex As Exception
            host.Abort()
            Throw
        End Try
    End Sub

I don't understand which user you're referring to

I wrote the current user in my log file, and it matches with the Windows credentials I logged in with ... so it's ok.

I do not have the VB6 dll source from my provider, so I have no way of getting the error.
I am attaching images of errors captured by SQL Profiler, but I don't think they can help.
The 1.png, 2.png and 3.png files are screenshots of the SQL profiler traces captured at Runtime, while the 1_Debug.png, 2_Debug.png and 3_Debug.png files are screenshots of the SQL profiler traces captured in Debug (so working).

Since the errors do not occur by calling the VB6 dll from VB6 or VB.NET applications, or by debugging my VB6 project which instantiates the external dll, I thought the problem lies in the process that hosts it.

Checking the VB6 code with the developer, we have identified the point where the error occurs: it cannot return a path of the configuration file (from which it reads the formatting of the dates), and uses the Windows API "GetEnvironmentVariable" .
I'm trying to figure out if there is any incompatibility between WCF and the VB6 API calls.