The following bug has been logged online: Bug reference: 6173 Logged by: Email address: pete_w...@symantec.com PostgreSQL version: 8.3.14 Operating system: Windows Server 2003 x64 Enterprise Edition Description: 8.3.14 and 8.3.15 do not work on Win2k3x64 Details:
Hello, I am upgrading the version of PostgreSQL used in our product from 8.3.9 to 8.3.15 to close some of the vulnerabilities. After upgrading, I found that it wouldn’t work on our Windows 2003 boxes, but it was fine on the 2008 ones. I downloaded every binary release from ..9 to ..15 (from here: http://www.postgresql.org/ftp/binary/) and found that the problem started with 8.3.14. What happens is when I try to launch any of the binaries, I get this message on the CLI: C:\tmp\postgresql-8.3.14-1-binaries-no-installer\pgsql\bin>pg_ctl.exe The system cannot execute the specified program. When I double-click it in Explorer, I get a dialog box with this message: "This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem." I then opened it up in Dependency Walker and got this message: Error: The Side-by-Side configuration information for "c:\tmp\postgresql-8.3.14-1-binaries-no-installer\pgsql\bin\PG_CTL.EXE" contains errors. This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem (14001). Error: The Side-by-Side configuration information for "c:\tmp\postgresql-8.3.14-1-binaries-no-installer\pgsql\bin\LIBPQ.DLL" contains errors. This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem (14001). It was also not detecting the MSVCR80.DLL, while 8.3.13 found it automatically. Here’s a screenshot of Dependency Walker comparing the new with the old: http://i.imgur.com/FxNkG.jpg Can someone help me figure out what’s missing? I found "Improve build support for Windows version" here http://archives.postgresql.org/pgsql-announce/2011-02/msg00000.php. Maybe that had something to do with it. Thanks, -Pete -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
