odbc3 ps.k version mismatch

176 views
Skip to first unread message

Roni Hoffman

unread,
Aug 10, 2018, 5:05:11 PM8/10/18
to Kdb+ Personal Developers
Hello,

I am trying to create an ODBC3 q server 


but am running into architecture error

ps.k version mismatch

I am running with w64 and have followed directions but doesnt seem to work, any ideas?

Thanks

pierre

unread,
Aug 10, 2018, 5:07:57 PM8/10/18
to personal...@googlegroups.com
the driver requests .s.ver over ipc to check if ps.k is present, so you should ensure that you're not overriding .s after loading ps.k

--
You received this message because you are subscribed to the Google Groups "Kdb+ Personal Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to personal-kdbplus+unsubscribe@googlegroups.com.
To post to this group, send email to personal-kdbplus@googlegroups.com.
Visit this group at https://groups.google.com/group/personal-kdbplus.
For more options, visit https://groups.google.com/d/optout.

Roni Hoffman

unread,
Aug 10, 2018, 5:12:47 PM8/10/18
to Kdb+ Personal Developers
Oh I'm sorry my mistake, got it now thanks pierre


On Friday, August 10, 2018 at 5:07:57 PM UTC-4, pierre wrote:
the driver requests .s.ver over ipc to check if ps.k is present, so you should ensure that you're not overriding .s after loading ps.k
On 10 August 2018 at 22:05, Roni Hoffman <hoffm...@gmail.com> wrote:
Hello,

I am trying to create an ODBC3 q server 


but am running into architecture error

ps.k version mismatch

I am running with w64 and have followed directions but doesnt seem to work, any ideas?

Thanks

--
You received this message because you are subscribed to the Google Groups "Kdb+ Personal Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to personal-kdbpl...@googlegroups.com.
To post to this group, send email to personal...@googlegroups.com.

YANG XI

unread,
Apr 2, 2019, 5:57:30 AM4/2/19
to Kdb+ Personal Developers
I encounter the same issue. The problem was that my KDB server was not setup for ODBC connection.
After my technical team setup ODBC connection in my KDB server, the problem resolved.
Reply all
Reply to author
Forward
0 new messages