Microsoft Knowledge Base Email Alertz
All KB/RSS Links  |  Hot Kb!  |  New Kb!  |  Scott Cate  |  FAQ / KB  |  Web Hosting  |  Unsubscribe  

(831715) - OLEDB provider gets access violation with the DBPROMPT_PROMPT property.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.
Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks
Article ID: 831715 - Last Review: November 15, 2007 - Revision: 3.2

"Catastrophic failure" error message when you use the "SQL Server Login" dialog box to set the database name

Hotfix download is availableHotfix Download Available
View and request hotfix downloads
View products that this article applies to.

SYMPTOMS

When you use Microsoft OLE DB Provider for SQL Server (SQLOLEDB), and you try to set the database name when you are prompted with the SQL Server Login dialog box, you receive the following error message:
2147418113 (8000ffff)': Catastrophic Failure'
Back to the top

CAUSE

This problem is caused by an error in OLE DB Provider for SQL Server. The OLE DB provider does not initialize a global pointer to the SQL client network library (Dbnetlib.dll) when the SQL Server Login dialog box appears.
Back to the top

RESOLUTION

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. 
 

  Date           Time  Version    Size       File name     
   --------------------------------------------------------
  18-Oct-2003  04:20  2000.85.1022.45   503,808  Sqloledb.dll
Note For a list of all the hotfixes available for MDAC 2.8, click the following article number to view the article in the Microsoft Knowledge Base:
839801  (http://kbalertz.com/Feedback.aspx?kbNumber=839801/ ) FIX: Hotfixes are available for MDAC 2.8

Back to the top

Steps to reproduce the behavior

  1. Create a new Standard EXE project in Microsoft Visual Basic. By default, a form that is named Form1 is created.
  2. On the Project menu, click Reference, and then click Microsoft ActiveX Data Object 2.6.
  3. Add a CommandButton control and a TextBox control to Form1.
  4. Add the following code to the Click event for the command button: 
      Dim con As New ADODB.Connection
                        con.Provider = "SQLOLEDB"
                        con.Properties("Prompt") = adPromptAlways
                        con.Open
                        Text1.Text = con.ConnectionString
  5. Press the F5 key to run the application, and then click the command button.
  6. In the SQL Server Login dialog box, follow these steps:
    1. Click Use Trusted Connection.
    2. Click SQL Server 2000 server, and then click Options.
    3. Click Database in the list. You receive the error message that is described in the "Symptoms" section.
Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
Back to the top

REFERENCES

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684  (http://kbalertz.com/Feedback.aspx?kbNumber=824684/ ) Description of the Standard Terminology That Is Used to Describe Microsoft Product Updates, Tools, and Add-ons
Back to the top
APPLIES TO
  • Microsoft Data Access Components 2.8
Back to the top
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbbug KB831715
Back to the top
        

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Copyright © 2002-2007 KBALERTZ.COM.  All Rights Reserved. Terms / Privacy. Discount ASP.NET Hosting