Page 1 of 1

Login leads to blank page

Posted: Thu Feb 24, 2005 12:47 am
by bobt
I've downloaded and installed a premium edition trial, set up apache, php, mysql, imagemagick.

The pacsone.php login page appears ok, but after hitting the login button, I just get a blank page. Any suggestions?

software versions are:
php 4.3.10
MySql 4.1.10
Apache 2.0.53
ImageMagick6.1.9

Posted: Thu Feb 24, 2005 1:38 am
by pacsone
This seems like a MySQL PHP extension problem.

Are you able to login to the MySQL database from a command shell? i.e.,

C:\mysql\bin>mysql -u USERNAME -p DATABASE

If you can login from the command shell but not from the web page, then the problem is definitely with the MySQL PHP extension. You need to make sure the mysql PHP extension is loaded successfully from the output of the test page:

http://localhost/pacsone/Hello.php

Also, you should not install the stand-alone ImageMagick 6.1.9, since PacsOne includes a custom-built ImageMagick PHP extension that will have conflicts with the stand-alone ImageMagick installation.

Posted: Thu Feb 24, 2005 5:22 pm
by Guest
MySql seems fine - no problem logging in.

There are entries for both MySql and ImageMagick on the Hello.php page. PHP 4.3.10 has builtin MySql support. There is a comment to this effect in the Windows extension section of php.ini:

;Windows Extensions
;Note that MySQL and ODBC support is now built in, so no dll is needed for it.

I hadn't realized that an ImageMagick install was unnecessary, but anyway I copied php_imagick.dll from pacs/php to php/extensions per the instructions in the Readme file. SHould this be ok?

Posted: Thu Feb 24, 2005 5:24 pm
by bobt
That's me above. I must have forgotten to log before posting
bobt

Posted: Thu Feb 24, 2005 6:09 pm
by pacsone
If you can see Mysql and imagick PHP extensions in the output of the test page, then your Apache and PHP configurations are fine, the only thing left in the Session.save_path variable.

Check the value of the Session.save_path variable in the output of the test page, and make sure it is set to a valid directory. If so, when you get the blank page after you've entered the username/password, check the content of that directory to see if you see any files there.

Posted: Thu Feb 24, 2005 6:34 pm
by Guest
No problem. A new session file is created for each login

Posted: Thu Feb 24, 2005 6:36 pm
by Guest
I mean, the problem is still there, but the session files get created

Posted: Thu Feb 24, 2005 7:02 pm
by pacsone
In that case, you can enable PHP error logging by setting the following variables in your PHP.INI file:

error_reporting = E_ALL
log_errors = On
error_log = C:/php/php_err.log

Afer restarting Apache, do the same login again and check the PHP error logs to see if there's any complaints.

Posted: Thu Feb 24, 2005 10:51 pm
by bobt
It's becasue the database.php script will still be looking for mysql_connect or mysqli_connect functions:

[24-Feb-2005 11:53:05] PHP Warning: mysql_connect(): Client does not support authentication protocol requested by server; consider upgrading MySQL client in C:\Program Files\PacsOne\php\database.php on line 83

[24-Feb-2005 11:53:05] PHP Fatal error: Call to undefined function: mysql_connect_error() in C:\Program Files\PacsOne\php\database.php on line 98

This version opf php does not include the php_mysql.dll or php_mysqli.dll. There is a libmysql.dll in the php "dlls" folder. I assume that this has equivalent functions, but that they have been renamed and so are not compatible with the PacsOne database.php script.

I'll see if I can find either of those two dlls and try them. Any idea where I could find either of the two old .dlls? I checked in the php4.1.0 release but no luck.

Posted: Fri Feb 25, 2005 2:07 am
by pacsone
bobt wrote: [24-Feb-2005 11:53:05] PHP Warning: mysql_connect(): Client does not support authentication protocol requested by server; consider upgrading MySQL client in C:\Program Files\PacsOne\php\database.php on line 83
This error means that your MySQL server version 4.1.10 is not compatible with older MySQL clients, including the MySQL PHP extension used in the PHP distribution you've installed (4.3.10).

I guess you can either upgrade your PHP installation to 5.0.2, or downgrade your MySQL installation to the last 4.0.x release.

Posted: Fri Feb 25, 2005 3:29 am
by bobt
I belatedly saw the note in the installation manual stating that I should use PHP5 for mysql4.1.x and above. So I've installed it, adjusted the apache httpd configuration, and set up php.ini per the instructions for php5.

But now, the apache service will not start. It hangs up, the status shows as "Starting", and I can't stop or restart it until I reboot. If I remove the LoadModule statement for php5, Apache will then start.

So it's a whole new problem here now with Apache and PHP5. Any ideas?

