I having problem on Umbraco 7.7.6 basically server call itself for tasks/publishing/keepalive details:
http://issues.umbraco.org/issue/U4-5391
the problem is that server admin is not allowing external access to internet from webserver so that means http://(domain)/umbraco is not reachable and Umbraco is throwing following error in log file.
2017--06 13:42:45,673 [P3048/D15/T45] ERROR Umbraco.Web.Scheduling.KeepAlive – Failed (at “http://(domain)/umbraco”).
System.Threading.Tasks.TaskCanceledException: A task was canceled.
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Umbraco.Web.Scheduling.KeepAlive.<PerformRunAsync>d__4.MoveNext()
how can I mitigate the issue without giving outbound connection to internet from server?
Related
We have installed Kaspersky anti-virus a few days ago, and when we ran our old Jmeter tests, it raises the exception below.
org.apache.http.NoHttpResponseException: target server failed to respond
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:141)
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:56) ...
When we ran some sample requests in Postman, it also raised errors like socket hang-up or connection reset, but after adding Postman to Kaspersky's exception list, the application executed the tests normally.
We tried adding the jmeter.bat and ApacheJmeter.jar file to the exception list, but Jmeter still raised the NoHttpResponseException even with the exact same request we ran with Postman (we used the test-script recording).
Are we missing more files to be added to the exception list?
Any help would be highly appreciated.
Try adding java.exe and javaw.exe to the exception list
We have a .net web application (outlook web addin) that is running on-premise on two WindowsServer-2012 R2. This application makes calls to the Microsoft Graph API. Since one week the esception at the an of the question occurs, but only on one server.
The application didn't change since may. We checked also all certificates in IIS, but they are all ok.
When calling the graph api the following exception occurs, as explained only on one server:
Microsoft.Graph.ServiceException: Code: generalException
Message: An error occurred sending the request.
---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)
at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
--- End of inner exception stack trace ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Graph.RedirectHandler.d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Graph.RetryHandler.d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Graph.CompressionHandler.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Graph.AuthenticationHandler.d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Graph.HttpProvider.d__19.MoveNext()
--- End of inner exception stack trace ---
at Uniqa.OLAddin.EBFWeb.Helpers.GraphHelper.d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Uniqa.OLAddin.EBFWeb.Controllers.DoWFController.d__5.MoveNext()
Might it be that one of the servers hasn't got the latest root CA updates?
The SSL certificate from graph.microsoft.com was issued September 15th which could coincide with your problems.
The certificate chain is this:
Try to open the website https://graph.microsoft.com/v1.0/me/ on the server in question. If you get a certificate error, then try updating root certs (it's a Windows update).
When trying to publish a V2 function from Visual Studio I'm getting a publish error:
Publish has encountered an error.
Publishing failed.
The messages from the Output windows are:
Web deployment task failed. (Web Deploy experienced a connection problem with the server and had to terminate the connection. Contact your server administrator if the problem persists.
Web Deploy experienced a connection problem with the server and had to terminate the connection. Contact your server administrator if the problem persists.
Unexpected end of file has occurred. The following elements are not closed: results. Line 1, position 550.
The contents of the diagnostics log are:
06/05/2019 11:32:37
System.AggregateException: One or more errors occurred. ---> System.Exception: Publishing failed.
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at Microsoft.Publish.Framework.Model.DefaultPublishSteps.<>c__DisplayClass26_0.b__2()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Publish.Framework.Model.DefaultPublishSteps.d__23.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Publish.Framework.ViewModel.ProfileSelectorViewModel.d__183.MoveNext()
---> (Inner Exception #0) System.Exception: Publishing failed.<---
I have created a new HTTP function, tested it locally and the attempted to publish it.
Anyone know how to fix this?
Found the fix to this problem by walking through the quick start guide (again):
Publish the Project to Azure
You need to select the option for "Run from package file (recommended)".
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 3 years ago.
Improve this question
I am trying to connect to MAC Build host from visual studio but when i press connect button, above error is shown (same as title of this question).Please spend a few minutes reading following log file and provide me with your precious suggestions to fix it.Thanks
Xamarin.VisualStudio.TastyPackage|Information|0|Hooked up SDB tracing adapter
Xamarin.VisualStudio.TastyPackage|Information|0|Initialization finished
Xamarin|Information|0|Xamarin - 4.4.0.34-d15-1+3f99c5a
Xamarin.VisualStudio.Activation.AccountManager|Information|0|VS2015 Enterprise
Xamarin.VisualStudio.ActivationManager|Information|0|No license found for iOS
Xamarin.VisualStudio.ActivationManager|Information|0|Running license sync for iOS
Xamarin.VisualStudio.ActivationManager|Information|0|No license found for Android
Xamarin.VisualStudio.ActivationManager|Information|0|Running license sync for Android
Xamarin.VisualStudio.TastyPackage|Information|0|Hooked up SDB tracing adapter
Xamarin.VisualStudio.TastyPackage|Information|0|Initialization finished
Xamarin.VisualStudio.IOS.XamarinIOSPackage|Warning|0|Initializing Xamarin.VisualStudio.IOS.XamarinIOSPackage.
Xamarin.VisualStudio.ActivationManager|Information|0|Updated license: iOS VSEnterprise
Xamarin.VisualStudio.ActivationManager|Information|0|Updated license: Android VSEnterprise
Xamarin.VisualStudio.TastyPackage|Information|0|Hooked up SDB tracing adapter
Xamarin.VisualStudio.TastyPackage|Information|0|Initialization finished
Xamarin.VisualStudio.Android.XamarinAndroidPackage|Warning|0|Initializing Xamarin.VisualStudio.Android.XamarinAndroidPackage
Xamarin.VisualStudio.ProjectFixerRunner|Information|0|Solution loaded: 'PasswordResetModule'
Xamarin.VisualStudio.ProjectFixerRunner|Information|0|running fixup on project 'C:\Users\Ali Raza\Desktop\Xamarin Assets\PasswordResetModule\PasswordResetModule\PasswordResetModule.Android\PasswordResetModule.Android.csproj'
Xamarin.VisualStudio.ProjectFixerRunner|Information|0|running fixup on project 'C:\Users\Ali Raza\Desktop\Xamarin Assets\PasswordResetModule\PasswordResetModule\PasswordResetModule.iOS\PasswordResetModule.iOS.csproj'
Xamarin.VisualStudio.Remote.RemoteServer|Error|0|Could not retrieve fingerprint.
System.OperationCanceledException: Could not retrieve fingerprint. ---> System.Net.Sockets.SocketException: 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
at Renci.SshNet.Abstractions.SocketAbstraction.Connect(IPEndPoint remoteEndpoint, TimeSpan connectTimeout)
at Renci.SshNet.Session.SocketConnect(String host, Int32 port)
at Renci.SshNet.Session.Connect()
at Renci.SshNet.BaseClient.Connect()
at Xamarin.Messaging.Ssh.SshFingerprintRetriever.<>c__DisplayClass1_0.<RetrieveFingerprintAsync>b__1() in C:\d\lanes\4471\3f99c5a7\source\xamarinvs\src\Messaging\Xamarin.Messaging.Ssh\SshFingerprintRetriever.cs:line 47
--- End of inner exception stack trace ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Xamarin.Messaging.Ssh.SshFingerprintRetriever.<RetrieveFingerprintAsync>d__0.MoveNext() in C:\d\lanes\4471\3f99c5a7\source\xamarinvs\src\Messaging\Xamarin.Messaging.Ssh\SshFingerprintRetriever.cs:line 24
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Xamarin.VisualStudio.Remote.FingerprintRetriever.<RetrieveFingerprintAsync>d__2.MoveNext() in C:\d\lanes\4471\3f99c5a7\source\xamarinvs\src\Core\Xamarin.VisualStudio.Remote\FingerprintRetriever.cs:line 20
--- End of stack trace from previous location where exception was thrown ---
I had this problem and eventually fixed the issue by rebooting my Mac.
This works for me.
Pair to Mac for Xamarin.iOS development
Connection Troubleshooting for a Xamarin.iOS Build Host
On MacBook Enable Remote Login
The adapter in network I changed it to NAT by bridge adapter
I know its sort of late but troubleshooting this issue is very simple with these easy steps
Check that your mac agent is not locked and not in sleeping state.
Go to your mac agents section.
Disconnect and then reconnect to your mac agent.
Deploy your app after making sure of Point 1.
In case of any queries revert!
I just deployed a MVC web app to my windows server 2012. It has Windows 8 and IIS v8 installed. The application uses SignalR, and I would like to use websockets, but it gives errors.
In every browser (chrome ff, ie) the error is the same:
"NetworkError: 500 Internal Server Error - https://domain.com/signalr/connect?transport=webSockets&connectionToken=wiiR333%2BkbKu0Ex2SPZLE9W9X6eAm5lBssbjXbqCvl0QpjAiGtHkn1xiIQHYGi3O4DDLIv7whTahVb8Ll5kfwjnrzaZaDYCApWj5aWm6d1cZzxH89K%2BouHziBH7dCt9I&connectionData=%5B%7B%22name%22%3A%22charthub%22%7D%5D&tid=8"
The detailed error message would be:
Exception information:
Exception type: InvalidOperationException
Exception message: Not a valid web socket request.
at Microsoft.AspNet.SignalR.Transports.WebSocketTransport.AcceptWebSocketRequest(Func`2 callback)
at Microsoft.AspNet.SignalR.PersistentConnection.ProcessRequest(HostContext context)
at Microsoft.AspNet.SignalR.Hubs.HubDispatcher.ProcessRequest(HostContext context)
at Microsoft.AspNet.SignalR.PersistentConnection.ProcessRequest(IDictionary`2 environment)
at Microsoft.Owin.Mapping.MapMiddleware.<Invoke>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.IntegratedPipelineContext.EndFinalWork(IAsyncResult ar)
at System.Web.HttpApplication.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
I asked in the SignalR Jabbr chat what the error would be and they told me something is blocking the connections. I checked, and both TCP port 80 and port 443 are listening.
The IIS trust level is Full (internal) and we're not using loadbalancing. The Websockets protocol is installed.
What could be wrong?