Skip site navigation (1) Skip section navigation (2)

Re: Porblem running on Windows 2003 server

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Massimiliano Ziccardi <massimiliano(dot)ziccardi(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Porblem running on Windows 2003 server
Date: 2009-09-24 11:49:40
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
On Thu, Sep 24, 2009 at 12:08 PM, Massimiliano Ziccardi
<massimiliano(dot)ziccardi(at)gmail(dot)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 :

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">
      <assemblyIdentity type="win32" name="Microsoft.VC80.CRT"
version="8.0.50727.762" processorArchitecture="x86"
publicKeyToken="1fc8b3b9a1e18e3b" />

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:

In response to


pgsql-bugs by date

Next:From: Massimiliano ZiccardiDate: 2009-09-24 12:23:09
Subject: Re: Porblem running on Windows 2003 server
Previous:From: dolejsi jiriDate: 2009-09-24 11:34:17
Subject: BUG #5079: postgres killed by signal 11 when executing xslt_process function from xml2 contrib module.

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group