Asp Forum - Data connection problems since loading ODBC Data Provider - microsoft.public.dotnet.framework.odbcnet

Tony Marler

7/2/2002 11:20:00 AM

I have recently loaded the ODBC Data Provider as I needed
to connect to a SQLBase ODBC source.

This seemed to work ok and indeed in code (did not use
Server Explorer/Data Adapter etc) I have created a
connection the SQLBase database and returned data.

But I have just tried to create a new connection in Server
Manager to SQL Server using OLE-DB Provider for SQL Server
and cannot make connection. Firstly trying a drop down
in "Select server" results in "Error enumerating data
servers. Enumerator reports 'Unspecified error'"

If I proceed and enter a valid server name and then
user/password combination clicking the test connection
works fine.

But clicking the "Select database" dropdown gives error
message "Login failed. Catalog information cannot be
retrieved". User name is definately correct and have also
tried integrated security. This occurs on several
different SQL Servers.

If I proceed and enter a known database name then clicking
OK results in message "Unable to add data connection.
Object reference not set to an instance of an object"

I have removed both the SQLBase ODBC driver and the ODBC
Data Provider but the same error occurs. I have not added
any other software or .NET components.

Very strange!

Any ideas gratefully appreciated.

Tony

4 Answers

(Steven Bras [MS])

7/2/2002 6:27:00 PM

Download and run our Component Checker tool, which will check for
corruption in your MDAC (Microsoft Data Access Components) installation.
Corruption in these components may be the cause.

You can download this utility from
http://www.microsof.../do.... Look for Component Checker at
the top of the list.

Once you've downloaded this, do the following on the server in question:
1. Run the cc.exe, a self-extracting executable, that will expand the files
to a directory on your drive;
2. Run the ComCheck executable from this folder;
3. A dialog will appear, prompting you for the type of analysis you wish to
perform; select the first option, "Perform analysis of your machine and
automatically determine...";
4. The utility will perform its analysis, and display a message box
displaying the version of MDAC it thinks is closest to what you have
installed. Make note of this message, especially if it reports that more
than one version matches your machine;
5. After that messagebox is dismissed, you'll see a two-pane window,
listing any major errors it found in the right pane;

If you see a large number of errors, reinstall the mdac_typ.exe
redistributable for the version you currently have, or a later one. These
are also available at http://www.microsof....

If you are unable to resolve these errors and wish assistance, you can open
a support incident with us (by calling 800-936-5800) and we will work with
you to clean up the problems.

Hope this helps!

Steven Bras, MCSD
Microsoft Developer Support/Visual Basic WebData

This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Microsoft Strategic Technology
Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.co....

Tony Marler

7/2/2002 10:19:00 PM

Steve

Thanks for your prompt reply. I completely reinstalled
MDAC 2.7 butto no avail. However, I have narrowed the
problem down further and it is not directly the .NET ODBC
Data Provider that is causing the problem! It is a
specific ODBC driver install.

To summarise
1. I loaded a new machine, new framework and new VS.NET -
OLE-DB Data Connections work fine.

2. I installed .NET ODBC Data Provider - OLE-DB Data
Connections work fine (didn't actually try ODBC connect
but looked ok)

3. Install the Centura Corporation SQLBase ODBC driver -
did not try to connect or test connection but immediately
after installing the above driver the VS.NET OLE-DB Data
Connections failed!

This is very worrying as it indicates the sort of DLL
issues that we had hoped were over with .NET. I appreciate
that this is not a Microsoft product but wonder if you
have any suggestions. Even uninstalling the SQLBase ODBC
driver and .NET ODBC Data Provider did not help. My
development machine still has the problem.

PC is Win2k, PIII 1.2Ghz with 256Mb RAM, MDAC 2.7, Latest
framework and VS.NET Prof.

Centura SQLBase ODBC driver is version 3.50 and is
provided by a file called c2gup1.dll

Thanks in advance.

Tony

>-----Original Message-----
>Download and run our Component Checker tool, which will
check for
>corruption in your MDAC (Microsoft Data Access
Components) installation.
>Corruption in these components may be the cause.
>
>You can download this utility from
>http://www.microsof.../do.... Look for
Component Checker at
>the top of the list.
>
>Once you've downloaded this, do the following on the
server in question:
>1. Run the cc.exe, a self-extracting executable, that
will expand the files
>to a directory on your drive;
>2. Run the ComCheck executable from this folder;
>3. A dialog will appear, prompting you for the type of
analysis you wish to
>perform; select the first option, "Perform analysis of
your machine and
>automatically determine...";
>4. The utility will perform its analysis, and display a
message box
>displaying the version of MDAC it thinks is closest to
what you have
>installed. Make note of this message, especially if it
reports that more
>than one version matches your machine;
>5. After that messagebox is dismissed, you'll see a two-
pane window,
>listing any major errors it found in the right pane;
>
>If you see a large number of errors, reinstall the
mdac_typ.exe
>redistributable for the version you currently have, or a
later one. These
>are also available at http://www.microsof....
>
>If you are unable to resolve these errors and wish
assistance, you can open
>a support incident with us (by calling 800-936-5800) and
we will work with
>you to clean up the problems.
>
>Hope this helps!
>
>Steven Bras, MCSD
>Microsoft Developer Support/Visual Basic WebData
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>Are you secure? For information about the Microsoft
Strategic Technology
>Protection Program and to order your FREE Security Tool
Kit, please visit
>http://www.microsoft.co....
>
>.
>

