Home > Unexpected Error > Unexpected Error Occurred 12037

Unexpected Error Occurred 12037

When using this combination - it works but is not ideal. Try JIRA - bug tracking software for your team. Header Winhttp.h See also WinHTTP Versions     Show: Inherited Protected Print Export (0) Print Export (0) Share IN THIS ARTICLE Is this page helpful? I call build -s JOB_NAME via cli. this content

Looking at your log files (see below) there is one instance where an error occurs 12 seconds after the previous timeout. While the tests pass in our local machines, we're randomly having failures in one of the modules in Jenkins. Can you please help? Before this behavior started, a download of Vista WAIK stopped at 50% completion. http://unexpected.error.occurred.12037.winwizards.org/

We repeated the test and are seeing this I/O error in chunked connection again. (right now only 1.441 running in Winstone will work without this error). Nothing is working - we still get the I/O chunked connection/Unexpected term of channel error. Finally we should really say thank you to George who managed to get a packet trace with the failure so that we could work out what was going on. It isn't clear whether these are for the same job or for something else.

  • The issue was due to webserver connection timeout before so it is likely to be something like 60, 30, 20 or 15 seconds.
  • Thanks Hide Permalink mark streit added a comment - 2012/Feb/07 11:05 PM Have attached logs from the Tomcat server where we are running this.
  • It isn't clear whether these are for the same job or for something else.
  • Looking at the source in FullDuplexHttpChannel.java that sets isRestricted based on user authentication so this could give a clue as to why it might occur for some and not others.

But its clear that the ping thread is definitely failing in this case so hopefully fixing that will make things work. Is it safe to assume the fixed version will be part of the official 1.459 release? Show Richard Mortimer added a comment - 2012/Mar/07 3:13 PM Well I think that pretty much rules out the ping interval directly. Progress since my last report.

I'm not running through any sort of Apache or Tomcat proxy so I don't have SSL running. Show Richard Mortimer added a comment - 2012/Feb/21 2:53 PM - edited Oops comment added to wrong issue! Unexpected Error Occurred 12037 Error Codes are caused in one way or another by misconfigured system files in your windows operating system. https://support.microsoft.com/en-us/kb/193625 The console shows: mavenExecutionResult exceptions not empty message : Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on project cm-web: Error occurred in starting fork, check output in log cause : Error occurred

This happens to workaround an issue in the remoting PingThread implementation which causes the ping to busy wait for the timeout period instead of keeping the channel alive. it appears to be WORKING NOW . Now with Jenkins 1.441 - we are getting the ERROR again and NOW WITH BOTH Winstone and the Tomcat configurations). The channel times out after 1 minute exactly.

Unexpected Error - Error Code: -2147221231 14. http://www.yqcomputer.com/1221_1186_1.htm Feb 6, 2012 2:48:00 PM hudson.remoting.Channel$ReaderThread run SEVERE: I/O error in channel Chunked connection to http: //99.99.99.94:8082/jenkins/cli java.io.IOException: Unexpected termination of the channel at hudson.remoting.Channel$ReaderThread.run(Channel.java:1133) 10.25.50.94 - - [06/Feb/2012:14:48:00 -0500] "POST Hide Permalink Richard Mortimer added a comment - 2012/Feb/16 11:01 PM I'm still max'd out with $dayjob and have not had time to look in much detail at this. Hide Permalink George Panayotov added a comment - 2012/Mar/26 8:51 PM I'm using internal Jenkins users with Matrix based security (global, not project-based).

Thanks Show mark streit added a comment - 2011/Dec/09 1:25 AM I will get logs from the Tomcat server. news Windows Server 2003 with SP1 and Windows XP with SP2:  This error is not supported. ERROR_WINHTTP_CONNECTION_ERROR 12030 The connection with the server has been reset or terminated, or an incompatible SSL protocol was The one difference that I'm aware of is that the connections in JENKINS-12037 are done over the cli channel using two HTTP connections rather than to the JNLP port. Alternately there may be something external that is breaking the connection.

Find out more Latest News & Blog News, views and ideas for your business Find out more MYOB Training Courses and materials designed to help you make the most of your That suggests that tomcat 7 is timing out in around 10 seconds. The console shows: mavenExecutionResult exceptions not empty message : Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on project cm-web: Error occurred in starting fork, check output in log cause : Error occurred have a peek at these guys Show mark streit added a comment - 2012/Feb/07 11:05 PM Have attached logs from the Tomcat server where we are running this.

Do you see any other activity on either of the two http streams (upstream and downstream) during the 60 seconds after the initial activity? Compatibility: Windows 7, 8, Vista, XP Download Size: 6MB Requirements: 300 MHz Processor, 256 MB Ram, 22 MB HDD Limitations: This download is a free evaluation version. This article contains information that shows you how to fix Unexpected Error Occurred 12037 both (manually) and (automatically) , In addition, this article will help you troubleshoot some common error messages

The snapshot build that you tested is direct from Jenkins on Jenkins builds.

That might be key to why I don't see this issue. This happens to workaround an issue in the remoting PingThread implementation which causes the ping to busy wait for the timeout period instead of keeping the channel alive. For now we have had to revert back to 1.441 running on Winstone only...and the original 1.441 CLI jar that came with it. I call build -s JOB_NAME via cli.

The Unexpected Error Occurred 12037 error is the Hexadecimal format of the error caused. Thanks Show mark streit added a comment - 2012/Mar/28 5:25 PM Based on the number of comments and information about the ping thread, is it safe to assume that it will Show George Panayotov added a comment - 2012/Mar/20 8:23 PM This is the Wireshark capture of the failing transaction. check my blog That suggests that tomcat 7 is timing out in around 10 seconds.

Without this the pinger busy waits retrying the same operation for the timeout period. There can be many events which may have resulted in the system files errors. If yes, why doesn't the website clear tell so?