This message indicates a problem with MySQL installation where Windows cannot find LIBMYSQL.DLL from either %SystemRoot%\System32 directory or directories listed in the system %PATH% environment variable.

There are two ways to get around this problem:

• Copy LIBMYSQL.DLL from your MySQL installation directory into %SystemRoot%\System32 or any directory that is in your system %PATH% environment variable.
• Modify your system %PATH% environment to include the directory where LIBMYSQL.DLL is located.

This error is cause by LIBMYSQL.dll distributed with MySQL release 4.0.0 or later, where the DLL entry point mysql_connect has become obsolete and is no longer supported.

There are two ways to get around this problem:

• Download version 1.0.0.3 or latest PacsOne installation package, which is compatible with both MySQL release 3.23.5x and 4.0.x
• Download MySQL release 3.23.53 or the closest 3.23.5x release instead

This error is caused by a bug in the PacsOne Server installation program which has since been fixed. To get around this problem, you can:

• Download version 1.0.0.2 or latest PacsOne Server installation package
• Setup database schema manually by performing the following steps: (Not recommended)
  • Open a DOS shell
  • Change directory to where PacsOne Server was installed, e.g., cd \Program Files\PacsOne
  • Run MySQL command: mysql -vvf --user=USERNAME --password=PASSWD DBNAME < db_schema > .\log\db_install.log where:

    DBNAME is the name of the MySQL database you setup for PacsOne Server
    USERNAME is a valid MySQL username with FULL priviledge to DBNAME database and
    PASSWD is the MySQL password for USERNAME.

  • Run setup.exe again but this time UNCHECK "Drop and create database tables" option box.

This message indicates problem(s) with your PHP.INI configurations. Make sure the file is saved in Windows file format, not UNIX file format. A recommended method of configuring the PHP.INI file is to take the sample php.ini-recommended file that comes with standard PHP distribution package, and make the following modifications based on your specific path configurations:

• extension_dir = {PHP_INSTALLATION_DIR}\extensions\ where {PHP_INSTALLATION_DIR} is the directory path of your PHP installation.
• Add extension=php_imagick.dll entry to the PHP dynamic extension list.
• session.save_path = {PATH} where {PATH} is a valid directory path.

There's a bug in PacsOne Server version 1.0.0.3 or earlier, which can make Efilm fail to establish associations with PacsOne Server if Efilm performs strict checking on the Association Accept (A_ASSOCIATE_AC) PDU sent by PacsOne Server. This bug has since been fixed in version 1.0.0.4 or later of PacsOne Server.

Follow the instructions detailed in the Upgrade section of the PacsOne Server Installation Guide.

There's a bug in PacsOne Server version 1.0.0.5 or earlier, where the database column name 'EthnicGroup' was incorrectly named as 'EthicGroup'. This bug has since been fixed in version 1.0.0.6 or later of PacsOne Server.

You can also correct the typo above manually (instead of doing a full upgrade) as follows:

• Type: mysql -u USER -p DBNAME from a command shell to login to MySQL database, where DBNAME is the name of MySQL database for PacsOne, USER is the MySQL username with FULL privileges for database DBNAME.
• From the MySQL shell prompt: mysql>alter table patient change ethicgroup ethnicgroup varchar(16);.

There's a bug in PacsOne Server version 1.0.0.8 'showImage.php', where the URL for the images was not constructed properly. This bug has since been fixed and included in the updated version 1.0.0.8. You can download the latest Php.zip and replace the old version of 'showImage.php' file under the 'php' sub-directory of your PacsOne installation.

The crashed is caused by a bug in the ImageMagick DICOM image display component 'IM_MOD_RL_dcm_.dll' which was distributed with PacsOne Server version 1.0.0.8 or earlier. This bug has since been fixed and included in version 1.0.0.9. You can download the latest Imagick.zip and replace the old version of 'IM_MOD_RL_dcm_.dll' file under the 'ImageMagick' sub-directory of your PacsOne installation.

This problem was caused by some browser agenets (IE 6.0 for example) that do not automatically UrlEncode the variables sent in the HTTP GET or POST requests. A fix is now available in the latest PHP.ZIP and will be included in the next version.

This problem was caused by a bug in the DICOM server component of PacsOne where it's sending the wrong Dataset Type when transmitting images to remote C-STORE SCP applications. This bug has since been fixed in version 1.0.0.11 and has been tested and verified to work with eFilm 1.5.3 and DCMTK Server.

