Обсуждение: Porblem running on Windows 2003 server
Hi all. Running every postgres executable on windows 2003 gives me The system cannot execute the specified program. Do you know any workaround? Thanks, Massimiliano
I'm truly sorry. A while after I sent the e-mail I found the solution. Look here : http://archives.postgresql.org/pgadmin-support/2009-09/msg00077.php Thanks, Massimiliano On Thu, Sep 24, 2009 at 12:56 PM, Massimiliano Ziccardi < massimiliano.ziccardi@gmail.com> wrote: > Hi all. > > Running every postgres executable on windows 2003 gives me > > The system cannot execute the specified program. > > Do you know any workaround? > > Thanks, > Massimiliano >
On Thu, Sep 24, 2009 at 12:08 PM, Massimiliano Ziccardi <massimiliano.ziccardi@gmail.com> wrote: > I'm truly sorry. > > A while after I sent the e-mail I found the solution. It's no problem - happens to all of us! > Look here : > http://archives.postgresql.org/pgadmin-support/2009-09/msg00077.php That shouldn't be the problem. In that case, it was my development VM that had picked up an updated version of the runtimes through a Microsoft patch. The build servers for PostgreSQL (both the EDB one-click ones, and the community one) don't have that patch and the resulting manifests from both builds look like this: <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <dependency> <dependentAssembly> <assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50727.762" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b" /> </dependentAssembly> </dependency> </assembly> which is the original runtime, and doesn't include the update. If I had to hazard a guess, I'd say you either installed PostgreSQL using the zip archive of the binaries, or you used the MSI installer, but ran it directly instead of running setup.bat, which meant that your system had no runtimes installed at all. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
Hi Dave, >If I had to hazard a guess, I'd say you either installed PostgreSQL >using the zip archive of the binaries That's exactly what I've done! My product installation installs postgresql and than creates a window service through the pg_ctl command. Without that patch, none of the postgres files did run... >That shouldn't be the problem I dont' think I've understood. What is the difference between the files installed by the installer and the zip archive? Thank you a lot! Massimiliano
On Thu, Sep 24, 2009 at 1:23 PM, Massimiliano Ziccardi <massimiliano.ziccardi@gmail.com> wrote: >>That shouldn't be the problem > > I dont' think I've understood. What is the difference between the files > installed by the installer and the zip archive? > > Thank you a lot! Nothing - but the email you referenced was discussing a custom build of pgagent I made for someone to test a bug fix. It was built on an entirely different machine than any of the core postgresql binaries in the release packages. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
>It was built on an >entirely different machine than any of the core postgresql binaries in >the release packages. Ok. I got it :-) However, the binaries I download from the postgres site didn't work without the microsoft patch indicated into that email : is this an expected behaviour? Thank you, Massimiliano
On Thu, Sep 24, 2009 at 1:53 PM, Massimiliano Ziccardi <massimiliano.ziccardi@gmail.com> wrote: >>It was built on an >>entirely different machine than any of the core postgresql binaries in >>the release packages. > > Ok. I got it :-) > > However, the binaries I download from the postgres site didn't work without > the microsoft patch indicated into that email : is this an expected > behaviour? Well they won't work without the runtimes installed, and I believe the patch is just an update to the runtimes. So my guess is that it would have worked with the standard version of the them, as originally intended (as described at http://www.postgresql.org/ftp/binary/v8.3.8/win32/). -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com