Errors in RC1

ajperezcrespo wrote on Friday, April 22, 2005:

Patient Summary in Notes:
Fault: Code: 2 Reason ‘Invalid return payload: enabling debugging to examine incoming payload’

On Magnifying Glass Icon under patient documents:
Warning: Missing argument 3 for find_action() in /srv/www/htdocs/openemr/controllers/C_PatientFinder.class.php on line 34

Generate Report with jpg Documents:
Document ‘wristjpeg.JPG’
NOTE: Document ‘wristjpeg.JPG’ cannot be displayed inline becuase its type is not supported by the browser.
Yet it is viewable under documents option.

ajperezcrespo wrote on Friday, April 22, 2005:

When updating a user (added a FDID)

Fault: Code: 2 Reason ‘Invalid return payload: enabling debugging to examine incoming payload’

sunsetsystems wrote on Friday, April 22, 2005:

Does ws_server.pl exist at the location specified in includes/config.php?

It appears that by default this is specified:

$GLOBALS[‘oer_config’][‘ws_accounting’][‘url’] = “/sql-ledger/ws_server.pl”;

whereas the value should really be something like "/sql-ledger/bin/ws_server.pl".

– Rod <rod at sunsetsystems dot com>

tekknogenius wrote on Friday, April 22, 2005:

Remember, under the openemr version of sql-ledger there was a symbolic link from sql-ledger/ws_server.pl to sql-ledger/bin/ws_server.pl so it just needs to point to where ever ws_server.pl is stored.

sunsetsystems wrote on Friday, April 22, 2005:

I’m not sure why the warning message occurs but it seems to be harmless.

The "type is not supported by the browser" message happens because the .JPG extension is not lower case.  This is a minor bug.

– Rod <rod at sunsetsystems dot com>

ajperezcrespo wrote on Friday, April 22, 2005:

I updated the includes/config.php to
$GLOBALS[‘oer_config’][‘ws_accounting’][‘url’] =
“/sql-ledger/bin/ws_server.pl”;
and I placed a sym link to it as well.  Further more I created a new patient as well.

Entry has not been previously sent to external system or no entry was found for them in the integration mapping, could not send claim. Patient: ‘35’

Warning: Cannot modify header information - headers already sent by (output started at /srv/www/htdocs/openemr/library/classes/WSClaim.class.php:159) in /srv/www/htdocs/openemr/interface/billing/billing_process.php on line 77

I’m hoping to find a work around before blowing the DB away. For my demo site I dont have a problem with this.  But I’m sure that a clients sqeal will not be one of joy.

sunsetsystems wrote on Friday, April 22, 2005:

So you got rid of the "invalid return payload" message?  Good!

You can check the integration_mapping table and others from the Administration/Database Reporting page, which is really phpMyAdmin.  See if you have an entry for that patient, or for any patients.  If you do, you can check the local_id in the patient_data table, and the foreign_id in the sql-ledger customer table (use psql or phpPgAdmin).

I don’t think blowing away the database will solve anything.  This is a debugging problem.

– Rod <rod at sunsetsystems dot com>

tekknogenius wrote on Friday, April 22, 2005:

Fatal error: Call to undefined function: pg_pconnect() in /usr/local/src/openemr_cvs/openemr/library/sql-ledger.inc on line 9

When I clicked on [Reports] from the billing screen.

tekknogenius wrote on Friday, April 22, 2005:

Since I’m using Gentoo, I think I forgot to compile postgresql support in. I’m recompiling now…

ajperezcrespo wrote on Saturday, April 23, 2005:

No the payload errors are in other areas.  But as you mentioned they seem to be cosmetic.

ajperezcrespo wrote on Saturday, April 23, 2005:

I checked, Aint nothin there. So lemme poke around a little more and see whats up.  Any hints, Ideas or voodoo appreciated.

ajperezcrespo wrote on Saturday, April 23, 2005:

The Search option on SuperBill Code doesnt seem to work either.

sunsetsystems wrote on Saturday, April 23, 2005:

No, the payload error sounds serious to me.  It may be related to the integration_mapping table not getting updated. Start by reproducing the problem and then checking your log files.  If you like, you could email your configuration files to me and I’ll check them over.

– Rod <rod at sunsetsystems dot com>

sunsetsystems wrote on Saturday, April 23, 2005:

There is more than one place that you can search.  What exactly did you do?  Is this something that used to work and is now broken?

– Rod <rod at sunsetsystems dot com>

ajperezcrespo wrote on Saturday, April 23, 2005:

Heres a silly question:  Where are the log files stored?

ajperezcrespo wrote on Saturday, April 23, 2005:

Never mind it only seaches Code Numbers not the Text.  Text is on the previous screen.

tekknogenius wrote on Saturday, April 23, 2005:

Probably /var/log/apache or /var/log/apache2 depending on your installation of apache. I’m assuming that you’re using apache here. If not, then it will probably be in /var/log somewhere

sunsetsystems wrote on Saturday, April 23, 2005:

This will be system-dependent.  On my Ubuntu (Debian-like) setup PHP errors go to /var/log/user.log and Apache errors to /var/log/apache2/error.log.  There can also be meaningful messages in places like /var/log/messages or /var/log/syslog.

– Rod <rod at sunsetsystems dot com>

ajperezcrespo wrote on Sunday, April 24, 2005:

Im using SuSE 9.  I did notice that /sql-ledger/bin/ws_server.pl points to srv/www/sql-ledger. I’ve changed it to /srv/www/htdocs/sql-ledger.  What entries should be in the pg_hba.conf file?

ajperezcrespo wrote on Sunday, April 24, 2005:

Still broken, cant send data to the integration map. I’m still searching for and through log files.