Can this be a Postgres issue? Because at MySQL it seems to work fine?!

jhubbs, can you attach an SQL dump of the database?

It probably is a Postgresql. It was mentioned that the tables had been modified and that perhaps the code hadn't been audited for case sensitivity for the various changes.
http://www.limesurvey.org/forum/installation-a-update-issues/73169-192-rc3-create-database-failures-during-install?lang=en#73189

I don't understand how this is a duplicate of 5710? It might be related but the file that I attached in 5710 doesn't fix this problem.

Sorry, but we did not use your file. I fixed it before seeing your patch - and it also fixed this one.

I'm running the development tree. It's not fixed
Repo: https://limesurvey.svn.sourceforge.net/svnroot/limesurvey/source/limesurvey_dev
Revision: 12263

It works just fine here. Did you try to install on a clean, newly created database?

Yes. Part of my process is to update the dev tree checkout I have and drop/create database.

Well, I just tested it again here, works just fine. No matter if I do it on Postgres 8.x or 9.x. So unless you give me access to such a system to debug I am afraid I can't do anything and have to close this issue.

I can provide you with access since it's running in a VM. I'll need an email.

Is there anything about installation/configuration that the wiki instructions haven't documented?

jhubbs, you can send the details to Carsten using carsten.schmitz(at)limesurvey.org

Yep :-)

jhubbs, did you send anything? Because I did not get anything.

I sent an email Feb 2 around 18:51 UTC to the address listed on the web page which matches Mazi's post. I'll upgrade to the latest and re-send the login info again.

I went through the usercontrol.php file and pulled out the password comparison. When I dumped them to the output I received the following output. As you can see the two values are drastically different. Is there encoding value that I didn't set properly somewhere? The database is set for UTF-8. The database setup files in the limesurvey files are using UTF8 for encoding.

Using the SHA256::hashing($_POST['password'])
5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8

from the database
5653838343839386461323830343731353164306535366638646336323932373733363033643064366161626264643632613131656637323164313534326438

Run the following SQL command

ALTER DATABASE limesurvey SET bytea_output='escape';

and check if it fixes your problem.

This is usually executed automatically in createdb.php , around line 42

if($createdbtype=='postgres' && $connect->pgVersion=='9') 
{
    $connect->execute("ALTER DATABASE {$dbname} SET bytea_output='escape';");
}

I guess it is no executed on your database during installation. Please find out why by dumping $connect->pgVersion

$connect->pgVersion == '9.1' on my setup. I modified the file to add a check for 9.1. I'm able to login as admin now.

Thank you for the assistance.

1.92 released