HI SCOTT:

I downloaded the PachydermInstaller-2.1beta3.jar and installed it on my Windows 2003 server. The software works great. The problem I had with creating multiple users has been solved. I can now create users and log in with their IDs to my heart’s content.

I had a couple of initial issues getting the login screen to work properly that were related to MySQL. The web server would not display the login page at all initially. It displayed a 404 error. This is because the table names in MySQL are case-sensitive. The table creation SQL scripts that are provided in the .jar create lowercase table names. However, the Pachyderm software expects uppercase table names for all tables except metadata2 and invitation. Modifying the install SQL scripts to create the correct case table names would give users a smoother installation experience.

Finally, I had two issues that were due to my setup of MySQL and my mail server. The login ID used for root access must be defined as a super user and have rights to the pachyderm database table before running the installer. The second issue was that my mail server on my Windows 2003 server had to have authentication set to anonymous instead of windows login because there are no credentials coming from Pachyderm for login.

I successfully created three presentations under different accounts and was able to publish them. I discovered that using the same account ID from multiple machines can cause errors if both try to publish around the same time. So I created multiple generic user IDs for our Special Collections folks and we are going to have them play with this version.

I currently have all the software set up on development machines for testing. MySQL is running on a separate Solaris x86 server, in its own zfs zone, from the web server and Pachyderm. The installation gui set this up without any problems. Good Job!

Thanks again to you and your team for all of the hard work in making this version of Pachyderm a reality.

Yes, the installer is still having problems with table names.

Caused by: Table 'pachyderm.APDEFAULT' doesn't exist at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1026)

The table name created by the installer is lower case but the external table name in APDefault.plist is UPPER case. As you discovered, this applies to most tables created by the install.

Hi-

So are you installing with an existing MySQL database on Windows or did you set everything up from scratch? Which version of windows are you using? What version of MySQL?

We have had a few dozen successful installations on Windows without these issues, but the were all done on fresh DB installations.

Thank you for your help.

-Scott

HI SCOTT:
I am running Pachyderm on a Windows 2003 Server version 5.2.3790, with Service Pack 2 Build 3790, and MySQL version 5.1.46 is running on a separate Solaris x86 server, in its own zfs zone.

User mspalti noted in this forum thread that he has the same problem with the sql table creations in the install script.

Hope this helps.

Hi Scott

I see now that this was a Windows server, but the problem is the same I run into every time on Linux. (In fact, I just tried the new installer on Redhat Linux and saw the error again.) I'm not an expert on mysql, but whether or not the OS file system is case sensitive does appear to matter. There might also be a config setting that causes mysql to be case-sensitive on a Windows system?

Anyway, for the record, I deleted the pachyderm table from mysql and started fresh on my Linux installation.

There's a simple fix. The script that initializes the database must use table names AND cases identical to the ones in the plist files -- and since that's not the case today, I go in after the installation and rename things. It would be great if we could get rid of that step by syncing things up in the installer.

Thanks!

Mike

Hi-

We had this case issue in the past with 2.0 and the very first beta of 2.1, but we thought we had it fixed.
A couple more questions.
1) Did you install over a past beta or 2.0 install of Pachyderm.
2) Confirming that you both used the 2.1.0.1R3 release?

Can you look in the database and tell me which tables are uppercase and which are lower? All should be lower case except one.

Thanks again for your assistance.

Best,
Scott