G
Guest
I'm having a problem using the Database wizard in Visual Studio 2003
(Academic version) to connect in a very basic way (not even any code yet) to
SQLEXPRESS, the only available version of SQL Server 2005 out so far. I was
running MDAC 2.7 XP SP 1 on Windows XP Pro and thought that maybe pulling
down a recent refresh for 2.7 might help (it didn't). So I went ahead and
upgraded to 2.8 and still have the error message 'error enumerating data
servers'. I know my databases are up and running because my management
console tells me so. The whole environment is local to my machine and I
don't think it's a permission problem. I'm wondering if maybe the fact that
Studio runs on .NET framework 1.1 and SQL Server 2005 express is running on
framework 2.x might be part of the problem but have no information so far
that confirms for me that trying to run Visual Studio on framework 2.x will
improve the situation. Component Checker was showing me just a few MDAC
mismatches on 2.7 but 2.8 is showing heavy mismatches ... too many to mention
and I couldn't say which ones are relevant anyway (but no change to the error
message so if something else is broken I'm not suffering from it yet). When
I search for oledb32.dll in the registry, I can't find it (though it is in my
file system) so I'm having trouble figuring out how to register it if it
isn't there now ... Many thanks for any help.
(Academic version) to connect in a very basic way (not even any code yet) to
SQLEXPRESS, the only available version of SQL Server 2005 out so far. I was
running MDAC 2.7 XP SP 1 on Windows XP Pro and thought that maybe pulling
down a recent refresh for 2.7 might help (it didn't). So I went ahead and
upgraded to 2.8 and still have the error message 'error enumerating data
servers'. I know my databases are up and running because my management
console tells me so. The whole environment is local to my machine and I
don't think it's a permission problem. I'm wondering if maybe the fact that
Studio runs on .NET framework 1.1 and SQL Server 2005 express is running on
framework 2.x might be part of the problem but have no information so far
that confirms for me that trying to run Visual Studio on framework 2.x will
improve the situation. Component Checker was showing me just a few MDAC
mismatches on 2.7 but 2.8 is showing heavy mismatches ... too many to mention
and I couldn't say which ones are relevant anyway (but no change to the error
message so if something else is broken I'm not suffering from it yet). When
I search for oledb32.dll in the registry, I can't find it (though it is in my
file system) so I'm having trouble figuring out how to register it if it
isn't there now ... Many thanks for any help.