John, We are trying to figure out what the specific issue is here. We haven't as of yet had trouble installing on Windows 2008, though haven't tried Windows 2008 R2. Are you running regular Windows 2008 or Windows 2008 R2? Also it is possible we aren't properly escaping special characters, can you verify that the password you thought you typed in is the one for the postgres PostgreSQL super user account, and not the postgres windows account? Although both users go by the same name -- the PostgreSQL account system is detached from the windows account system, so although they have the same name, they might not have the same password. This has caused quite a lot of confusion for people particularly people new to PostgreSQL. We are also a bit puzzled about the setting pg_hba.conf to trust and it not working. In this setting any password you type even if it is wrong would work. Did you reload the config or restart the service? The settings don't take effect unless you reload the config with a postgresql reload or restart the service. We'll experiment on our end to see if the % in password is causing a problem. Thanks, Leo and Regina http://www.postgis.us
_____ From: [email protected] [mailto:[email protected]] On Behalf Of john lace Sent: Thursday, April 22, 2010 10:39 PM To: [email protected] Subject: [postgis-users] Bug in postgis installation on WinServer2008-64bit Hi, I just found a problem with the Postgis 1.5 installation on a Windows Server 2008 64 bit platform, When I installed postgres, it requested a more "secure" password for user 'postgres', maybe because this is a policy on WinServer2008, and I used a combination of special chars, something like 'my00%$password&' Postgres accepted it very well, but the installation of postgis didn't. Not postgis 1.4, nor 1.5, not on postgres 8.3, 8.3.7, 8.4.3. I kept installing different options and watching them fail. The postgis installation kept failing, with an error 'password is incorrect for user postgres', even when I edited pg_hba.conf to make it trust 127.0.0.1 The problem got worse, because when the postgis installation failed, some process was left behind, and next installation could fail on a different part of the installation. Workaround? I added another postgres user, as a superuser, granted everything. I didn't give this user special chars in the password, and I installed postgis with this user. It worked flawlesly. End of the problem. I'm writing just to let you know, in case it helps someone else or someone can upload it to the bug list to get corrected. If a password is accepted on postgres, should be accepted on a postgis installation. Best regards. John Lace _____
_______________________________________________ postgis-users mailing list [email protected] http://postgis.refractions.net/mailman/listinfo/postgis-users
