From tentin.quarantino at gmail.com Thu Jun 4 23:30:56 2009 From: tentin.quarantino at gmail.com (Tentin Quarantino) Date: Fri Jun 5 07:31:06 2009 Subject: [egenix-users] InterfaceError: HY024 Message-ID: Hello, Recently, this error started to display: ----- File "mx/ODBCConnect/Common/ProxyObjects.py", line 1319, in process_response mx.ODBCConnect.Error.InterfaceError: ('HY024', -1023, "[Microsoft][ODBC Microsoft Access Driver] '(unknown)' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.", 10102) ### I thought to ask here in case it was a common error. Is this saying that the database file is missing somehow? Could it be locked, as in another application possibly has locked it? Cheers! From mal at egenix.com Fri Jun 5 14:17:31 2009 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jun 5 13:17:35 2009 Subject: [egenix-users] InterfaceError: HY024 In-Reply-To: References: Message-ID: <4A28FECB.3040704@egenix.com> Tentin Quarantino wrote: > Hello, > > Recently, this error started to display: > ----- > File "mx/ODBCConnect/Common/ProxyObjects.py", line 1319, in process_response > mx.ODBCConnect.Error.InterfaceError: ('HY024', -1023, > "[Microsoft][ODBC Microsoft Access Driver] '(unknown)' is not a valid > path. Make sure that the path name is spelled correctly and that you > are connected to the server on which the file resides.", 10102) > > ### > > I thought to ask here in case it was a common error. > Is this saying that the database file is missing somehow? > Could it be locked, as in another application possibly has locked it? This sounds like a permissions problem. Make sure that you define the DSN as a system DSN and that the service account under which mxODBC Connect Server runs has access to this DSN and/or Access file. Here's something Google returns for the above error: http://social.msdn.microsoft.com/Forums/en-US/adodotnetdataproviders/thread/c2750880-ef19-4ec4-88bf-9fadfe677d1e That discussion there suggests a problem with the authentication management used for the Access DB. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Jun 05 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2009-06-29: EuroPython 2009, Birmingham, UK 23 days to go ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ From tentin.quarantino at gmail.com Tue Jun 9 19:24:08 2009 From: tentin.quarantino at gmail.com (Tentin Quarantino) Date: Wed Jun 10 03:24:14 2009 Subject: [egenix-users] license installation issue Message-ID: Hello, I ran the installer for the Windows mxODBC.Connect 1.0.2 installer, for the purpose of updating a license file. When I attempted to test whether installation was succesful I see the output appended below. Also, how can one determine the version of ODBC.Connect that is installed, if the sw is complaining about an expired license ? I am confident that I selected the proper license for installation. I see it referenced in the log file after startup. Thank you... ##### Python 2.6.2 (r262:71605, Apr 14 2009, 22:40:02) [MSC v.1500 32 bit (Intel)] on win32 Type "copyright", "credits" or "license()" for more information. **************************************************************** Personal firewall software may warn about the connection IDLE makes to its subprocess using this computer's internal loopback interface. This connection is not visible on any external interface and no data is sent to or received from the Internet. **************************************************************** IDLE 2.6.2 >>> import mx.ODBC.Windows as ODBC Traceback (most recent call last): File "", line 1, in import mx.ODBC.Windows as ODBC File "mx\ODBC\Windows\__init__.py", line 9, in ImportError: initialization of module mxODBC failed (:license for mxODBC has expired) >>> From mal at egenix.com Wed Jun 10 11:11:02 2009 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jun 10 10:11:08 2009 Subject: [egenix-users] license installation issue In-Reply-To: References: Message-ID: <4A2F6A96.3070308@egenix.com> Tentin Quarantino wrote: > Hello, > > I ran the installer for the Windows mxODBC.Connect 1.0.2 installer, > for the purpose of updating a license file. You probably meant the 1.0.1 installer - we are currently underway to prepare the 1.0.2 release. > When I attempted to test whether installation was succesful I see the > output appended below. > > Also, how can one determine the version of ODBC.Connect that is installed, > if the sw is complaining about an expired license ? > > I am confident that I selected the proper license for installation. I > see it referenced in the log file after startup. > > Thank you... > > ##### > > Python 2.6.2 (r262:71605, Apr 14 2009, 22:40:02) [MSC v.1500 32 bit > (Intel)] on win32 > Type "copyright", "credits" or "license()" for more information. > > **************************************************************** > Personal firewall software may warn about the connection IDLE > makes to its subprocess using this computer's internal loopback > interface. This connection is not visible on any external > interface and no data is sent to or received from the Internet. > **************************************************************** > > IDLE 2.6.2 >>>> import mx.ODBC.Windows as ODBC > > Traceback (most recent call last): > File "", line 1, in > import mx.ODBC.Windows as ODBC > File "mx\ODBC\Windows\__init__.py", line 9, in > ImportError: initialization of module mxODBC failed ( 'mx.ODBC.Windows.LicenseError'>:license for mxODBC has expired) If you are using the mxODBC Connect Client, then the import should be: import mx.ODBCConnect.Client Note that the mxODBC Connect Client does not need the installation of a license. It can be used free of charge provided you have an mxODBC Connect Server installed. Now, if you want to use the stand-alone version of mxODBC, you'd use the import you mentioned above: import mx.ODBC.Windows The message you are seeing can either be caused by an evaluation license or a wrong date setting on the machine. To check the used license, have a look at the license attribute: print mx.ODBC.Windows.license If this prints e.g. "EVALUATION USE ..." then mxODBC is picking up an evaluation license. To check the location of the license file, you can import the license module and check it's location: import mx.ODBC.license print mx.ODBC.license.__file__ Hope that helps, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Jun 10 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2009-06-29: EuroPython 2009, Birmingham, UK 18 days to go ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ From info at egenix.com Thu Jun 11 12:10:36 2009 From: info at egenix.com (eGenix Team: M.-A. Lemburg) Date: Thu Jun 11 11:17:49 2009 Subject: [egenix-users] ANN: eGenix pyOpenSSL Distribution 0.9.0-0.9.8k Message-ID: <4A30CA0C.2010709@egenix.com> ________________________________________________________________________ ANNOUNCING eGenix.com pyOpenSSL Distribution Version 0.9.0-0.9.8k An easy to install and use repackaged distribution of the pyOpenSSL Python interface for OpenSSL - available on Windows, Mac OS X and Unix platforms This announcement is also available on our web-site for online reading: http://www.egenix.com/company/news/eGenix-pyOpenSSL-Distribution-0.9.0-0.9.8k-1-GA.html ________________________________________________________________________ INTRODUCTION The eGenix.com pyOpenSSL Distribution includes everything you need to get started with SSL in Python. It comes with an easy to use installer that includes the most recent OpenSSL library versions in pre-compiled form. pyOpenSSL is an open-source Python add-on (http://pyopenssl.sf.net/) that allows writing SSL aware networking applications as well as certificate management tools. OpenSSL is an open-source implementation of the SSL protocol (http://www.openssl.org/). For more information, please see the product page: http://www.egenix.com/products/python/pyOpenSSL/ ________________________________________________________________________ NEWS This new release of the eGenix.com pyOpenSSL Distribution updates the included pyOpenSSL version to 0.9, which includes a new fix for a serious problem in pyOpenSSL 0.8 related to threaded applications. It also comes with an important bug-fix update of OpenSSL, now at version 0.9.8k. The problem causes invalid thread states in the Python interpreter which then result in random core dumps and seg faults when using pyOpenSSL 0.8.0 with multi-threaded applications. The new fix is slightly different than the one we included in 0.8.1 and based on a code analysis we did together with Jean-Paul Calderone to track down the cause of the problem. Binaries are available for Linux x86 and x64 as well as Windows x86 and Mac OS X PPC/Intel. They include both pyOpenSSL and the necessary OpenSSL libraries. For Plone users and friends of buildout scripts, we have added pre-built binaries for Windows. They install just like the Linux versions and allow easy integration of the archives into buildout scripts. For our Mac OS X users, we have included new pre-built binaries for Mac OS X PPC and Intel platforms. ________________________________________________________________________ DOWNLOADS The download archives and instructions for installing the package can be found at: http://www.egenix.com/products/python/pyOpenSSL/ ________________________________________________________________________ UPGRADING Before installing this version of pyOpenSSL, please make sure that you uninstall any previously installed pyOpenSSL version. Otherwise, you could end up not using the included OpenSSL libs. _______________________________________________________________________ SUPPORT Commercial support for these packages is available from eGenix.com. Please see http://www.egenix.com/services/support/ for details about our support offerings. Enjoy, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Jun 11 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2009-06-29: EuroPython 2009, Birmingham, UK 17 days to go ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ From tentin.quarantino at gmail.com Sat Jun 13 13:41:23 2009 From: tentin.quarantino at gmail.com (Tentin Quarantino) Date: Sat Jun 13 21:41:28 2009 Subject: [egenix-users] ODBC Connect config file Message-ID: Hello, I recently experienced the following while using the ODBC Connect product. In my config file, there was a comment following a name-value pair. I am not necessarily experienced in ODBC conventions. However, it seems reasonable to put comments on the same line as data: [Logging] log_file = client.log [Communication] server_connections = mxODBCServerConnection [mxODBCServerConnection] # host = 192.168.1.100 # a comment host = 192.168.1.121 # a comment port = 6632 using_ssl = 0 Apparently, putting a comment after the "name = value" pair will cause the software to fail and the resulting error message could possibly mislead the programmer, IMHO. 0010 2009-06-13 12:31:26.87 [p2561] Could not open log file "" - using stderr 0500 2009-06-13 12:31:26.87 [p2561] Connection to 10.10.3.252 #:6632 failed - fail-over to the next. 0010 2009-06-13 12:31:26.87 [p2561] ERROR: None of the configured mxODBC Connect Servers allow connections. I believe it would be better to have a layer of error checking between the place where the program reads the config file and where that data is delivered to the code that uses it. i.e. check & sanitize the data before using it. If error handling and messaging was slightly more helpful, then the marginal improvement would move ODBC Connect toward real world clas product status. Many thanks for the very helpful product support! Cheers! From charlie at egenix.com Sat Jun 13 23:26:45 2009 From: charlie at egenix.com (Charlie Clark) Date: Sat Jun 13 22:26:51 2009 Subject: [egenix-users] ODBC Connect config file In-Reply-To: References: Message-ID: Am 13.06.2009, 21:41 Uhr, schrieb Tentin Quarantino : > # host = 192.168.1.100 # a comment > host = 192.168.1.121 # a comment > port = 6632 > using_ssl = 0 > Apparently, putting a comment after the "name = value" pair will cause > the software to fail and the resulting error message could possibly > mislead the programmer, IMHO. > 0010 2009-06-13 12:31:26.87 [p2561] Could not open log file " file 'test-client.log', mode 'w' at 0x2d85c0>" - using stderr > 0500 2009-06-13 12:31:26.87 [p2561] Connection to 10.10.3.252 #:6632 > failed - fail-over to the next. > 0010 2009-06-13 12:31:26.87 [p2561] ERROR: None of the configured > mxODBC Connect Servers allow connections. > I believe it would be better to have a layer of error checking between > the place where the program reads the config file and where that data > is delivered to the code that uses it. i.e. check & sanitize the data > before using it. > If error handling and messaging was slightly more helpful, then the > marginal improvement would move ODBC Connect toward real world clas > product status. Hiya, actually the solution is to use the correct comments for the file format! ;-) See http://en.wikipedia.org/wiki/INI_file for more details and check out the ConfigParser module in the standard library. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ From tentin.quarantino at gmail.com Sat Jun 13 23:08:45 2009 From: tentin.quarantino at gmail.com (Tentin Quarantino) Date: Sun Jun 14 07:08:51 2009 Subject: [egenix-users] ODBC Connect config file In-Reply-To: References: Message-ID: > > actually the solution is to use the correct comments for the file format! > ;-) > > See > http://en.wikipedia.org/wiki/INI_file > > for more details and check out the ConfigParser module in the standard > library. > That's very helpful! (and should save me some troubles,no? lol!) The comment on line by themselves did not generate an error. :) :) Clearly, I was not aware. I am very grateful to learn this, accidently or not. :) Many many thanks! Cheers! PS: thx for advice to read about ConfigParser too. From tentin.quarantino at gmail.com Sat Jun 13 23:23:19 2009 From: tentin.quarantino at gmail.com (Tentin Quarantino) Date: Sun Jun 14 07:23:24 2009 Subject: [egenix-users] ODBC Connect config file In-Reply-To: References: Message-ID: FYI, based on my testing, semicolons cause the eGenix ODBC Connect software to break, when used as described on the INI format wiki page. Are you implying with the reference to ConfigParser that if the software is broken, it is due to bug in this Python standard library? Many thanks! Cheers! From tentin.quarantino at gmail.com Sat Jun 13 23:28:23 2009 From: tentin.quarantino at gmail.com (Tentin Quarantino) Date: Sun Jun 14 07:28:27 2009 Subject: [egenix-users] ODBC Connect config file In-Reply-To: References: Message-ID: I guess the take-away from this is the following. Your software would be easier to use if the error handling and error messaging was more helpful so that the programmer could distinguish between a problem with a client config file versus a problem on the server between the ODBC Connect layer and the database on the file system of the server. At least, that is how I was confused based on the error message. Cheers! From support at egenix.com Tue Jun 16 15:28:15 2009 From: support at egenix.com (eGenix Support: Charlie Clark) Date: Tue Jun 16 14:28:27 2009 Subject: [egenix-users] ODBC Connect config file In-Reply-To: References: Message-ID: Am 16.06.2009, 02:37 Uhr, schrieb Tentin Quarantino : > Hi Charlie, > What does the author say? Please keep posts on the mailing list and refer to the documentation. We do not think that the error handling of mxODBC Connect is incorrect. Charlie -- Charlie Clark eGenix.com Professional Python Services directly from the Source >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ From tentin.quarantino at gmail.com Tue Jun 16 11:58:33 2009 From: tentin.quarantino at gmail.com (Tentin Quarantino) Date: Tue Jun 16 19:58:38 2009 Subject: [egenix-users] ODBC Connect config file In-Reply-To: References: Message-ID: My apologies for not keeping this dialog on the list. I will try to accomodate your wishes. Is there some nuance I am missing, here? You pointed me to the documentation for how the INI config file should be written. My test indicates your software fails when those guidelines are followed. The response from your ODBC Connect client software could (arguably) be improved in the case of failure. Cheers! -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20090616/4233b3fd/attachment.htm From info at egenix.com Mon Jun 29 12:06:47 2009 From: info at egenix.com (eGenix Team: M.-A. Lemburg) Date: Mon Jun 29 11:08:32 2009 Subject: [egenix-users] ANN: eGenix mxODBC Connect 1.0.2 - Python Database Interface Message-ID: <4A488427.1000504@egenix.com> ________________________________________________________________________ ANNOUNCING eGenix.com mxODBC Connect Python Database Interface Version 1.0.2 Our new client-server product for connecting Python applications to relational databases - from all major platforms This announcement is also available on our web-site for online reading: http://www.egenix.com/company/news/eGenix-mxODBC-Connect-1.0.2-GA.html ________________________________________________________________________ INTRODUCTION The mxODBC Connect Database Interface for Python allows users to easily connect Python applications to all major databases on the market today in a highly portable and convenient way. Unlike our mxODBC Python extension, mxODBC Connect is designed as client-server application, so you no longer need to find production quality ODBC drivers for all the platforms you target with your Python application. Instead you use an easy to install Python client library which connects directly to the mxODBC Connect database server over the network. This makes mxODBC Connect the ideal basis for writing cross-platform database programs and utilities in Python, especially if you run applications that need to communicate with databases such as MS SQL Server and MS Access, Oracle Database, IBM DB2 and Informix, Sybase ASE and Sybase Anywhere, MySQL, PostgreSQL, SAP MaxDB and many more, that run on Windows or Linux machines. By removing the need to install and configure ODBC drivers on the client side, mxODBC Connect greatly simplifies setup and configuration of database driven client applications, while at the same time making the network communication between client and database server more efficient and more secure. For more information, please see the product page: http://www.egenix.com/products/python/mxODBCConnect/ ________________________________________________________________________ NEWS mxODBC Connect 1.0.2 is a patch-level release of our new mxODBC Connect product. * More Secure We have upgraded the server to our latest eGenix pyOpenSSL release 0.9.0-0.9.8k, which includes a number of important bug fixes to both pyOpenSSL and the used OpenSSL library. * More Robust Previous versions had a timeout issue that we have solved with this release. We have have also added a special case for shutting down the client with a broken server connection. In such cases, the client will no longer wait for a timeout and terminate much faster. * Ideal for Building Bridges mxODBC Connect Client now works on all major Python platforms. As a result, connecting from e.g. Linux or Mac OS X to an SQL Server database has never been easier. You can even keep the data sources you already have configured on your Windows machine and connect to them as if your application were running on the database server itself. ________________________________________________________________________ UPGRADING You are encouraged to upgrade to this latest mxODBC Connect release. When upgrading, please always upgrade both the server and the client installations to the same version - even for patch level releases. Customers who have purchased mxODBC Connect 1.0 licenses can download and upgrade their existing installations without having to purchase new licenses or upgrades. The licenses will continue to work with version 1.0.2. Users of our stand-alone mxODBC product will have to purchase new licenses from our online shop in order to use mxODBC Connect. You can request 30-day evaluation licenses by visiting our web-site or writing to sales@egenix.com, stating your name (or the name of the company) and the number of eval licenses that you need. http://www.egenix.com/products/python/mxODBCConnect/#Evaluation ________________________________________________________________________ DOWNLOADS The download archives as well as instructions for installation and configuration of the product can be found on the product page: http://www.egenix.com/products/python/mxODBCConnect/ If you want to try the package, jump straight to the download instructions: https://cms.egenix.com/products/python/mxODBCConnect/#Download Fully functional evaluation licenses for the mxODBC Connect Server are available free of charge: http://www.egenix.com/products/python/mxODBCConnect/#Evaluation mxODBC Connect Client is always free of charge. _______________________________________________________________________ SUPPORT Commercial support for this product is available from eGenix.com. Please see http://www.egenix.com/services/support/ for details about our support offerings. Enjoy, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Jun 29 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/