Thread: BUG #6705: 32 bit
The following bug has been logged on the website: Bug reference: 6705 Logged by: Jimmy Creeks Email address: gj19861103@gmail.com PostgreSQL version: 9.1.4 Operating system: Windows 7 Description:=20=20=20=20=20=20=20=20 Hi, I cannot install 8.3, 9.0, or 9.1 version of postgreSQL. I also try shutting down windows firewall. Here is the bug report: Problem running post-install step. Installation may not complete correctly Error reading file D:/Program Files/PostgreSQL/8.3/data/postgresql.conf. Please tell me if you have any suggested solutions. Thank you.
On 06/25/2012 04:19 AM, gj19861103@gmail.com wrote: > The following bug has been logged on the website: > > Bug reference: 6705 > Logged by: Jimmy Creeks > Email address: gj19861103@gmail.com > PostgreSQL version: 9.1.4 > Operating system: Windows 7 > Description: > > Hi, > > I cannot install 8.3, 9.0, or 9.1 version of postgreSQL. I also try shutting > down windows firewall. Here is the bug report Please see: http://wiki.postgresql.org/wiki/Troubleshooting_Installation At minimum we need your installation log, the exact version of windows eg "Windows 7 Professional 64-bit", whether you're on a Windows corporate domain, and what/any antivirus software you have running. Please reply to pgsql-bugs@postgresql.org, not to me. Dave: Is there any chance the installers link to that page from their error dialogs, or a static-and-sanitised version of it in docs? If you're ok updating the installer messages I'll collect up a sanitized version that doesn't link to other wiki pages (or make it clear they're external) and convert it for the docs. -- Craig Ringer
On Mon, Jun 25, 2012 at 5:41 AM, Craig Ringer <ringerc@ringerc.id.au> wrote: > > Dave: Is there any chance the installers link to that page from their error > dialogs, or a static-and-sanitised version of it in docs? If you're ok > updating the installer messages I'll collect up a sanitized version that > doesn't link to other wiki pages (or make it clear they're external) and > convert it for the docs. We can't do clickable links in those message boxes, so I'm not sure how useful it'll be in practice. The other question is; on which ones would we want to include extra text? Certainly not all errors/warnings, as some are things like "invalid installation directory", which users would just accept, correct their typo or whatever and try again. We wouldn't want to clutter up all message boxes with URLs. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
On 06/25/2012 11:10 PM, Dave Page wrote: > On Mon, Jun 25, 2012 at 5:41 AM, Craig Ringer <ringerc@ringerc.id.au> wrote: >> Dave: Is there any chance the installers link to that page from their error >> dialogs, or a static-and-sanitised version of it in docs? If you're ok >> updating the installer messages I'll collect up a sanitized version that >> doesn't link to other wiki pages (or make it clear they're external) and >> convert it for the docs. > We can't do clickable links in those message boxes, so I'm not sure > how useful it'll be in practice. Argh. I've been in the browser-based app too long, I simply forget that URL handling isn't everywhere. The main ones that IMO need a where-to-go-next hint are the messages that arise when an external process step fails, like initdb, failure to install the runtime, etc. It's /always/ necessary to ask a poster asking for help for the installer log - and how many people don't post or ask for help, just get stuck and confused? -- Craig Ringer
On Mon, Jun 25, 2012 at 4:38 PM, Craig Ringer <ringerc@ringerc.id.au> wrote: > On 06/25/2012 11:10 PM, Dave Page wrote: > > On Mon, Jun 25, 2012 at 5:41 AM, Craig Ringer <ringerc@ringerc.id.au> wrote: > > Dave: Is there any chance the installers link to that page from their error > dialogs, or a static-and-sanitised version of it in docs? If you're ok > updating the installer messages I'll collect up a sanitized version that > doesn't link to other wiki pages (or make it clear they're external) and > convert it for the docs. > > We can't do clickable links in those message boxes, so I'm not sure > how useful it'll be in practice. > > Argh. I've been in the browser-based app too long, I simply forget that URL > handling isn't everywhere. > > The main ones that IMO need a where-to-go-next hint are the messages that > arise when an external process step fails, like initdb, failure to install > the runtime, etc. It's always necessary to ask a poster asking for help for > the installer log - and how many people don't post or ask for help, just get > stuck and confused? Any ideas for a one-liner to add? I'm struggling to find nice wording, that doesn't invite people to report issues without investigating themselves first: * If you need help, please review http://xxxxxx before seeking further assistance. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Hi, As I am having the installation problem and have tried installed postgresql tens of times, I am still in need of your help. Could you tell me under what folder generated by the installer I can find the installation log? Thanks. Best, Jimmy 2012/6/25 Craig Ringer <ringerc@ringerc.id.au> > On 06/25/2012 04:19 AM, gj19861103@gmail.com wrote: > > The following bug has been logged on the website: > > Bug reference: 6705 > Logged by: Jimmy Creeks > Email address: gj19861103@gmail.com > PostgreSQL version: 9.1.4 > Operating system: Windows 7 > Description: > > Hi, > > I cannot install 8.3, 9.0, or 9.1 version of postgreSQL. I also try shutting > down windows firewall. Here is the bug report > > Please see: > > http://wiki.postgresql.org/wiki/Troubleshooting_Installation > > At minimum we need your installation log, the exact version of windows eg > "Windows 7 Professional 64-bit", whether you're on a Windows corporate > domain, and what/any antivirus software you have running. > > Please reply to pgsql-bugs@postgresql.org, not to me. > > Dave: Is there any chance the installers link to that page from their > error dialogs, or a static-and-sanitised version of it in docs? If you're > ok updating the installer messages I'll collect up a sanitized version that > doesn't link to other wiki pages (or make it clear they're external) and > convert it for the docs. > > -- > Craig Ringer >
On Wed, Jun 27, 2012 at 2:01 AM, Jimmy Creeks <gj19861103@gmail.com> wrote: > Hi, > > As I am having the installation problem and have tried installed > postgresql tens of times, I am still in need of your help. Could you tell > me under what folder generated by the installer I can find the installation > log? Thanks. > Installation logs can be found in your system's temp directory (%TEMP% on windows).. > Best, > > Jimmy > > > 2012/6/25 Craig Ringer <ringerc@ringerc.id.au> > >> On 06/25/2012 04:19 AM, gj19861103@gmail.com wrote: >> >> The following bug has been logged on the website: >> >> Bug reference: 6705 >> Logged by: Jimmy Creeks >> Email address: gj19861103@gmail.com >> PostgreSQL version: 9.1.4 >> Operating system: Windows 7 >> Description: >> >> Hi, >> >> I cannot install 8.3, 9.0, or 9.1 version of postgreSQL. I also try shutting >> down windows firewall. Here is the bug report >> >> Please see: >> >> http://wiki.postgresql.org/wiki/Troubleshooting_Installation >> >> At minimum we need your installation log, the exact version of windows eg >> "Windows 7 Professional 64-bit", whether you're on a Windows corporate >> domain, and what/any antivirus software you have running. >> >> Please reply to pgsql-bugs@postgresql.org, not to me. >> >> Dave: Is there any chance the installers link to that page from their >> error dialogs, or a static-and-sanitised version of it in docs? If you're >> ok updating the installer messages I'll collect up a sanitized version that >> doesn't link to other wiki pages (or make it clear they're external) and >> convert it for the docs. >> >> -- >> Craig Ringer >> > > -- Regards, Sachin Srivastava EnterpriseDB, India
On 06/26/2012 06:26 PM, Dave Page wrote: > Any ideas for a one-liner to add? I'm struggling to find nice wording, > that doesn't invite people to report issues without investigating > themselves first: > > * If you need help, please review http://xxxxxx before seeking further > assistance. The positive wording is good. Maybe even: "Guidance for resolving installation issues can be found at http://.... " ... where that provides the common-issues list, a pointer to look at the installation log, then a report template for cases where it wasn't one of the common quick-fixes. I'm happy to work on the docs side, possibly even do a quick JavaScript+form report template to ensure fields like detailed OS version, exact Pg version, etc are supplied. Which reminds me, I need to find out how to detect whether a Windows box is on a domain with non-default group policy, and how/if antivirus can be detected. -- Craig Ringer
On Jun 27, 2012 8:26 AM, "Craig Ringer" <ringerc@ringerc.id.au> wrote: > > On 06/26/2012 06:26 PM, Dave Page wrote: >> >> Any ideas for a one-liner to add? I'm struggling to find nice wording, >> that doesn't invite people to report issues without investigating >> themselves first: >> >> * If you need help, please review http://xxxxxx before seeking further >> assistance. > > > The positive wording is good. Maybe even: > > "Guidance for resolving installation issues can be found at http://.... " > > ... where that provides the common-issues list, a pointer to look at the installation log, then a report template for cases where it wasn't one of the common quick-fixes. > > I'm happy to work on the docs side, possibly even do a quick JavaScript+form report template to ensure fields like detailed OS version, exact Pg version, etc are supplied. Which reminds me, I need to find out how to detect whether a Windows box is on a domain with non-default group policy, and how/if antivirus can be detected. > From the browser? Pretty sure that's impossible, and for very good reasons... /Magnus
On 06/27/2012 02:33 PM, Magnus Hagander wrote: > > > ... where that provides the common-issues list, a pointer to look at > the installation log, then a report template for cases where it wasn't > one of the common quick-fixes. > > > > I'm happy to work on the docs side, possibly even do a quick > JavaScript+form report template to ensure fields like detailed OS > version, exact Pg version, etc are supplied. Which reminds me, I need > to find out how to detect whether a Windows box is on a domain with > non-default group policy, and how/if antivirus can be detected. > > > > From the browser? Pretty sure that's impossible, and for very good > reasons... > No, not from the browser. What a horrible thought. No, just "run this command" or "look here" or "copy this registry key" stuff. (It is possible to collect this stuff from the browser, but you'd have to use an ActiveX control or an Java Web Start application, and the security implications are absolutely horrific. I'd never, ever, ever, ever want to go there.) Maybe eventually I'd be able to put together a little script to run to collect info; if it's not bundled in the installer it doesn't have the same necessity to be absolutely robust and correct in all situations and can be easily updated to collect more. It can also collect stuff like installed-program lists, environment data, etc because the user would be _knowingly_ and _explicitly_ submitting the report with that info and have a chance to redact portions if desired. For now, though, all I'm talking about is a helping-hand web form with hints about how to find out the exact Windows version, architecture, antivirus in use, etc. Nothing but a web page with some jQuery code. -- Craig Ringer
On Jun 27, 2012 8:42 AM, "Craig Ringer" <ringerc@ringerc.id.au> wrote: > > On 06/27/2012 02:33 PM, Magnus Hagander wrote: >> >> >> > ... where that provides the common-issues list, a pointer to look at the installation log, then a report template for cases where it wasn't one of the common quick-fixes. >> > >> > I'm happy to work on the docs side, possibly even do a quick JavaScript+form report template to ensure fields like detailed OS version, exact Pg version, etc are supplied. Which reminds me, I need to find out how to detect whether a Windows box is on a domain with non-default group policy, and how/if antivirus can be detected. >> > >> >> From the browser? Pretty sure that's impossible, and for very good reasons... >> > No, not from the browser. What a horrible thought. No, just "run this command" or "look here" or "copy this registry key" stuff. Good. Scared me there for a second :-) > (It is possible to collect this stuff from the browser, but you'd have to use an ActiveX control or an Java Web Start application, and the security implications are absolutely horrific. I'd never, ever, ever, ever want to go there.) Yeah let's not go there. Active X would also encourage the bad practice of using Internet explorer of course, which is another good reason not to go there :-) > Maybe eventually I'd be able to put together a little script to run to collect info; if it's not bundled in the installer it doesn't have the same necessity to be absolutely robust and correct in all situations and can be easily updated to collect more. It can also collect stuff like installed-program lists, environment data, etc because the user would be _knowingly_ and _explicitly_ submitting the report with that info and have a chance to redact portions if desired. > > For now, though, all I'm talking about is a helping-hand web form with hints about how to find out the exact Windows version, architecture, antivirus in use, etc. Nothing but a web page with some jQuery code. > There are some easy api to get whether the box is on a domain or not, and it's easily accessible from wsh as well. And it ought to be trivial in power shell... As for the av, I'm less sure. Maybe it's better to just dump a list of installed programs? I'd expect all av to be installed by installers that register them.. The other idea would be to find out if there is an api corresponding to the "your computer is at risk" is warning bubble, and just use it backwards. I have non idea if there is though, I've never done any work in that area at all. /Magnus
On 06/27/2012 02:49 PM, Magnus Hagander wrote: > There are some easy api to get whether the box is on a domain or not, > and it's easily accessible from wsh as well. And it ought to be > trivial in power shell... > Good to know. Since it's a troubleshooting tool there's no real problem with saying "First, go install powershell" - but it'd be better not to need to if it's available via wsh. Ick ick ick. I've kept away from this stuff and been happy about it, why do I keep volunteering myself for horrid Windows guts stuff? > > As for the av, I'm less sure. Maybe it's better to just dump a list of > installed programs? I'd expect all av to be installed by installers > that register them. > There's no guarantee they won't try to hide, though. AV software vendors may think it's a good idea to make it hard for software on the machine to tell what AV is running. I'm hoping not, but it's quite possible. > > The other idea would be to find out if there is an api corresponding > to the "your computer is at risk" is warning bubble, and just use it > backwards. I have non idea if there is though, I've never done any > work in that area at all. > That's what I'm hoping is possible, but like you haven't dug into it yet. -- Craig Ringer
On Wed, Jun 27, 2012 at 9:48 AM, Craig Ringer <ringerc@ringerc.id.au> wrote:
> On 06/27/2012 02:49 PM, Magnus Hagander wrote:
>
>> There are some easy api to get whether the box is on a domain or not, and
>> it's easily accessible from wsh as well. And it ought to be trivial in power
>> shell...
>>
> Good to know. Since it's a troubleshooting tool there's no real problem with
> saying "First, go install powershell" - but it'd be better not to need to if
> it's available via wsh.
"msinfo32.exe /report foo.txt" would likely give us most of what we'd
want to see (aside from the installation logs), but for some reason
Microsoft seem to have removed the options to include only certain
categories of info in the reports it creates, so you now get 3+ MB of
info that's not very useful as well as the good stuff. On the plus
side, it does compress nicely (3.8MB -> 175KB on my dev VM).
There's also the systeminfo command, which gives something like:
C:\Users\dpage>systeminfo
Host Name: RAPTOR-WIN7
OS Name: Microsoft Windows 7 Ultimate
OS Version: 6.1.7601 Service Pack 1 Build 7601
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
Registered Owner: dpage
Registered Organization:
Product ID: wwww-zzz-yyyyy-xxxx
Original Install Date: 01/12/2010, 16:09:14
System Boot Time: 27/06/2012, 10:05:48
System Manufacturer: VMware, Inc.
System Model: VMware Virtual Platform
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 37 Stepping 5
GenuineIntel ~2792 Mhz
BIOS Version: Phoenix Technologies LTD 6.00, 02/06/2011
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume1
System Locale: en-gb;English (United Kingdom)
Input Locale: en-gb;English (United Kingdom)
Time Zone: (UTC) Dublin, Edinburgh, Lisbon, London
Total Physical Memory: 2,047 MB
Available Physical Memory: 985 MB
Virtual Memory: Max Size: 4,095 MB
Virtual Memory: Available: 2,824 MB
Virtual Memory: In Use: 1,271 MB
Page File Location(s): C:\pagefile.sys
Domain: WORKGROUP
Logon Server: \\RAPTOR-WIN7
Hotfix(s): 125 Hotfix(s) Installed.
[01]: 982861
<skip 127 other hotfixes>
You can also use the WMI console pretty easily - maybe a few choice
queries there is the answer. For example:
C:\Users\dpage>wmic product get name,version
Name
Version
Microsoft Application Error Reporting
12.0.6012.5000
Microsoft Application Error Reporting
12.0.6015.5000
Microsoft Office OneNote MUI (English) 2010
14.0.6029.1000
Microsoft Office InfoPath MUI (English) 2010
14.0.6029.1000
Microsoft Office Visio MUI (English) 2010
14.0.6029.1000
Microsoft Office Project MUI (English) 2010
14.0.6029.1000
Microsoft Office Access MUI (English) 2010
14.0.6029.1000
Microsoft Office Shared Setup Metadata MUI (English) 2010
14.0.6029.1000
Microsoft Office Excel MUI (English) 2010
14.0.6029.1000
Microsoft Office Shared 64-bit Setup Metadata MUI (English) 2010
14.0.6029.1000
Microsoft Office Access Setup Metadata MUI (English) 2010
14.0.6029.1000
Microsoft Office PowerPoint MUI (English) 2010
14.0.6029.1000
Microsoft Office Publisher MUI (English) 2010
14.0.6029.1000
Microsoft Office Outlook MUI (English) 2010
14.0.6029.1000
Microsoft Office Office 64-bit Components 2010
14.0.6029.1000
Microsoft Office Shared 64-bit MUI (English) 2010
14.0.6029.1000
Microsoft Office Groove MUI (English) 2010
14.0.6029.1000
Microsoft Office Word MUI (English) 2010
14.0.6029.1000
Microsoft Office Proofing (English) 2010
14.0.6029.1000
Microsoft Office Shared MUI (English) 2010
14.0.6029.1000
Microsoft Office Proof (English) 2010
14.0.6029.1000
Microsoft Office Proof (Spanish) 2010
14.0.6029.1000
Microsoft Office Proof (French) 2010
14.0.6029.1000
Microsoft Office Professional Plus 2010
14.0.6029.1000
Microsoft Office Visio 2010
14.0.6029.1000
Microsoft Office Project Professional 2010
14.0.6029.1000
Microsoft Windows SDK for Visual Studio 2008 Tools
6.1.5288.17011
Windows Installer XML Toolset 3.0
3.0.5419.0
Microsoft Visual Studio 2010 ADO.NET Entity Framework Tools
10.0.30319
Microsoft ASP.NET MVC 2
2.0.50217.0
Microsoft Help Viewer 1.1
1.1.40219
Microsoft .NET Compact Framework 1.0 SP3 Developer
1.0.4292
Visual C++ 2008 x86 Runtime - (v9.0.30729.4148)
9.0.30729.4148
Microsoft Visual C++ 2005 ATL Update kb973923 - x86 8.0.50727.4053
8.0.50727.4053
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.4148
9.0.30729.4148
Visual C++ 2008 IA64 Runtime - (v9.0.30729)
9.0.30729
Visual C++ 2008 x64 Runtime - (v9.0.30729)
9.0.30729
Jasc Paint Shop Pro 8
8.10.0000
Microsoft Sync Framework Runtime v1.0 SP1 (x64)
1.0.3010.0
Microsoft Windows SDK for Visual Studio 2008 .NET Framework Tools
3.5.21022
Visual Studio 2010 Prerequisites - English
10.0.40219
Visual C++ 2008 x64 Runtime - KB2465361 - (v9.0.30729.5570)
9.0.30729.5570
Microsoft Visual C++ 2010 x86 Runtime - 10.0.40219
10.0.40219
Microsoft Windows SDK Intellisense and Reference Assemblies (30514)
7.1.30514
Microsoft Visual C++ 2005 Redistributable
8.0.59193
Crystal Reports for Visual Studio
12.51.0.240
Microsoft Windows SDK for Visual Studio .NET 4.0 Framework Tools
7.1.30514
VMware Tools
8.8.4.13798
Microsoft Visual C++ 2010 x64 Designtime - 10.0.30319
10.0.30319
Microsoft Sync Framework SDK v1.0 SP1
1.0.3010.0
Microsoft Visual Studio 2008 Professional Edition - ENU
9.0.21022
Java(TM) 6 Update 24
6.0.240
J2SE Development Kit 5.0 Update 22
1.5.0.220
Java(TM) SE Development Kit 6 Update 24
1.6.0.240
Microsoft Document Explorer 2005
8.0.50727.42
Microsoft Sync Framework Services v1.0 SP1 (x64)
1.0.3010.0
Microsoft Team Foundation Server 2010 Object Model - ENU
10.0.30319
Microsoft Windows SDK Net Fx Interop Headers And Libraries (30514)
7.1.30514
Microsoft .NET Framework 2.0 SDK (x64) - ENU
2.0.50727
Microsoft Security Client
4.0.1526.0
Microsoft ASP.NET MVC 2 - Visual Studio 2010 Tools
2.0.50217.0
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.6161
9.0.30729.6161
VMware vSphere Client 5.0
5.0.0.16964
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161
9.0.30729.6161
Microsoft Visual Studio 2010 Professional - ENU
10.0.30319
Microsoft Visual C++ 2008 Redistributable - x86 9.0.21022
9.0.21022
Visual Studio .NET Prerequisites - English
9.0.30729
Microsoft Team Foundation Server 2010 Object Model for Lightswitch
2011 - ENU 10.0.40219
J2SE Runtime Environment 5.0 Update 22
1.5.0.220
Microsoft .NET Framework 4 Multi-Targeting Pack
4.0.30319
Microsoft Sync Services for ADO.NET v2.0 SP1 (x64)
2.0.3010.0
Web Deployment Tool
1.1.0618
Microsoft .NET Compact Framework 2.0 SP2
2.0.7045
WCF RIA Services V1.0 SP1
4.1.60114.0
VC Runtimes MSI
9.0.21022
Microsoft Visual C++ 2008 ATL Update kb973924 - x64 9.0.30729.4148
9.0.30729.4148
Microsoft Windows SDK .NET Framework Tools (30514)
7.1.30514
Microsoft Windows SDK for Visual Studio 2008 Win32 Tools
6.1.5288.17011
Visual C++ 2008 x64 Runtime - (v9.0.30729.4148)
9.0.30729.4148
Microsoft .NET Compact Framework 3.5
3.5.7283
Python 2.7.2 (64-bit)
2.7.2150
Windows SDK IntellisenseNFX
7.1.30514
Microsoft Document Explorer 2008
9.0.21022
Microsoft Visual C++ 2010 x64 Redistributable - 10.0.30319
10.0.30319
Microsoft Visual C++ 2005 Redistributable
8.0.61001
Microsoft Windows SDK for Windows 7 Common Utilities (30514)
7.1.30514
Microsoft .NET Framework 4 Extended
4.0.30319
Visual C++ 2008 x86 Runtime - KB2465361 - (v9.0.30729.5570)
9.0.30729.5570
Microsoft Windows SDK for Visual Studio 2008 SDK Reference Assemblies
and IntelliSense 6.1.5288.17011
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.4148
9.0.30729.4148
Microsoft Visual C++ 2010 x86 Redistributable - 10.0.30319
10.0.30319
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17
9.0.30729
Visual C++ 2008 x86 Runtime - (v9.0.30729)
9.0.30729
Microsoft Windows SDK for Windows 7 (7.1)
7.1.30514
Microsoft Silverlight
5.1.10411.0
Microsoft .NET Framework 4 Client Profile
4.0.30319
Microsoft Visual Studio Macro Tools
9.0.30729
Debugging Tools for Windows (x64)
6.12.2.633
Microsoft Visual J# 2.0 Redistributable Package - SE (x64)
2.0.50728
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.17
9.0.30729
ActivePerl 5.12.2 Build 1202
5.12.1202
Java Auto Updater
2.0.3.1
Microsoft Visual C++ 2010 x64 Runtime - 10.0.40219
10.0.40219
Microsoft Windows SDK for Visual Studio 2008 Headers and Libraries
6.1.5288.17011
Though the slightly disturbing thing about that is that it isn't
listing PostgreSQL, of which I have many versions installed. Not sure
why - I'm fairly certain it's not just dumping the windows installer
database, as it shows Paint Shop Pro which is a very old product and
almost certainly not an MSI based installer.
> Ick ick ick. I've kept away from this stuff and been happy about it, why do
> I keep volunteering myself for horrid Windows guts stuff?
:-)
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Wed, Jun 27, 2012 at 7:25 AM, Craig Ringer <ringerc@ringerc.id.au> wrote: > On 06/26/2012 06:26 PM, Dave Page wrote: >> >> Any ideas for a one-liner to add? I'm struggling to find nice wording, >> that doesn't invite people to report issues without investigating >> themselves first: >> >> * If you need help, please review http://xxxxxx before seeking further >> assistance. > > > The positive wording is good. Maybe even: > > "Guidance for resolving installation issues can be found at http://.... " Hmm, yeah, I like that. > ... where that provides the common-issues list, a pointer to look at the > installation log, then a report template for cases where it wasn't one of > the common quick-fixes. > > I'm happy to work on the docs side, possibly even do a quick JavaScript+form > report template to ensure fields like detailed OS version, exact Pg version, > etc are supplied. Thanks. We already have some of that on the Wiki, but you know that of course. > Which reminds me, I need to find out how to detect whether > a Windows box is on a domain with non-default group policy, and how/if > antivirus can be detected. Running on a domain is easy (wmic ntdomain), and the AV can either be found in the list of running processes or installed programs I believe. I can't find any way to see if a non-default group policy is (or has previously been) applied. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
I looked at the logs you sent. Strangely the command *"D:\Program Files\PostgreSQL\9.1\bin\initdb.exe" --locale=C --encoding=UTF-8 -A md5 -U postgres -d "D:\Program Files\PostgreSQL\9.1\data"* * * produces no output in the log. Can you try to manually execute this above command and share the output you get. On Wed, Jun 27, 2012 at 11:10 AM, Sachin Srivastava < sachin.srivastava@enterprisedb.com> wrote: > > > On Wed, Jun 27, 2012 at 2:01 AM, Jimmy Creeks <gj19861103@gmail.com>wrote: > >> Hi, >> >> As I am having the installation problem and have tried installed >> postgresql tens of times, I am still in need of your help. Could you tell >> me under what folder generated by the installer I can find the installation >> log? Thanks. >> > > Installation logs can be found in your system's temp directory (%TEMP% on > windows).. > > >> Best, >> >> Jimmy >> >> >> 2012/6/25 Craig Ringer <ringerc@ringerc.id.au> >> >>> On 06/25/2012 04:19 AM, gj19861103@gmail.com wrote: >>> >>> The following bug has been logged on the website: >>> >>> Bug reference: 6705 >>> Logged by: Jimmy Creeks >>> Email address: gj19861103@gmail.com >>> PostgreSQL version: 9.1.4 >>> Operating system: Windows 7 >>> Description: >>> >>> Hi, >>> >>> I cannot install 8.3, 9.0, or 9.1 version of postgreSQL. I also try shutting >>> down windows firewall. Here is the bug report >>> >>> Please see: >>> >>> http://wiki.postgresql.org/wiki/Troubleshooting_Installation >>> >>> At minimum we need your installation log, the exact version of windows >>> eg "Windows 7 Professional 64-bit", whether you're on a Windows corporate >>> domain, and what/any antivirus software you have running. >>> >>> Please reply to pgsql-bugs@postgresql.org, not to me. >>> >>> Dave: Is there any chance the installers link to that page from their >>> error dialogs, or a static-and-sanitised version of it in docs? If you're >>> ok updating the installer messages I'll collect up a sanitized version that >>> doesn't link to other wiki pages (or make it clear they're external) and >>> convert it for the docs. >>> >>> -- >>> Craig Ringer >>> >> >> > > > -- > Regards, > Sachin Srivastava > EnterpriseDB, India > -- Regards, Sachin Srivastava EnterpriseDB, India