By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
432,510 Members | 1,815 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 432,510 IT Pros & Developers. It's quick & easy.

PostgreSQL and OleDb

P: 4
Hi, I'm pretty new with Postgre. So far I've managed to create databases, functions, etc and access them from Windows applications written in C# via Odbc and Npgsql. I am requested to use OleDb, so I got hold of this provider. I registered the dll and can actually create the connection, but when I try to open it I get an exception saying 'invalid command-line arguments for server process'. I enabled logging and got the whole error message.

My connection string (for an OleDbConnection) is:
Expand|Select|Wrap|Line Numbers
  1. private const string cadena = "Provider=PostgreSQL OLE DB Provider;Data Source=127.0.0.1;location=Prueba;User ID=postgres;password=pwd;timeout=1000";
and the error log is:

Starting logging
IDBPropertiesImpl::GetPropertyInfo
m_pCUtlPropInfo == NULL
IDBPropertiesImpl::GetProperties
IDBPropertiesImpl::SetProperties
IDBInitializeImpl::Initialize
IDBCreateSessionImpl::CreateSession
IDBPropertiesImpl::GetProperties
CErrorLookupService::ClearErrorCPgSession::PQerror Message FATAL: invalid command-line arguments for server process
HINT: Try "postgres --help" for more information.
PgSource::PgConnectDB failed to open database connection:
FATAL: invalid command-line arguments for server process
HINT: Try "postgres --help" for more information.
CErrorLookupService::ReportCustomError HRES 80004005:
FATAL: invalid command-line arguments for server process
HINT: Try "postgres --help" for more information.

CErrorLookupService::GetErrorDescription

I couldn't find anything regarding the error number. Anyone's had the same problem?
Jul 11 '07 #1
Share this Question
Share on Google+
3 Replies


Expert 100+
P: 534
Is there a way to generate extended logging so you could see what actually sent to the backend prior to the crash?
Jul 14 '07 #2

P: 4
I think what I attached is the extended logging.
Jul 16 '07 #3

Expert 100+
P: 534
I see; then I'm afraid I won't be really helpful to you - I don't have any experience with npgsql.
I suppose you already tried to google this error?
Jul 16 '07 #4

Post your reply

Sign in to post your reply or Sign up for a free account.