Hi Mary, Using HTTP here was my suggestion, to validate that the connection was OK between Nick's machine and the server (it looked like a connection error to me.) This was just a convenient way to test connection using universal HTTP tools.
Nick's message confirms the connection is OK, and indeed the fact that it returns an error in response to a HTTP request was expected. So it seems there is something else, then. .. Regards, -- Florent Georges H2O Consulting http://h2o.consulting/ On 24 March 2017 at 16:48, Mary Holstege wrote: > > The error is misleading: the real problem is that the ODBC port does not > communicate via the HTTP protocol and it reads HTTP messages as garbage. > It expects to be communicating with the Postgres backend protocol. > > //Mary > > > On Fri, 24 Mar 2017 08:04:46 -0700, Nick Heidke wrote: > > > If I run a connection test from the ODBC Administrator, it’s successful. > > If I hit server:<odbcport> with a browser, I get this back: > > > > E hSERROR C08000 MXDMP-ODBCRCVMSGTOOBIG size=1195725856, > > conn=192.168.30.217:8052-192.168.21.34:33275 > > > > It looks like the pipe is open between my machine and the ODBC port on > > the server. > > > > Furthermore, I can see entries in the <odbcport>_AccessLog.txt. However, > > they aren’t terribly helpful: > > > > 192.168.21.34 - nickh [23/Mar/2017:09:43:36 -0400] init > > 192.168.21.34 - nickh [23/Mar/2017:09:43:36 -0400] password > > 192.168.21.34 - nickh [23/Mar/2017:09:43:36 -0400] query > > 192.168.21.34 - nickh [23/Mar/2017:09:43:36 -0400] query > > 192.168.21.34 - nickh [23/Mar/2017:09:43:36 -0400] query > > 192.168.21.34 - nickh [23/Mar/2017:09:43:36 -0400] query > > 192.168.21.34 - nickh [23/Mar/2017:09:43:36 -0400] query > > 192.168.21.34 - nickh [23/Mar/2017:09:43:36 -0400] terminate > > > > The <odbcport>_ErrorLog.txt is blank, however. > > > > Thanks for helping out!! > > > > Nick Heidke > > Business Intelligence Consultant > > [Description: Description: cid:[email protected]] > > 5250 E Terrace Dr #130, Madison, WI > > d:608.284.2040 ext. 2305 | c:920.385.9110 > > [email protected]<mailto:[email protected]> > > > > From: [email protected] > > [mailto:[email protected]] On Behalf Of Florent > > Georges > > Sent: Friday, March 24, 2017 9:06 AM > > To: MarkLogic Developer Discussion <[email protected]> > > Subject: Re: [MarkLogic Dev General] Connecting to MarkLogic 9ea on > > CentOS via ODBC > > > > Hi, > > > > Looks like a connection issue to me. Can you make sure you can access > > the host > > + port from the same machine? The easiest is to send a HTTP GET request > > to the > > ODBC port. It then responds with an ODBC error, which is ill-formed > > HTTP, that > > starts with "EgSERRORC08000MXDMP" (including some NULL chars.) > > > > You can even use your browser to test that. It must connect to the host > > and > > port, but display an error that the HTTP response is invalid. E.g. with > > Chrome: > > > > The ml9ea3 page isn’t working > > ml9ea3 sent an invalid response. > > ERR_INVALID_HTTP_RESPONSE > > > > Of course, you need to make sure you use the same host and port number > > you > > configured ODBC with, and issue it from the same machine you issue ODBC > > requests from. > > > > Regards, > > > > -- > > Florent Georges > > H2O Consulting > > http://h2o.consulting/ > > > > > > On 23 March 2017 at 17:47, Nick Heidke wrote: > > All- > > > > Are there any specific ODBC settings that need to be set in order to > > connect to a MarkLogic ODBC app server running on CentOS? We’re using > > MarkLogic 9ea. > > > > I’ve got an identical set up running locally on my Windows 10 machine > > with MarkLogic 8, and I’m able to connect to it via ODBC without issue. > > > > Here’s the error I’m seeing: > > > > [cid:[email protected]] > > > > Attached is a ODBC log file from tracing the event. > > > > Nick Heidke > > Business Intelligence Consultant > > [Description: Description: cid:[email protected]] > > 5250 E Terrace Dr #130, Madison, WI > > d:608.284.2040 ext. 2305 | c:920.385.9110 > > [email protected]<mailto:[email protected]> > > > > *****This electronic message contains information from Omni Resources, > > Inc. that may be confidential or privileged. The information is intended > > to be used solely by the individual or entity named above. If you are > > not the intended recipient, you are hereby notified that any disclosure, > > copying, distribution, or use of the contents of this information is > > prohibited. If you have received this transmission in error, please > > destroy it and notify us immediately by replying to this email. Omni > > Resources, Inc. does not represent, warrant or guarantee neither the > > integrity of this communication has been maintained nor that the > > communication is free of errors, viruses or interference. Omni > > Resources, Inc. assumes no responsibility for damages resulting from > > unauthorized access, disclosure or tampering, which could have occurred > > during transmission. ******** > > > > _______________________________________________ > > General mailing list > > [email protected]<mailto:[email protected]> > > Manage your subscription at: > > http://developer.marklogic.com/mailman/listinfo/general > > > > > > > > > -- > Using Opera's revolutionary email client: http://www.opera.com/mail/ > _______________________________________________ > General mailing list > [email protected] > Manage your subscription at: > http://developer.marklogic.com/mailman/listinfo/general >
_______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
