Error 800a0e7c, 'Parameter object is improperly defined...', is one those errors that is practicely useless for troubleshooting.
Here is more of the error as logged by the Pivotal Lifecycle Server XML interface:
<error> <errorNumber>800a0e7c</errorNumber> <errorText>Parameter object is improperly defined. Inconsistent or incomplete information was provided.</errorText> <errorDetails> HRESULT = 800A0E7C -- Unknown error
...
</errorDetails> </error>
I've seen this error before when working with VB6, and you may have also. The error is thrown by ADODB, an ActiveX Data Object. My most recent occurrance was in troubleshooting a web service implementing RXMLWriteSystem, a Pivotal Lifecycle Server XML interface. The web service submits an XML payload using the DoXMLCommand method.
What is counter-intuitive when troubleshooting this Pivotal XML interface ADODB error is that whether the command is a record insert or update, the command correctly executes a transaction to insert or update a record. However, instead of returning a command result containing a record id for an insert or nothing for an update, the aforementioned error is returned. Since an error is returned to the calling program other errors may be thrown or the calling program does not perform as intended.
I remember troubleshooting this error years ago in a similar situation. Back then I had documented the error, its circumstance and resolution. This gave me an advantage in quickly resolving the issue.
The resolution to this error from my experience is the following:
The application pool running the web service that implements the Pivotal XML Interface must use an account identity having sufficient security permissions in Pivotal. The system account ‘Network Service’ can not be used for the application pool identity.
From the transaction result and the resolution, you can see that the error does not offer much help in providing insight to a resolution.
