Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


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'


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.


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: 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 FIX: Hotfixes are available for MDAC 2.8

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
    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.


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


For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the Standard Terminology That Is Used to Describe Microsoft Product Updates, Tools, and Add-ons

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!