Potgres Architecture Mismatch error

[Simon22]

I have just installed v11 64bit on Windows 2008 Server R2 64bit
Whilst the phone system works fine I found that the installation
of Postgres was the original 32bit.
Unfortunatly this creates a conflict when SQL 64bit is installed
when trying to port data from Postgres to SQL via DTS / SSIS
you get an Architecture Mismatch error whichever POstgres driver
you use 64 bit / 32 bit / ANSI / Unicode.
I used SQL in the 32bit version on 3CX v9/v10 which worked really
well. I use this because it gives you much better scope for the
data with more flexibility and I convert all the WAV files
to MP3 via Lame for ease of use and storage, and also reorganise them
in a date basis making it easier to track the calls
and archive them.
The 3CX storage by extension is inefficient and needs to be changed.

I have 14 clients that will be unable to upgrade unless a solution
for this problem is found.

I need a solution can anyone give advice?

 

[millsey]

I don't see why this is a 3CX problem.

For any data source on a 64 bit server, where the driver is 32 bit, you need to use the 32 bit ODBC admin console to create the data source. Look for odbcad32.exe which is the 32 bit version of ODBC administrator on your system.

The 3CX storage engine is not inefficient as you say simply because you wish it were SQL server. If you want to connect at the database level you must be prepared to learn the syntax and details of PostgreSQL. It is not feasible for 3CX to use MS SQL since the free SQL express is not big enough for larger installs, and the Standard version is too expensive for many smaller / medium sized customers.

Millsey

 

[Simon22]

There are 2 odbc32.exe (oddly) one 32bit and one 64bit
one in the WOW64 directory and the other in system32 (I think off the top of my head)
When you use either 32 or 64 bit ODBC drivers it still generates the same problem
as 64bit SQL uses a native 64bit driver for SQL Server.

I guarantee you that this problem will raise its head time an time again and start to become
a serious problem at which point I suspect it will be addressed.

I am not having at go at 3CX I think it is an outstanding very stable piece of software.
I am not saying its a 3CX problem, but I have found this to be typical of all software
writers, they become very defensive and utter the magic words its not my problem
it must be the other piece of software. I would much rather have a solution that
works whereby we can all move forward.

What I don't understand is why 3CX force installation of version 11 on a 64bit machine
and then couple it with a 32bit Postgres database and driver, that doesnt make sense.

As I say 3CX is a stunning piece of software much easier to configure and use
than Asterisk or Trixbox (and much better than the offerings of Avaya and cheaper than CISCO !!!)

I am just looking for a solution to this and I can upgrade 14 clients and add a few more
with the current version.
If not I need to know if its possible to continue to buy version 10 32 bit going forward
and get support and licenses for it, along with a discounted price.

Any suggestions or solutions would be greatly appreciated.

Many thanks in anticipation.

 

[craigreilly]

3cx does not force v11 on 64 bit Windows.
I am running 32 bit windows 7 which means my install is 32 bit.

 

[Simon22]

Hi Craig,

I think you misunderstand me,
I was informed by a support agent at 3CX that
you have to install v11 on a 64bit system, however this is not the case.
3CX supports native 64bit OSs incorrect information was supplied.

However I am still looking for a resolution to the Architecture Mismatch error
I get when 32bit Postgres is installed on a 64bit OS.

I have looked on the internet and found this is a common fault.
there is no easy way round it,
I would really appreciate a resolution other wise I cant take advantage
of 64bit OS installation and would have to install Server 2003 or 32bit Windows 7
I would rather not go backwards

Many Thanks for any suggestions or help

 

[millsey]

I checked what we have. We have a 32 bit microsoft sql server and so we have an odbc set up on that server using 32 bit driver. We then define that odbc sleeve as a linked server so we can then query via the sql server. One thing we found was that Sql server does not accept linked server name to start with a number so you cannot call it 3cx. We used threecx instead.

S linked server query can then either be stated as select x from threecx.. tabke
Or use openquery statement.

I guess then that even on 64bit 3cx install the postgresql is 32 bit?

Millsey.

 

[Simon22]

Millsey,

Many thanks for that, I shall try to figure that out,
I had seen something on the internet about a linked server before
but it seems a long way round to achieve something that should
work straight out of the box.

I have just tried to install version 11 on 32bit Windows Server 2003
and it wont install, keep getting errors during installation
I have all the prerequisite software installed and all patched up but wont install.

Looks like I am stuck with v10
I am going to contact 3CX direct and enquire about just using v10
from now on and whether I can get any discounts on licensing for v10

Simon

 

[millsey]

You might enquire as to whether you can replace the 32 bit postgresql with a 64 bit version, but I cannot help you with that and there are risks attached.

Brian

 

[Simon22]

Thanks for that,

There is a 64bit Postgres version available
unfortunately 3CX bundle the 32bit version with the 64bit focused version 11

I have decided to schedule command line 'PSQL' commands
But need assistance here

Does anyone know the commands for PSQL
how to set it up for auto login (I believe there is some PASSFILE)
and auto output to a CSV file

From this point I am going to import data back in to SQL