LsteventattendeeHistory suddenly started returning no resultsLsteventattendeeHistory suddenly started returning no resultshttp://developer.cisco.com/c/message_boards/find_thread?p_l_id=&threadId=48294992013-05-23T12:03:41Z2013-05-23T12:03:41ZRE: LsteventattendeeHistory suddenly started returning no resultsSteven Woodshttp://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=48295022011-03-16T18:26:09Z2011-03-16T18:26:09Zjust noticed that original thread had MS Word corrupted data in it. Edited original post to show the correct textSteven Woods2011-03-16T18:26:09ZLsteventattendeeHistory suddenly started returning no resultsSteven Woodshttp://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=48294982011-03-16T18:24:34Z2011-03-16T13:58:04ZI had a production system that was working well, but just recently, it appears that the original call just started returning a "No results" message, even on events that were originally fine. Did something change?
The original call is:
<?xml version=\"1.0\" encoding=\"UTF-8\"?>
<serv:message xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xmlns:serv=\"http://www.webex.com/schemas/2002/06/service\" xsi:schemaLocation=\"http://www.webex.com/schemas/2002/06/service.xsd\">
<header>
<securityContext>
<webExID>aaron.rothschild</webExID>
<password>XXXXX</password>
<siteName>apidemoeu</siteName>
</securityContext></header>
<body>
<bodyContent xsi:type=\"java:com.webex.service.binding.history.LsteventattendeeHistory\">
<sessionKey>692122123</sessionKey>
</bodyContent></body></serv:message>
and the message that it now returns is:
<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<serv:message xmlns:serv=\"http://www.webex.com/schemas/2002/06/service\" xmlns:com=\"http://www.webex.com/schemas/2002/06/common\" xmlns:history=\"http://www.webex.com/schemas/2002/06/service/history\">
<serv:header><serv:response>
<serv:result>FAILURE</serv:result>
<serv:reason>Sorry, no record found</serv:reason>
<serv:gsbStatus>PRIMARY</serv:gsbStatus>
<serv:exceptionID>000015</serv:exceptionID>
</serv:response></serv:header>
<serv:body><serv:bodyContent/>
</serv:body></serv:message>
any insights would be *greatly* appreciated.Steven Woods2011-03-16T13:58:04Z