{"id":580,"date":"2012-05-22T12:46:33","date_gmt":"2012-05-22T17:46:33","guid":{"rendered":"http:\/\/xlinesoft.com\/blog\/?p=580"},"modified":"2012-05-22T12:46:33","modified_gmt":"2012-05-22T17:46:33","slug":"troubleshooting-charts-in-phprunner-and-asprunnerpro-applications","status":"publish","type":"post","link":"https:\/\/xlinesoft.com\/blog\/2012\/05\/22\/troubleshooting-charts-in-phprunner-and-asprunnerpro-applications\/","title":{"rendered":"Troubleshooting charts in PHPRunner and ASPRunnerPro applications"},"content":{"rendered":"<p>In this tutorial we&#8217;ll find out how to troubleshoot chart errors in our applications. PHPRunner and ASPRunnerPro applications use Flash-based charting component that receives data in XML format. If any error happens while generating XML input you will see the following message instead of chart:<\/p>\n<pre>XML Parser failure:\r\nThe element type must be terminated by the matching end-tag.<\/pre>\n<p>Lets go a bit deeper. Right anywhere on the page (except on chart itself) and choose &#8216;View source&#8217;. In HTML source search for the first occurrence of <strong>dchartdata.php?<\/strong> (<strong>dchartdata.asp?<\/strong> in ASPRunnerPro) string. You should see something like this:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2012\/05\/chart_dchartdata.png\" alt=\"\" title=\"chart_dchartdata\" width=\"737\" height=\"548\" class=\"alignleft size-full wp-image-587\" srcset=\"https:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2012\/05\/chart_dchartdata.png 737w, https:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2012\/05\/chart_dchartdata-300x223.png 300w, https:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2012\/05\/chart_dchartdata-150x111.png 150w, https:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2012\/05\/chart_dchartdata-400x297.png 400w\" sizes=\"auto, (max-width: 737px) 100vw, 737px\" \/><\/p>\n<p>Highlight <strong>dchartdata.php?chartname=Cars_Chart<\/strong> part, right click on it and choose <em>Copy<\/em>. Now paste it to the browser address line replacing <em>Cars_Chart_chart.php<\/em>. URL is supposed to look like this: <em>http:\/\/yourwebsite.com\/dchartdata.php?chartname=Cars_Chart<\/em>. Hit Enter.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2012\/05\/chart_dchartdata_browser.png\" alt=\"\" title=\"chart_dchartdata_browser\" width=\"741\" height=\"516\" class=\"alignleft size-full wp-image-582\" srcset=\"https:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2012\/05\/chart_dchartdata_browser.png 741w, https:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2012\/05\/chart_dchartdata_browser-300x208.png 300w, https:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2012\/05\/chart_dchartdata_browser-150x104.png 150w, https:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2012\/05\/chart_dchartdata_browser-400x278.png 400w\" sizes=\"auto, (max-width: 741px) 100vw, 741px\" \/><\/p>\n<p><strong>dchartdata<\/strong> file generates XML. As we can see something went wrong and this file produces the error. View the source of this page again. Search for &#8216;php error happened&#8217; string (&#8216;asp error happened&#8217; in ASPRunnerPro). <\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2012\/05\/chart_error_found.png\" alt=\"\" title=\"chart_error_found\" width=\"849\" height=\"560\" class=\"alignleft size-full wp-image-583\" srcset=\"https:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2012\/05\/chart_error_found.png 849w, https:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2012\/05\/chart_error_found-300x197.png 300w, https:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2012\/05\/chart_error_found-150x98.png 150w, https:\/\/xlinesoft.com\/blog\/wp-content\/uploads\/2012\/05\/chart_error_found-400x263.png 400w\" sizes=\"auto, (max-width: 849px) 100vw, 849px\" \/><\/p>\n<p>Now we can see the actual error message. In this specific case table named &#8216;Cars&#8217; s missing in the database. Probably table was removed or renamed after project was built. To fix this you either need to change the chart definition in your project or to rename this table back. <\/p>\n","protected":false},"excerpt":{"rendered":"<p>In this tutorial we&#8217;ll find out how to troubleshoot chart errors in our applications. PHPRunner and ASPRunnerPro applications use Flash-based charting component that receives data in XML format. If any error happens while generating XML input you will see the following message instead of chart: XML Parser failure: The element type must be terminated by the matching end-tag. Lets go a bit deeper. Right anywhere on the page (except on chart itself) and choose &#8216;View source&#8217;. In HTML source search for the first occurrence of&#8230;<span class=\"clearfix clearfix-post\"><\/span><a href=\"https:\/\/xlinesoft.com\/blog\/2012\/05\/22\/troubleshooting-charts-in-phprunner-and-asprunnerpro-applications\/\" class=\"more-link\">Continue Reading <span class=\"screen-reader-text\">&#8220;Troubleshooting charts in PHPRunner and ASPRunnerPro applications&#8221;<\/span> <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-580","post","type-post","status-publish","format-standard","hentry","category-php-category"],"_links":{"self":[{"href":"https:\/\/xlinesoft.com\/blog\/wp-json\/wp\/v2\/posts\/580","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/xlinesoft.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/xlinesoft.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/xlinesoft.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/xlinesoft.com\/blog\/wp-json\/wp\/v2\/comments?post=580"}],"version-history":[{"count":5,"href":"https:\/\/xlinesoft.com\/blog\/wp-json\/wp\/v2\/posts\/580\/revisions"}],"predecessor-version":[{"id":590,"href":"https:\/\/xlinesoft.com\/blog\/wp-json\/wp\/v2\/posts\/580\/revisions\/590"}],"wp:attachment":[{"href":"https:\/\/xlinesoft.com\/blog\/wp-json\/wp\/v2\/media?parent=580"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/xlinesoft.com\/blog\/wp-json\/wp\/v2\/categories?post=580"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/xlinesoft.com\/blog\/wp-json\/wp\/v2\/tags?post=580"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}