Sorry an unexpected error was encountered validating your input


Most values also have a default message defined, which can be used to map the value to a human-readable text message; when this is done, the HRESULT value is also known as a message identifier.

Note: In the following descriptions, a percentage sign (%) followed by one or more alphanumeric characters (for example, "%1" or "%hs") indicates a variable that is replaced by text at the time the value is returned. However, this is a coordinated transaction, and a number of enlisted resources were aborted outright because they could not support abort-retaining semantics.

You specify how the component behaves when truncation or an error occurs by setting options on individual columns in the input or output.

For example, you can specify that the component should fail if customer name data is truncated, but ignore errors on another column that contains less important data.

The error encountered was: 500 Can't connect to localhost:8888 (connect: Connection refused) We were getting the following error while checking the domain in W3C validator and we managed to fix it by installing CA Bundle and Intermediate Root certificates for the same domain.

Now, the domain is able to pass through the W3C validation check and reporting appropriate result.

221 - The domain service is closing the transmission channel (also called SMTP Error 2.2.1) SMTP Error 221 : The server is ending the mail session - it is closing the conversation with the ISP as it has no more mail to send in this sending session.

Tip: Next time you see that message, try validating your document directly at instead.

Because if you see that 500 error it means the validator is trying to reach the HTML5 backend, which runs as a separate service/process responding at localhost:8888 on the validator host.

On the other hand if you get a 404 from it most likely means you caught me in the middle of restarting/redeploying the W3C HTML5 validator backends to pull in changes I've made to the sources from But that never takes me more than a few minutes, so on your end you should never be seeing that 500 error for more than, say, 10 minutes at most.

So if/when you do see it for any longer than that, please report it either by tweeting to @w3c or @sideshowbarker on twitter, or pinging me on IRC (Mike Smith on #whatwg or #w3c on

But we actually run several validator hosts, round-robin, so if you see that 500 error it could mean that only one of the HTML5 backends on one of the hosts is temporarily down.

You must have an account to comment. Please register or login here!