Microsoft KB Archive/197323

= How To Troubleshoot "ADODB.Connection" Error 800a0bb9 from Recordset DTC =

Article ID: 197323

Article Last Modified on 1/12/2007

-

APPLIES TO


 * Microsoft Visual InterDev 6.0 Standard Edition
 * Microsoft Internet Information Server 3.0
 * Microsoft Internet Information Server 4.0
 * Microsoft ActiveX Data Objects 2.0
 * Microsoft ActiveX Data Objects 2.1 Service Pack 2

-



This article was previously published under Q197323



SUMMARY
A Visual InterDev Design-Time Control (DTC) may return the following error message:

ADODB.Connection error '800a0bb9'

The application is using arguments that are of the wrong type, are out of acceptable range, or are in conflict with one another.

This article outlines some of the common steps to take to troubleshoot this error message.



MORE INFORMATION
This error occurs because the Recordset Design-Time Control errors are filtered through the Visual InterDev 6.0 Script Library. Usually the problem manifests as a blank or incorrect connection string.

To troubleshoot this error, follow these steps:  This error often occurs because the Global.asa file does not fire. As a result, the Application and Session variables that are initialized in the Session_OnStart and Application_OnStart events are not created. The most common cause for Global.asa not firing is if the virtual folder that contains the file is not set up as an application.

IIS 3.0

To resolve this problem in Internet Information Server (IIS) 3.0, set up a virtual folder where the Global.asa and .asp files exist in IIS. Allow this folder Read and Execute permissions.

IIS 4.0 and IIS 5.0

To resolve this problem in IIS 4.0 and 5.0, make your virtual directory an "Application" as follows:

 Open Microsoft Management Console. Right-click on the virtual folder where the Global.asa file exists, and then click Properties. On the Directory tab, click Create. Click OK to close the Properties window.

Personal Web Server

To resolve this problem for Personal Web Server on a computer that is running Microsoft Windows 95 or Windows 98, see the following article in the Microsoft Knowledge Base:

184572 PRB: Creating Application with PWS 4.0, Windows 95 and VID

 Verify that Global.asa is not losing session state instead of not firing at all. To do this, follow these steps:   Open the Global.asa file, and add the following code into the Session_OnStart event: Session("Test") = Now </li>  Create an Active Server Pages (ASP) page named Test.asp. Use the following code to write out that session variable: <% Response.Write "Session variable: " & Session("Test") %>                       </li> In your browser, view Test.asp. If the date/time string appears after the "Session variable: " text, Global.asa is firing.</li></ol>

For additional information about this error when Global.asa is firing, but the session state or application state is being lost, click the article numbers below to view the articles in the Microsoft Knowledge Base:

281298 PRB: Session Variables Do Not Persist When Application Contains Empty Global.asa

182891 INFO: Session ID Does Not Persist in Active Server Pages

172864 BUG: ASP Pages Fail on Access to Session and Application Objects

178037 PRB: Session Variables Are Lost When ASP Is Located in Frameset

173307 PRB: Nested Virtual Roots Can Lose Session State

</li> This error can occur because of a permissions problem. Turn on Basic Authentication for this application only to see if there is a permissions problem. To do this, follow these steps:

 Open Microsoft Management Console.</li> Right-click the virtual directory where the Global.asa file exists, and then click Properties.</li> On the Directory Security tab, under Anonymous Access and Authentication Control, click Edit.</li> Clear all of the checkboxes, and then select the Basic Authentication check box.</li> Click Apply, and then click OK.</li> View the page again. When you are prompted to log on, use an Administrator account.</li></ol>

If the Web page works correctly when you use Basic Authentication, you most likely have a permissions problem on a file. Change back to your default authentication scheme, and use the Windows NT File Monitor to check for file "Access Denied" errors. Windows NT File Monitor is available from the following Sysinternals Web site:

http://www.microsoft.com/technet/sysinternals/utilities/filemon.mspx

</li> This error can occur if a bound field contains spaces in its name, such as "Field One". The Visual InterDev 6.0 Script Library does not delimit field names. As a result, a syntax error occurs. To resolve this problem, see the following article in the Microsoft Knowledge Base:

259388 PRB: 800a0bb9 Error Occurs With Data Bound Design-Time Control

</li> Verify that the TEMP and TMP environment variables exist as system variables when you connect to a file-based database, such as Microsoft Access.

To do this, follow these steps:  <li>On the Start menu, click Settings, click Control Panel, and then double-click the System icon.</li> <li>On Microsoft Windows NT, click the Environment tab.

On Microsoft Windows 2000, click the Advanced tab, and then click Environment Variables.</li> <li>Under System Variables, search for the TEMP and TMP variables. If these variables exist, verify that the path is correct.

If these variables do not exist, under System Variables, click New. In the Variable Name box, type TEMP. In the Variable Value box, type c:\temp .</li> <li>Repeat the previous step for the TMP variable.</li></ol> </li></ol>

<div class="references_section">