Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Intermittent ODBC error
Message
 
À
18/03/2002 09:20:28
Stacey King
Koala Publishing Ltd
Bristol, Royaume Uni
Information générale
Forum:
Microsoft SQL Server
Catégorie:
Autre
Divers
Thread ID:
00634048
Message ID:
00636227
Vues:
18
Stacey;

Have you checked:

http://search.microsoft.com/Default.asp?&so=RECCNT&boolean=ALL&siteid=us&p=1&nq=NEW&qu=Drivers+error+%2780040e21%27+&btnsearch=GO&IntlSearch=&ig=1&ig=2&ig=3&ig=4&ig=5&ig=6&ig=7&ig=8&ig=9&ig=10&i=00&i=01&i=02&i=03&i=04&i=05&i=06&i=07&i=08&i=09


There may be a clue there.

Tom




>We have a web site implemented using Active Server pages and VBScript.
>
>We have the following error message being generated by SQL/Server 7
>
>Microsoft OLE DB Provider for ODBC Drivers error '80040e21'
>The request properties can not be supported by this ODBC Driver.
>
>On the face of it, maybe straightforward. However, the circumatances make a big difference, i.e.
>
>1. It NEVER seems to occur when talking to the site via ADSL
>
>2. It ALWAYS occurs when using 56k dial-up. However, if you do excatly the same query immediately afterwards, the problem goes away and back come the results as expected.
>
>3. It SOMETIMES occurs when using an ISDN line - as with dial-up, if you repeat the same query, the problem goes away.
>
>4. It NEVER occurs on LAN test setup with exactly the same software. On both the LAN server and the web server we have the latest Microsoft SPs installed.
>
>
>The fact that it ALWAYS works with ADSL suggests it isn't an application code problem, but some kind of environment problem. Given the evidence listed above, we assumed it must be a timing problem, so we increased the timeout to 300 seconds. This didn't make the slightest difference.
>
>Anybody have any ideas what's wrong?
>
>Gordon Dennis
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform