S
SortaNortth
Has anybody actually ever resolved the problem described below? If so,
would you please share the solution?
I am trying to use MS Visual Studio to connect to an SQL Server database.
When I use the Tools/Connect to Database, the DataLink Properties window
pops up and I select the provider (MS OLEDB for SQL Server), then the server
name and database on server. Then I check "Test Connection" and immediately
get a dialog box that says "Test Connection Succeeded." I click the OK
button and then I get 17 boxes, sequentially that say "Login Failed, Catalog
Information cannot be retrieved." I dismiss each box by clicking "OK" and
eventually the boxes all go away.
I have seen this message numerous times in user groups over the last year,
but I have not seen a solution that seems to have resolved the problem. I
have twice reloaded the MDAC. The same file works fine when run from my
server running Windows 2000 and SQL Server 2000, Enterprise Edition, so it
isn't a bad database file. It also works fine in conventional ASP(VBScript)
coding from the IIS on my XP Machine.
I am running:
- Windows XP with all the latest patches, fixes, etc.;
- Visual Studio .NET, Enterprise Architect, Framework ver 1.0.3705, MDE
2002, ver 7.0.9466
- SLQ Server 2000 Desktop Engine
- MDAC 2.8 (tried 2.7SP1WinXP same result)
Thanks for any assistance
Dick Marcum
(e-mail address removed)
would you please share the solution?
I am trying to use MS Visual Studio to connect to an SQL Server database.
When I use the Tools/Connect to Database, the DataLink Properties window
pops up and I select the provider (MS OLEDB for SQL Server), then the server
name and database on server. Then I check "Test Connection" and immediately
get a dialog box that says "Test Connection Succeeded." I click the OK
button and then I get 17 boxes, sequentially that say "Login Failed, Catalog
Information cannot be retrieved." I dismiss each box by clicking "OK" and
eventually the boxes all go away.
I have seen this message numerous times in user groups over the last year,
but I have not seen a solution that seems to have resolved the problem. I
have twice reloaded the MDAC. The same file works fine when run from my
server running Windows 2000 and SQL Server 2000, Enterprise Edition, so it
isn't a bad database file. It also works fine in conventional ASP(VBScript)
coding from the IIS on my XP Machine.
I am running:
- Windows XP with all the latest patches, fixes, etc.;
- Visual Studio .NET, Enterprise Architect, Framework ver 1.0.3705, MDE
2002, ver 7.0.9466
- SLQ Server 2000 Desktop Engine
- MDAC 2.8 (tried 2.7SP1WinXP same result)
Thanks for any assistance
Dick Marcum
(e-mail address removed)