Ticket #279 ( Closed )

Short Description Invalid data returned by HTTP Post
Entered By: MentisMan When: 1999-04-07 17:58:33 Build: 1.03.27e
Categories Type: Problem   Department: Product   Category: Troubleshooting
I get the following error message whenever the stml section which follows the error message is run:

Error occurred in CFX_SURFER tag Invalid data returned by HTTP Post--No <AMAZONSTREAM> in contents! (221):

HTTP/1.0 200 OK Date: Wednesday Wed, 7 Apr 1999 21:46:16 GMT 
Server: IELUA/1.0 MIME-version: 1.0 
Content-type: text/html Allow: GET,POST 
Last-Modified: Wednesday Wed, 7 Apr 1999 21:46:08 GMT
Content-length: 1008189
POST /clisurf/pme_scrapes HTTP/1.0 
Content-type: application/octet-stream 
Content-length: 87


<TESECTION pme_scrapes
	When tranpath_1 is "pme_scrapes">
 <TEPUTSECTION pstar.GetSession>
           USERID="amazon" PASSWORD="amazon">
 <teset PPV_PME.time_now = web.time_now>
 <!--- define insert statement into ppv_sched to 
       hold data --->
Append By: WindSurfer  When: 1999-04-07 20:07:26  New Status: Pending Customer
Comment Sorry, your entry got truncated by our current 2000 character limit in SupportCenter-- we are upgrading to Screensurfer 2.0Beta pretty soon, and at that time will be able to implement 8K appends...

Anyway, this is hard to diagnose without an accompanying trace (maybe can you send the template trace that corresponds to this error?)...my guess is that the SQL DELETE is giving you a +100 error code (no rows found), and since you aren't implementing any error handling, it is jumping to the end of execution...

This is still a bug, because regardless of how execution ends, you should still get a proper returned Status{} record in that outbound AMAZONSTREAM.

A work-around, and a good thing to know about, is to do a:

<TESET Task.UserErrors=1>
At the top of your section-- this will prevent the logic from jumping out on any SQL error, and give you the opportunity to check the sqlcode yourself.
Append By: POS Team  When: 1999-04-08 11:30:19  New Status: Closed
Comment Have added: as suggested. You are right, however, in that the error occurs when there are no records to delete. Thanks, j