Microsoft KB Archive/831715

= &quot;Catastrophic failure&quot; error message when you use the &quot;SQL Server Login&quot; dialog box to set the database name =

Article ID: 831715

Article Last Modified on 11/15/2007

-

APPLIES TO


 * Microsoft Data Access Components 2.8

-



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'



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.



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

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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
 Create a new Standard EXE project in Microsoft Visual Basic. By default, a form that is named Form1 is created. On the Project menu, click Reference, and then click Microsoft ActiveX Data Object 2.6. Add a CommandButton control and a TextBox control to Form1.  Add the following code to the Click event for the command button: Dim con As New ADODB.Connection con.Provider = &quot;SQLOLEDB&quot; con.Properties(&quot;Prompt&quot;) = adPromptAlways con.Open Text1.Text = con.ConnectionString  Press the F5 key to run the application, and then click the command button. In the SQL Server Login dialog box, follow these steps: <ol style="list-style-type: lower-alpha;"> Click Use Trusted Connection.</li> Click SQL Server 2000 server, and then click Options.</li> Click Database in the list. You receive the error message that is described in the &quot;Symptoms&quot; section.</li></ol> </li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section of this article.

<div class="references_section">