topic CIM ASP Sample Code Error in Integration and Testing

CIM ASP Sample Code Error

keepkonnected — Thu, 15 Sep 2011 22:20:08 GMT

I am attempting to use the ASP sample code for the CIM process to create a new user profile and I get the following error:

Raw response: <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Header><soap12:Upgrade xmlns:soap12="http://www.w3.org/2003/05/soap-envelope"><soap12:SupportedEnvelope qname="soap:Envelope" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" /><soap12:SupportedEnvelope qname="soap12:Envelope" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope" /></soap12:Upgrade></soap:Header><soap:Body><soap:Fault><faultcode>soap:VersionMismatch</faultcode><faultstring>Possible SOAP version mismatch: Envelope namespace AnetApi/xml/v1/schema/AnetApiSchema.xsd was unexpected. Expecting http://schemas.xmlsoap.org/soap/envelope/.</faultstring><detail /></soap:Fault></soap:Body></soap:Envelope>

Microsoft VBScript runtime error '800a01a8'

Object required: 'objResponse.selectSingleNode(...)'

/web/util.asp, line 47

The only item I have edited in the sample code is the login name, transaction key, and the API URL. Anyone have an idea what is wrong?

Re: CIM ASP Sample Code Error

nbardach — Sun, 08 Jan 2012 07:35:20 GMT

I'm facing the same issue, having just switched from my demo account to a real account. Were you ever able to solve this issue? LMK. Thanks! Noah

Re: CIM ASP Sample Code Error

Trevor — Mon, 09 Jan 2012 21:28:59 GMT

I'm afraid that the ASP sample code isn't actively maintained anymore since that language is no longer supported. I quickly looked at the code and it would seem this error was most likely caused because the transaction response was not recorded. I would recommend dumping the objResponse object to see what it contains. Most likely, the error is actually occuring during the SendApiRequest and simply isn't being reported until the response parsed later in the code.