We're getting the following error.
An exception occurred when setting up mail server parameters. This exception was caused by: javax.mail.MessagingException: Connect failed; nested exception is: java.net.ConnectException: Connection timed out: connect.
I've read that this issue is normally caused by an issue with the CF mailer. But we are sent any errors that happen on our system, so doubtful it's that. Here is the flow (from what I've found)
Use cfpop to login to gmail and get emails.
Send mail (using cfmail) to me with a dump of the previous cfpop call (Part of another problem, so to debug I'm emailing myself what CF gets back from the cfpop call).
Error happens and is caught.
Coldfusion sends me this error in a email, using cfmail.
Do note I thought that there might be too many emails for CF to download them all, so I tried getting less mails to no avail. All cfmail calls use the same details (server, username, password). Also I've tested this on another server (multiple) and it worked then with no issue.
Does anybody have any idea? Anything?
Here is the code in the cfpop. Do note that I have called the underlying Java code to get this working over SSL.
<CFPOP ACTION="GetAll" NAME="popHeader"
SERVER="#Application.emailServer#"
PORT="995"
USERNAME="#Application.emailUsername#"
PASSWORD="#Application.emailPassword#"
ATTACHMENTPATH="#expandPath('./files/')#"
GENERATEUNIQUEFILENAMES="YES"/>
Related
We are trying to reach to an API hosted in our company network using rest connector in ADF (SHIR is used). Linked service connection is successful but dataset is unable to read the data and copy activity is as well failing with below error. Please suggest your thoughts in resolving the same.
Failure happened on 'Source' side. ErrorCode=UserErrorFailToReadFromRestResource,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=An error occurred while sending the request.,Source=Microsoft.DataTransfer.ClientLibrary,''Type=System.Net.Http.HttpRequestException,Message=An error occurred while sending the request.,Source=mscorlib,''Type=System.Net.WebException,Message=Unable to connect to the remote server,Source=System,''Type=System.Net.Sockets.SocketException,Message=A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond ,Source=System,'
This error is mostly seen due to firewall issues. You might want to verify your network firewall setting to allow the API request to be read.
Also, verify if your API call is working as expected using other API testing tools. If the issue persists you can raise a support ticket for engineers to investigate more on the issue.
If you are able to preview data in your source , then check your sink connection as this issue can occur when the Sink in the copy activity is behind a firewall, I was getting the same issue and I tried copying to a container without a firewall and it worked. Its weird that the error is related to Source and the issue is with Sink.
I am uploading files from a specific drive in the host computer to a Sharepoint Site, for this I have used Microsoft.SharePoint.Client.dll & Microsoft.SharePoint.Client.Runtime.dll. Most of the times my script works fine, but at times I get the error:
"Failed to connect to SharePoint Online site: 'https://XXX.sharepoint.com/sites/XXX'"
"Exception Type: System.Management.Automation.MethodInvocationException"
"Exception Message: Exception calling ""ExecuteQuery"" with ""0"" argument(s): ""The remote name could not be resolved: 'XXX.sharepoint.com'"""
Any ideas of what might be causing the error and how I could prevent the script from crashing again?
Thank you!
As most of the times, the script works.
I assuming that it could be some network issue in your side.
Did you use some proxy in you side and can you access the site url in browser directly ?
I suggest you can trace the request using Fiddler to see if there is some detailed error message when executing the script:
Fiddler
I have a powershell script to check a webserver page availability and task runs for every 5mins.
But I am getting TLS/SSL request is aborted error for every 3-4 hour once.
I have used the below one in my code and it's works fine.
[Net.ServicePointManager]::SecurityProtocol =[Net.SecurityProtocolType]::Tls12
I had setup timeout secs(100) for invoking my web request but it doesn't seem to work this way.
Someone can help me why it's giving TLS/SSL errors all of a sudden? And how to fix this?
This is an interesting issue. It could be many issues:
This could be an issue with the server; Perhaps the server is dropping requests or has some internal handling issues.
The request may be timing out before it has a chance to receive a response.
There could be network errors unrelated to your script or the target server.
I wrap your web request method in a try-catch, if it catches than it tries again, up to a certain specified amount of times. If this does not fix it, there is a chance that the problem lies with the server and not your script.
I have an SSRS reporting service which sends reports as email subscription. Everything was working fine.
Now I added a expression to one of the column. After that I was able to view the reports in the URL, but the timely subscribed emails are not flowing out. The status is pending for so long and finally it fails saying "Thread aborted"
Can anyone help on this ?
Usually, the error "System.Threading.ThreadAbortException: Thread was being aborted." occurs when we call Thread.Abort() explicit, or there is unhandled exception occurred.
In this case, it should be unhandled exception, as SQL Server Reporting Services(SSRS) catches almost all exceptions. Maybe you could enable verbose log for SSRS to trace more detailed error log, this may help us to troubleshooting the issue. If there is dump file generated. The dump files will be generated in the same folder of the log files.
Dont have the rep to post this a comment.
I'm trying to deploy an application via web deploy to a windows 2012 r2 server.
First tried installing iis, web deploy using the msi. After getting an unreachable error I saw somewhere that I needed wmsvc to be installed and installed it via powershell command Install-WindowsFeature Web-Mgmt-Service.
I stopped getting the unreachable error and started getting this error ->
Error: Could not complete the request to remote agent URL 'http://xx.x.xx.xx:8172/MSDEPLOYAGENTSERVICE'.
Error: The operation has timed out
On the server's event viewer under system I get the following error ->
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 1203.
Any idea of what could be going on? Did I miss something on the installation?
After this I also tried installing everything but without iis and I get the same error.
So, this is really not a PoSH issue.
Maybe you should consider movin gthis question to another forum.
Anyway, you have either real server config issues (this can sometimes mean wipe and rebuild - very ugly option - but if it's a virtual machine and you have a snapshot, just roll back), or an app causing this.
Typically for Schannel type of error, it has to do with application or service in machine not able to complete any SSL connection sort of connection.
The error state parameter of 1203 means client error connecting to server, ie invalid ClientHello from the client
See if you can collect more data by...
https://support.microsoft.com/en-us/help/260729/how-to-enable-schannel-event-logging-in-iis
I realized this is an old question, but in case somebody ran into the same issue, here are my solution.
I had to follow this guidelines : https://learn.microsoft.com/en-us/aspnet/web-forms/overview/deployment/configuring-server-environments-for-web-deployment/configuring-a-web-server-for-web-deploy-publishing-web-deploy-handler
Copy the resulting publishsetting file. In the Publish/Profile page import it.
In the Publish/Connection page, change the server to the server address with the 8172 port. Add the password. Change the Destination URL to the site to go to after the publish is completed.
Then after Validate connection was completed, go ahead and publish it!