upgrading to Pascone 5.1.2

dwilljch2 · Post by **dwilljch2** » Fri Jul 27, 2007 3:01 pm

we have been running pacone server 5.1.1(extreme edition) under trial license which expires on aug 23 ,2007 )with success .

Downloaded ver 5.1.2 and tried install. Followed prescribed procedures of a. stopping Apache Server, stopping Pascone server 5.12 , started install of ver 5.12.

at a certain point is is asking for a upgrade password.

WHAT IS THAT PASSWORD.

Thanks.

Post by **pacsone** » Fri Jul 27, 2007 3:20 pm

The upgrade password is available to those customers who have purchased one of the annual technical support options, which entitles them to free and unlimited upgrades to newer versions of PacsOne Server within the 12-month support period.

So if you are still on a trial license of PacsOne Server, you would not have received the upgrade password for your server since you have not made any purchase yet. However, you can still upgrade to version 5.1.2 executables by checking the Drop and create database tables checkbox from the Installer window, which will drop and create a fresh database instead of upgrading your existing database. Since you are still on a PacsOne Server trial license, there should not be more than 10000 images in the database, so you can simply re-send the images to PacsOne running version 5.1.2.

If you want to preserve the existing database with the upgrade, you would need to purchase a full PacsOne Server license and one of the annual technical support options, in order to receive the upgrade password which is required for upgrading the existing database.

dwilljch2 · Post by **dwilljch2** » Mon Jul 30, 2007 6:17 pm

upon upgrading to pacsone 5.12. as you suggested , and redefind the remote diccom AeTitles, i cannot modify certain parameters ( i.e. preferfered transfer syntax).

Is this possible because we are upgranding using a trial license.

thanks

Post by **pacsone** » Tue Jul 31, 2007 3:16 am

The trial license is not related here, as you can modify any parameters with the Modify privilege enabled for the logged-in user.

What's the error you got when you said you cannot modify certain parameters?

dwilljch2 · Post by **dwilljch2** » Tue Jul 31, 2007 1:40 pm

I am logged in as the superuser "root". when i change preferred transfer syntax to "JPEG lossless---" and hit the modify button the value will not change.

Thanks

Post by **pacsone** » Tue Jul 31, 2007 1:46 pm

It does not seem that your database tables have been upgraded successfully. Can you run the following query from a MySQL shell, after logging into the PacsOne Server database:

Code: Select all

mysql>describe applentity;

dwilljch2 · Post by **dwilljch2** » Tue Jul 31, 2007 2:52 pm

when i use the database and describe the applentity table all fields hase been appropriately defined. then when i "SELECT * FROM applentity;", all DICOM entries which i redefined after the upgrade are there. Again, when i try to modify "prefered syntax the change will not take place.

thanks,

dwilljch2 · Post by **dwilljch2** » Wed Aug 01, 2007 1:33 pm

i can modifiy all fields in an Aetille (applentity table ) except the "preferredmTransfer Syntax" --- trying to change from "none" to "JPEG lossless"

Thanks

Post by **pacsone** » Wed Aug 01, 2007 1:37 pm

1. Did you get any error when you tried to modify the preferred transfer syntax for a defined AE? If not, what happens after you click on the Modify button?

2. If there any way that we can access this server remotely? If so, please send the IP address and a valid remote login to pacsone@pacsone.net so that we can check it out remotely.

Post by **pacsone** » Thu Aug 02, 2007 12:59 am

It's not safe to post the public IP address of your server, or username/password here since this is a public forum where anyone (including spambots) can read your posts here.

This is confirmed to be a bug in the "modifyAeTitle.php" script which is preventing you from selecting the JPEG Lossless transfer syntax as the preferred transfer syntax for a remote AE. We've fixed it for your server and will make the fix available for the next release. Thank you very much for reporting this bug.

dwilljch2 · Post by **dwilljch2** » Thu Aug 02, 2007 12:34 pm

Thanks for the safety warning.