Can't call method "bind_param" on an undefined value

Hi there,

We’re testing out submitting a confirmation statment to the beta gateway but every request we submit gets the following response returned:

 <GovTalkErrors>
  <Error>
    <RaisedBy>CH_XML_Gateway</RaisedBy>
    <Number>9999</Number>
    <Type>fatal</Type>
    <Text>Can't call method "bind_param" on an undefined value</Text>
    <Location></Location>
  </Error>
</GovTalkErrors>

We’re validating the XML against the XSDs before we send it and they’re reporting that it’s structurally sound. I thought maybe we were missing some detail in our PSCs element so we’ve scaled it back to just sending a single PSCStatement, but we still get the same problem.

This is a snippet of the XML we’re sending

<ConfirmationStatement xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xsi:schemaLocation="http://xmlgw.companieshouse.gov.uk http://xmlbeta.companieshouse.gov.uk/v1-0/schema/forms/ConfirmationStatement-v1-0-rc1.xsd" xmlns="http://xmlgw.companieshouse.gov.uk">
	<ReviewDate>2016-06-14</ReviewDate>
	<StatementOfCapital>
		<Capital>
			<TotalAmountUnpaid>0</TotalAmountUnpaid>
			<TotalNumberOfIssuedShares>1.0</TotalNumberOfIssuedShares>
			<ShareCurrency>GBP</ShareCurrency>
			<TotalAggregateNominalValue>1.00000000</TotalAggregateNominalValue>
			<Shares>
				<ShareClass>Ordinary</ShareClass>
				<PrescribedParticulars>BLAH BLAH BLAH</PrescribedParticulars>
				<NumShares>1</NumShares>
				<AggregateNominalValue>1</AggregateNominalValue>
			</Shares>
		</Capital>
	</StatementOfCapital>
	<PSCs>
		<StatementNotifications>
			<StatementNotification>
				<PSCStatement>PSC_EXISTS_BUT_NOT_IDENTIFIED</PSCStatement>
			</StatementNotification>
		</StatementNotifications>
	</PSCs>
	<StateConfirmation>true</StateConfirmation>
</ConfirmationStatement>

Is there something we’re not doing/doing wrong or some combination of data that we’re missing? Anything you can do to point us in the right direction would be much appreciated.

Thanks,

Dave

Its not you doing anything wrong we have a problem on Beta with the confirmation statement which we are investigating, thanks