|
Problem IC63951
|
Status: Closed |
32 BIT .NET PROVIDER NOT GETTING INSTALLED ON 64 BIT WINDOWS. |
| product: |
DB2 CONNECT / DB2CONNCT / 950 - DB2 |
| Problem description: |
When installing 32 bit IBM data server client on a 64 bit
Windows, .NET Provider does not get registered.
The client installation finishes successfully, but VSAI fails
to install with the following error.
1: ERROR:To install IBM Database Add-Ins for Visual Studio, you
must have one of the following providers installed:
IBM Data Server Provider for .NET |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users installing V9.5 32 bit IBM Database add-ins *
* forVisualStudio. *
****************************************************************
* PROBLEM DESCRIPTION: *
* When installing 32 bit IBM database add-ins forVisualStudio *
* on a 64 bit Windows machine, .NET Provider doesnotget *
* registered.The client installation finishessuccessfully, but *
* VSAIfails to install with the followingerror.1: ERROR:To *
* install IBM Database Add-Ins for VisualStudio,you must have *
* one of the following providersinstalled:IBM Data Server *
* Provider for .NET *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V9.5 FP6 *
**************************************************************** |
| Local Fix: |
Workaround is to manually register the driver using db2nmpcfg. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in V9.5 FP6. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.10.2009
09.09.2010
09.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
