mxODBC problems

Dilton McGowan II diltonm at pacbell.net
Fri Aug 23 07:00:15 CEST 2002


"m.haberfeld" <m.haberfeld at insightbb.com> wrote in message
news:xDh99.215590$sA3.312102 at rwcrnsc52.ops.asp.att.net...
> Alrighty, here's the deal, I'm writing an application server in Python
that
> makes use of the mxODBC module.  I've used this module many times before
and
> am certain of it's stability so I think the problem must be in the SQL
> server settings.
>
> I wrote a threaded application that checks the server every 30 seconds for
> entries into a table that would have been inserted by a user from a web
> page.  If there is a new entry, the program pulls the entry, opens a
> connection to another DB, updates a few tables,  closes the connection and
> continues on its merry way.
>
> There is, apparently, no errors in the script programming as the server
will
> run through about 6 minutes worth of cycles before giving the error:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
>
> I figure it has something to do with either the multiple connections
maxing
> out the network buffer, or the connections not being closed properly.
> However, I don't know of a way to monitor this to check it or any way to
> test/fix it.  I tried changing  the network packet size to no avail.  I
was
> even able to lessen the amount of connections needed by the application in
> half, but nothing seemed to work.
>
> Dropping the number of connections didn't even increase the average amount
> of time the application would run before an Access Denied message.  I'm
all
> out of ideas.
>
> Any thoughts or suggestions would be quite appreciated.
>
> Best regards,
>
> Jeremy Reed
>

Microsoft SQL will have a license check run for it periodically by the
licensing service. If you've exceeded the number of licesnes alloted then
you could run into this. Check the event log for traces of licensing issues.





More information about the Python-list mailing list