MDAC update caused access problems

I just updated MDAC on one of my machines and I'm now having trouble accessing my SQL server. It's a local connection using SQLOLEDB in a VB dll. It was working fine before the update and now I get:

Microsoft OLE DB Provider for SQL Server error '80004005'

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

/cms25/CMS.asp, line 33

Most of the information I can find on this refers to TCP/IP connections but the SQL server is local. My connect function looks like this:

Public Sub ADOConnect()

With m_ADOConnection
.Provider = "SQLOLEDB"
.CursorLocation = adOpenStatic
.CommandTimeout = 20
.Mode = adModeReadWrite
.ConnectionString = "Data Source=" & m_strServer & ";Database=" & m_strName & ";" & m_strUsernamePassword
.open
End With

End Sub

On this server, m_strServer = "(local)". What am I missing? Thanks for any help in advance!

a.From which version of MDAC to which version?

On what platform?

Biggest headache I had was that 2.5 default connection library was Named pipes while 2.7 and later, the default was TCP. If you didn't have TCP and DNS configured properly, then the upgrade would result in errors that you may not have noticed previously.

Regards,

hmscott|||I believe I went from something like 2.5 to 2.8 so you might be right. How do I make sure the server is configured properly? Where do I set up named pipes?

UPDATE:

As soon as I enabled the TCP/IP access, it worked so I guess I'm not using named pipes... I'll have to look into this some more because I'd like to avoid using TCP/IP entirely. I'm assuming named pipes is faster?|||Check this KBA http://support.microsoft.com/kb/328306/en-us for the relevant reasons.sql

mdac error

Hi,

I have updated my Win98 SE with MDAC 2.7 program and checked
it with component checker (cc.exe) from Microsoft website. Found a warning
that is as following:

Item Name,Item Type,ErrorString,Status
MSADCO.DLL,COM,Unknown Class ID =
{9381d8f1-0288-11d0-9501-00aa00b911a5},Warning

And I attached the screen. Please tell me the impact and any solution?
Thanks.

SupernovaThat dll may be a browser related ADO component?? are you having some kind of issue with web applications (that interface to your database) on the workstation?|||Originally posted by DBA
That dll may be a browser related ADO component?? are you having some kind of issue with web applications (that interface to your database) on the workstation?

Actually not web application. It's a ODBC/SQL server application running at workstation.|||Have you tried running comcheck with switch 'd' (this is a reconfiguration option) ? Have you noticed any problems ? The screen attachment never made it.