(Steven Bras [MS])

7/3/2002 6:00:00 PM

I'm afraid I'm not familiar with the SQLBase driver; it would be best that
you obtain assistance from them as well as their product is obviously
corrupting the installation of our OLEDB managed provider.

Again, I would run component checker on that machine to determine what data
access components have been corrupted.

Steven Bras, MCSD
Microsoft Developer Support/Visual Basic WebData

This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Microsoft Strategic Technology
Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.co....

Craig Hinchliffe

8/29/2002 10:50:00 AM

We have now resolved this problem

Before you reinstall your version of MDAC you need to
remove one line from registry See below

Reinstalling MDAC

Before reinstalling the current version of MDAC you will
need to remove the following registry entry before you
reinstall, but make a backup of it first just in case you
have problems.

'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersi
on\Setup\Exceptio
nComponents'

Note: This has been tested only with 2.7

Craig Hinchliffe
Prosolve Software
http://www.pros...

>-----Original Message-----
>Steve
>
>Thanks for your prompt reply. I completely reinstalled
>MDAC 2.7 butto no avail. However, I have narrowed the
>problem down further and it is not directly the .NET ODBC
>Data Provider that is causing the problem! It is a
>specific ODBC driver install.
>
>To summarise
>1. I loaded a new machine, new framework and new VS.NET -
>OLE-DB Data Connections work fine.
>
>2. I installed .NET ODBC Data Provider - OLE-DB Data
>Connections work fine (didn't actually try ODBC connect
>but looked ok)
>
>3. Install the Centura Corporation SQLBase ODBC driver -
>did not try to connect or test connection but immediately
>after installing the above driver the VS.NET OLE-DB Data
>Connections failed!
>
>This is very worrying as it indicates the sort of DLL
>issues that we had hoped were over with .NET. I
appreciate
>that this is not a Microsoft product but wonder if you
>have any suggestions. Even uninstalling the SQLBase ODBC
>driver and .NET ODBC Data Provider did not help. My
>development machine still has the problem.
>
>PC is Win2k, PIII 1.2Ghz with 256Mb RAM, MDAC 2.7, Latest
>framework and VS.NET Prof.
>
>Centura SQLBase ODBC driver is version 3.50 and is
>provided by a file called c2gup1.dll
>
>Thanks in advance.
>
>Tony
>
>
>
>
>>-----Original Message-----
>>Download and run our Component Checker tool, which will
>check for
>>corruption in your MDAC (Microsoft Data Access
>Components) installation.
>>Corruption in these components may be the cause.
>>
>>You can download this utility from
>>http://www.microsof.../do.... Look for
>Component Checker at
>>the top of the list.
>>
>>Once you've downloaded this, do the following on the
>server in question:
>>1. Run the cc.exe, a self-extracting executable, that
>will expand the files
>>to a directory on your drive;
>>2. Run the ComCheck executable from this folder;
>>3. A dialog will appear, prompting you for the type of
>analysis you wish to
>>perform; select the first option, "Perform analysis of
>your machine and
>>automatically determine...";
>>4. The utility will perform its analysis, and display a
>message box
>>displaying the version of MDAC it thinks is closest to
>what you have
>>installed. Make note of this message, especially if it
>reports that more
>>than one version matches your machine;
>>5. After that messagebox is dismissed, you'll see a two-
>pane window,
>>listing any major errors it found in the right pane;
>>
>>If you see a large number of errors, reinstall the
>mdac_typ.exe
>>redistributable for the version you currently have, or a
>later one. These
>>are also available at http://www.microsof....
>>
>>If you are unable to resolve these errors and wish
>assistance, you can open
>>a support incident with us (by calling 800-936-5800) and
>we will work with
>>you to clean up the problems.
>>
>>Hope this helps!
>>
>>Steven Bras, MCSD
>>Microsoft Developer Support/Visual Basic WebData
>>
>>This posting is provided "AS IS" with no warranties, and
>confers no rights.
>>
>>Are you secure? For information about the Microsoft
>Strategic Technology
>>Protection Program and to order your FREE Security Tool
>Kit, please visit
>>http://www.microsoft.co....
>>
>>.
>>
>.
>

microsoft.public.dotnet.framework.odbcnet

Data connection problems since loading ODBC Data Provider

Tony Marler

(Steven Bras [MS])

Tony Marler

(Steven Bras [MS])

Craig Hinchliffe

x Login to ForumsZone