There are two possible sources of this problem:

• PacsOne Server is not running: You can verify if this is the case by opening the Windows Task Manager (CTRL-ALT-DLT then Task Manager), if you see a task named "PacsOne.exe" on the task list, then PacsOne Server is running.
• PacsOne Server has been configured to listen to a different TCP port from the one the remote AE is connecting to. Please verify that the configured TCP port in the following Registry value is the same as the port the remote AE is connecting to:

  HKEY_LOCAL_MACHINE\Software\RainbowFish Software\PacsOne\ServerPortNumber

This error means that this remote AE is unknown/not configured to PacsOne Server, or access has been Disabled for this remote AE by PacsOne Server. You need to add this remote AE in the Application Entity page of PacsOne Server if you have not done so already, and Enable access for this remote AE.

This message means that your trial license has expired. If you have indeed purchased an official license for PacsOne Server Premium Edition but still receive this error, then it might be possible that the license file "License.dat" (under the directory where PacsOne Server Premium Edition is installed) is either missing or corrupted. Please send your license file "License.dat" in a ZIP file attachment to: licensing.info@rainbowfishsoftware.com for repair.

Starting from version 3.1.1, significant database optimizations have been implemented in PacsOne Server Premium Edition to improve the performance of database queries. In addition to these optimizations by PacsOne Server, you can also tweak more performance improvement from your MySQL Server by following the MySQL database tuning tips below:

• Server Hardware Optimizations for MySQL Database:
  • Store the MySQL data files on RAID disk whenever possible
  • If you have a choice for RAID levels, use RAID-10, RAID-1, and RAID-0 as your order of preference
  • Always use faster RPM disks whenever possible
  • Use faster clock-speed ECC Memory whenever possible


• Fine-Tuning Your MySQL Server Software Configurations:

  MySQL Table Type	MY.INI Settings
  INNODB	Variable	Description	Recommended Setting
  	innodb_additional_mem_pool_size	Additional memory pool that is used by InnoDB to store metadata information. If InnoDB requires more memory for this purpose it will start to allocate it from the OS. As this is fast enough on most recent operating systems, you normally do not need to change this value. SHOW INNODB STATUS will display the current amount used.	32 M
  	innodb_log_buffer_size	The size of the buffer InnoDB uses for buffering log data. As soon as it is full, InnoDB will have to flush it to disk. As it is flushed once per second anyway, it does not make sense to have it very large (even with long transactions).	1 M
  	innodb_buffer_pool_size	InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and row data. The bigger you set this the less disk I/O is needed to access data in tables. On a dedicated database server you may set this parameter up to 80% of the machine physical memory size. Do not set it too large, though, because competition of the physical memory may cause paging in the operating system. Note that on 32bit systems you might be limited to 2-3.5G of user level memory per process, so do not set it too high.	60% of total physical memory
  	innodb_log_file_size	Size of each log file in a log group. You should set the combined size of log files to about 25%-100% of your buffer pool size to avoid unneeded buffer pool flush activity on log file overwrite. However, note that a larger logfile size will increase the time needed for the recovery process.	50% of innodb_buffer_pool_size value above
  MyISAM	key_buffer_size	Size of the Key Buffer, used to cache index blocks for MyISAM tables. Do not set it larger than 30% of your available memory, as some memory is also required by the OS to cache rows. Even if you're not using MyISAM tables, you should still set it to 8-64M as it will also be used for internal temporary disk tables.	25% of total physical memory
  	myisam_sort_buffer_size	If the temporary file used for fast index creation would be bigger than using the key cache by the amount specified here, then prefer the key cache method. This is mainly used to force long character keys in large tables to use the slower key cache method to create the index.	64 M
  	sort_buffer_size	This buffer is allocated when MySQL needs to rebuild the index in REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE into an empty table. It is allocated per thread so be careful with large settings.	1 M
  	read_buffer_size	Size of the buffer used for doing full table scans of MyISAM tables. Allocated per thread, if a full scan is needed.	1 M

The trial license expiration message displayed at the bottom of PacsOne Server web pages is merely a courtesy reminder which is calculated based on the file creation date of the trial license file. It has no affect whatsover on whether or when the license will expire. This message will disappear on the date shown, or if you want it to disappear sooner, you can comment out the expiration date calculation function in the script php/footer.php under the directory where PacsOne Server is installed.

Please checkout our PacsOne Server Migration Guide online for transferring an existing PacsOne Server database to a new server.