I have a web application that I made to connect to my Exchange EWS that mainly looks at a user's Outlook categories. Not sure what changed recently but when connecting, the webpage outputs the following error - Error: The request failed. The underlying connection was closed: An unexpected error occurred on a send.
Where can I begin troubleshooting this error?
I had to update my httpRuntime targetFramework to
The server no longer accepts anything but tls 1.2 and the target framework as set to 4.5 which doesn't support tls by default.
Related
Sending SMTP mail via an Office 365 mail server, using .NET System.Net.Mail.SmtpClient I'm getting the following error:
The server response was: 4.3.21 Mailbox server busy; mail intentionally delayed
I can't find any reference to this specific code anywhere - the closest thing I can find is 4.3.2 mailbox busy
It seems to be a transient error, but I'm getting a lot of them.
Any idea what the code means?
I have an application (packaged software from a vendor) that runs on Oracle WebLogic.
There are few operations that, if I try them, I consistently get the following error page:
(WebLogic Bridge Message) Failure of Web Server bridge: No backend server available for connection: timed out after 10 seconds or idempotent set to OFF or method not idempotent.
The error occurs consistently almost exactly five minutes after I try the operation.
The page does not look like the typical error page you get when the application logic fails. It looks like something to do with the infrastructure (e.g., WebLogic configuration).
I am pursuing the issue with the software vendor, but that's not going well.
Has anyone seen this message and/or suggest an approach for diagnosing the root cause here?
Looks like you are using a Proxy Server between Browser and Weblogic Server. By seeing the error it's evident that proxy server unable to connect to back-end WLS server. You may have to enable proxy debugs to get more info.
I'm configuring the adapter for AX, all the steps in the configuration have been performed.
In the inbound ports I found this one: http://servername/MicrosoftDynamicsAxAif60/ScribeAxWebService/xppservice.svc but I get this error:
Connection Error: The HTTP request is unauthorized with client
authentication scheme 'Anonymous'. The authentication header
received from the server was 'Negotiate,NTLM'.
If I go in AX and change the security mode to "None" for using anonymous authentication then I get
The client and service bindings may be mismatched.
The remote server returned an error: (415)
Cannot process the message because the content type
'application/soap+xml; charset=utf-8' was not the
expected type 'text/xml; charset=utf-8'..
Where can I find the right one?
Your question is for propriety software, so this isn't exactly the right forum for it, but I've used some older versions of Scribe (4+ yrs ago).
I'd guess the domain user account running the Scribe service is not added as an AX user. Where are you getting "unauthorized"?
You already have indicated that web.config is changed, but there is a good example on MSDN, see the section XML Snippet from Web.Config. There are TWO changes to be made. The wsHttpBinding section, and then to each service that it's binding = "wsHttpBinding" is correct.
Finally, I also add a log file to AIF during the testing phase.
I have web application deploy on WildFly Application Server 8.2.0.Final on Openshift.
My application serves websockets endpoint.
I connect to the websocket endpoint with my java (tyrus implementation) client application and after short period (few hours) connection is closed by server side. I receive close reason "Closed abnormally" and close reason code: "1006".
Client does automatic reconnection and then exactly every hour connection is again broken with mentioned close reason.
Is this builtin mechanism working on openshift serverside? Some sort of cleaning mechanism?
I would like to have permanent websocket connection to server.
Would buying openshift broze/silver support solve this problem?
The problem is in your browser, not in the server:
Close Code 1006 is a special code that means the connection was closed abnormally (locally) by the browser implementation.
If your browser client reports close code 1006, then you should be looking at the websocket.onerror(evt) event for details.
See this SO answer for more details:
https://stackoverflow.com/a/19305172/212224
Is there any whay that I can get RestSharp to ignore errors in SSL certificates on Windows phone 8? I have a test client, and the service I connect to does not yet have a valid cetificate.
When I make a request now I get the error:
The underlying connection was closed: Could not establish trust
relationship for the SSL/TLS secure channel.
Thanks in advance