XML Issues with submissions and retrieving data

Incorporation
1

There is currently an issue on XML submissions with customers receiving XML failed schema validation: XML error: Fatal error encountered during schema scan line 8 column 68
or
Fatal error encountered during schema scan line 1 column 367 amongst others.
IT are currently investigating the issue.

2

Good morning,

We are experiencing this issue on incorporation requests, as well as StatusAck messages. e.g.,

XML failed schema validation: XML error: Fatal error encountered during schema scan line 24 column 247

Has the issue been resolved?

Many thanks for your help.

3

Hi Misrab, I can confirm the issue is ongoing. Apologies for any inconvenience this is causing. I can confirm IT are still working on a solution.

4

Hi - any update on this? Just submitted XML message for Accounts and received [XML failed schema validation: XML error: Fatal error encountered during schema scan line 1 column 384]

5

No at the moment sorry. IT are still working on it and will post it on here as soon as I have an update.

6

Hi All,

Are there also similar issues with Confirmation statements at the minute? We are seeing intermittent errors when trying to retrieve CS01 data over the past few days.

Thanks.

7

Hi Marion, yes this is affecting all types of documents filed using xml.

8

Thanks for confirming, I’ll watch out for an update on here. Can you confirm how long this has been happening for? We have had intermittent reports of issues since Monday. Is that likely to be the same thing?

Kind Regards

9

We have some clients who have been able to submit CS01 filings and others are coming back with this problem with submission error message for example: Rejection Code: 7777 Description: There was a problem processing your submission.

Are we to assume if we see the rejection code 7777 on any submission until this issue is resolved that it is linked to the problem on the Companies House side rather than an issue with the data being sent over from the software provider?

10

We have seen a big drop in errors, please can you try it again now. Thank you

11

Thanks for the update will try again

12

Hi we are still getting the following for StatusAck:

XML failed schema validation: XML error: Fatal error encountered during schema scan line 24 column 247

13

Hi Misrab, Please can you try again and if it fails can you send me the raw data xml request and response to xml@companieshouse.gov.uk marking it for the attention of Richard and I will take a look at it. Thank you.

14

Thank you, I have sent an email. Below is the response we are getting for a Company Incorporation. We are receiving similar responses for other calls, such as StatusAck, PSCNotification and others.

This is now P0 critical to us, disrupting business services. Your help is much appreciated.

Example response:

<?xml version="1.0" encoding="UTF-8" ?>
<GovTalkMessage xsi:schemaLocation="http://www.govtalk.gov.uk/schemas/govtalk/govtalkheader http://xmlgw.companieshouse.gov.uk/v1-0/schema/Egov_ch.xsd" xmlns="http://www.govtalk.gov.uk/schemas/govtalk/govtalkheader" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns:gt="http://www.govtalk.gov.uk/schemas/govtalk/core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >
  <EnvelopeVersion>1.0</EnvelopeVersion>
  <Header>
    <MessageDetails>
      <Class></Class>
      <Qualifier>error</Qualifier>
      <TransactionID></TransactionID>
      <GatewayTimestamp>2020-06-26T11:03:02-00:00</GatewayTimestamp>
    </MessageDetails>
    <SenderDetails>
      <IDAuthentication>
        <SenderID>REDACTED</SenderID>
        <Authentication>
          <Method>CHMD5</Method>
          <Value>REDACTED</Value>
        </Authentication>
      </IDAuthentication>
    </SenderDetails>
  </Header>
  <GovTalkDetails>
    <Keys/>
	<GovTalkErrors>
	  <Error>
	    <RaisedBy>CH_XML_Gateway</RaisedBy>
	    <Number>100</Number>
	    <Type>fatal</Type>
	    <Text>XML failed schema validation: XML error: Fatal error encountered during schema scan  line 24 column 269</Text>
	    <Location></Location>
	  </Error>
	</GovTalkErrors>
  </GovTalkDetails>
  <Body>
  </Body>
</GovTalkMessage>
15

We can assure you we are working as hard as we can to identify the cause of this problem - Please bear with us, whilst we continue our investigations.

Apologies to all, we understand this is a major issue for you.

SDN

1 Like
16

Apologies for the interruption. The issue has been located and fixed.