Posted: Fri Feb 25, 2005 4:20 am
by pacsone
Make sure you have the php5ts.dll as well as the Apache PHP module php5apache2.dll in the directory where you installed PHP.

You can also check the Apache error logs under the \Apache Group\Apache2\logs\ directory for any clues.

Posted: Sat Feb 26, 2005 12:58 am
by bobt
I moved the statement

AddType application/x-httpd-php .php

out from the <IfModule mod_mime.c> block and placed it below the LoadModule statement.

Apache starts up fine now.

One question I hope you can answer today: I've tried to do an Import Studies from directory. I get the warning about no Dicomdir, and the job shows up in the Job Status as "submitted", but it has yet to execute. Nothing else is going on. What's the problem?

Posted: Sat Feb 26, 2005 1:02 am
by bobt
Here's the log for the import job:
Fri Feb 25 16:28:53 2005 INFO - Processing database job <4>
Fri Feb 25 16:28:53 2005 INFO - JobID [4]: Start importing from directory [C:/dev/dicom/images/].
Fri Feb 25 16:28:53 2005 WARNING - JobID [4]: Failed to open DICOM directory: [C:/dev/dicom/images/DICOMDIR], reading raw files instead.
Fri Feb 25 16:28:53 2005 ERROR - Error reading Unique ID: Group = 0x2 Element = 0x13
Fri Feb 25 16:28:53 2005 ERROR - Error reading Unique ID: Group = 0x2 Element = 0x13
Fri Feb 25 16:28:53 2005 ERROR - Error reading Unique ID: Group = 0x8 Element = 0
Fri Feb 25 16:28:53 2005 ERROR - Error reading Unique ID: Group = 0x8 Element = 0
Fri Feb 25 16:28:54 2005 INFO - 24 tags processed in CDataSetPdv
Fri Feb 25 16:28:54 2005 INFO - 26 tags processed in CDataSetPdv
Fri Feb 25 16:28:54 2005 ERROR - EXECUTE: SQL Bad Query: Duplicate entry '' for key 1
Fri Feb 25 16:28:54 2005 INFO - 25 tags processed in CDataSetPdv
Fri Feb 25 16:28:54 2005 ERROR - EXECUTE: SQL Bad Query: Duplicate entry '' for key 1
Fri Feb 25 16:28:54 2005 INFO - 23 tags processed in CDataSetPdv
Fri Feb 25 16:28:54 2005 ERROR - EXECUTE: SQL Bad Query: Duplicate entry '' for key 1
Fri Feb 25 16:28:54 2005 INFO - 19 tags processed in CDataSetPdv
Fri Feb 25 16:28:54 2005 ERROR - EXECUTE: SQL Bad Query: Duplicate entry '' for key 1
Fri Feb 25 16:28:54 2005 INFO - 22 tags processed in CDataSetPdv
Fri Feb 25 16:28:54 2005 ERROR - EXECUTE: SQL Bad Query: Duplicate entry '' for key 1
Fri Feb 25 16:28:54 2005 INFO - 25 tags processed in CDataSetPdv
Fri Feb 25 16:28:54 2005 ERROR - EXECUTE: SQL Bad Query: Duplicate entry '' for key 1
Fri Feb 25 16:28:54 2005 INFO - 25 tags processed in CDataSetPdv
Fri Feb 25 16:28:54 2005 ERROR - EXECUTE: SQL Bad Query: Duplicate entry '' for key 1
Fri Feb 25 16:28:54 2005 INFO - 20 tags processed in CDataSetPdv
Fri Feb 25 16:28:54 2005 ERROR - EXECUTE: SQL Bad Query: Duplicate entry '' for key 1
Fri Feb 25 16:28:54 2005 INFO - 20 tags processed in CDataSetPdv
Fri Feb 25 16:28:54 2005 ERROR - EXECUTE: SQL Bad Query: Duplicate entry '' for key 1
Fri Feb 25 16:28:54 2005 INFO - 19 tags processed in CDataSetPdv
Fri Feb 25 16:28:54 2005 ERROR - EXECUTE: SQL Bad Query: Duplicate entry '' for key 1
Fri Feb 25 16:28:54 2005 ERROR - EXECUTE: SQL Bad Query: Duplicate entry '' for key 1
Fri Feb 25 16:28:54 2005 INFO - 21 tags processed in CDataSetPdv
Fri Feb 25 16:28:54 2005 ERROR - EXECUTE: SQL Bad Query: Duplicate entry '' for key 1
Fri Feb 25 16:28:54 2005 INFO - JobID [4]: Finish importing from directory [C:/dev/dicom/images/].

Posted: Sat Feb 26, 2005 1:05 am
by bobt
Ooops, sorry. It looks like it has finally run. Sorry for the bother