PokerTracker

Please see my post "Installing PostGreSQL 'Over Itself' from different OS", (https://www.pokertracker.com/forums/viewtopic.php?f=17&t=29911) earlier in this forum.

Prior to switching over to my new OS on the other HD, I attempted to uninstall/reinstall PostGreSQL, and encountered a tale of woe .

The PostGreSQL version I previously has was ver 8.3, which I successfully uninstalled, from D:\Poker Stuff\PostGreSQL, following the instructions in the file

PokerTracker3_Manual_Uninstall_Reinstall_PostgreSQL.pdf

downloaded from this site. I also moved the PostgreSQL 8.3 shortcuts to a temporary folder. I did not delete the D:\Poker Stuff\PostGreSQL folder, which still has 2 subfolders - bin & data - within it. The data folder contains a file "PG_VERSION" which, when opened in Notepad says "8.3" (no quotes) only. I will be happy to send screen dumps of the contents of any folder requested.

Following the uninstall, I restarted Windows.

I then attempted to install
postgresql-8.4.4-1-windows.exe

per instructions in
"PokerTracker3_Manual_Uninstall_Reinstall_PostgreSQL8-4.pdf".
At Installation Options, I named D:\Poker Stuff\PostGreSQL as the installation directory, and selected D:\Poker Stuff\PostGreSQL\data as the data directory.

Ooops.

I got an Error Message: "The existing data directory (catalog version: ) is not compatible with this server (catalog version 200904091) OK" (Screen dump available).

So now I have no access to my data (but it is backed up to another HD), and I guess I'm not playing a lot of poker until we get this fixed.
Please help, preferably with a detailed step-by-step approach, as I am utterly ignorant about PostgreSQL, and this kind of stuff scares me crapless.
TIA
Jimmy

Uninstall PostgreSQL 8.4.4. It will not work with the data directory you have. Install 8.3.11 as per the documentation on our documentation page. It is compatible with the data directory you have and should work just fine.

Thanx for your quick response, kraada. In a less-panicky mental mode, and after some consideration, I had separately concluded tha reinstalling 8.3.11 might be the better solution, especially given risk/reward and the unpersuasive rationalisations in the PostgreSQL site (http://www.postgresql.org/support/versioning.

Unfortunately, when I ran postgresql-8.3.11-1-windows.exe, i GOT A "postgresql-8.3.11 data directory floating-point incompatible error message" (Screen dump available), so I cancelled this install. Instead, I ran postgresql-8.3.msi and it installed, exactly as in the PokerTracker3_Manual_Uninstall_Reinstall_PostgreSQL.pdf (v1.01, Mar 8, 2010 version).

Installed to D:\Poker Stuff\PostGreSQL, data file D:\Poker Stuff\PostGreSQL\data, no worries.

Opened PT2, oops get "Unable to connect....999 - SQLSTATE = IM002.....ODBC Driver Manager" Error. (BTW, "Add/Remove..." does not contain the psqlODBC entry, the PostgreSQL settings in PT2 are exactly as before, as are the databases in File, Maintain Database Names Window, and PT3 runs just fine against its database in the same folder ????)

Grateful ideas, please, and, as always, thanx for your terrific support. If the rest of the apps industry were half as good as youse guys, we'd be in a happier place.
Jimmy

For PT2 you still need to run the Stack Builder and install the ODBC driver under the Drivers section.

Thanx, kraada, I ran the Application Stack Builder from Start, Programs....
It installed v8.3.5, and after a Windows restart, I reopened PT2, got the same error message (999 - SQLSTATE...). Poked around in PT2, and on this site, found this thread https://www.pokertracker.com/forums/viewtopic.php?f=29&t=15748&hilit=install+ODBc+driver&start=10, followed Pat's advice in his Fri Jan 02, 2009 5:06 pm post

Open the PostgreSQL Settings window. Make a note of the values you have selected here.

Now use the Remove button to remove the entry and then click the Add button and re-enter the information again. Then save and close and reopen PT.

When I tried to re-enter the information, found the "ODBC Entry to use" dropdown empty, so I guess this driver is not yet installed. I realise I may be on the verge of becoming a PITA, but I really have no idea as to how to install this driver. Can you please advise & Much TIA,
Jimmy

Follow the steps here to create a new DSN for the ODBC driver and then you should be able to select it from that drop down.

I'm truly sorry, kraada, but this is now driving both of us nuts.

In my ODBC Data Source System DSN tab, I try to Add an SQL Server, but the dropdown box in the "Which SQL Server do you want to connect to?" is empty.

However, the System Data Sources I see, in addition to PT MS Access drivers, there are:
1. PT3DB (Driver: PostgreSQL ANSI) and
2. PTPGSQL Test Port 5432 (Driver: PostgreSQL Unicode) and
3. PTPGSQL1 (Driver: PostgreSQL Unicode)
entries.

Further, when I click the Configure button on any of these, I get, an Error Message:
"Microsoft ODBC Administrator: The setup routines for the PostgreSQL Unicode/ANSI driver could not be found. Please reinstall the driver." Clicking OK, I get:
"Driver's ConfigDSN, ConfigDriver, or ConfigTranslator failed: Component not found in the registry" with an "OK" button.

If we're now a a point of frustration such that I have to uninstall/reinstall the whole damned PostgreSQL app over again, can you please direct me to an idiot's guide, so we can both get on with doing far better things than this?

Your support is appreciated, believe me,
Jimmy

At this point it will probably be easier to create a support ticket that references this thread requesting remote assistance. It will be faster and easier on both of us to continue in that way.

Agreed, kraada, and done. Thanks for your patience and support,
Jimmy

I've just finished a remote asssistance session with kraada, and I want to let him, and all other forum readers, know how much I appreciated the patience and skill he showed in fixing my problem to my complete satisfaction.

The level of support for these PT applications way exceeds that for any other app on my PC, now or in the past.
You guys are amazing.
My grateful thanks
Jimmy