Hi

On a new PC I've installed Win XP Pro with SP2 and SQL Express 2005.
According to the registry (and Microsoft) this should include the latest
MDAC 2.8. I also have an SQL Server 2000 on the network. However when I use
Microsoft Data Link and select the "Microsoft OLE DB Provider for SQL
Server" I can't connect to any of the SQL Servers. After 6 hours of
frustration I found the entry
HKEY_CLASSES_ROOT\CLSID\{0C7FF16C-38E3-11d0-97AB-00C04FC2AD98}\InprocServer32
was set to c:\Windows\system32\sqloledb.dll. This file is dated april 1999
and seems to be very old. In the directory C:\Program Files\Common
Files\System\Ole DB I found another version of sqloledb.dll dated august
2004. After simply changing the registry entry to this file I can now
connect to both my SQL 2000 Server and SQLExpress 2005.

But why do I need to do this? I've tried to install a number of new MDAC
versions and even SQLExpress 2005 and I would have expect this entry to be
updated.

As a side effect of trying to fix this I now have a lot of files etc. for
older MDAC's installed. Is there any way to clean this up?

Your comments would be appreciated,- thanks

Peter

Peter Hemmingsen (Only_use_phe (AT) softco (DOT) dk) writes:
What error did you get?

I don't really know about the MDAC mess you got yourself into, but I like
to point out that with SQL Express you got SQL Native Client, a single
DLL which containts both an updated OLE DB provider and an updated ODBC
driver for SQL Server. So, I recommend that you use SQLNCLI rather than
SQLOLEDB.



--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Thanks for your reply.

I got error:
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Createfile()).]

I don't have access to the source so I have to use the OLE DB for SQL
Server.

Peter

"Erland Sommarskog" <esquel (AT) sommarskog (DOT) se> wrote

Peter Hemmingsen (phe (AT) softco (DOT) dk) writes:
I don't know what you mean with "don't have access to the source". When
you installed SQL Express on the machine, SQL Native Client was installed
as part of that installation, so you have it.

Since I don't really know what Microsoft Data Link is, what happens if
you try to connect with SQLCMD from the command line?


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

My original problem was that one of my applications (based on OLEDB for SQL)
didn't work. I narrowed the problem down to the oledb for sql as described
and also reproduced the same behaviour with Microsoft Data Link.

So even if I can get it to work in Microsoft Data Link with the native
provider it wouldn't work in my application that had the problem (and for
which I don't have the source)

Try to create an empty file called test.udl and double click it. This will
(normally) start Microsoft Data Link. Using this UI you can now specify a
connection and when finished the connection string can be found in the udl
file as simple text. Very convinient.

Peter

"Erland Sommarskog" <esquel (AT) sommarskog (DOT) se> wrote